Redwood Logistics
/
Transportation Carrier Shipment Status Message
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from Redwood Logistics. Contact Redwood Logistics for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Redwood Logistics logo

X12 214 Transportation Carrier Shipment Status Message

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Transportation Carrier Shipment Status Message Transaction Set (214) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by a transportation carrier to provide shippers, consignees, and their agents with the status of shipments in terms of dates, times, locations, route, identifying numbers, and conveyance.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI sample
    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
    B10
    020
    Beginning Segment for Transportation Carrier Shipment Status Message
    Max use 1
    Required
    L11
    030
    Job (Project) Number
    Max use 300
    Optional
    L11
    030
    Stop Sequence Number
    Max use 300
    Optional
    Consignee or Ship From or Shipper or Ship To
    0200 Loop
    LX
    130
    Assigned Number
    Max use 1
    Required
    AT8
    200
    Shipment Weight, Packaging and Quantity Data
    Max use 10
    Optional
    0210 Loop
    SE
    610
    Transaction Set Trailer
    Max use 1
    Required
    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

    QM
    Transportation Carrier Shipment Status Message (214)
    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).
    214
    Transportation Carrier Shipment Status Message
    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

    B10
    020

    Beginning Segment for Transportation Carrier Shipment Status Message

    RequiredMax use 1

    To transmit identifying numbers and other basic data relating to the transaction set

    Usage notes

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

    Example: B10339346807936*SCAC~

    Example
    B10-01
    127
    Reference Identification
    Required
    Min 1Max 30

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

    • B1001 is the carrier assigned reference number.
    • B1001 is the carrier's PRO (invoice number) that identifies the shipment.
    Usage notes

    Carrier’s unique identifier for the shipment (typically PRO number).

    B10-02
    145
    Shipment Identification Number
    Required
    Min 1Max 30

    Identification number assigned to the shipment by the shipper that uniquely identifies the shipment from origin to ultimate destination and is not subject to modification; (Does not contain blanks or special characters)

    Usage notes

    Redwood customer’s unique identifier for the shipment.

    B10-03
    140
    Standard Carrier Alpha Code
    Required
    Min 2Max 4

    Standard Carrier Alpha Code

    • B1003 is required when used in Transaction Set 214.
    Usage notes

    Carrier’s designated SCAC identifier code.

    L11
    030

    Job (Project) Number

    OptionalMax use 300

    To specify instructions in this business relationship or a reference number

    Example
    Variants (all may be used)
    L11 Stop Sequence Number
    At least one of Reference Identification (L11-01) or Description (L11-03) is required
    L11-01
    127
    Reference Identification
    Optional
    Min 1Max 30

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

    Usage notes

    Reference Value

    L11-02
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    JB
    Job (Project) Number
    L11-03
    352
    Description
    Optional
    Min 1Max 80

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

    Usage notes

    Reference Description

    L11
    030

    Stop Sequence Number

    OptionalMax use 300

    To specify instructions in this business relationship or a reference number

    Usage notes

    Stop # reference is mandatory for multi-stop loads. Otherwise, L11s are optional.

    Used to specify additional reference numbers beyond those provided on the B10 segment.

    L11 segment with qualifier QN must be included to indicate which stop sequence number the status message pertains to. Any other L11s may be included.

    Example: L112QN~

    Example
    Variants (all may be used)
    L11Job (Project) Number
    L11-01
    127
    Reference Identification
    Required
    Min 1Max 30

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

    Usage notes

    Reference Value

    L11-02
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    Usage notes

    Reference of QN is required for all stops.

    QN
    Stop Sequence Number
    L11-03
    352
    Description
    Optional
    Min 1Max 80

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

    Usage notes

    Reference Description

    0100 Consignee or Ship From or Shipper or Ship To
    RequiredMax >1
    Variants (all may be used)
    0100Customer
    N1
    050

    Name

    RequiredMax use 1

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

    Usage notes

    Examples:
    N1SHSHIPPERZZABC~
    N1CNRECIPIENTZZDEF~

    Example
    At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
    If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
    N1-01
    98
    Entity Identifier Code
    Required

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

    CN
    Consignee
    SF
    Ship From
    SH
    Shipper
    ST
    Ship To
    N1-02
    93
    Name
    Optional
    Min 1Max 60

    Free-form name

    N1-03
    66
    Identification Code Qualifier
    Optional

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

    Usage notes

    If using a location identifier codes, use 93.

    93
    Code assigned by the organization originating the transaction set
    ZZ
    Mutually Defined
    N1-04
    67
    Identification Code
    Optional
    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

    If using location identifier codes, please send code as received on tender.

    N3
    070

    Address Information

    RequiredMax use 2

    To specify the location of the named party

    Usage notes

    Example: N31765 N Elston AveSuite 300~

    Example
    N3-01
    166
    Address Information
    Required
    Min 1Max 55

    Address information

    N3-02
    166
    Address Information
    Optional
    Min 1Max 55

    Address information

    N4
    080

    Geographic Location

    RequiredMax use 1

    To specify the geographic place of the named party

    Usage notes

    Example: N4CHICAGOIL60622USA~

    Example
    N4-01
    19
    City Name
    Optional
    Min 2Max 30

    Free-form text for city name

    • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
    N4-02
    156
    State or Province Code
    Optional
    Min 2Max 2

    Code (Standard State/Province) as defined by appropriate government agency

    • N402 is required only if city name (N401) is in the U.S. or Canada.
    N4-03
    116
    Postal Code
    Optional
    Min 3Max 15

    Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

    N4-04
    26
    Country Code
    Optional
    Min 2Max 3

    Code identifying the country

    0100 Customer
    RequiredMax >1
    N1
    050

    Name

    RequiredMax use 1

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

    Usage notes

    Example: N1LWCustomer Name93CUSTOMERCODE~

    If the Entity Identifier Code of “LW” is included in the tender, the data in the N1 segment must be included on corresponding 214 messages.

    Example
    At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
    N1-01
    98
    Entity Identifier Code
    Required

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

    LW
    Customer
    N1-02
    93
    Name
    Optional
    Min 1Max 60

    Free-form name

    N1-03
    66
    Identification Code Qualifier
    Optional

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

    93
    Code assigned by the organization originating the transaction set
    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

    Redwood Customer Code

    0200 Loop
    RequiredMax >1
    LX
    130

    Assigned Number

    RequiredMax use 1

    To reference a line number in a transaction set

    Usage notes

    For each LX loop, there should be a single AT7, a single MS1, and a single MS2.

    Example: LX*1~

    Example
    LX-01
    554
    Assigned Number
    Required
    Min 1Max 6

    Number assigned for differentiation within a transaction set

    Usage notes

    Example: 1

    0205 Loop
    RequiredMax >1
    AT7
    140

    Shipment Status Details

    RequiredMax use 1

    To specify the status of a shipment, the reason for that status, the date and time of the status and the date and time of any appointments scheduled.

    Usage notes

    AT701 –X6 and AG messages are expected every four hours, if possible, based on partners system capabilities.

    Example: AT7AFNS**201909181130*LT~

    Example
    If either Shipment Status Code (AT7-01) or Shipment Status or Appointment Reason Code (AT7-02) is present, then the other is required
    Only one of Shipment Status Code (AT7-01) or Shipment Appointment Status Code (AT7-03) may be present
    If either Shipment Appointment Status Code (AT7-03) or Shipment Status or Appointment Reason Code (AT7-04) is present, then the other is required
    If Time Code (AT7-07) is present, then Time (AT7-06) is required
    AT7-01
    1650
    Shipment Status Code
    Optional

    Code indicating the status of a shipment

    • If AT701 is present, AT705 is the date the status occurred. If AT703 is present, AT705 is a date related to an appointment.
    • If AT701 is present, AT706 is the time of the status. If AT703 is present, AT706 is the time of the appointment.
    Usage notes

    Redwood accepts all standard shipment status codes.

    AF
    Actual Pickup
    AG
    Estimated Delivery
    D1
    Completed Unloading at Delivery Location
    X1
    Arrived at Delivery Location
    X2
    Estimated Date and/or Time of Arrival at Consignee's Location
    X3
    Arrived at Pick-up Location
    X6
    En Route to Delivery Location
    AT7-02
    1651
    Shipment Status or Appointment Reason Code
    Optional

    Code indicating the reason a shipment status or appointment reason was transmitted

    Usage notes

    Redwood accepts all standard reason codes default is NS.

    NS
    Normal Status
    AT7-03
    1652
    Shipment Appointment Status Code
    Optional

    Code indicating the status of an appointment to pick-up or deliver a shipment

    Usage notes

    Redwood accepts all standard shipment appointment status codes.

    AA
    Pick-up Appointment Date and/or Time
    AB
    Delivery Appointment Date and/or Time
    AT7-04
    1651
    Shipment Status or Appointment Reason Code
    Optional

    Code indicating the reason a shipment status or appointment reason was transmitted

    Usage notes

    Redwood accepts all standard reason codes for appointments default is NA.

    NA
    Normal Appointment
    AT7-05
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    AT7-06
    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)

    Usage notes

    Format: HHMM

    AT7-07
    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

    • If AT707 is not present then AT706 represents local time of the status.
    Usage notes

    Redwood requests that all status updates be provided in local time to the location of the status, so if this element is included, it should be set to LT.

    LT
    Local Time
    MS1
    143

    Equipment, Shipment, or Real Property Location

    RequiredMax use 1

    To specify the location of a piece of equipment, a shipment, or real property in terms of city and state or longitude and latitude

    Usage notes

    Example: MS1CHICAGOIL*USA~

    Example
    If State or Province Code (MS1-02) is present, then City Name (MS1-01) is required
    If City Name (MS1-01) is present, then at least one of State or Province Code (MS1-02) or Country Code (MS1-03) is required
    If Country Code (MS1-03) is present, then City Name (MS1-01) is required
    MS1-01
    19
    City Name
    Optional
    Min 2Max 30

    Free-form text for city name

    MS1-02
    156
    State or Province Code
    Optional
    Min 2Max 2

    Code (Standard State/Province) as defined by appropriate government agency

    MS1-03
    26
    Country Code
    Optional
    Min 2Max 3

    Code identifying the country

    MS2
    146

    Equipment or Container Owner and Type

    OptionalMax use 1

    To specify the owner, the identification number assigned by that owner, and the type of equipment

    Usage notes

    May be required for certain customers.

    Example: MS2SCACEQUIP*TR~

    Example
    If either Standard Carrier Alpha Code (MS2-01) or Equipment Number (MS2-02) is present, then the other is required
    MS2-01
    140
    Standard Carrier Alpha Code
    Optional
    Min 2Max 4

    Standard Carrier Alpha Code

    Usage notes

    Carrier’s designated SCAC identifier code.

    MS2-02
    207
    Equipment Number
    Optional
    Min 1Max 10

    Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)

    Usage notes

    Identifier code for the equipment.

    MS2-03
    40
    Equipment Description Code
    Optional

    Code identifying type of equipment used for shipment

    • MS203 identifies the type for the equipment specified in MS202.
    TL
    Trailer (not otherwise specified)
    TR
    Tractor
    AT8
    200

    Shipment Weight, Packaging and Quantity Data

    OptionalMax use 10

    To specify shipment details in terms of weight, and quantity of handling units

    Usage notes

    Example: AT8GL150040~

    Example
    If either Weight Qualifier (AT8-01), Weight Unit Code (AT8-02) or Weight (AT8-03) are present, then the others are required
    AT8-01
    187
    Weight Qualifier
    Optional

    Code defining the type of weight

    G
    Gross Weight
    AT8-02
    188
    Weight Unit Code
    Optional

    Code specifying the weight unit

    K
    Kilograms
    L
    Pounds
    AT8-03
    81
    Weight
    Optional
    Min 1Max 10

    Numeric value of weight

    Usage notes

    Example: 1500

    AT8-04
    80
    Lading Quantity
    Optional
    Min 1Max 7

    Number of units (pieces) of the lading commodity

    • AT804 is the quantity of handling units that are not unitized (for example a carton). When added to the quantity in AT805, it is the total quantity of handling units in the shipment.
    Usage notes

    Example: 40

    0210 Loop
    OptionalMax >1
    CD3
    210

    Carton (Package) Detail

    RequiredMax use 1

    To transmit identifying codes, weights, and other related information related to an individual carton (package)

    • Loops 0210, 0215 and 0220 shall be used in conjunction with loop 0200 to convey status for small package carrier shipments.
    Example
    NM1
    240

    Individual or Organizational Name

    OptionalMax use 1

    To supply the full name of an individual or organizational entity

    Usage notes

    Example: NM1NS1LASTNAMEFIRSTNAME~

    Example
    NM1-01
    98
    Entity Identifier Code
    Required

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

    N5
    Party Who Signed the Delivery Receipt
    NM1-02
    1065
    Entity Type Qualifier
    Required

    Code qualifying the type of entity

    • NM102 qualifies NM103.
    1
    Person
    NM1-03
    1035
    Name Last or Organization Name
    Optional
    Min 1Max 35

    Individual last name or organizational name

    Usage notes

    Freeform individual last name or organization name.

    NM1-04
    1036
    Name First
    Optional
    Min 1Max 25

    Individual first name

    0250 Loop
    OptionalMax >1
    SPO
    410

    Shipment Purchase Order Detail

    RequiredMax use 1

    To specify the purchase order details for a shipment

    Usage notes

    Example: SPO*100920041~

    Example
    SPO-01
    324
    Purchase Order Number
    Required
    Min 1Max 22

    Identifying number for Purchase Order assigned by the orderer/purchaser

    Usage notes

    Freeform text purchase order number assigned by the purchaser.

    SE
    610

    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

    Sample

    B10*339346*807936*SCAC~
    L11*2*QN~
    L11*12345*JB~
    N1*LW*Customer Name*93*CUSTOMERCODE~
    N1*SH*SHIPPER*ZZ*ABC~
    N3*1234 MY STREET~
    N4*CHICAGO*IL*60606*USA~
    N1*CN*RECIPIENT*ZZ*DEF~
    N3*1234 THEIR STREET~
    N4*CHICAGO*IL*60611*USA~
    LX*1~
    AT7*AF*NS***20190918*1130*LT~
    MS1*CHICAGO*IL*USA~
    MS2*SCAC*EQUIP~
    AT8*G*L*558*21~
    CD3~
    NM1*N5*1*Supplier*Full Name~
    SPO*100920041~

    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.