X12 856 Ship Notice/Manifest
This X12 Transaction Set 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
- ^ Repetition
- None included
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code identifying 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 identifying 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)
Code indicating 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
Code indicating 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
Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator
- ^
- Repetition Separator
Code specifying the version number of the interchange control segments
- 00501
- Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
A control number assigned by the interchange sender
Code indicating sender's request for an interchange acknowledgment
- 0
- No Interchange Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested (TA1)
Code indicating 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
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
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 identifying the issuer of the standard; this code is used in conjunction with Data Element 480
- 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
- 005010
- Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
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) is 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
Code identifying purpose of transaction set
- 00
- Original
- 01
- Cancellation
- 06
- Confirmation
A unique control number assigned by the original shipper to identify a specific shipment
Unique Shipment ID Number
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
- BSN03 is the date the shipment transaction set is created.
ASN create 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)
- BSN04 is the time the shipment transaction set is created.
ASN create time
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
Carrier Details (Quantity and Weight)
To specify the transportation details relative to commodity, weight, and quantity
If more than one packing medium is included, the TD1 group should be repeated with a lading quantity (TD102) for each packing medium.
- At least one iteration of TD1, with TD101 and TD102 is required.
- At least one iteration of TD1, with TD106, TD107 and TD108 is required
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
Valid codes are:
CTN (Carton)
CTN25 (Corrugated Carton)
PLT (Pallet)
PLT94 (Wood Pallet)
- CTN
- Carton
- PLT
- Pallet
- 25
- Corrugated or Solid
- 94
- Wood
Number of units (pieces) of the lading commodity
Code defining the type of weight
- G
- Gross Weight
- N
- Actual Net Weight
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- KG
- Kilogram
- LB
- Pound
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
One of either SCAC (TD503) or Carrier Routing (TD505) must be present.
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
Min/ Max = 2/4
Code specifying the method or type of transportation for the shipment
- A
- Air
- LT
- Less Than Trailer Load (LTL)
- M
- Motor (Common Carrier)
- O
- Containerized Ocean
- R
- Rail
- T
- Best Way (Shippers Option)
- U
- Private Parcel Service
- VE
- Vessel, Ocean
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
Carrier Routing / Name
Code indicating the level of transportation service or the billing service offered by the transportation carrier
- 3D
- Three Day Service
- CG
- Ground
- CX
- Express Service
Applicable for LTL shipment
- DC
- Delivery Confirmation
- ET
- Proof of Delivery (POD) with Signature
- FC
- First Class
- G2
- Standard Service
Applicable for LTL shipments
- IE
- Expedited Service - Worldwide
- IX
- Express Service - Worldwide
- ND
- Next Day Air
- ON
- Overnight
- PB
- Priority Mail
- PI
- Priority Mail Insured
- SA
- Same Day
- SC
- Second Day Air
- SE
- Second Day
- SG
- Standard Ground
Carrier Details (Equipment)
To specify transportation details relating to the equipment used by the carrier
Prefix or alphabetic part of an equipment unit's identifying number
Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)
Reference Information
To specify identifying information
- One of Bill of lading (BM) or Carrier Pro numbers (CN) are required for Truck Load and Less than Truck Load Shipments (Common Carrier moves) (not both). Import shipments require an Ocean Container Number (OC).
- For Parcel carrier Shipments, the Pick up/Tracking number (21) or Carrier Assigned Package number (CN) is required. Do not send both. (If there is no pick up number use one of the carrier assigned carton numbers for this field).
- When shipping via WSI the WSI assigned Bill Of Lading number must be sent in REF02 (REF01 = BM) and formatted as 'RT' + ten numeric characters.
- If the order was shipped on a Williams Sonoma account number, that account number must be included inREF02, with REF01 of GK.
If available the vessel name should be sent in REF03, with REF01 of WU.
Note: If this is a flow through order, with the final mile designated as parcel, the master tracking number must be provided as well as the file mile parcel tracking number.
Code qualifying the Reference Identification
- 2I
- Tracking Number
- 87
- Functional Category
Used to advise the Purchase Order Category ('INT' for international and 'DOM' for domestic). 850 value must be returned.
- BM
- Bill of Lading Number
- CN
- Carrier's Reference Number (PRO/Invoice)
- GK
- Third Party Reference Number
- OC
- Ocean Container Number
- WU
- Vessel
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Code identifying the major duty or responsibility of the person or group named
- IC
- Information 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
Estimated Delivery
To specify pertinent dates and times
Shipped
To specify pertinent dates and times
F.O.B. Related Instructions
To specify transportation instructions relating to shipment
Code identifying payment terms for transportation charges
- FOB01 indicates which party will pay the carrier.
- CC
- Collect
- DF
- Defined by Buyer and Seller
- PP
- Prepaid (by Seller)
Code identifying type of location
- FOB02 is the code specifying transportation responsibility location.
- DE
- Destination (Shipping)
- OR
- Origin (Shipping Point)
A free-form description to clarify the related data elements and their content
Code identifying type of location
- FOB06 is the code specifying the title passage location.
- DE
- Destination (Shipping)
- OR
- Origin (Shipping Point)
A free-form description to clarify the related data elements and their content
Party Identification
To identify a party by type of organization, name, and code
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)
- 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.
Party Location
To specify the location of the named party
Required on direct to consumer shipments when BSN01 = 06.
Geographic Location
To specify the geographic place of the named party
Required on Direct to Consumer shipments, when BSN01 = 06
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)
Party Identification
To identify a party by type of organization, name, and code
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.
The Williams Sonoma Ship To (N101 = ST) location number must be included in the N104 field for all Stand Alone, Flow and Direct Ship orders (BSN01 = 00) as well as all Flow Through orders (BSN01 = 06, but with an end consumer buying party)
Party Location
To specify the location of the named party
Required on direct to consumer shipments when BSN01 = 06.
Geographic Location
To specify the geographic place of the named party
Required on Direct to Consumer shipments, when BSN01 = 06
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)
Vessel Identification
To provide vessel details and voyage number
Name of ship as documented in "Lloyd's Register of Ships"
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
Purchase Order Reference
To provide reference to a specific purchase order
Identifying number for Purchase Order assigned by the orderer/purchaser
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
- PRF04 is the date assigned by the purchaser to purchase order.
Reference Information
To specify identifying information
Code qualifying the Reference Identification
- CO
- Customer Order Number
Required if present on the Purchase Order
- IA
- Internal Vendor Number
Williams Sonoma assigned Vendor ID - Mandatory
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Party Identification
To identify a party by type of organization, name, and code
This is the end consumers address to be included on the GS1-128 label when present on the order..
Party Location
To specify the location of the named party
Geographic Location
To specify the geographic place of the named party
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)
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
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
Numeric value of gross weight per pack
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- KG
- Kilogram
- LB
- Pound
Marks and Numbers Information
To indicate identifying marks and numbers for shipping containers
- If shipping to a Williams Sonoma facility the barcode sequence number from the shipping label must be included in the MAN02, with MAN01 = GM.
- Parcel tracking numbers must be included in MAN02 with MAN01 = CP
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.
- CP
- Carrier-Assigned Package ID Number
- GM
- EAN.UCC Serial Shipping Container Code (SSCC) 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.
When MAN01 = GM, MAN02 must be a 20 character GS1 shipping barcode label sequence
See the barcode label designs for additional information on label formats.
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
Item Identification
To specify basic item identification data
If Bundle and Component items are included on the Purchase Order, only the component items should be returned on the ASN
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
The line sequence number from the Purchase Order must be returned on the ASN.
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.
- SK
- Stock Keeping Unit (SKU)
Williams Sonoma assigned SKU
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- UK
- GTIN 14-digit Data Structure
- UP
- UCC - 12
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- UK
- GTIN 14-digit Data Structure
- UP
- UCC - 12
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- UK
- GTIN 14-digit Data Structure
- UP
- UCC - 12
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
Item Detail (Shipment)
To specify line-item detail relative to shipment
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
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.
- EA
- Each
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
The number of eaches per inner container
Inner Pack Value
Product/Item Description
To describe a product or process in coded or free-form format
Code indicating the format of a description
- If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
- F
- Free-form
Code identifying the general class of a product or process characteristic
- 08
- Product
A free-form description to clarify the related data elements and their content
Lot Number
To specify identifying information
This segment is required for products produced that have Lot/batch Numbers associated to them.
Code qualifying the Reference Identification
- LT
- Lot Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Route Number
To specify identifying information
For import orders the REF01 of RU is required. REF02 should be the Ship Via code and REF03 is the WSI assigned UPS Hub Code (both will be on the 850).
Code qualifying the Reference Identification
- RU
- Route Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Date/Time Reference
To specify pertinent dates and times
This segment is required for products produced that have Expiration dates, Production Dates or Shelf Life Dates associated to them
Party Identification
To identify a party by type of organization, name, and code
Geographic Location
To specify the geographic place of the named party
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.
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
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.