X12 940 940 Warehouse Shipping Order
This Draft Standard for Trial Use contains the format and establishes the data contents of the Warehouse Shipping Order Transaction Set (940) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to enable the depositor to advise a warehouse to make a shipment, confirm a shipment, or modify or cancel a previously transmitted shipping order.
- ~ 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
- OW
- Warehouse Shipping Order (940)
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).
- 940
- Warehouse Shipping Order
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Shipping Order Identification
To transmit identifying numbers and other basic data for this transaction set
Code identifying purpose of transaction set
- N
- Original
Identifying number for warehouse shipping order assigned by the depositor
Seller’s Assigned Order Number
Identifying number for Purchase Order assigned by the orderer/purchaser
Retailer’s Original Purchase Order Number
A two-part number in the form "SSSTTT" where "SSS" is a sequentially assigned number and "TTT" equals the highest sequential number being used within the associated (linked) group (Leading zeros are required for both "SSS" and "TTT")
Not used, hard coded to ‘111111’ to satisfy standard requirements.
Reference number assigned by the sender to relate a transaction set to a master transaction (When associating a group of purchase orders, invoices or other transaction sets, use the master reference (link) number to identify the group and the link sequence number to identify individual transaction sets within the group)
Seller’s Assigned Pick Ticket Number
Code specifying the type of transaction
- WO
- Work Order
Name
To identify a party by type of organization, name, and code
At least 1 N1 segment/loop will be sent per transaction set to denote the ship to location (N101 = ‘ST’).
For B2C orders: A 2nd N1 segment (N101 = ‘BT’) can also be sent to denote the bill-to party for printing purposes.
For B2b/retail orders: If the shipment is a cross dock (i.e. ship to one location but mark for a different location) then an additional N1 segment (N101 = ‘Z7’) will be sent to denote the mark for location. An additional N1 segment (N101 = ‘SF’) can be transmitted for display purposes on printed material and for possible differentiation between divisions.
Code identifying an organizational entity, a physical location, property or an individual
- BT
- Bill-to-Party
- SF
- Ship From
- Z7
- Mark-for Party
Code designating the system/method of code structure used for Identification Code (67)
- 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.
This is the location code as defined by N101. The source of the code is defined by N103. For N101 = ’Z7’ & N101 = ‘ST’, N103 will normally equal ‘92’. If N101 = ‘SF’, N103 & N104 are optional.
THE VALUE TRANSMITTED IN THIS FIELD MUST BE SENT BACK ON THE 945
Additional Name Information
To specify additional names or those longer than 35 characters in length
This segment will be used to transmit the additional location codes and (if applicable) names to be used for printed material (labels, forms, packing slips, etc) for the location identified in the parent N1 segment.
Free-form name
This is the location code to be printed on related documentation as defined by N101.
THE VALUE TRANSMITTED IN THIS FIELD IS NOT REQUIRED
BACK…NOR WILL THIS SEGMENT BE USED IF THE N101=’SF’.
Free-form name
This field is used to pass secondary or additional name values (usually referred to as DBA names) for the location qualified in N101 of the parent N1 segment.
Address Information
To specify the location of the named party
Address information will be sent primarily for printing purposes but can also be used to update your customer’s location reference tables as needed in relation to the codes transmitted in the corresponding N104 element.
Up-to 4 address lines (2 sets of N301 and N302) can be sent per 940.
Geographic Location
To specify the geographic place of the named party
City, State, Zip & Country will be sent primarily for printing purposes but can also be used to update your customer’s location reference tables as needed in relation to the codes transmitted in the corresponding N104 element.
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)
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
When possible CGS will transmit the information about the primary contact of each location specified in the corresponding N1 segment. PER03/04 will always be populated if the PER segment is sent. In situations where both phone and email are available PER05/06 will also be sent.
Code identifying the major duty or responsibility of the person or group named
- CN
- General Contact
Code identifying the type of communication number
- EM
- Electronic Mail
- TE
- Telephone
Complete communications number including country or area code when applicable
Code identifying the type of communication number
- EM
- Electronic Mail
- TE
- Telephone
Complete communications number including country or area code when applicable
Name
To identify a party by type of organization, name, and code
At least 1 N1 segment/loop will be sent per transaction set to denote the ship to location (N101 = ‘ST’).
For B2C orders: A 2nd N1 segment (N101 = ‘BT’) can also be sent to denote the bill-to party for printing purposes.
For B2b/retail orders: If the shipment is a cross dock (i.e. ship to one location but mark for a different location) then an additional N1 segment (N101 = ‘Z7’) will be sent to denote the mark for location. An additional N1 segment (N101 = ‘SF’) can be transmitted for display purposes on printed material and for possible differentiation between divisions.
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)
- 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.
This is the location code as defined by N101. The source of the code is defined by N103. For N101 = ’Z7’ & N101 = ‘ST’, N103 will normally equal ‘92’.
THE VALUE TRANSMITTED IN THIS FIELD MUST BE SENT BACK ON THE 945
Additional Name Information
To specify additional names or those longer than 35 characters in length
This segment will be used to transmit the additional location codes and (if applicable) names to be used for printed material (labels, forms, packing slips, etc) for the location identified in the parent N1 segment.
Free-form name
This is the location code to be printed on related documentation as defined by N101.
THE VALUE TRANSMITTED IN THIS FIELD IS NOT REQUIRED
BACK…NOR WILL THIS SEGMENT BE USED IF THE N101=’SF’.
Free-form name
This field is used to pass secondary or additional name values (usually referred to as DBA names) for the location qualified in N101 of the parent N1 segment.
Address Information
To specify the location of the named party
Address information will be sent primarily for printing purposes but can also be used to update your customer’s location reference tables as needed in relation to the codes transmitted in the corresponding N104 element.
Up-to 4 address lines (2 sets of N301 and N302) can be sent per 940.
Geographic Location
To specify the geographic place of the named party
City, State, Zip & Country will be sent primarily for printing purposes but can also be used to update your customer’s location reference tables as needed in relation to the codes transmitted in the corresponding N104 element.
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)
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
When possible CGS will transmit the information about the primary contact of each location specified in the corresponding N1 segment. PER03/04 will always be populated if the PER segment is sent. In situations where both phone and email are available PER05/06 will also be sent.
Code identifying the major duty or responsibility of the person or group named
- CN
- General Contact
Code identifying the type of communication number
- EM
- Electronic Mail
- TE
- Telephone
Complete communications number including country or area code when applicable
Code identifying the type of communication number
- EM
- Electronic Mail
- TE
- Telephone
Complete communications number including country or area code when applicable
Reference Identification
To transmit identifying information as specified by the Reference Identification Qualifier
Reference numbers will be transmitted based on previous agreements between seller and shipping facility. Items transmitted must be utilized either in print or as part of picking/shipping process. BC Customer Number will always be sent.
Code qualifying the Reference Identification
- 3P
- 3
- CU
- BC Customer Number
- DP
- Department Number
- DV
- Division Number
- IA
- Supplier Number
- OT
- BC Order Type
- SC
- Shipper/Carrier/Service Code
- TM
- Order Terms (Sender)
- TR
- Shipment Terms Code (Sender)
- UD1
- User Defined 1
- UD2
- User Defined 2
- UD3
- User Defined 3
- VAT
- VAT Number
- WV
- Dealer Identification
- rd
- Party Account Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
When N901=TM, the value sent in this element will be the BC terms code, the BC terms description will then be sent in the N903 element.
Free-form descriptive text
Department Description if N901=’DP’, Terms Description if N901=’TM’.
Date/Time
To specify pertinent dates and times
Up to 4 G62 segments can be sent to denote original PO date, requested ship date, cancel after date and/or must arrive by date. At least one G62 segment will always be sent.
NOTE: Time can also be sent if available (currently only when G6201 = ‘04’). If time is sent then G6203, G6204 and G6205 will all be sent.
Code specifying type of date
- 01
- Cancel After This Date
- 04
- Original PO date
- 10
- Requested Ship Date/Pick-up Date
- 67
- Must Arrive By Date
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)
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
- CS
- Central Standard Time
- ES
- Eastern Standard Time
- LT
- Local Time
- MS
- Mountain Standard Time
- PS
- Pacific Standard Time
Note/Special Instruction
To transmit information in a free-form format, if necessary, for comment or special instruction
This segment will be used to transmit various notes/messages/codes from the seller to the 3PL (based on the qualifier in NTE01). Information transmitted must be followed and may need to be printed.
**GIFT MESSAGES: For gift messages, the NTE01 will be ‘GFT’. **
**EDI DATA WARHOUSE:
For instances where extended EDI Data Warehouse functionality is required, NTE01 will be ‘EDI’…multiple NTE segments can be sent with NTE01 = ‘EDI’
When NTE01=’EDI’ the NTE02 value will be formatted as follows:
{segment}.{element}.{qualifier}.{value} (examples: PO1.07.CB.840081X4,
REF.02.DP.0138, DTM.02.011.20130114, TD5.05..UPSN_NG}
**
Code identifying the functional area or purpose for which the note applies
- AMT
- Merchandise Amount
- BOL
- Bill of Lading Number
- BOS
- BC Order Source
- BWV
- BC Wave Number
- CAC
- Relationship Information (DBA Name)
- CAT
- Catalog
- CUR
- Currency Code
- CUS
- Customer Type
- DEL
- Shipping/Routing
- EDI
- EDI Data Warehouse
- GFT
- Gift Message
- LOI
- Load ID
- MBO
- Manifest (Master Bill of Lading)
- MRT
- EDI PO Type
- OS
- PDN
- Promotion /Deal Number
- PHC
- Ship Mod
- PKG
- Packaging
- PRO
- Carrier PRO Number
- REF
- Secondary PO/Reference Number
- SPH
- Special Handling
- SPS
- BC SPS Billing Code
- STT
- Store Type (Sender)
- TC
- TC Number
- WHI
- Warehouse Instructions
- ZZZ
- Mutually Defined Reference Number
A free-form description to clarify the related data elements and their content
Warehouse Carrier Information
To specify transportation instructions relating to shipment
This segment will be used to transmit the requested ship method and/or the specific shipper to be used when shipping items from this transaction. W6601 & W6602 will always be transmitted. W6603 will not be transmitted if W6602 = ‘T’.
The shipment payment method will be transmitted to alert qualified shipping facilities to which party will pay for freight charges.
Code identifying payment terms for transportation charges
- 3P
- Third Party
- CC
- Collect
- PP
- Prepaid (by Seller)
Code specifying the method or type of transportation for the shipment
- A
- Air
- AE
- Air Express
- CE
- Customer Pickup
- D
- Parcel Post
- E
- Expedited Truck
- LT
- Less Than Trailer Load (LTL)
- M
- Motor
- R
- Rail
- S
- Ocean
- T
- Best Way (Shipping facility Option)
- U
- Private Parcel Service
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
Route Information
To specify carrier and routing sequences and details
This segment will be used to transmit additional routing (sequence) information. If the order is to be shipped in stages then one R2 will be transmitted for each additional router beyond the first (identified in the W66 segment).
R202 will start at a value of ‘1’ for the 1st additional router and increment by 1 for each additional router.
FOR FUTURE USE
Code describing the relationship of a carrier to a specific shipment movement
Code specifying the method or type of transportation for the shipment
- A
- Air
- AE
- Air Express
- CE
- Customer Pickup
- D
- Parcel Post
- E
- Expedited Truck
- LT
- Less Than Trailer Load (LTL)
- M
- Motor
- R
- Rail
- S
- Ocean
- T
- Best Way (Shipping facility Option)
- U
- Private Parcel Service
Detail
Assigned Number
To reference a line number in a transaction set
There will be 1 LX loop (used to report the ‘bulk’ breakdown of the entire shipping order) or multiple LX loops (used to report the required content of each container/carton of the order to be shipped). What is actually received will be based on agreements between the shipping facility and seller.
The value of LX01 will start at 1 for each transaction set and then increment by 1 for each container (if any).
Number assigned for differentiation within a transaction set
Line Item Detail - Warehouse
To transmit basic and most frequent shipment-related line-item data elements
The seller’s style number and UPC will always be transmitted. If the W01 segment refers to either a prepack or a component of a prepack then the W0115/W0116 elements will be used to indicate whether the current W01 line is the prepack or a component of that prepack.
Quantity ordered
This is the quantity to be shipped as determined by the seller.
*For prepacks (W0116=’PPK’, the quantity is in eaches!!! To determine the number of prepacks you must divide this quantity by the sum of the units of the components (W0116=’SLN’).
W01180EAUP737411419038VNM11M9200Q***VUPPK~
W01*2EAUP737411479045VNM11M9200Q***VUSLN~
W01*4EAUP737411479097VNM11M9200Q***VUSLN~
W01*6EAUP737411479114VNM11M9200Q***VUSLN~
W01*4EAUP737411479128VNM11M9200Q***VUSLN~
W01*2EAUP737411479136VNM11M9200Q****VUSLN~
The number of prepacks = 180 / (2+4+6+4+2) = 10
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
Universal Product Code (UPC) or EAN Code
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VN
- Seller’s Style Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VU
- Vendor's Basic Unit Number
Identifying number for a product or service
‘SLN’ (means this W01 is a component of a prepack)
‘PPK’ (means this W01 is a prepack…components W01 to follow)
‘OPN’ (means this W01 is a open size/stock…is not a prepack or a component of a prepack)
Line Item Detail - Description
To describe an item in free-form format
Used to transmit the item description, color code and size code. If this segment is used then there will always be 3 segments transmitted.
The 1st G69 segment will contain the product description.
The 2nd G69 segment will contain the size description.
The 3rd G69 segment will contain the color code.
The 4th G69 segment will contain the color name.
Free-form descriptive text
Product description (1st occurrence)
Size description (2nd occurrence)
Color code (3rd occurrence)
Color name (4th occurrence)
Reference Identification
To transmit identifying information as specified by the Reference Identification Qualifier
This segment will be used to transmit additional item information.
*NOTE: If label code is transmitted in the 940 it MUST be sent back in the 945.
Code qualifying the Reference Identification
- 79
- BC Price
- AQ
- BC Assortment Quantity
- AS
- BC Assortment Number
- AX
- BC Auxiliary SKU
- BM
- NRF Color Code
- CB
- Buyer’s SKU
- DM
- BC Dimension Code
- EN
- EAN Number
- GF
- BC Gift Box Style
- LB
- BC Label Code
- PI
- BC Net Price
- PV
- BC order line number
- SB
- BC Size Bucket
- SM
- NRF Size Code
- SR
- BC Size Range
- SZ
- BC Size Code
- VC
- BC Color Code
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Reference Identification Special Charge or Allowance Code
To transmit identifying information as specified by the Reference Identification Qualifier
This segment will be used to transmit charges information related to the item represented in the parent W01 element.
*NOTE: LIMITED USE: This occurrence of the N9 segment is for restricted/limited use. Do NOT use unless otherwise instructed to do so by the originator of this transaction!
Code qualifying the Reference Identification
- 22
- Special Charge or Allowance Code
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
BC Charge Type Code
Free-form descriptive text
BC Charge Amount (Numeric value)
Note/Special Instruction
To transmit information in a free-form format, if necessary, for comment or special instruction
This segment will be used to transmit various notes/messages from the seller to the 3PL (based on the qualifier in NTE01). Information transmitted must be followed and may need to be printed.
**EDI DATA WARHOUSE:
For instances where extended EDI Data Warehouse functionality is required, NTE01 will be ‘EDI’…multiple NTE segments can be sent with NTE01 = ‘EDI’.
When NTE01=’EDI’ the NTE02 value will be formatted as follows:
{segment}.{element}.{qualifier}.{value} (examples: PO1.07.CB.840081X4,
REF.02.DP.0138, DTM.02.011.20130114, TD5.05..UPSN_NG}
**
Code identifying the functional area or purpose for which the note applies
- CAT
- Catalog
- DEL
- Shipping/Routing
- EDI
- EDI Data Warehouse
- GFT
- Gift Message
- PKG
- Packaging
- SPH
- Special Handling
- WHI
- Warehouse Instructions
A free-form description to clarify the related data elements and their content
Line-Item Detail - Miscellaneous
To specify packing details of the items shipped
This segment will be sent specify packing details of the items shipped.
The number of inner containers, or number of eaches if there are no inner containers, per outer container
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
- UN
- Unit
Quantity
To specify quantity information
This segment will be sent to denote the number of gift boxes to apply to the current W01 detail line item. The actual gift box style/type code will be transmitted in the parent W01 segment (in element W0116).
Monetary Amount
To indicate the total monetary amount
The qualifier used in element AMT01 is not part of the X12 version 4010
standards. If this will cause a problem for your system please contact the seller immediately.
Code to qualify amount
- 8P
- Retail Price
- NP
- Net to Pay Total
Monetary amount
The price is sent with a decimal point only when needed, e.g., $15.95 would be sent as "15.95", and $29.00 would be sent as "29".
Summary
Total Shipping Order
To specify summary details of total items shipped in terms of quantity, weight, and volume
Total stock keeping units to be shipped. If the order contains prepacks then each prepack (case) will be considered to be one stock keeping unit.
Quantity ordered
- Quantity ordered (W7601) is a hash total and the unit of measure is not required.
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
Sample Transmission Data (B2B open size order w/ cross-dock)
GS*OW*SENDERGS*RECEIVERGS*20231207*035448*000000001*X*004010~
ST*940*1234~
W05*N*100012*P5152041-02*111111*91003~
N1*ST*WALMART WHSE # 0008*92*0078742000008~
N2*00008*WAL-MART MEGA DC 8~
N3*234 LINCOLN BLVD*DOCK B~
N4*JOHNSON CITY*NM*85830~
N1*Z7*WALMART STORE # 023*92*0078742000023~
N2*00023*WAL-MART LONG ISLAND FM~
N3*31610 ROUTE 110~
N4*FARMINGDALE*NY*11831~
N1*SF*JACK SCHWARTZ SHOES~
N9*DP*240*MENS OUTERWEAR~
N9*IA*3462113~
N9*CU*WALMART~
N9*3P*MVU850017-04~
N9*TM*005*NET 10 EOM + 35~
N9*WV*4810~
N9*SC*RDY~
N9*OT*B2B~
G62*04*20061201*Q*135217*LT~
G62*10*20061210~
G62*01*20061225~
G62*67*20061228~
NTE*PKG*ALL CARTONS MUST HAVE MATCHING UCC-128 CARTON LABEL BEFORE SHIPPING~
NTE*WHI*DO NOT SHORT SHIP~
NTE*OS*BEX~
NTE*EDI*REF.02.DP.0128~
NTE*EDI*DTM.02.036.20061228~
NTE*CUR*USD~
W66*PP*M***ROADWAY*****RDWY~
LX*1~
W01*800*EA**UP*737411458202*VN*W23W9100D~
G69*JACKET – SHORT BOXY~
G69*6 PETITE~
G69*BLACK~
N9*CB*38103K~
N9*LB*WMT1~
N9*VC*BLK~
N9*SZ*6P~
N9*SR*SZEC~
N9*SB*4~
N9*PV*1~
N9*79*14.5~
NTE*EDI*PO1.07.IN.02884001X54~
NTE*EDI*PID.05.08.SHORT BOXY JACKET (6P)~
AMT*8P*32.25~
LX*2~
W01*900*EA**UP*737411419021*VN*M11M9100P~
G69*JACKET – SHORT BOXY~
G69*8 PETITE~
G69*BLACK~
N9*CB*284381D~
N9*VC*BLK~
N9*SZ*8P~
N9*SR*SZEC~
N9*SB*6~
N9*PV*1~
N9*79*18.25~
NTE*EDI*PO1.07.IN.02884001X62~
NTE*EDI*PID.05.08.SHORT BOXY JACKET (8P)~
AMT*8P*35.75~
W76*1700~
SE*63*1234~
GE*1*000000001~
IEA*1*000000001~
Sample Transmission Data (B2C gift order)
GS*OW*SENDERGS*RECEIVERGS*20231207*035242*000000001*X*004010~
ST*940*1234~
W05*N*100012*P5152041-01*111111*91003~
N1*ST*JOHN SMITH~
N3*123 MAIN STREET*APT 1A~
N4*JOHNSTOWN*NH*05830~
PER*CN**TE*(381)381-3031*EM*JSMITH@YAHOO.COM~
N1*BT*MARTHA JONES~
N3*ROUTE 101*BOX 90~
N4*DOUGLAS*IL*59481~
PER*CN**TE*(912)544-3456*EM*MJONES@YAHOO.COM~
N9*CU*WEBORDER~
N9*TM*002*NET 30~
N9*SC*UP1~
N9*OT*B2B~
G62*04*20061201*Q*124203*LT~
G62*10*20061210~
G62*01*20061225~
G62*67*20061227~
NTE*GFT*DEAR JOHN, HAPPY BIRTHDAY! LOVE GRANDMA~
NTE*OS*BET~
NTE*CUR*USD~
W66*PP*U***UPS GROUND*****UPSG~
LX*1~
W01*2*EA**UP*737411419014*VN*M11M9100P~
G69*JACKET – SHORT BOXY~
G69*LARGE~
G69*BLACK~
G69*DEEP DARK BLACK~
N9*VC*BLK~
N9*SZ*L~
N9*GF*GIFTBOX1~
N9*PV*1~
N9*PI*27.55~
QTY*QU*4~
AMT*8P*99.95~
AMT*NP*199.90~
LX*2~
W01*3*EA**UP*737411419021*VN*M11M9100P~
G69*TIE – WHALE SURF~
G69*ONE SIZE~
G69*BLUE/GREEN~
G69*BLUE OCEAN & DARK FOREST GREEN~
N9*VC*BLG~
N9*SZ*OS~
N9*GF*GIFTBOX4~
N9*PV*3~
N9*PI*7.85~
QTY*QU*1~
AMT*8P*29.95~
W76*4~
SE*51*1234~
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.