Amazon
/
Direct Fulfillment Inventory Inquiry/Advice
  • Specification
  • EDI Inspector
Import
Stedi maintains this guide based on public documentation from Amazon. Contact Amazon for official EDI specifications. To report any errors in this guide, please contact us.
Go to EDI Guide Catalog
Amazon logo

X12 846 Direct Fulfillment Inventory Inquiry/Advice

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Inventory Inquiry/Advice Transaction Set (846) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used in the following ways: (1) for a seller of goods and services to provide inventory information to a prospective purchaser, with no obligation to the purchaser to acquire these goods or services; (2) for a representative of a seller of goods and services to supply inventory information to that seller; (3) for one location to supply another location with inventory information; and (4) for an inquiry as to the availability of inventory with no obligation on the seller of goods and services to reserve that inventory.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI samples
    View the latest version of this implementation guide as an interactive webpage
    Powered by
    Build free EDI implementation guides at stedi.com
    Overview
    ISA
    -
    Interchange Control Header
    Max use 1
    Required
    GS
    -
    Functional Group Header
    Max use 1
    Required
    heading
    ST
    010
    Transaction Set Header
    Max use 1
    Required
    BIA
    020
    Beginning Segment for Inventory Inquiry/Advice
    Max use 1
    Required
    DTM
    050
    Date/Time Reference
    Max use 10
    Optional
    N1 Loop
    GE
    -
    Functional Group Trailer
    Max use 1
    Required
    IEA
    -
    Interchange Control Trailer
    Max use 1
    Required
    ISA

    Interchange Control Header

    RequiredMax use 1

    To start and identify an interchange of zero or more functional groups and interchange-related control segments

    Example
    ISA-01
    I01
    Authorization Information Qualifier
    Required

    Code to identify the type of information in the Authorization Information

    00
    No Authorization Information Present (No Meaningful Information in I02)
    ISA-02
    I02
    Authorization Information
    Required
    Min 10Max 10

    Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)

    ISA-03
    I03
    Security Information Qualifier
    Required

    Code to identify the type of information in the Security Information

    00
    No Security Information Present (No Meaningful Information in I04)
    ISA-04
    I04
    Security Information
    Required
    Min 10Max 10

    This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)

    ISA-05
    I05
    Interchange ID Qualifier
    Required
    Min 2Max 2

    Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

    Codes
    ISA-06
    I06
    Interchange Sender ID
    Required
    Min 15Max 15

    Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element

    ISA-07
    I05
    Interchange ID Qualifier
    Required
    Min 2Max 2

    Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

    Codes
    ISA-08
    I07
    Interchange Receiver ID
    Required
    Min 15Max 15

    Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them

    ISA-09
    I08
    Interchange Date
    Required
    YYMMDD format

    Date of the interchange

    ISA-10
    I09
    Interchange Time
    Required
    HHMM format

    Time of the interchange

    ISA-11
    I10
    Interchange Control Standards Identifier
    Required

    Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer

    U
    U.S. EDI Community of ASC X12, TDCC, and UCS
    ISA-12
    I11
    Interchange Control Version Number
    Required

    This version number covers the interchange control segments

    00401
    Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
    ISA-13
    I12
    Interchange Control Number
    Required
    Min 9Max 9

    A control number assigned by the interchange sender

    ISA-14
    I13
    Acknowledgment Requested
    Required
    Min 1Max 1

    Code sent by the sender to request an interchange acknowledgment (TA1)

    0
    No Acknowledgment Requested
    1
    Interchange Acknowledgment Requested
    ISA-15
    I14
    Usage Indicator
    Required
    Min 1Max 1

    Code to indicate whether data enclosed by this interchange envelope is test, production or information

    I
    Information
    P
    Production Data
    T
    Test Data
    ISA-16
    I15
    Component Element Separator
    Required
    Min 1Max 1

    Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator

    >
    Component Element Separator

    Functional Group Header

    RequiredMax use 1

    To indicate the beginning of a functional group and to provide control information

    Example
    GS-01
    479
    Functional Identifier Code
    Required

    Code identifying a group of application related transaction sets

    IB
    Inventory Inquiry/Advice (846)
    GS-02
    142
    Application Sender's Code
    Required
    Min 2Max 15

    Code identifying party sending transmission; codes agreed to by trading partners

    GS-03
    124
    Application Receiver's Code
    Required
    Min 2Max 15

    Code identifying party receiving transmission. Codes agreed to by trading partners

    GS-04
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    GS-05
    337
    Time
    Required
    HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

    Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

    GS-06
    28
    Group Control Number
    Required
    Min 1Max 9

    Assigned number originated and maintained by the sender

    GS-07
    455
    Responsible Agency Code
    Required
    Min 1Max 2

    Code used in conjunction with Data Element 480 to identify the issuer of the standard

    T
    Transportation Data Coordinating Committee (TDCC)
    X
    Accredited Standards Committee X12
    GS-08
    480
    Version / Release / Industry Identifier Code
    Required

    Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed

    004010
    Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997

    Heading

    ST
    010

    Transaction Set Header

    RequiredMax use 1

    To indicate the start of a transaction set and to assign a control number

    Example
    ST-01
    143
    Transaction Set Identifier Code
    Required

    Code uniquely identifying a Transaction Set

    • The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
    846
    Inventory Inquiry/Advice
    ST-02
    329
    Transaction Set Control Number
    Required
    Min 4Max 9

    Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

    BIA
    020

    Beginning Segment for Inventory Inquiry/Advice

    RequiredMax use 1

    To indicate the beginning of an Inventory Inquiry/Advice Transaction Set

    Usage notes

    BIA00DD150223201502231835~
    BIA
    25DD20150320182025055000201503201920~

    Example
    BIA-01
    353
    Transaction Set Purpose Code
    Required

    Code identifying purpose of transaction set

    Usage notes

    Use '00' for Full Inventory Availability Feeds.
    Use '25' for the Incremental Change Availability Feeds.

    00
    Original
    25
    Incremental
    BIA-02
    755
    Report Type Code
    Required

    Code indicating the title or contents of a document, report or supporting item

    DD
    Distributor Inventory Report
    BIA-03
    127
    Reference Identification
    Required
    Min 1Max 30

    Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

    • BIA03 identifies the number of the inquiry/advice that is transferred.
    Usage notes

    Unique Sequential Reference number for this Inventory Feed, assigned by sender.

    BIA-04
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    • BIA04 identifies the date of the inquiry/advice that is transferred.
    Usage notes

    Date (Format: CCYYMMDD).

    BIA-05
    337
    Time
    Optional
    HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

    Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

    • BIA05 identifies the time of the inquiry/advice that is transferred.
    Usage notes

    Time (Format: HHMM) expressed in UTC format.

    DTM
    050

    Date/Time Reference

    OptionalMax use 10

    To specify pertinent dates and times

    Example
    DTM-01
    374
    Date/Time Qualifier
    Required
    Min 3Max 3

    Code specifying type of date or time, or both date and time

    DTM-02
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD

    DTM-03
    337
    Time
    Optional
    HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

    Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

    DTM-04
    623
    Time Code
    Optional

    Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow

    GM
    Greenwich Mean Time
    N1 Loop
    RequiredMax >1
    N1
    080

    Name

    RequiredMax use 1

    To identify a party by type of organization, name, and code

    Usage notes

    N1ZZABC Company92ADSX~

    Example
    N1-01
    98
    Entity Identifier Code
    Required

    Code identifying an organizational entity, a physical location, property or an individual

    ZZ
    Mutually Defined
    N1-02
    93
    Name
    Required
    Min 1Max 60

    Free-form name

    Usage notes

    This will be the Amazon code representing the warehouse that the order should ship from. This is usually a four character alpha code (e.g. ABCD).

    N1-03
    66
    Identification Code Qualifier
    Required

    Code designating the system/method of code structure used for Identification Code (67)

    92
    Assigned by Buyer or Buyer's Agent
    N1-04
    67
    Identification Code
    Required
    Min 2Max 80

    Code identifying a party or other code

    • This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
    Usage notes

    This will be the Amazon code representing the warehouse that the order should ship from. This is usually a four character alpha code (e.g. ABCD).

    Detail

    LIN Loop
    RequiredMax >1
    LIN
    010

    Item Identification

    RequiredMax use 1

    To specify basic item identification data

    Usage notes

    LIN1SK*893270000999~

    Example
    LIN-01
    350
    Assigned Identification
    Required
    Min 1Max 20

    Alphanumeric characters assigned for differentiation within a transaction set

    • LIN01 is the line item identification
    Usage notes

    Line Item ID. This should be a sequential number for each LIN loop sent (e.g. 1, 2, 3, etc).

    LIN-02
    235
    Product/Service ID Qualifier
    Required

    Code identifying the type/source of the descriptive number used in Product/Service ID (234)

    • LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
    Usage notes

    Use 'SK' for all valid item numbers.

    SK
    Stock Keeping Unit (SKU)
    LIN-03
    234
    Product/Service ID
    Required
    Min 1Max 48

    Identifying number for a product or service

    Usage notes

    Item Number. Item ID's will vary by vendor and will be agreed upon before beginning the implementation process (SKU, UPC, ASIN, etc.). Whichever item type is sent in this 846 will be used throughout the entire order life cycle.

    SDQ
    220

    Destination Quantity

    RequiredMax use 500

    To specify destination and quantity detail

    Usage notes

    SDQEA92ADSX0~

    Example
    SDQ-01
    355
    Unit or Basis for Measurement Code
    Required

    Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

    EA
    Each
    SDQ-02
    66
    Identification Code Qualifier
    Required

    Code designating the system/method of code structure used for Identification Code (67)

    • SDQ02 is used only if different than previously defined in the transaction set.
    92
    Assigned by Buyer or Buyer's Agent
    SDQ-03
    67
    Identification Code
    Required
    Min 2Max 80

    Code identifying a party or other code

    • SDQ03 is the store number.
    Usage notes

    This will be the Amazon code representing the warehouse that the order should ship from. This is usually a four character alpha code (e.g. ABCD). Only one warehouse code allowed per ST/SE loop .

    SDQ-04
    380
    Quantity
    Required
    Min 1Max 15

    Numeric value of quantity

    Usage notes

    Available Quantity. If an item is out of stock, send "0", do not leave blank.

    Quantity not to exceed 999,999. If a quantity exceeds this amount we will default to 999,999 until the quantity drops below that amount.

    Summary

    CTT
    010

    Transaction Totals

    OptionalMax use 1

    To transmit a hash total for a specific element in the transaction set

    • Number of line items (CTT01) is the accumulation of number of LIN segments. If used, hash total (CTT02) is the sum of the values of the quantities (QTY02) of each QTY segment.
    Usage notes

    CTT111029~

    Example
    CTT-01
    354
    Number of Line Items
    Required
    Min 1Max 6

    Total number of line items in the transaction set

    Usage notes

    Total number of line items.

    CTT-02
    347
    Hash Total
    Optional
    Min 1Max 10

    Sum of values of the specified data element. All values in the data element will be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the left most digits if the sum is greater than the maximum size of the hash total of the data element.

    ## Example:
    -.0018 First occurrence of value being hashed.
    .18 Second occurrence of value being hashed.
    1.8 Third occurrence of value being hashed.
    18.01 Fourth occurrence of value being hashed.

    1855 Hash total prior to truncation.
    855 Hash total after truncation to three-digit field.

    Usage notes

    Total number of units in the transaction set.

    SE
    020

    Transaction Set Trailer

    RequiredMax use 1

    To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

    Example
    SE-01
    96
    Number of Included Segments
    Required
    Min 1Max 10

    Total number of segments included in a transaction set including ST and SE segments

    SE-02
    329
    Transaction Set Control Number
    Required
    Min 4Max 9

    Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

    Functional Group Trailer

    RequiredMax use 1

    To indicate the end of a functional group and to provide control information

    Example
    GE-01
    97
    Number of Transaction Sets Included
    Required
    Min 1Max 6

    Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

    GE-02
    28
    Group Control Number
    Required
    Min 1Max 9

    Assigned number originated and maintained by the sender

    Interchange Control Trailer

    RequiredMax use 1

    To define the end of an interchange of zero or more functional groups and interchange-related control segments

    Example
    IEA-01
    I16
    Number of Included Functional Groups
    Required
    Min 1Max 5

    A count of the number of functional groups included in an interchange

    IEA-02
    I12
    Interchange Control Number
    Required
    Min 9Max 9

    A control number assigned by the interchange sender

    EDI Samples

    Full Feed

    ISA*00* *00* *ZZ*SENDERID *ZZ*AMAZONDS *220924*2001*U*00401*000000076*0*P*>~
    GS*IB*SENDERID*AMAZONDS*20220924*2001*76*X*004010~
    ST*846*319101~
    BIA*00*DD*37*20220912*1230~
    N1*ZZ*WHSE*92*WHSE~
    LIN*1*SK*M3199W~
    SDQ*EA*92*WHSE*9~
    LIN*2*SK*M8010A~
    SDQ*EA*92*WHSE*52~
    LIN*3*SK*M4799V~
    SDQ*EA*92*WHSE*3~
    LIN*4*SK*M4899Q~
    SDQ*EA*92*WHSE*0~
    LIN*5*SK*K5155C~
    SDQ*EA*92*WHSE*0~
    LIN*6*SK*K5152N~
    SDQ*EA*92*WHSE*16~
    LIN*7*SK*K5101O~
    SDQ*EA*92*WHSE*4~
    LIN*8*SK*K5101C~
    SDQ*EA*92*WHSE*10~
    LIN*9*SK*K5152O~
    SDQ*EA*92*WHSE*9~
    LIN*10*SK*K5101N~
    SDQ*EA*92*WHSE*24~
    LIN*11*SK*K5155O~
    SDQ*EA*92*WHSE*11~
    LIN*12*SK*K5155N~
    SDQ*EA*92*WHSE*15~
    LIN*13*SK*K5152C~
    SDQ*EA*92*WHSE*10~
    LIN*14*SK*K5101W~
    SDQ*EA*92*WHSE*13~
    LIN*15*SK*K5152W~
    SDQ*EA*92*WHSE*15~
    LIN*16*SK*K5155W~
    SDQ*EA*92*WHSE*15~
    CTT*16*196~
    SE*38*319101~
    GE*1*76~
    IEA*1*000000076~

    Partial Feed

    ISA*00* *00* *ZZ*SENDERID *ZZ*AMAZONDS *220924*2001*U*00401*000000077*0*P*>~
    GS*IB*SENDERID*AMAZONDS*20220924*2001*77*X*004010~
    ST*846*405101~
    BIA*25*DD*45*20220924*1531~
    N1*ZZ*WHSE*92*WHSE~
    LIN*1*SK*M0413CP~
    SDQ*EA*92*WHSE*16~
    LIN*2*SK*M4801W~
    SDQ*EA*92*WHSE*0~
    LIN*3*SK*M4791C~
    SDQ*EA*92*WHSE*0~
    LIN*4*SK*M4755C~
    SDQ*EA*92*WHSE*63~
    LIN*5*SK*M5928Q~
    SDQ*EA*92*WHSE*12~
    LIN*6*SK*M5924Q~
    SDQ*EA*92*WHSE*11~
    LIN*7*SK*M5921Q~
    SDQ*EA*92*WHSE*2~
    LIN*8*SK*M5926Q~
    SDQ*EA*92*WHSE*14~
    CTT*8*118~
    SE*22*405101~
    GE*1*77~
    IEA*1*000000077~

    Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.