Target
/
Drop Ship Purchase Order Acknowledgment
  • Specification
  • EDI Inspector
Import guide into your account
Target logo

X12 855 Drop Ship Purchase Order Acknowledgment

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Acknowledgment Transaction Set (855) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business and industry practice relative to a seller's acknowledgment of a buyer's purchase order. This transaction set can also be used as notification of a vendor generated order. This usage advises a buyer that a vendor has or will ship merchandise as prearranged in their partnership.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI samples
    View the latest version of this implementation guide as an interactive webpage
    https://www.stedi.com/app/guides/view/target/drop-ship-purchase-order-acknowledgment/01HBRNR9KV1KGYN4PWQ964K148
    Powered by
    Build EDI implementation guides at stedi.com
    Overview
    ISA
    -
    Interchange Control Header
    Max use 1
    Required
    GS
    -
    Functional Group Header
    Max use 1
    Required
    heading
    detail
    PO1 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
    String (AN)
    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
    String (AN)
    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
    Identifier (ID)
    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
    String (AN)
    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
    Identifier (ID)
    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
    String (AN)
    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
    Numeric (N0)
    Min 9Max 9

    A control number assigned by the interchange sender

    ISA-14
    I13
    Acknowledgment Requested
    Required
    Identifier (ID)
    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
    Identifier (ID)
    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
    String (AN)
    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

    PR
    Purchase Order Acknowledgement (855)
    GS-02
    142
    Application Sender's Code
    Required
    String (AN)
    Min 2Max 15

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

    GS-03
    124
    Application Receiver's Code
    Required
    String (AN)
    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
    Numeric (N0)
    Min 1Max 9

    Assigned number originated and maintained by the sender

    GS-07
    455
    Responsible Agency Code
    Required
    Identifier (ID)
    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
    Heading > ST

    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).
    855
    Purchase Order Acknowledgment
    ST-02
    329
    Transaction Set Control Number
    Required
    Numeric (N)
    Min 4Max 9

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

    BAK
    020
    Heading > BAK

    Beginning Segment for Purchase Order Acknowledgment

    RequiredMax use 1

    To indicate the beginning of the Purchase Order Acknowledgment Transaction Set and transmit identifying numbers and dates

    Usage notes

    BAK00AC123456789020100215

    Example
    BAK-01
    353
    Transaction Set Purpose Code
    Required

    Code identifying purpose of transaction set

    00
    Original
    BAK-02
    587
    Acknowledgment Type
    Required

    Code specifying the type of acknowledgment

    AC
    Acknowledge - With Detail and Change
    BAK-03
    324
    Purchase Order Number
    Required
    String (AN)
    Min 1Max 22

    Identifying number for Purchase Order assigned by the orderer/purchaser

    BAK-04
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    • BAK04 is the date assigned by the purchaser to purchase order.
    Usage notes

    Date of Target PO.

    REF
    050
    Heading > REF

    Reference Identification

    RequiredMax use >1

    To specify identifying information

    Usage notes

    REFVR12345

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    VR
    Vendor ID Number
    REF-02
    127
    Reference Identification
    Required
    String (AN)
    Min 4Max 30

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

    Usage notes

    Target.com assigned vendor number (minimum of 4 digits).

    Heading end

    Detail

    PO1 Loop
    RequiredMax >1
    PO1
    010
    Detail > PO1 Loop > PO1

    Baseline Item Data

    RequiredMax use 1

    To specify basic and most frequently used line item data

    • PO102 is required.
    Usage notes

    Note: Target.com requires the manufacturer style number (SK) to be sent on the 855.

    The CB qualifier and identifying number cannot be sent on the 855.

    PO101 cannot be duplicated in the 855. Only one line 1, line 2, etc.

    Sample PO1 Segment

    ---

    PO111***SK130134~

    Example
    If either Product/Service ID Qualifier (PO1-10) or Product/Service ID (PO1-11) is present, then the other is required
    If either Product/Service ID Qualifier (PO1-08) or Product/Service ID (PO1-09) is present, then the other is required
    PO1-01
    350
    Assigned Identification
    Required
    String (AN)
    Min 1Max 20

    Alphanumeric characters assigned for differentiation within a transaction set

    • PO101 is the line item identification.
    Usage notes

    Order Line Number. Must match line number sent on Purchase Order.

    PO1-02
    330
    Quantity Ordered
    Required
    Decimal number (R)
    Min 1Max 15

    Quantity ordered

    Usage notes

    Target.com expects to receive the order quantity that was sent on the 850 PO.

    PO1-06
    235
    Product/Service ID Qualifier
    Required

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

    • PO106 through PO125 provide for ten different product/service IDs per each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
    EN
    European Article Number (EAN) (2-5-5-1)
    EO
    EAN/USS 8
    IN
    Buyer's Item Number
    SK
    Stock Keeping Unit (SKU)
    UA
    U.P.C./EAN Case Code (2-5-5)
    UK
    U.P.C./EAN Shipping Container Code (1-2-5-5-1)

    A 14-digit code that uniquely identifies the manufacturer's shipping unit, including the packaging indicator and check digit; the first digit is the packaging indicator, the next two digits are the number system characters, the next five digits are the manufacturer ID number, the second five digits are the item code, and the final digit is the check digit

    UP
    U.P.C. Consumer Package Code (1-5-5-1)
    PO1-07
    234
    Product/Service ID
    Required
    String (AN)
    Min 1Max 48

    Identifying number for a product or service

    Usage notes

    When PO106 = SK, this contains the Manufacturer's style number
    When PO106 = IN, this contains the Target.com item number( 6 to 8 digits)
    When PO106 = UP, this contains the UPC (12 digits)
    When PO106 = EO, this value is the 8 digit EAN
    When PO106 = EN, this value is the 13 digit EAN
    When PO106= IB, this value is the ISBN
    When PO106 = UK, this value is the 14 digit barcode

    PO1-08
    235
    Product/Service ID Qualifier
    Optional

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

    EN
    European Article Number (EAN) (2-5-5-1)
    EO
    EAN/USS 8
    IN
    Buyer's Item Number
    SK
    Stock Keeping Unit (SKU)
    UA
    U.P.C./EAN Case Code (2-5-5)
    UK
    U.P.C./EAN Shipping Container Code (1-2-5-5-1)

    A 14-digit code that uniquely identifies the manufacturer's shipping unit, including the packaging indicator and check digit; the first digit is the packaging indicator, the next two digits are the number system characters, the next five digits are the manufacturer ID number, the second five digits are the item code, and the final digit is the check digit

    UP
    U.P.C. Consumer Package Code (1-5-5-1)
    PO1-09
    234
    Product/Service ID
    Optional
    String (AN)
    Min 1Max 48

    Identifying number for a product or service

    Usage notes

    When PO108 = SK, this contains the Manufacturer's style number
    When PO108 = IN, this contains the Target.com item number( 6 to 8 digits)
    When PO108 = UP, this contains the UPC (12 digits)
    When PO108 = EO, this value is the 8 digit EAN
    When PO108 = EN, this value is the 13 digit EAN
    When PO108= IB, this value is the ISBN
    When PO108 = UK, this value is the 14 digit barcode

    PO1-10
    235
    Product/Service ID Qualifier
    Optional

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

    EN
    European Article Number (EAN) (2-5-5-1)
    EO
    EAN/USS 8
    IN
    Buyer's Item Number
    SK
    Stock Keeping Unit (SKU)
    UA
    U.P.C./EAN Case Code (2-5-5)
    UK
    U.P.C./EAN Shipping Container Code (1-2-5-5-1)

    A 14-digit code that uniquely identifies the manufacturer's shipping unit, including the packaging indicator and check digit; the first digit is the packaging indicator, the next two digits are the number system characters, the next five digits are the manufacturer ID number, the second five digits are the item code, and the final digit is the check digit

    UP
    U.P.C. Consumer Package Code (1-5-5-1)
    PO1-11
    234
    Product/Service ID
    Optional
    String (AN)
    Min 1Max 48

    Identifying number for a product or service

    Usage notes

    When PO110 = SK, this contains the Manufacturer's style number
    When PO110 = IN, this contains the Target.com item number( 6 to 8 digits)
    When PO110 = UP, this contains the UPC (12 digits)
    When PO110 = EO, this value is the 8 digit EAN
    When PO110 = EN, this value is the 13 digit EAN
    When PO110= IB, this value is the ISBN
    When PO110 = UK, this value is the 14 digit barcode

    ACK Loop
    RequiredMax >1
    ACK
    270
    Detail > PO1 Loop > ACK Loop > ACK

    Line Item Acknowledgment

    RequiredMax use 1

    To acknowledge the ordered quantities and specify the ready date for a specific line item

    Usage notes

    Note 1: Used byTarget.com to clarify rejection.

    Note 2: Only one ACK segment per item (PO1 segment) is accepted by Target.com.

    Note 3: If ACK01=IA do not send a value in the ACK29.

    Note 4: If ACK01=IR, a value must be sent in the ACK29.

    Sample ACK Segments

    ---

    ACKIA
    ACK
    IR****************************OUTOFSTOCK

    Example
    ACK-01
    668
    Line Item Status Code
    Required

    Code specifying the action taken by the seller on a line item requested by the buyer

    IA
    Item Accepted

    When IA is used do not send a value in the ACK29.

    IR
    Item Rejected

    When IR is used, a value must be sent in the ACK29

    ACK-05
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD

    ACK-29
    1271
    Industry Code
    Optional

    Code indicating a code from a specific industry code list

    • ACK29 Industry Reason Code may be used to identify the item status. In addition, it may be used in conjunction with ACK01 to further clarify the status.
    Usage notes

    Used by Target.com to clarify the rejection.
    When ACK01 = IA, do not send a value in the ACK29.
    When ACK01 = IR, a value must be sent in the ACK29.

    ONLY the values listed below are allowed.
    It is critical to send the value as it appears below - spelling and in upper case.
    If the value is not sent as listed, your 855 may be rejected. The description is here for informational purposes only. Do NOT send the description value.

    48STATESONLY
    Shipment to contiguous 48 states only
    BADADDRESS
    Invalid Address
    DISCONTINUED
    Item is discontinued
    NOSHIPAPOFPOPO
    No shipment to APO, FPO or PO Box
    OUTOFSTOCK
    Item Out of Stock
    PRICE
    Invalid Price
    SKU
    Invalid SKU
    ACK Loop end
    PO1 Loop end
    Detail end

    Summary

    CTT Loop
    RequiredMax >1
    CTT
    010
    Summary > CTT Loop > CTT

    Transaction Totals

    RequiredMax use 1

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

    • The number of line items (CTT01) is the accumulation of the number of PO1 segments. If used, hash total (CTT02) is the sum of the value of quantities ordered (PO102) for each PO1 segment.
    Usage notes

    CTT*1

    Example
    CTT-01
    354
    Number of Line Items
    Required
    Numeric (N0)
    Min 1Max 6

    Total number of line items in the transaction set

    Usage notes

    The number of PO1 segments in this transaction set

    CTT Loop end
    SE
    030
    Summary > SE

    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
    Numeric (N0)
    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
    Numeric (N)
    Min 4Max 9

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

    Summary end

    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
    Numeric (N0)
    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
    Numeric (N0)
    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
    Numeric (N0)
    Min 1Max 5

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

    IEA-02
    I12
    Interchange Control Number
    Required
    Numeric (N0)
    Min 9Max 9

    A control number assigned by the interchange sender

    EDI Samples

    Sample 855

    ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *231006*0233*U*00401*000000001*0*T*>
    GS*PR*SENDERGS*RECEIVERGS*20231006*023306*000000001*X*004010
    ST*855*0001
    BAK*00*AC*1234567890*20100215
    REF*VR*12345
    PO1*1*1****SK*130134~
    ACK*IA
    PO1*2*1****SK*130135~
    ACK*IR****************************OUTOFSTOCK
    CTT*2
    SE*9*0001
    GE*1*000000001
    IEA*1*000000001

    Sample 855 (2)

    ISA*00* *00* *ZZ*1112001111 *ZZ*AABBCC *230801*1752*U*00401*100000111*0*P*}~
    GS*PR*1112001111*AABBCC*20230801*1752*1111*X*004010~
    ST*855*1111~
    BAK*00*AC*123123123*20230801~
    REF*VR*543543~
    PO1*1*1****IN*111111*SK*AAA-BBB-CCC-D*UP*4534534534543~
    ACK*IA~
    CTT*1~
    SE*7*1111~
    GE*1*1111~
    IEA*1*100000111~

    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.