Advance Ship Notice - Jobisez LLC

Amazon ASN Specs (ANSI X12 856) Page 1

Advance Ship Notice ANSI X12 856 Version 4010

Author: Amazon.com

Modified: 11/04/2004


Document Overview

The purpose of this document is to provide Amazon’s trading partners with detailed specifications and guidelines for implementing electronic advance shipment notice feeds (856) with Amazon.com. The advance shipment notice (ASN) is a key component to multiple aspects of the Amazon business process. It gives Amazon a view of what you’ve shipped, allows labor to be planned ahead of time based on estimated time of arrival information and what product is shipped. It allows for score carding to be processed on ordered vs. shipped vs. received product information and is key to helping reduce friction in the front end of the supply chain. The 856 is the most widely use and the most diverse of all the EDI ANSI X12 messages used. Amazon’s specifications are compliant with, but not identical to, generally established ANSI X12 standards. The following specs will provide Amazon specific definitions for key data elements and the expected format for the data to be sent in. While Amazon will be implementing data validation rules were applicable, the onus of data integrity will be upon the sending party. Any and all data inaccuracies should be noted and corrected as soon as possible. Please Read and Note the following regarding shipment identification information:

I. Concerning Truckload and Less Than Truckload carriers:

For Truckload and Less than Truckload shipments Amazon.com follows the VICS (http://www.vics.org,

/http://www.vics.org/documents/docs/VICSBOL2004revisions.doc)

standard for Bill of Lading (BOL) and tracking requirements. In appendix C you will find an example of a VICS BOL.

You may use any BOL you wish, but it must confirm the general format of the VICS BOL shown in the appendix

including

o Bill of Lading Number (BOL#) on the top right and clearly marked as a BOL# which is your own internal reference

number for the shipment of goods marked on the paper BOL.

o Carrier Shipment Reference Number (PRO shown in the example) top right clearly marked as a PRO # below your

BOL number which is the carrier’s PRO number, i.e. their internal reference number for identifying the shipment of

goods marked on the paper BOL and what they use to track and report status on the shipment.

o ALL purchase order numbers relevant to the shipment of goods being tendered to the carrier.

For ALL Truckload and Less than Truckload shipments prepaid and collect going from your facility to Amazon.com

your ASN must include ALL of the key reference numbers that reference the shipment off of the paper BOL which

includes:

1. The Bill of Lading Number (BOL#) matched exactly as shown on your paper bill of lading including any leading

or trailing 0s and any dashes or punctuation

2. Carrier Reference Number (PRO# for LTL and TL Carrier’s) matched exactly as shown on your paper bill of

lading including any leading or trailing 0s and any dashes or punctuation

II. Concerning Airfreight Carriers:

For Airfreight (both package and heavy weight) you must include all of the air carriers AIRBILL Numbers, which are the

internal reference numbers for airfreight identifying the shipment(s)

o For most heavyweight air freight each AIRBILL Number represents a separate pallet of freight

o For most package air freight each AIRBILL Number represents separate shipment of each carton/package

III. Concerning Small Package Carriers:

For ALL small package shipments such as UPS you must include the carrier’s tracking number representing separate

shipments of each carton/package.

If you do not provide the appropriate shipment identification numbers relevant to your shipment as described above you will

not be in compliance with Amazon.com ASN business requirements. We must be able to confirm in production testing that you

are able to send these valid identification numbers and you must continue to stay in compliance once in production.

If we can not tie your shipment to the relevant carrier status or shipment appointment request because we do not have

appropriate shipment identification numbers you will be contacted to resolve. If not resolved long term you can be subject to

incur relevant charges in accordance with the loss of visibility and resource time for Amazon.com. Please see the vendor

manual for more information.

http://www.vics.org/


ASN Key Values

The following table defines the key data elements and their Amazon definitions. All qualifiers and other data spec information can be found in the specification section below.

Element Name

Element Description ANSI X12 Location

Mandatory?

Airbill Number

An airbill number is the unique identifier air carriers use to identify a package or pallet. The carrier may use this number to invoice as well. The airbill number is assigned by the carrier to either the package for small parcel shipments or to the pallet for large shipments. The airbill number(s) may be provided in either the Shipment or Package Level ASN. If you choose to report the airbill number at the Shipment level, then one ASN is required per airbill Number. Or vendors may provide each airbill Number in multiple package levels.

REF02, when REF01=CN

CONDITIONAL

Amz DC This field will be a unique ID representing the Amazon FC where this shipment will be delivered.

N104 WHEN N101 = ST

REQUIRED

ASNID This field will be a unique ID which represents this ASN.

BSN02 REQUIRED

ASN Sent Date/Time

This field will be the date/time that the ASN information was pulled from the database. Both date and time are required if more than one ASN file will be submitted per shipment ASN ID.

BSN03/04 REQUIRED/

CONDITIONAL

ASN Type Code describing the message format. BSN05 REQUIRED

BOL

Bill of Lading (BOL) reference number is required for truckload and less than truckload (LTL) shipments. The Amazon.com definition of BOL is defined in reference to truckload and LTL shipments only. BOL reference number is the unique number assigned by the shipper in creating the Bill of Lading. This is a number that identifies a unique shipment. Note: the BOL reference number on the paper BOL should match the reference number provided in this data element.

REF02, where REF01=BM

CONDITIONAL

Carrier SCAC

The Standard Carrier Alpha Code (SCAC) is a unique two-to-four-letter code used to identify a carrier. Carrier SCAC codes are assigned and maintained by the NMFTA (National Motor Freight Association). To obtain a SCAC code or the list of all SCAC codes contact the NMFTA at (703) 838-1868. NMFTA developed the SCAC identification codes in the late 1960's to facilitate computerization in the transportation industry.

TD503 REQUIRED

Carton Count This field will be the total number of cartons making up a shipment.

If TD101 = CTN, TD102

REQUIRED

Freight Terms Code defining whether the shipment is pre-paid or collect.

FOB01 REQUIRED

Load Type This field is used to indicate whether a shipment is TD105 OPTIONAL


floor loaded or not. A value of FLR indicates that the shipment is floor loaded. A value of PLT indicates a shipment of pallets.

Pallet Count This field will be the total number of pallets making up the shipment.

If TD101 = SKD, TD102

OPTIONAL

PO#

This field will contain the Amazon purchase order number. It will be supplied for all Amazon.com Purchase Order numbers relevant to each shipment and that shipment's paper bill of lading (BOL).

PRF01 REQUIRED

PRO#

PRO number is required for truckload and less than truckload (LTL) shipments. The PRO is a unique number assigned by the carrier. It is used to identify and track the shipment that goes out for delivery.

REF02, when REF01=CN

CONDITIONAL

Product ID Amazon systems require either a UPC or ISBN. LIN03 REQUIRED

Purpose Code Code defining whether the ASN is an original, update or replacement.

BSN01; 00 – Original 05 – Replace

REQUIRED

QTY Shipped This field will be the number of units shipped for this item related to this order.

SN102 REQUIRED

Seal# This field will be the container's seal number. REF02, when REF01=SN

OPTIONAL

Shipped Date This field will contain the date/time that the shipment departed.

DTM02 REQUIRED

Shipped From City City for the origins’ warehouse location N401, when the N101 = SF

REQUIRED

Shipped From State/Province

State/Province code for the origins’ warehouse location.

N402, when the N101 = SF

REQUIRED

Shipped From Postal Code

Postal code for the origins’ warehouse location. N403, when the N101 = SF

REQUIRED

Shipped From Country Code

ISO Country code for the origins’ warehouse location.

N404, when the N101 = SF

REQUIRED

SSCC This field will be the UCC-128 code associated with this package.

MAN02 OPTIONAL

Tracking Number

A Tracking Number is the number that small package/parcel carriers (carriers that ship smaller weight shipments usually <250 lb) use to identify each package they are shipping. The Tracking number(s) may be provided in either the Shipment or Package Level ASN. If you choose to report the tracking number at the Shipment level, then one ASN is required per tracking number. Or vendors may provide each tracking number in multiple package levels.

REF02, when REF01=CN CONDITIONAL

Unit Price Price of the product.

SLN06 when SLN07 = 'NET' OPTIONAL

Vendor Code This field will be a unique ID that represents the warehouse where this shipment originated from.

N104 WHEN N101 = SF

REQUIRED

Weight This field will be the gross weight of the shipment. TD107 REQUIRED


856 Ship Notice/Manifest

Functional Group=SH

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.

Not Defined: Pos Id Segment Name Req Max Use Repeat Notes

010 ISA Interchange Control Header M 1

GS Functional Group Header M 1

Heading: Pos Id Segment Name Req Max Use Repeat Notes

010 ST Transaction Set Header M 1

020 BSN Beginning Segment for Ship Notice M 1

Detail: Pos Id Segment Name Req Max Use Repeat Notes

LOOP ID - HL 200000 C2/010L

010 HL Hierarchical Level M 1 C2/010

110 TD1 Carrier Details (Quantity and Weight) M 20

110 TD1 Carrier Details (Quantity and Weight) O 20

120 TD5 Carrier Details (Routing Sequence/Transit Time) M 12

150 REF Bill of Lading C >1

150 REF Pro Number/Tracking ID/Airbill Number C >1

150 REF Seal Number O >1

200 DTM Shipped Date M 10 N2/200

200 DTM Estimated Arrival Date M 10

210 FOB F.O.B. Related Instructions M 1

LOOP ID - N1 200

220 N1 Name M 1

250 N4 Geographic Location M 1

LOOP ID - N1 200

220 N1 Name M 1

LOOP ID - HL 200000 C2/010L


050 PRF Purchase Order Reference M 1

LOOP ID - HL 200000 C2/010L

010 HL Hierarchical Level C 1 C2/010


150 REF Tracking ID/Airbill Number C >1

190 MAN Marks and Numbers C >1

LOOP ID - HL 200000 C2/010L



020 LIN Item Identification M 1

030 SN1 Item Detail (Shipment) M 1

040 SLN Subline Item Detail O 1000

Summary: Pos Id Segment Name Req Max Use Repeat Notes

010 CTT Transaction Totals M 1 N3/010

020 SE Transaction Set Trailer M 1

Not Defined: Pos Id Segment Name Req Max Use Repeat Notes

GE Functional Group Trailer M 1

IEA Interchange Control Trailer M 1

Notes: 2/200

3/010 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.

Comments: 2/010L The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.

2/010 The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.

2/010L The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.







ISA Interchange Control Header Pos: 010 Max: 1

Not Defined - Mandatory

Loop: N/A Elements: 16

Element Summary: Ref Id Element Name Req Type Min/Max Usage

ISA01 I01 Authorization Information Qualifier M ID 2/2 Must use

Code Name

00 No Authorization Information Present (No Meaningful Information in I02)

ISA02 I02 Authorization Information M AN 10/10 Must use

ISA03 I03 Security Information Qualifier M ID 2/2 Must use

Code Name

00 No Security Information Present (No Meaningful Information in I04)

ISA04 I04 Security Information M AN 10/10 Must use

ISA05 I05 Interchange ID Qualifier M ID 2/2 Must use

ISA06 I06 Interchange Sender ID External Information: This field will contain the unique sender ID which represents the message creator.

M AN 15/15 Must use

ISA07 I05 Interchange ID Qualifier M ID 2/2 Must use

Code Name

ZZ Mutually Defined

ISA08 I07 Interchange Receiver ID Formatting Notes: AMAZON

M AN 15/15 Must use

ISA09 I08 Interchange Date External Information: This field will be the date that the EDI message was created.

M DT 6/6 Must use

ISA10 I09 Interchange Time External Information: This field will be the time that the EDI message was created.

M TM 4/4 Must use

ISA11 I10 Interchange Control Standards Identifier All valid standard codes are used.

M ID 1/1 Must use

ISA12 I11 Interchange Control Version Number M ID 5/5 Must use

Code Name

00400 Standard Issued as ANSI X12.5-1997

ISA13 I12 Interchange Control Number External Information: This field will contain a

unique nine digit number representing this EDI transaction.

M N0 9/9 Must use

ISA14 I13 Acknowledgment Requested M ID 1/1 Must use

Code Name

0 No Acknowledgment Requested

ISA15 I14 Usage Indicator M ID 1/1 Must use

Code Name

P Production Data

T Test Data

ISA16 I15 Component Element Separator External Information: This field will contain the

character used to designate the subelement separation.

M AN 1/1 Must use


GS Functional Group Header Pos: Max: 1




GS01 479 Functional Identifier Code M ID 2/2 Must use

Code Name

SH Ship Notice/Manifest (856)

GS02 142 Application Sender's Code External Information: This field will be a code identifying the sender.

M AN 2/15 Must use

GS03 124 Application Receiver's Code Formatting Notes: AMAZON

M AN 2/15 Must use

GS04 373 Date External Information: This field will be the date that the EDI message was created.

M DT 8/8 Must use

GS05 337 Time External Information: This field will be the time that the EDI message was created.

M TM 4/8 Must use

GS06 28 Group Control Number External Information: This field will contain a unique number representing this GS-GE transaction.

M N0 1/9 Must use

GS07 455 Responsible Agency Code M ID 1/2 Must use

Code Name

X Accredited Standards Committee X12

GS08 480 Version / Release / Industry Identifier Code M AN 1/12 Must use

Code Name

004010 Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997

Semantics:

1. GS04 is the group date.

2. GS05 is the group time.

3. The data interchange control number GS06 in this header must be identical to the same data element in the associated functional group trailer, GE02.

Comments:

1. A functional group of related transaction sets, within the scope of X12 standards, consists of a collection of similar transaction sets enclosed by a functional group header and a functional group trailer.


ST Transaction Set Header Pos: 010 Max: 1

Heading - Mandatory



ST01 143 Transaction Set Identifier Code M ID 3/3 Must use

Code Name

856 Ship Notice/Manifest

ST02 329 Transaction Set Control Number External Information: This field will contain a unique number representing this ST-SE transaction.

M AN 4/9 Must use

Semantics:

1. 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).


BSN Beginning Segment for Ship Notice

Pos: 020 Max: 1

Heading - Mandatory



BSN01 353 Transaction Set Purpose Code M ID 2/2 Must use

Code Name

00 Original

05 Replace

BSN02 396 Shipment Identification External Information: This field will be a unique ID which represents this ASN.

M AN 2/30 Must use

BSN03 373 Date External Information: This field will be the date that the ASN information was pulled from the database.

M DT 8/8 Must use

BSN04 337 Time External Information: This field is required if the vendor intends to submit more than one ASN file per shipment ASN ID. note: The format must be reported in hours. minutes and seconds: HHMMSS note: Local time must be converted to either Greenwich Mean Time or Universal Time Coordinates. Formatting Notes: HHMMSS

C TM 4/8 Used

BSN05 1005 Hierarchical Structure Code M ID 4/4 Must use

Code Name

0001 Shipment, Order, Packaging, Item

0003 Shipment, Packaging, Order, Item

0004 Shipment, Order, Item

Semantics:

1. BSN03 is the date the shipment transaction set is created.

2. BSN04 is the time the shipment transaction set is created.

Example: BSN*00*0305140907*20030514**0001 BSN*05*0305140907*20030515**0001

Please note:: If you send an ASN that is meant to replace the original, send the same shipment identification in the BSN02 and a value of 05 in the BSN02.


Loop HL Pos: 010 Repeat: 200000

Mandatory

Loop: HL Elements: N/A

Loop Summary: Pos Id Segment Name Req Max Use Repeat

010 HL Hierarchical Level M 1

110 TD1 Carrier Details (Quantity and Weight) M 20


120 TD5 Carrier Details (Routing Sequence/Transit Time) M 12

150 REF Bill of Lading C >1

150 REF Pro Number/Tracking ID/Airbill Number C >1

150 REF Seal Number O >1

200 DTM Shipped Date M 10

200 DTM Estimated Arrival Date M 10

210 FOB F.O.B. Related Instructions M 1

220 Loop N1 M 200

220 Loop N1 M 200


HL Hierarchical Level Pos: 010 Max: 1

Detail - Mandatory

Loop: HL Elements: 4


HL01 628 Hierarchical ID Number External Information: This will be a unique ID number which sequentially increase with each subsequent HL loop.

M AN 1/12 Must use

HL02 734 Hierarchical Parent ID Number External Information: This field will be the HL01 element for the HL loop that this loop belongs to. Orders => Shipments Packages => Orders Items => Packages or Orders

O AN 1/12 Recommended

HL03 735 Hierarchical Level Code M ID 1/2 Must use

Code Name

S Shipment

HL04 736 Hierarchical Child Code O ID 1/1 Recommended

Code Name

1 Additional Subordinate HL Data Segment in This Hierarchical Structure.

Comments:

1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data.

2. The HL segment defines a top-down/left-right ordered structure.

3. 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.

4. HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.

5. 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.

6. HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.

Example: HL*1**S


TD1 Carrier Details (Quantity and Weight)

Pos: 110 Max: 20

Detail - Mandatory



TD101 103 Packaging Code M AN 3/5 Must use

Code Name

CTN Carton

TD102 80 Lading Quantity External Information: This field will be the total number of cartons making up a shipment.

M N0 1/7 Must use

TD105 79 Lading Description External Information: This field is used to indicate whether a shipment is floor loaded or not. A value of FLR indicates that the shipment is floor loaded. A value of PLT indicates a shipment of pallets. Please Note: All non-small parcel shipments must be palletized.

O AN 1/50 Used

TD106 187 Weight Qualifier M ID 1/2 Must use

Code Name

G Gross Weight

TD107 81 Weight External Information: This field will be the gross weight of the shipment.

M R 1/10 Must use

TD108 355 Unit or Basis for Measurement Code M ID 2/2 Must use

Code Name

KG Kilogram

LB Pound

Syntax: 1. C0102 - If TD101 is present, then all of TD102 are required

Example: TD1*CTN*45****G*1297.03*LB TD1*CTN*45***PLT*G*1297.03*LB TD1*CTN*4***FLR*G*12.03*LB



Pos: 110 Max: 20

Detail - Optional



TD101 103 Packaging Code O AN 3/5 Used

Code Name

PLT Pallet

TD102 80 Lading Quantity External Information: This field will be the total number of pallets making up the shipment.

O N0 1/7 Used


Example: TD1*PLT*6


TD5 Carrier Details (Routing Sequence/Transit Time)

Pos: 120 Max: 12

Detail - Mandatory



TD502 66 Identification Code Qualifier M ID 1/2 Must use

Code Name

2 Standard Carrier Alpha Code (SCAC)

TD503 67 Identification Code External Information: The Standard Carrier Alpha Code (SCAC) is a unique two-to-four-letter code used to identify a carrier. Carrier SCAC codes are assigned and maintained by the NMFTA (National Motor Freight Association). To obtain a SCAC code or the list of all carrier SCAC codes contact the NMFTA at (703) 838-1868. NMFTA developed the SCAC identification codes in the late 1960's to facilitate computerization in the transportation industry. The following is a list of preferred Amazon.com carriers and their corresponding SCAC code: RBTW - CH Robinson PHTS - Phoenix SUSE - SuperSaver ABFS - ABF Freight - YFSY - Yellow Freight- FXFW - Fedexfreight West FXFE - Fedexfreight East FDEN - Federal Express Heavy Weight (Air freight > 250lb) EXP - Federal Express Parcel/Package/Overnight RPSI - FedEx Ground UPSN - UPS Small Parcel Carrier AIRB - Airborne

Formatting Notes: aaaa

M AN 2/80 Must use

Syntax: 1. R0204050612 - At least one of TD502,TD504,TD505,TD506,TD512 is required

2. C0203 - If TD502 is present, then all of TD503 are required

Example: TD5**2*ABFS TD5**2*UPSN


REF Bill of Lading Pos: 150 Max: >1

Detail - Conditional



REF01 128 Reference Identification Qualifier M ID 2/3 Must use

Code Name

BM Bill of Lading Number

REF02 127 Reference Identification External Information: Bill of Lading (BOL) reference number is required for truckload and less than truckload (LTL) shipments. The Amazon.com definition of BOL is defined in reference to truckload and LTL shipments only. BOL reference number is the unique number assigned by the shipper in creating the Bill of Lading. This is a number that identifies a unique shipment. Note: the BOL reference number on the paper BOL should match the reference number provided in this data element.

M AN 1/30 Must use

Syntax: 1. R0203 - At least one of REF02,REF03 is required

Semantics:

1. REF04 contains data relating to the value cited in REF02.

Example: REF*BM*600305100059


REF Pro Number/Tracking ID/Airbill Number

Pos: 150 Max: >1





Code Name

CN Carrier's Shipment Reference Number

User Note 1:

A value of CN is used to qualify the following values: => carrier PRO Number for LTL and TL Carriers => carrier tracking number for small parcel carriers => carrier airbill number for air freight.

REF02 127 Reference Identification External Information: PRO number is required for truckload and less than truckload (LTL) shipments. The PRO Number (Pro Number) is a unique number assigned by the carrier. It is used to identify and track the shipment that goes out for delivery. Note regarding small parcel shipments: For small parcel carriers the tracking number per package is required in this field. If you are unable to provide a tracking number per package at the shipment level, you may provide each tracking number in the package level REF segment. Note regarding air freight: The airbill number replaces the tracking number or PRO number for air freight shipments. An airbill number is the unique identifier air carriers use to identify a package or pallet. The carrier may use this number to invoice as well. The airbill number is assigned by the carrier to either the package for small parcel shipments or to the pallet for large shipments. The airbill number per package/pallet is required in this field. If you are unable to provide an airbill number per package/pallet at the shipment level, you may provide each airbill number in the package level REF segment.

M AN 1/30 Must use


Semantics:



Segment Use: If there is only one PRO/Tracking number/Airbill number, the REF segment must exist at the Shipment Level. If there are multiple unique PRO/Tracking Numbers/Airbill numbers, you may use the REF segment in the Package Level.

Example: (example of valid Pro Number from trucking company) REF*CN*009447616 (example of valid tracking number from small parcel carrier) REF*CN*1ZE1628E0340236740


REF Seal Number Pos: 150 Max: >1

Detail - Optional



REF01 128 Reference Identification Qualifier O ID 2/3 Used

Code Name

SN Seal Number

REF02 127 Reference Identification External Information: This field will be the container's seal number.

O AN 1/30 Used


Semantics:



DTM Shipped Date Pos: 200 Max: 10

Detail - Mandatory



DTM01 374 Date/Time Qualifier M ID 3/3 Must use

Code Name

011 Shipped

DTM02 373 Date External Information: This field will contain the date/time that the shipment departed. Formatting Notes: CCYYMMDD

M DT 8/8 Must use

DTM03 337 Time C TM 4/8 Used

DTM04 623 Time Code C ID 2/2 Used

Code Name

GM Greenwich Mean Time

UT Universal Time Coordinate

Syntax: 1. R020305 - At least one of DTM02,DTM03,DTM05 is required

2. C0403 - If DTM04 is present, then all of DTM03 are required

3. P0506 - If either DTM05,DTM06 is present, then all are required

Example: (example with mandatory fields) DTM*011*20030507 (example with mandatory and optional fields) DTM*011*20030507*0907*GM


DTM Estimated Arrival Date Pos: 200 Max: 10

Detail - Mandatory



DTM01 374 Date/Time Qualifier M ID 3/3 Must use

Code Name

017 Estimated Delivery

DTM02 373 Date External Information: This field will be the estimated date of arrival will be for this shipment. Formatting Notes: CCYYMMDD

M DT 8/8 Must use

Syntax: 1. R020305 - At least one of DTM02,DTM03,DTM05 is required

2. C0403 - If DTM04 is present, then all of DTM03 are required

3. P0506 - If either DTM05,DTM06 is present, then all are required

Example: DTM*017*20030514


FOB F.O.B. Related Instructions Pos: 210 Max: 1

Detail - Mandatory



FOB01 146 Shipment Method of Payment M ID 2/2 Must use

Code Name

CC Collect

PO Prepaid Only

Semantics:

1. FOB01 indicates which party will pay the carrier.

Example: FOB*CC FOB*PO


Loop N1 Pos: 220 Repeat: 200

Mandatory

Loop: N1 Elements: N/A


220 N1 Name M 1

250 N4 Geographic Location M 1

Example: N1*SF*SUPPLIER*15*1234567 N4*NASHVILLE*TN*37214


N1 Name Pos: 220 Max: 1

Detail - Mandatory

Loop: N1 Elements: 4


N101 98 Entity Identifier Code M ID 2/3 Must use

Code Name

SF Ship From

N102 93 Name O AN 1/60 Used

N103 66 Identification Code Qualifier M ID 1/2 Must use

Code Name

1 D-U-N-S Number, Dun & Bradstreet

15 Standard Address Number (SAN)

ZZ Mutually Defined

N104 67 Identification Code External Information: This field will be a unique ID that represents the warehouse where this shipment originated from.

M AN 2/80 Must use

Syntax: 1. R0203 - At least one of N102,N103 is required

2. P0304 - If either N103,N104 is present, then all are required

Comments:

1. 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.

2. N105 and N106 further define the type of entity in N101.


N4 Geographic Location Pos: 250 Max: 1

Detail - Mandatory



N401 19 City Name M AN 2/30 Must use

N402 156 State or Province Code M ID 2/2 Must use

N403 116 Postal Code M ID 3/15 Must use

N404 26 Country Code Formatting Notes: United States - US Canada - CA United Kingdon - GB France - FR Germany - DE Japan - JP

M ID 2/3 Must use

Comments:

1. A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.

2. N402 is required only if city name (N401) is in the U.S. or Canada.


Loop N1 Pos: 220 Repeat: 200

Mandatory

Loop: N1 Elements: N/A


220 N1 Name M 1


N1 Name Pos: 220 Max: 1

Detail - Mandatory



N101 98 Entity Identifier Code M ID 2/3 Must use

Code Name

ST Ship To

N102 93 Name O AN 1/60 Used

N103 66 Identification Code Qualifier X ID 1/2 Used

Code Name

15 Standard Address Number (SAN)

92 Assigned by Buyer or Buyer's Agent

N104 67 Identification Code External Information: This field will be a unique ID representing the Amazon FC where this shipment will be delivered. Formatting Notes: PHL1 => New Castle, DE RNO1 => Fernley, NV LEX1 => Lexington, KY TUL1 => Coffeeville, KS SDF1 => Campbellsville, KY PRTO => Mississauga , ON

X AN 2/80 Used

Syntax: 1. R0203 - At least one of N102,N103 is required

2. P0304 - If either N103,N104 is present, then all are required

Comments:

1. 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.

2. N105 and N106 further define the type of entity in N101.

Example: N1*ST*AMAZON COM INC*92*RNO1 N1*ST*AMAZON COM INC*15*1566008



Mandatory




050 PRF Purchase Order Reference M 1



Detail - Mandatory




M AN 1/12 Must use


O AN 1/12 Used


Code Name

O Order

HL04 736 Hierarchical Child Code All valid standard codes are used.

O ID 1/1 Used

Comments:








PRF Purchase Order Reference Pos: 050 Max: 1

Detail - Mandatory



PRF01 324 Purchase Order Number External Information: This field will contain the Amazon purchase order number. It will be supplied for all Amazon.com Purchase Order numbers relevant to each shipment and that shipment's paper bill of lading (BOL). Formatting Notes: annnnnnn

M AN 1/22 Must use

Semantics:

1.

Example: PRF*S3993317



Conditional



010 HL Hierarchical Level C 1


150 REF Tracking ID/Airbill Number C >1

190 MAN Marks and Numbers C >1

Segment Use: The HL-Package loop is only required when license plate receive is in progress or multiple tracking numbers exist for a single ASN.







M AN 1/12 Must use


O AN 1/12 Used


Code Name

P Pack


O ID 1/1 Used

Comments:









Pos: 110 Max: 20

Detail - Optional



TD101 103 Packaging Code O AN 3/5 Not used

Code Name

CTN Carton

PLT Pallet

TD102 80 Lading Quantity X N0 1/7 Used

TD103 23 Commodity Code Qualifier O ID 1/1 Not used

TD104 22 Commodity Code O AN 1/30 Not used

TD105 79 Lading Description O AN 1/50 Used

TD106 187 Weight Qualifier O ID 1/2 Used

Code Name

G Gross Weight

TD107 81 Weight O R 1/10 Used

TD108 355 Unit or Basis for Measurement Code O ID 2/2 Used

Code Name

KG Kilogram

LB Pound

TD109 183 Volume X R 1/8 Used

TD110 355 Unit or Basis for Measurement Code All valid standard codes are used.

X ID 2/2 Used


2. P0708 - If either TD107,TD108 is present, then all are required

3. P0910 - If either TD109,TD110 is present, then all are required

Example: TD1*CTN*1****G*2.5*LB TD1*PLT*1****G*50.75*LB


REF Tracking ID/Airbill Number Pos: 150 Max: >1





Code Name

CN Carrier's Tracking/Airbill Number

User Note 1:

A value of CN is used to qualify the following values: => carrier tracking number for small parcel carriers => carrier airbill number for air freight.

REF02 127 Reference Identification External Information: For small parcel shipments,

this field may contain the carrier tracking number per package. For air freight, this field may contain the air bill (assigned by the carrier) per package/pallet.

M AN 1/30 Must use


Semantics:


Segment Use:

Example: REF*CN*1ZE1628E0340236740


MAN Marks and Numbers Pos: 190 Max: >1




MAN01 88 Marks and Numbers Qualifier M ID 1/2 Must use

Code Name

GM SSCC-18 and Application Identifier

MAN02 87 Marks and Numbers External Information: This field will be the UCC-128 code asociated with this package. Refer to Appendix A for more information regarding LP Receive with Amazon.com and our label specifications.

M AN 1/48 Must use

Syntax: 1. P0405 - If either MAN04,MAN05 is present, then all are required

2. C0605 - If MAN06 is present, then all of MAN05 are required

Segment Use: This segment must be used if companies are involved in the Amazon license plate receive process.

Example: MAN*GM*00000388080758591512



Mandatory




020 LIN Item Identification M 1

030 SN1 Item Detail (Shipment) M 1

040 SLN Subline Item Detail O 1000



Detail - Mandatory




M AN 1/12 Must use


O AN 1/12 Used


Code Name

I Item


O ID 1/1 Used

Comments:








LIN Item Identification Pos: 020 Max: 1

Detail - Mandatory



LIN01 350 Assigned Identification External Information: This will be a unique line number representing this item.

O AN 1/20 Used

LIN02 235 Product/Service ID Qualifier M ID 2/2 Must use

Code Name

EN European Article Number (EAN) (2-5-5-1)

IB International Standard Book Number (ISBN)

UP U.P.C. Consumer Package Code (1-5-5-1)

LIN03 234 Product/Service ID External Information: The value in this field should match the line item identifier supplied by Amazon.com when the order was placed either via EDI or some alternative method such as email.

M AN 1/48 Must use

Semantics:

1. LIN01 is the line item identification

Example: LIN**IB*0718002431


SN1 Item Detail (Shipment) Pos: 030 Max: 1

Detail - Mandatory



SN101 350 Assigned Identification External Information: This will be a unique line number representing this item.

O AN 1/20 Used

SN102 382 Number of Units Shipped External Information: This field will be the number

of units shipped for this item related to this order.

M R 1/10 Must use

SN103 355 Unit or Basis for Measurement Code M ID 2/2 Must use

Code Name

EA Each

UN Unit

Syntax: 1. P0506 - If either SN105,SN106 is present, then all are required

Semantics:

1. SN101 is the ship notice line-item identification.

Comments:

1. SN103 defines the unit of measurement for both SN102 and SN104.

Example: SN1**1*EA


SLN Subline Item Detail Pos: 040 Max: 1000

Detail - Optional



SLN01 350 Assigned Identification External Information: This will be a unique line number representing this item.

M AN 1/20 Must use

SLN02 350 Assigned Identification O AN 1/20 Not used

SLN03 662 Relationship Code M ID 1/1 Must use

Code Name

I Included

SLN06 212 Unit Price M R 1/17 Must use

SLN07 639 Basis of Unit Price Code M ID 2/2 Must use

Code Name

NT Net

Syntax: 1. P0405 - If either SLN04,SLN05 is present, then all are required

2. C0706 - If SLN07 is present, then all of SLN06 are required

3. C0806 - If SLN08 is present, then all of SLN06 are required

4. P0910 - If either SLN09,SLN10 is present, then all are required










Semantics:

1. SLN01 is the identifying number for the subline item.

2. SLN02 is the identifying number for the subline level. The subline level is analogous to the level code used in a bill of materials.

3. SLN03 is the configuration code indicating the relationship of the subline item to the baseline item.

Comments:

1. See the Data Element Dictionary for a complete list of IDs.

2. 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.

Example: SLN*PRICE**O***6.5*NT


CTT Transaction Totals Pos: 010 Max: 1

Summary - Mandatory



CTT01 354 Number of Line Items External Information: Logical count of all HL loops in the message.

M N0 1/6 Must use

CTT02 347 Hash Total External Information: Sum of all SN102 segments.

M R 1/10 Must use

Syntax: 1. P0304 - If either CTT03,CTT04 is present, then all are required

2. P0506 - If either CTT05,CTT06 is present, then all are required

Comments:

1. This segment is intended to provide hash totals to validate transaction completeness and correctness.

Example: CTT*537*2426


SE Transaction Set Trailer Pos: 020 Max: 1

Summary - Mandatory



SE01 96 Number of Included Segments M N0 1/10 Must use

SE02 329 Transaction Set Control Number M AN 4/9 Must use

Comments:

1. SE is the last segment of each transaction set.


GE Functional Group Trailer Pos: Max: 1




GE01 97 Number of Transaction Sets Included M N0 1/6 Must use

GE02 28 Group Control Number M N0 1/9 Must use

Semantics:

1. The data interchange control number GE02 in this trailer must be identical to the same data element in the associated functional group header, GS06.

Comments:

1. The use of identical data interchange control numbers in the associated functional group header and trailer is designed to maximize functional group integrity. The control number is the same as that used in the corresponding header.


IEA Interchange Control Trailer Pos: Max: 1




IEA01 I16 Number of Included Functional Groups M N0 1/5 Must use

IEA02 I12 Interchange Control Number M N0 9/9 Must use


Appendix A Sample Paper BOL

Your paper BOL is required to always include your BOL Number, Carrier Reference Number (PRO Number). It is also required that the paper bill of lading reference ALL Purchase Orders that are included in this shipment so we may tie back to invoice if

there are any problems. In turn your EDI Advance Shipment Notification must always reference the Bill of Lading Number and Pro Number as referenced below on the paper bill of lading and your ASN must provide details for all ALL Purchase Orders included on your shipment

and in turn on the paper bill of lading.

Characteristics: Carrier Information lists total cartons per NMFC#

VICS Standard BOL: WWW.VICS.ORG For Complete VICS BOL Guideline Information Date: 02/01/1999 BILL OF LADING Page 1

SHIP FROM

Name: ABC Company Bill of Lading Number: _06141411234567890_

Address: 1000 ABC Drive City/State/Zip: Any City, AB, 10000 SID#: FOB:

(402) 06141411234567890 SHIP TO CARRIER NAME: __LTL Transportation_________

Name: XYZ Company Location #:__0669__ Trailer number:

Address: 9000 XYZ Drive Seal number(s):

City/State/Zip: Some City, ZY 90000 SCAC: ABCD

CID#: FOB: Pro number: 12345678901234567890

THIRD PARTY FREIGHT CHARGES BILL TO:

(9012K) ABCD12345678901234567890

Name: Address: City/State/Zip:

Freight Charge Terms: (freight charges are prepaid unless marked otherwise)

SPECIAL INSTRUCTIONS: Prepaid ________ Collect __X__ 3rd

Party _____

(check box)

Master Bill of Lading: with attached underlying Bills of Lading

CUSTOMER ORDER INFORMATION CUSTOMER ORDER NUMBER # PKGS WEIGHT PALLET/SLIP

ADDITIONAL SHIPPER INFO

45012345698 144 ctns 1152 lbs Y N

6805673 15 ctns 45 lbs Y N

Y N

Y N

Y N

Y N

GRAND TOTAL 159 ctns 1197 lbs

CARRIER INFORMATION HANDLING UNIT PACKAGE COMMODITY DESCRIPTION LTL ONLY

QTY TYPE QTY TYPE WEIGHT H.M. (X)

Commodities requiring special or additional care or attention in handling or stowing must be so marked and packaged as to ensure safe

transportation with ordinary care. See Section 2(e) of NMFC Item 360

NMFC # CLASS

1 plts 48 ctns 384 lbs Sport Accessories 154865 00 70

2 plts 96 ctns 768 lbs Video, Tape Recording 168955 03 92.5

15 ctns 15 ctns 45 lbs Recordings, Sound, Disc, Tape 168945 01 100

18 159 1197 lbs GRAND TOTAL

Where the rate is dependent on value, shippers are required to state specifically in writing the agreed or declared value of the property as follows:

COD Amount: $ ______________________

“The agreed or declared value of the property is specifically stated by the shipper to be not exceeding __________________ per ___________________.

Fee Terms: Collect: Prepaid: Customer check acceptable:

NOTE Liability Limitation for loss or damage in this shipment may be applicable. See 49 U.S.C. 14706(c)(1)(A) and (B).

RECEIVED, subject to individually determined rates or contracts that have been agreed upon in writing between the

carrier and shipper, if applicable, otherwise to the rates, classifications and rules that have been established by the carrier

and are available to the shipper, on request. The shipper hereby certifies that he/she is familiar with all the terms and

conditions of the NMFC Uniform Straight Bill of Lading, including those on the back thereof, and the said terms and

conditions are hereby agreed to by the shipper and accepted for him/herself and his/her assigns.

The carrier shall not make delivery of this shipment without payment of freight and all other lawful charges. _______________________________________Shipper Signature

SHIPPER SIGNATURE / DATE Trailer Loaded: Freight Counted: CARRIER SIGNATURE / PICKUP DATE

This is to certify that the above named materials are properly classified, described, packaged, marked and labeled, and are in proper condition for transportation according to the applicable regulations of the DOT.

By Shipper By Driver

By Shipper By Driver/pallets said to contain

Carrier acknowledges receipt of packages and required placards. Carrier certifies emergency response information was made available and/or carrier has the DOT emergency response guidebook or equivalent documentation in the vehicle.

By Driver/Pieces Property described above is received in good order, except as noted.


Appendix B

LP Receive With Amazon.com Operational Requirements: A. Shipping label should include the SSCC information and: (1) The words “SSCC Label” (2) Numeric SSCC (in case bar code doesn’t scan) (3) Scannable SSCC Barcode that is UCC-128 compliant that is at least 14 pt font (http://www.uc-council.org/reflib/00603/01/010403.html)

(4) PO Number (preferably scannable) SSCC codes must always be present at the carton level. If only pallet or trailer level SSCC codes are available, please contact Robin Stebbins ([email protected]). B. Placement of label Label should be placed on the side of the carton 1 to 2” from the side or top edge. The label should not be placed over the carton seam or in a place where it can get obstructed by tape or another label. Clear tape creates “reflection,” which causes the label to be unreadable. The SSCC should not be placed on the top of the carton. C. Reuse of the SSCC number: SSCC codes must be unique and not reused within 12 months from the time it is shipped to Amazon.com D. Stacking of pallets, when applicable Build pallets with SSCC labels facing outwards and clearly visible, whenever possible without compromising stability and density of pallet, so receiver can scan the barcode without breaking down the pallet. E. Item level defects must be within reasonable limits i. All products must have a valid and functional bar code

ii. Products bar code must be linked to proper ASIN (Amazon Standard Identification Number)

F. Timing: ASNs must be received prior to the physical receipt of the product It is the supplier’s responsibility to ensure that information is provided before the shipment arrives at any fulfillment center.

Certification of Vendors Gold Certification “Allows for one scan receive”

(1) Must be on EDI with Amazon using 856s (see ASN details) (2) ASN Loading

a. SSCC barcodes must have a minimum of a 98% load rate, while code is being developed to process replacements (purpose codes) for a period of 3 weeks. Once code is complete, 99% load rate for 3 weeks will be required

b. Shipping label approved by Amazon.com c. Package sent to FC with approved shipping label to validate that the barcode scans d. Load rate calculation: (Total SSCC labels sent - No / bad SSCC label + SSCC not on file)/ (Total

number of SSCC labels received + No/ bad SSCC label + SSCC not on file)

(3) Test shipment: Vendor and Amazon will work together to audit a shipment to one of Amazon.com’s FC. Audit will verify compliant shipping label, product defects, overage / shortages in order and within containers, “switcheroos” within containers and in order, damages, etc.

a. Inventory accuracy (overage, shortage) must be 99.4% Note that Amazon.com reserves the right to change this number at any time throughout the certification process

b. Product defect rate remain between 0 and 5% of units shipped.


(4) If accuracy level drops below required levels or SSCC load rate drops below 98% for more than 7 consecutive days, vendor will be suspended from license plate receive program and will be audited until performance is back to 98% for seven consecutive days.

Platinum Certification: “Allows for one scan receive and stow” Note: Certification levels will freeze during Q4 In addition to maintaining the gold level performance, vendor must also:

(1) Maintain a gold level certification for 3 months (2) Inventory accuracy (container vs. ASN) must be 99.9%; vendor must maintain accuracy rate for 2 months

prior to achieving Platinum status.

Vendors dropping below performance targets for more than 5 days out of a week will return to Gold Certification status and will restart the clock on Platinum certification.

UCC128 Label Specifications

Other additions: FULL CASE PACKS. Please include a scannable UPC either on the shipping label (with the quantity inside the box) or on the outside of the box. MULTIPLE Pos PER BOX: Please list all Pos in box if not we require a carton packing slip inside the carton and a PO that reads MIXED SKUS. If you are an ASN vendor on LP Receive, if you meet accuracy standard we will relax this requirement.


PARTIAL CARTONS: If you are sending a carton with incomplete quantities, there must be a sticker on the outside of the box telling us it’s a partial order. MIXED SKUS: If you are approved to send boxes with Mixed SKUs, you must label the container with MIXED SKU label. Placement of the label: We prefer that the shipping label code is in the bottom right hand corner. If it must go on top (UPS or automated process), it must be offset so the label does not cover the seam (we lose valuable info this way resulting in potential misreceives.)


Appendix C

General Contact Information EDI Hotline Number: 206-266-7188 EDI Fax Number: 206-266-7665 e-mail: [email protected]

Technical Contacts Enterprise Integration Implementation: Carolyn Waldow Systems Integration Analyst 206-266-6817 [email protected] Miche’le Giannini Systems Integration Analyst 206-266-2953 [email protected]

Technical Contact Enterprise Integration Operations (post production): Amazon.com EI-Operations Hotline: 206-266-6800 [email protected]

Enterprise Integration Implementation Manager Kyle Hurst 206-266-1576 [email protected]

mailto:[email protected]





Documents

Advance Ship Notice - Jobisez LLC