X12 856 Ship Notice/Manifest
This Draft Standard for Trial Use contains the format and establishes the data contents of the Ship Notice/Manifest Transaction Set (856) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to list the contents of a shipment of goods as well as additional information relating to the shipment, such as order information, product description, physical characteristics, type of packaging, marking, carrier information, and configuration of goods within the transportation equipment. The transaction set enables the sender to describe the contents and configuration of a shipment in various levels of detail and provides an ordered flexibility to convey information.
The sender of this transaction is the organization responsible for detailing and communicating the contents of a shipment, or shipments, to one or more receivers of the transaction set. The receiver of this transaction set can be any organization having an interest in the contents of a shipment or information about the contents of a shipment.
- ~ Segment
- * Element
- > Component
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code to identify the type of information in the Authorization Information
- 00
- No Authorization Information Present (No Meaningful Information in I02)
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)
Code to identify the type of information in the Security Information
- 00
- No Security Information Present (No Meaningful Information in I04)
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)
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
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
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
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
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
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
A control number assigned by the interchange sender
Code sent by the sender to request an interchange acknowledgment (TA1)
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code to indicate whether data enclosed by this interchange envelope is test, production or information
- I
- Information
- P
- Production Data
- T
- Test Data
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
To indicate the beginning of a functional group and to provide control information
Code identifying a group of application related transaction sets
- SH
- Ship Notice/Manifest (856)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission. Codes agreed to by trading partners
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)
Assigned number originated and maintained by the sender
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
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
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
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).
- 856
- Ship Notice/Manifest
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment for Ship Notice
To transmit identifying numbers, dates, and other basic data relating to the transaction set
BSN00281982200907311245*0001
A unique control number assigned by the original shipper to identify a specific shipment
Date expressed as CCYYMMDD
- BSN03 is the date the shipment transaction set is created.
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)
- BSN04 is the time the shipment transaction set is created.
Code indicating the hierarchical application structure of a transaction set that utilizes the HL segment to define the structure of the transaction set
- 0001
- Shipment, Order, Packaging, Item
Detail
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- S
- Shipment
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Carrier Details (Quantity and Weight)
To specify the transportation details relative to commodity, weight, and quantity
TD1CTN251235*G24504*LB3750CF
Code identifying the type of packaging; Part 1: Packaging Form, Part 2: Packaging Material; if the Data Element is used, then Part 1 is always required
- CTN25
- Corrugated carton
Number of units (pieces) of the lading commodity
Number of cartons in shipment
Numeric value of weight
Gross weight of entire shipment
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- KG
- Kilogram
- LB
- Pound
Value of volumetric measure
Gross volume of entire shipment
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- CF
- Cubic Feet
- CM
- Cubic Meters
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
A valid SCAC is REQUIRED in TD503. If the correct SCAC is unknown, please contact Shoe Carnival’s EDI Department for direction before sending the 856. A list of valid SCACs can be provided.
TD507 and 08 are not required for regular Landed orders.
TD510 and 11 are not required if an estimated arrival date is given in a DTM*067 segment.
Example TD5
TD5*2AVRTMAVERITT EXPRESS***CD5
Code designating the system/method of code structure used for Identification Code (67)
- When specifying a routing sequence to be used for the shipment movement in lieu of specifying each carrier within the movement, use TD502 to identify the party responsible for defining the routing sequence, and use TD503 to identify the actual routing sequence, specified by the party identified in TD502.
- 2
- Standard Carrier Alpha Code (SCAC)
Code identifying a party or other code
SCAC
Code specifying the method or type of transportation for the shipment
- A
- Air
- C
- Consolidation
- M
- Motor (Common Carrier)
- R
- Rail
- S
- Ocean
- U
- Private Parcel Service
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
Free-form carrier name
Code identifying type of location
- PA
- Port of Arrival
- PE
- Port of Entry
Code which identifies a specific location
U.S. Customs Port Code or Free-form Port name
Code specifying the value of time used to measure the transit time
- CD
- Calendar Days (Includes weekends and Holidays)
The numeric amount of transit time
Number of calendar days between shipping date listed in DTM and estimated arrival date at Shoe Carnival
Carrier Details (Equipment)
To specify transportation details relating to the equipment used by the carrier
If a seal number is available, it should be included in the TD309 element.
Example TD3
TD3TL534907***2572610
Code identifying type of equipment used for shipment
- CN
- Container
- TL
- Trailer (not otherwise specified)
Domestic Trailer
Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)
Trailer Number or Container Number
Bill of Lading Number
To specify identifying information
REFBM06604180002491555
Code qualifying the Reference Identification
- BM
- Bill of Lading Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Carrier's Reference Number (PRO/Invoice)
To specify identifying information
This REF segment is optional for Direct Shipments, but mandatory for all others
When an order is a drop-shipment order, the carrier’s tracking number should be in REF02.
Example REF
REFCN1532628462
Code qualifying the Reference Identification
- CN
- Carrier's Reference Number (PRO/Invoice)
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Current Schedule Delivery
To specify pertinent dates and times
This additional DTM segment is required for Direct Shipments, and is required for regular Landed orders if the TD510 and 11 elements do not pass an estimated number of transit days
The estimated arrival date is only required in this DTM segment if a number of transit days is not provided in the TD511 element in the shipping level.
Example DTM
DTM06720100614
Shipped
To specify pertinent dates and times
DTM01120100521
F.O.B. Related Instructions
To specify transportation instructions relating to shipment
Drop-shipments should be Prepaid; Direct Shipments should be Mixed; all other shipments are on a Collect basis.
Example FOB
FOB*CC
Code identifying payment terms for transportation charges
- FOB01 indicates which party will pay the carrier.
- CC
- Collect
- MX
- Mixed
- PP
- Prepaid (by Seller)
Name
To identify a party by type of organization, name, and code
N1SFVendor Name92Vendor_Code – the code in N104 can be agreed upon…
N1SF**91Company Name - …or just be the free-form name of the Vendor
N1SF**1
Code identifying an organizational entity, a physical location, property or an individual
- SF
- Ship From
Code designating the system/method of code structure used for Identification Code (67)
- 1
- D-U-N-S Number, Dun & Bradstreet
- 91
- Assigned by Seller or Seller's Agent
- 92
- Assigned by Buyer or Buyer's Agent
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.
Ship from Code
Geographic Location
To specify the geographic place of the named party
Shoe Carnival would prefer to only receive the five-digit zipcode in N403 and not the ZIP+4 format.
The country of origin is required in N404 for first cost orders and direct shipments, but no landed orders if they are shipped from a U.S. address.
Example N4
N4ANYTOWNCA*90210
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
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.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Name
To identify a party by type of organization, name, and code
N1STShoe Carnival Distribution Center92098
N1ST**9298 – this version is more common and perfectly acceptable
Code identifying an organizational entity, a physical location, property or an individual
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
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.
Ship to Location
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- O
- Order
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Purchase Order Reference
To provide reference to a specific purchase order
PRF*859950
Identifying number for Purchase Order assigned by the orderer/purchaser
Carrier Details (Quantity and Weight)
To specify the transportation details relative to commodity, weight, and quantity
TD1CTN257***G27.56*LB
Code identifying the type of packaging; Part 1: Packaging Form, Part 2: Packaging Material; if the Data Element is used, then Part 1 is always required
- CTN25
- Corrugated Carton
Number of units (pieces) of the lading commodity
Number of cartons in order level
Numeric value of weight
Gross weight of entire order
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- KG
- Kilogram
- LB
- Pound
Value of volumetric measure
Gross volume of entire order
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- CF
- Cubic Feet
- CM
- Cubic Meters
Reference Identification
To specify identifying information
Providing the invoice number on the 856 is not mandatory. If the invoice number is known at the time the 856 is sent, its inclusion here would be appreciated.
Example REF
REFIV938937
Code qualifying the Reference Identification
- IV
- Seller's Invoice Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Seller Invoice Number
Name
To identify a party by type of organization, name, and code
Shoe Carnival prefers the use of the “BY” qualifier but can accept either “BY” or “Z7”.
Example N1
N1BY**9298
Code identifying an organizational entity, a physical location, property or an individual
- BY
- Buying Party (Purchaser)
- Z7
- Mark-for Party
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
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.
Destination Store Number
Mark for Store Location
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- P
- Pack
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
The PO4 segment is not yet mandatory, but it should be implemented soon. When the PO4 segment is utilized in the Pack Level, all listed elements become Mandatory.
Example PO4
PO412*****46.5LB*23.512*14.25IN
The number of inner containers, or number of eaches if there are no inner containers, per outer container
Number of units in carton
Numeric value of gross weight per pack
Gross weight of carton
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- KG
- Kilogram
- LB
- Pound
Largest horizontal dimension of an object measured when the object is in the upright position
Shorter measurement of the two horizontal dimensions measured with the object in the upright position
Vertical dimension of an object measured when the object is in the upright position
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- PO413 defines the unit of measure for PO410, PO411, and PO412.
- CM
- Centimeter
- IN
- Inch
- MR
- Meter
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
MANGM00009999999000000011
Code specifying the application or source of Marks and Numbers (87)
- MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the same physical container.
- When MAN01 contains code "UC" (U.P.C. Shipping Container Code) and MAN05/MAN06 contain a range of ID numbers, MAN03 is not used. The reason for this is that the U.P.C. Shipping Container code is the same on every carton that is represented in the range in MAN05/MAN06.
- GM
- SSCC-18 and Application Identifier
Marks and numbers used to identify a shipment or parts of a shipment
- When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 is the ending number of that range.
UCC/EAN/GS1-128 Serial Shipping Container Code
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- I
- Item
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
Item Identification
To specify basic item identification data
This segment is used with the SN1 segment to describe a “solid” case and can be used in part to describe a “casepack”. The conditionality of the LIN elements become mandatory if the SN1 segment is used.
Example LIN
LIN*UP999999350836
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
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.
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
UPC
Item Detail (Shipment)
To specify line-item detail relative to shipment
This segment is used with the LIN segment to describe a “solid” case and can be used in part to describe a “casepack”. The conditionality of the SN1 elements become mandatory if the LIN segment is used.
Example SN1
SN16*EA - Item-level
SN1202*CA - Pack-level
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
Number of units contained in this carton with the UPC listed in previous LIN segment
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- SN103 defines the unit of measurement for both SN102 and SN104.
- AS
- Assortment
Pack-level
- CA
- Case
Pack-level
- EA
- Each
Item-level
- PR
- Pair
Item-level
Subline Item Detail
To specify product subline detail item data
If the SLN segments are used to communicate a casepack carton, then all conditional elements become mandatory; If PrePack UPC is used in LIN03, then SLN segments are not required
Example SLNs
SLN1.01**I2EA8.9*UP999999350836 – example of a single SLN segment
SLN*1.01I1EA*UP883668350874 – example of a 6-pair casepack described with SLN segments
SLN*1.02I2EA*UP883668350898
SLN*1.03I2EA*UP883668350911
SLN*1.04I1EA**UP883668350928
Alphanumeric characters assigned for differentiation within a transaction set
- SLN01 is the identifying number for the subline item.
- SLN01 is related to (but not necessarily equivalent to) the baseline item number. Example: 1.1 or 1A might be used as a subline number to relate to baseline number 1.
Code indicating the relationship between entities
- SLN03 is the configuration code indicating the relationship of the subline item to the baseline item.
- I
- Included
Numeric value of quantity
Quantity of this item, in this case
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
Price per unit of product, service, commodity, etc.
This is the price at which Shoe Carnival dictates each pair of shoes in the casepack be marked.
The selling price is sent with a decimal point only when needed, i.e., $15.95 would be “15.95” and $29.00 would be “29”.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SLN09 through SLN28 provide for ten different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
UPC
Summary
Transaction Totals
To transmit a hash total for a specific element in the transaction set
- Number of line items (CTT01) is the accumulation of the number of HL segments.
If used, hash total (CTT02) is the sum of the value of units shipped (SN102) for each SN1 segment.
CTT*20
Total number of line items in the transaction set
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Total number of segments included in a transaction set including ST and SE segments
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Assigned number originated and maintained by the sender
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Bulk Landed Order 856
GS*SH*SENDERGS*RECEIVERGS*20231103*024612*000000001*X*004010
ST*856*3001
BSN*00*0015907*20091027*1549*0001
HL*1**S
TD1*CTN25*32****G*820*LB*1176*CF
TD5**2*AVRT*M*AVERITT*****CD*4
TD3*TL**534907******2572610
REF*BM*06604180002491555
REF*CN*1532628462
DTM*011*20091027
FOB*CC
N1*ST**92*98
N1*SF**1*<DUNS #>
N4*ANYTOWN*MN*99999
HL*2*1*O
PRF*600057
TD1*CTN25*32****G*820*LB*1176*CF
REF*IV*938937
N1*BY**92*98
HL*3*2*P
MAN*GM*00012345670006519801
HL*4*3*I
LIN**UP*737973704418
SN1**1*EA
HL*5*3*I
LIN**UP*737973704425
SN1**1*EA
HL*6*3*I
LIN**UP*737973704371
SN1**1*EA
HL*7*3*I
LIN**UP*737973704388
SN1**1*EA
HL*8*3*I
LIN**UP*737973704395
SN1**1*EA
HL*9*3*I
LIN**UP*737973704401
SN1**1*EA
CTT*9
SE*40*3001
GE*1*000000001
IEA*1*000000001
Drop-shipment Order 856 (1)
GS*SH*SENDERGS*RECEIVERGS*20231103*024625*000000001*X*004010
ST*856*0001
BSN*00*600374X3*20101227*0810*0001
HL*1**S
TD1*CTN25*1****G*10*LB
TD5**2*UPSN*M*UPS
REF*BM*600374X3
REF*CN*1Z12345600374
DTM*011*20101101
DTM*067*20101105
FOB*PP
N1*ST**92*363
N1*SF**1*999999999
N4*CITY OF INDUSTRY*CA*91748
HL*2*1*O
PRF*600374
TD1*CTN25*1****G*10*LB
N1*BY**92*363
HL*3*2*P
MAN*GM*00007379740000000018
HL*4*3*I
LIN**UP*737974517097
SN1**3*EA
HL*5*3*I
LIN**UP*737974517134
SN1**6*EA
HL*6*3*I
LIN**UP*737974517158
SN1**3*EA
HL*7*3*I
LIN**UP*737974517172
SN1**6*EA
CTT*7
SE*33*0001
GE*1*000000001
IEA*1*000000001
Drop-shipment Order 856 (2)
GS*SH*SENDERGS*RECEIVERGS*20231103*024635*000000001*X*004010
ST*856*0002
BSN*00*600374X5*20101227*0810*0001
HL*1**S
TD1*CTN25*1****G*10*LB
TD5**2*UPSN*M*UPS
REF*BM*600374X5
REF*CN*1Z12345600375
DTM*011*20101101
DTM*067*20101105
FOB*PP
N1*ST**92*363
N1*SF**1*999999999
N4*CITY OF INDUSTRY*CA*91748
HL*2*1*O
PRF*600374
TD1*CTN25*1****G*10*LB
N1*BY**92*363
HL*3*2*P
MAN*GM*00007379740000000049
HL*4*3*I
SLN*1**I*3*EA*6.25***UP*737974517301
SLN*2**I*4*EA*6.25***UP*737974517325
SLN*3**I*4*EA*6.25***UP*737974517349
SLN*4**I*4*EA*6.25***UP*737974517363
SLN*5**I*3*EA*6.25***UP*737974517387
CTT*4
SE*27*0002
GE*1*000000001
IEA*1*000000001
Store-packed Order 856
GS*SH*SENDERGS*RECEIVERGS*20231103*024647*000000001*X*004010
ST*856*411000006
BSN*00*07379710002739670*20100302*1647*0001
HL*1**S
TD1*CTN25*13****G*151*LB*854*CF
TD5**2*CNWY*M*CONWAY TRANSPORTATION*****CD*3
TD3*TL**534907
REF*BM*07379710002739670
REF*CN*1532628462
DTM*011*20100302
FOB*CC
N1*ST**92*98
N1*SF**91*SHOE VENDOR CO.
N4*ANYTOWN*MO*90210
HL*2*1*O
PRF*600110
TD1*CTN25*3****G*151*LB
REF*IV*235596
N1*BY**92*98
HL*3*2*P
MAN*GM*00007379714921872012
HL*4*3*I
LIN**UP*737972498196
SN1**3*EA
HL*5*3*I
LIN**UP*017113596337
SN1**2*EA
HL*6*3*I
LIN**UP*737972498233
SN1**2*EA
HL*7*2*P
MAN*GM*00007379714921872029
HL*8*7*I
LIN**UP*737972498233
SN1**4*EA
HL*9*7*I
LIN**UP*737972498318
SN1**1*EA
HL*10*7*I
LIN**UP*737972498271
SN1**5*EA
HL*11*7*I
LIN**UP*737972498356
SN1**1*EA
HL*12*2*P
MAN*GM*00007379714921872036
HL*13*12*I
LIN**UP*737973596375
SN1**8*EA
HL*14*12*I
LIN**UP*737973596290
SN1**4*EA
HL*15*1*O
PRF*600110
TD1*CTN25*3****G*151*LB
N1*BY**92*03
HL*16*15*P
MAN*GM*00007379714921873019
HL*17*16*I
LIN**UP*737972498196
SN1**3*EA
HL*18*16*I
LIN**UP*737973596375
SN1**5*EA
HL*19*16*I
LIN**UP*737973596290
SN1**3*EA
HL*20*15*P
MAN*GM*00007379714921873026
HL*21*20*I
LIN**UP*737972498318
SN1**2*EA
HL*22*20*I
LIN**UP*737973596337
SN1**7*EA
HL*23*20*I
LIN**UP*737972498356
SN1**1*EA
HL*24*20*I
LIN**UP*737972498271
SN1**1*EA
HL*25*15*P
MAN*GM*00007379714921873033
HL*26*25*I
LIN**UP*737972498233
SN1**5*EA
HL*27*25*I
LIN**UP*737972498271
SN1**7*EA
HL*28*1*O
PRF*600110
TD1*CTN25*3****G*151*LB
N1*BY**92*34
HL*29*28*P
MAN*GM*00007379714921874016
HL*30*29*I
LIN**UP*737972498196
SN1**4*EA
HL*31*29*I
LIN**UP*737973596290
SN1**3*EA
HL*32*29*I
LIN**UP*737972498356
SN1**3*EA
HL*33*28*P
MAN*GM*00007379714921874023
HL*34*33*I
LIN**UP*737972498233
SN1**6*EA
HL*35*33*I
LIN**UP*737973596337
SN1**2*EA
HL*36*33*I
LIN**UP*737972498271
SN1**4*EA
HL*37*28*P
MAN*GM*00007379714921874030
HL*38*37*I
LIN**UP*737972498271
SN1**4*EA
HL*39*37*I
LIN**UP*737973596290
SN1**4*EA
HL*40*37*I
LIN**UP*737972498318
SN1**2*EA
HL*41*37*I
LIN**UP*737973596375
SN1**1*EA
HL*42*1*O
PRF*600110
TD1*CTN25*4****G*151*LB
N1*BY**92*363
HL*43*42*P
MAN*GM*00007379714921876010
HL*44*43*I
LIN**UP*737972498196
SN1**3*EA
HL*45*43*I
LIN**UP*737973596337
SN1**7*EA
HL*46*42*P
MAN*GM*00007379714921876027
HL*47*46*I
LIN**UP*737972498233
SN1**7*EA
HL*48*46*I
LIN**UP*737973596290
SN1**4*EA
HL*49*42*P
MAN*GM*00007379714921876034
HL*50*49*I
LIN**UP*737972498271
SN1**8*EA
HL*51*49*I
LIN**UP*737973596337
SN1**2*EA
HL*52*42*P
MAN*GM*00007379714921876041
HL*53*52*I
LIN**UP*737973596375
SN1**3*EA
HL*54*52*I
LIN**UP*737972498318
SN1**2*EA
HL*55*52*I
LIN**UP*737972498356
SN1**7*EA
CTT*55
SE*169*411000006
GE*1*000000001
IEA*1*000000001
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.