Amazon
/
Retail Purchase Order
  • Specification
  • EDI Inspector
Import guide into your account
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 Stedi Network
Amazon logo

X12 850 Retail Purchase Order

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Transaction Set (850) 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 the placement of purchase orders for goods and services. This transaction set should not be used to convey purchase order changes or purchase order acknowledgment information.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI samples
    View the latest version of this implementation guide as an interactive webpage
    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
    ST
    010
    Transaction Set Header
    Max use 1
    Required
    BEG
    020
    Beginning Segment for Purchase Order
    Max use 1
    Required
    REF
    050
    Associated Purchase Orders
    Max use 1
    Optional
    REF
    050
    Customer Reference Number
    Max use 1
    Required
    REF
    050
    Promotion/Deal Number
    Max use 1
    Optional
    FOB
    080
    F.O.B. Related Instructions
    Max use 1
    Optional
    CSH
    110
    Sales Requirements
    Max use 5
    Required
    DTM
    150
    Do Not Deliver After
    Max use 10
    Required
    DTM
    150
    Do Not Deliver Before
    Max use 10
    Required
    PKG
    220
    Marking, Packaging, Loading
    Max use 200
    Optional
    N9 Loop
    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

    PO
    Purchase Order (850)
    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).
    850
    Purchase Order
    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

    BEG
    020

    Beginning Segment for Purchase Order

    RequiredMax use 1

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

    Usage notes

    Example:
    BEG00NE*G7984251**20221102

    Example
    BEG-01
    353
    Transaction Set Purpose Code
    Required

    Code identifying purpose of transaction set

    00
    Original
    BEG-02
    92
    Purchase Order Type Code
    Required

    Code specifying the type of Purchase Order

    CN
    Consigned Order
    NE
    New Order
    NP
    New Product Introduction
    RO
    Rush Order
    BEG-03
    324
    Purchase Order Number
    Required
    Min 1Max 22

    Identifying number for Purchase Order assigned by the orderer/purchaser

    Usage notes

    This field will contain the Amazon PO number for this order.
    Formatting Notes: 8-character alpha-numeric code

    BEG-05
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

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

    This field will be the PO date

    REF
    050

    Associated Purchase Orders

    OptionalMax use >1

    To specify identifying information

    Usage notes

    This field contains the Amazon Container Consolidation ID (CCID). All purchase orders from Amazon with the same CCID should be shipped together as a Full Truck Load (FTL). To enroll into this program please work with your respective Vendor Manager. This applies only to vendors who participate in Amazon FTL program.

    Example:
    REFANA131243523

    Example
    Variants (all may be used)
    REFCustomer Reference NumberREFPromotion/Deal Number
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    AN
    Associated Purchase Orders
    REF-02
    127
    Reference Identification
    Optional
    Min 1Max 30

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

    REF
    050

    Customer Reference Number

    RequiredMax use >1

    To specify identifying information

    Usage notes

    This field contains the Amazon vendor code for which the PO is created. This is not the PO number.

    Example:
    REFCRAMZN_VENDORCODE

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    CR
    Customer Reference Number
    REF-02
    127
    Reference Identification
    Required
    Min 1Max 30

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

    REF
    050

    Promotion/Deal Number

    OptionalMax use >1

    To specify identifying information

    Usage notes

    This segment will be sent for import vendors only. To receive this segment
    in EDI file please reach out to your Amazon business representative.
    Example:
    REFPDPROMO_CODE

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    PD
    Promotion/Deal Number
    REF-02
    127
    Reference Identification
    Optional
    Min 1Max 30

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

    FOB
    080

    F.O.B. Related Instructions

    OptionalMax use >1

    To specify transportation instructions relating to shipment

    Usage notes

    This segment will be only sent for import vendors.

    Example:
    FOBBP*01CFROVYANTIAN, CHINA

    Example
    If Transportation Terms Qualifier Code (FOB-04) is present, then Transportation Terms Code (FOB-05) is required
    If Description (FOB-07) is present, then Location Qualifier (FOB-06) is required
    FOB-01
    146
    Shipment Method of Payment
    Required

    Code identifying payment terms for transportation charges

    • FOB01 indicates which party will pay the carrier.
    Usage notes

    If the recipient requests, this field will contain a the Shipment Method of Payment

    BP
    Paid by Buyer
    CC
    Collect
    DF
    Defined by Buyer and Seller
    FO
    FOB Port of Call
    PP
    Prepaid (by Seller)
    PS
    Paid by Seller
    FOB-04
    334
    Transportation Terms Qualifier Code
    Optional

    Code identifying the source of the transportation terms

    01
    Incoterms
    FOB-05
    335
    Transportation Terms Code
    Optional

    Code identifying the trade terms which apply to the shipment transportation responsibility

    CFR
    Cost and Freight
    CIF
    Cost, Insurance, and Freight
    CIP
    Carriage and Insurance Paid To
    CPT
    Carriage Paid To
    DAF
    Delivered at Frontier
    DDP
    Delivered Duty Paid
    DDU
    Deliver Duty Unpaid
    EXW
    Ex Works
    FCA
    Free Carrier
    FOB
    Free on Board
    FOB-06
    309
    Location Qualifier
    Optional

    Code identifying type of location

    • FOB06 is the code specifying the title passage location.
    OV
    On Vessel (Free On Board [FOB] point)
    FOB-07
    352
    Description
    Optional
    Min 1Max 80

    A free-form description to clarify the related data elements and their content

    Usage notes

    In that field the port will be specified

    CSH
    110

    Sales Requirements

    RequiredMax use 5

    To specify general conditions or requirements of the sale

    Usage notes

    This segment is used to identify if backorder is allowed for this PO.
    Example:
    CSH*N

    Example
    CSH-01
    563
    Sales Requirement Code
    Required

    Code to identify a specific requirement or agreement of sale

    N
    No Back Order
    Y
    Back Order if Out of Stock
    DTM
    150

    Do Not Deliver After

    RequiredMax use 10

    To specify pertinent dates and times

    Usage notes
    1. Amazon paid freight: Read the date in the field as the latest date that Amazon expects to pick up the freight. If the same date is listed in both DTM02 fields, then read that date as the date that Amazon expects to pick up the freight.

    2. Vendor paid freight: Read the date in the DTM02 field as the latest date that Amazon expects the freight to be delivered to the Amazon fulfillment center listed on the purchase order.

    Example:
    DTM06320221209

    Example
    Variants (all may be used)
    DTM Do Not Deliver Before
    DTM-01
    374
    Date/Time Qualifier
    Required

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

    063
    Do Not Deliver After
    DTM-02
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    DTM
    150

    Do Not Deliver Before

    RequiredMax use 10

    To specify pertinent dates and times

    Usage notes
    1. Amazon paid freight: Read the date in the field as the earliest date that Amazon expects to pick up the freight. If the same date is listed in both DTM02 fields, then read that date as the date that Amazon expects to pick up the freight.

    2. Vendor paid freight: Read the date in the DTM02 field as the earliest date that Amazon expects the freight to be delivered to the Amazon fulfillment center listed on the purchase order.

    Example:
    DTM06420221203

    Example
    Variants (all may be used)
    DTMDo Not Deliver After
    DTM-01
    374
    Date/Time Qualifier
    Required

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

    064
    Do Not Deliver Before
    DTM-02
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    PKG
    220

    Marking, Packaging, Loading

    OptionalMax use 200

    To describe marking, packaging, loading, and unloading requirements

    Usage notes

    This segment is used for Direct Import POs only.
    Example:
    PKGFCS***40'HC

    Example
    If Description (PKG-05) is present, then Item Description Type (PKG-01) is required
    PKG-01
    349
    Item Description Type
    Optional

    Code indicating the format of a description

    • If PKG01 equals "F", then PKG05 is used. If PKG01 equals "S", then PKG04 is used. If PKG01 equals "X", then both PKG04 and PKG05 are used.
    F
    Free-form
    PKG-02
    753
    Packaging Characteristic Code
    Optional

    Code specifying the marking, packaging, loading and related characteristics being described

    CS
    Container Shape
    PKG-05
    352
    Description
    Optional
    Min 1Max 80

    A free-form description to clarify the related data elements and their content

    • Special marking or tagging data can be given in PKG05 (description).
    Usage notes

    This field will specify the container size

    N9 Loop
    OptionalMax >1
    N9
    295

    Reference Identification

    RequiredMax use 1

    To transmit identifying information as specified by the Reference Identification Qualifier

    Usage notes

    If segment N9 is used, segment MSG is required.
    Example:
    N9L1SPECIAL INSTRUCTIONS

    Example
    N9-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    L1
    Letters or Notes
    N9-02
    127
    Reference Identification
    Optional
    Min 1Max 30

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

    MSG
    300

    Message Text

    RequiredMax use 1000

    To provide a free-form format that allows the transmission of text information

    Usage notes

    Example:
    MSG*PREFERENCE IS PALLET-LOAD, BUT IF CONTAINERS ARE FLOOR-LOADED, THEN PLEASE DO CLAMP-LOAD OR STRAIGHT FLOOR-LOAD. DO NOT USE SLIP SHEET FOR THIS FC DESTINATION. PAYMENT TERMS ARE PER CONTAINER.

    Example
    MSG-01
    933
    Free-Form Message Text
    Required
    Min 1Max 264

    Free-form message text

    Usage notes

    This field will specify additional comments or messages from the buying contact.

    N1 Loop
    RequiredMax >1
    N1
    310

    Name

    RequiredMax use 1

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

    Usage notes

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

    Example:
    N1ST**151553992

    Example
    N1-01
    98
    Entity Identifier Code
    Required

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

    ST
    Ship To
    N1-03
    66
    Identification Code Qualifier
    Required

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

    15
    Standard Address Number (SAN)
    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 field will be a code that represents the ship to location. View spreadsheet titled Amazon_North_America_Fulfillment_Center_Address_List.csv for a list of Amazon ship to values.

    Detail

    PO1 Loop
    RequiredMax >1
    PO1
    010

    Baseline Item Data

    RequiredMax use 1

    To specify basic and most frequently used line item data

    • PO102 is required.
    Usage notes

    Example:
    PO111EA4.12PEEN*9780812508420

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

    Alphanumeric characters assigned for differentiation within a transaction set

    • PO101 is the line item identification.
    PO1-02
    330
    Quantity Ordered
    Required
    Min 1Max 15

    Quantity ordered

    Usage notes

    This field will be the quantity of this item ordered

    PO1-03
    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

    CA
    Case
    EA
    Each
    PO1-04
    212
    Unit Price
    Required
    Min 1Max 15

    Price per unit of product, service, commodity, etc.

    Usage notes

    This field will either be the Price to Amazon Each (Cost) or the Price to Amazon Each (List), depending on the price basis coding in PO105 segment.

    Formatting Notes: nnnnn.nn
    Please note: Only two decimals are included for values provided via this field (e.g., 8.20).

    PO1-05
    639
    Basis of Unit Price Code
    Required

    Code identifying the type of unit price for an item

    PE
    Price per Each
    RE
    Retail Price per Each
    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.
    Usage notes

    This value should be what is returned in the PO106 element in the POA(855)

    BP
    Buyer's Part Number
    EN
    European Article Number (EAN) (2-5-5-1)
    IB
    International Standard Book Number (ISBN)
    UA
    U.P.C./EAN Case Code (2-5-5)
    UK
    U.P.C./EAN Shipping Container Code (1-2-5-5-1)
    UP
    U.P.C. Consumer Package Code (1-5-5-1)
    VN
    Vendor's (Seller's) Item Number
    PO1-07
    234
    Product/Service ID
    Required
    Min 1Max 48

    Identifying number for a product or service

    Usage notes

    This field will be the item ID

    Summary

    CTT Loop
    OptionalMax >1
    CTT
    010

    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

    Example:
    CTT560

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

    Total number of line items in the transaction set

    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

    This field will be the total number of items ordered.

    SE
    030

    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

    Retail Direct Import

    ISA*00* *00* *ZZ*AMAZON *ZZ*VENDOR *221110*0201*U*00401*000012911*0*P*>~
    GS*PO*AMAZON*VENDOR*20221110*0201*12911*X*004010~
    ST*850*0001~
    BEG*00*NE*T82Z63Y5**20221110~
    REF*CR*AMZN_VENDORCODE~
    FOB*CC~
    CSH*N~
    DTM*064*20221203~
    DTM*063*20221209~
    N1*ST**92*RNO1~
    PO1*1*8*EA*39*PE*UP*028877454078~
    PO1*2*6*EA*40*PE*UP*028877454077~
    CTT*2*14~
    SE*12*0001~
    GE*1*12911~
    IEA*1*000012911~

    Retail First Order

    ISA*00* *00* *ZZ*AMAZON *ZZ*VENDOR *221101*0201*U*00401*000012911*0*P*>~
    GS*PO*AMAZON*VENDOR*20221101*0201*12911*X*004010~
    ST*850*0001~
    BEG*00*NE*T82Z63Y5**20221101~
    REF*CR*AMZN_VENDORCODE~
    CSH*N~
    DTM*064*20221203~
    DTM*063*20221209~
    N1*ST**92*RNO1~
    PO1*1*8*EA*39*PE*UP*028877454078~
    PO1*2*6*EA*40*PE*UP*028877454077~
    CTT*2*14~
    SE*11*0001~
    GE*1*12911~
    IEA*1*000012911~

    Retail FTL

    ST*850*0001~
    BEG*00*NE*T82Z63Y5**20221110~
    REF*CR*AMZN_VENDORCODE~
    REF*AN*AMZN_CCID~
    CSH*N~
    DTM*064*20221203~
    DTM*063*20221209~
    N1*ST**92*RNO1~
    PO1*1*8*EA*39*PE*UP*028877454078~
    PO1*2*6*EA*40*PE*UP*028877454077~
    CTT*2*14~
    SE*12*0001~

    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.