WePay Ops Manual NAAmazon

Carrier Manual
Requirements & Expectations

(Inbound WePay Carriers)
We appreciate all your feedback and want to ensure we are providing the most up-to-date information possible.
If you believe any content is missing or needs to be addressed, please let us know!
Effective Date: May 12, 2023

Inbound Carrier Manual
TABLE OF CONTENTS
1. OVERVIEW ................................................................................................................................................................. 3
2. NEW PROGRAMS & RECENT ADDITIONS ......................................................................................................... 3
3. KEY DEFINITIONS .................................................................................................................................................... 3
4. SHIPPER INBOUND OVERVIEW........................................................................................................................... 5
5. TRUCKLOAD (TL) .................................................................................................................................................... 5
6. INTERMODAL (IM) .................................................................................................................................................. 8
7. LESS-THAN-TRUCKLOAD (LTL) ........................................................................................................................ 11
8. SMALL PARCEL (SP) .............................................................................................................................................. 14
9. IMPORT LINEHAUL (TRANSLOADS) ................................................................................................................ 14
10. WAREHOUSE TRANSFERS (WT) ....................................................................................................................... 17
11. GENERAL INFORMATION (FOR ALL BUSINESS TYPES)............................................................................. 19
12. BASE RATES AND LANE OWNERSHIP ............................................................................................................. 22
13. EDI .............................................................................................................................................................................. 23
14. INVOICING PROCESS AND OFF MANIFEST RESOLUTION ......................................................................... 37
ADDENDUM A – CASE MANAGEMENT AND RESOLUTION ................................................................................ 40
ADDENDUM B - EDI 210 INVOICE GUIDE ............................................................................................................... 41
ADDENDUM C – REFERENCE NUMBER TABLE ..................................................................................................... 47
ADDENDUM D – AWS S3 CARRIER PORTAL .......................................................................................................... 48
ADDENDUM E – YARD SAFETY RULES .................................................................................................................... 49
ADDENDUM F – EDI X12-204 ..................................................................................................................................... 50
ADDENDUM G – LTL TENDER REJECTION REASONS.......................................................................................... 69
Page | 2
1. Overview
1.1. Carrier partners play a critical role in helping Amazon succeed in our goal to be the most Customer-centric
company on Earth. We aim to work together to create a highly efficient experience that satisfies Amazon’s and
our partners’ business needs. We place a high value on both service performance and responsiveness, and
reward carriers that consistently deliver superior results. Some of the metrics that we use to evaluate our
carrier partners include:
1.1.1. On-time pickup (OTPU)
1.1.2. Missed Pickup Recovery
1.1.3. Electronic data interchange (EDI) compliance (per Section 13)
1.1.4. Tender Acceptance/Capacity
1.1.5. Billing/Invoice Accuracy (i.e. “first time billing” success)
1.1.6. Appointment Compliance (difference between earliest available CRDD and CRDD chosen)
1.2. In this manual are the requirements, policies, and expectations for Inbound WePay carrier to succeed as a
partner with Amazon.com Services LLC and Amazon Canada Fulfillment Services, ULC. The intention of this
manual is to enhance the operations between Amazon and our carrier partners to improve performance,
consistency, and the carrier experience. The expectation is that all carriers read and adhere to this manual in
its entirety.
1.3. This manual will be kept up to date with current expectations and programs, but does not supersede or change
any official documents or contractual terms between carriers and Amazon.
2. New Programs & Recent Additions

2.1. This manual will be updated regularly and be made available to all carriers onboarded with Amazon. This section
will be utilized to inform carriers of changes to this manual each update that occurs.
2.2. Amazon encourages feedback from all carriers. Our goal is to make processes as efficient as possible and we ask
for assistance from carriers in doing so. All feedback regarding this manual or any policies can be sent via the link
on the first page.
2.3. Major additions/changes since last update (changes are highlighted):
2.3.1. Additional security/safety guidelines at check-in (Section 11.10.5) Important mid-
2.3.2. IM lane deprecation/conversion expectations updated (Section 6.13)
cycle updates
2.3.3. Updated seal direction for process of removal (Section 11.9.5)
2.3.4. Added detailed Truckload Scorecard breakdown (Section 5.13)
2.3.5. Updated Carrier Central defect definitions and use guidelines (Section 11.4)
2.3.6. Clarification for multiple regional vendor locations in carrier’s system (Section 11.13.5)
2.3.7. Clarification on rate bid cycles (Section 12.2)
2.3.8. Disruption management communication process update (Addendum A)
3. Key Definitions
3.1. Relay Operations Center (ROC) – The operations center that acts as a round-the-clock frontline team
responsible for monitoring and resolving issues due to events, such as change in supply, change in demand, or
execution delays
3.1.1. Methods of communicating with ROC:
3.1.1..1. Cases created per Addendum A
3.1.1..2. Through the Relay Mobile App (Relay App use section to be included in future updates)
3.2. Inbound Scheduling Team – Team dedicated to resolving issues with deliveries and appointments at Amazon
facilities
3.2.1. Methods for communicating with IB Scheduling Team:
3.2.1..1. IB Scheduling Chat Feature
3.2.1..2. IB Scheduling Hotline – (866) 203-8372 Option 1
Page | 3
3.3. Transportation Operations Management (TOM) – The central management team supporting FC operations,
yard management, and acting to resolve issues on a site level
3.4. Middle Mile Partner Manager (MMPM) –Act as a central contact to communicate performance, processes, and
track progress for Truckload, Intermodal, and Imports carriers
3.5. Strategic Carrier Manager (SCM) – Responsible for managing and acting as a central point of contact for 3P Less
than Truckload carriers. Will track carrier’s performance and facilitate communications
3.6. Fulfillment Center (FC) - Amazon facility designed as destination for inbound shipments to hold goods for
periods of time before transitioning inventory into customer shipments
3.7. Inbound Crossdock (IXD) – A facility where inbound shipments are received so they can be strategically
consolidated and shipped to their final destination at an FC. IXDs do not store inventory
3.8. Inbound Ship Modes
3.8.1. Truckload (TL) – Loads are picked up at one origin site as a full trailer and transported via linehaul to
an Amazon facility. Max weight is 40,000 lbs., max volume is 3,500 cu. ft., and max. number of pallets
is 60 stackable/30 un-stackable pallets. TL shipments are allowed to be floor loaded
3.8.2. Intermodal (IM) – Loads travelling significant distances, usually over 500 miles, may be transported
through the use of a rail system in addition to linehaul means. IM shipments are allowed to be floor
loaded
3.8.3. Less Than Truckload (LTL) – Shipments that do not require an entire trailer, typically <50% of 53 ft
trailer and must be palletized. Freight originates from several destinations and organized by carrier,
often through use of a crossdock before being sent to destination
3.8.4. Small Parcel (SP) – Loads consisting of smaller packages that weigh less than 150 lb. per carton, less
than 1000 lb. per shipment, less than 350 cu. ft. total shipment volume, no liquid or fragile
components, and will not be palletized. SP shipments are required to be floor loaded
3.9. Import Linehaul (IPLH) – Loads running from 3rd party trans-loaders to FC following arrival via international
transport. May also be imported via intermodal once offloaded by transloader
3.10. Business Day –Refers to Monday-Friday, not including federal holidays
3.11. Holidays – Recognized US holidays are: New Year’s Day, MLK Jr. Day, Memorial Day, Independence Day, Labor
Day, Thanksgiving, and Christmas. For holidays outside of the US, contact your MMPM/SCM/Carrier Manager
3.12. Bill of Lading (BOL) – Serves three purposes: 1) Acts as a receipt for the goods transferred to the carrier, 2)
defines the contract of carriage of the goods from origin to destination according to the responsibilities of the
service provider, and 3) under certain circumstances, provides evidence of title for the goods
3.13. Freight Ready Date (FRD) –The date that the shipper has designated when they will have freight ready for pick
up by the carrier. Shippers are expected to have freight ready within business hours AND by 0800 local time
3.14. Vehicle Run ID (VRID) – An alpha-numeric identifier unique to the truck and load for the assigned trip. A unique
VRID is required for every load shipped to ensure proper billing. A single VRID can transport multiple ARNs
3.15. Amazon Reference Number (ARN) – The reference number assigned by Amazon upon receipt of a routing
request from shippers, applicable only to Collect/WePay shipments. ARNs are the building block of shipments
with Amazon and have only one origin, destination, FRD, and VRID
3.16. No Call, No Show (NCNS) - A confirmed appointment that is missed without prior rescheduling or notification.
Carriers are expected to maintain a network wide goal of <3% NCNS, with a goal of 0%. To prevent NCNS,
contact the IB Scheduling Team per Section 3.2 for assistance
3.17. Purchase Order (PO) – Used by customers, i.e. Amazon, to procure/track materials from suppliers. Amazon uses
an alphanumeric format that begins with a number, followed by 6 letters/numbers and ends with a letter
3.18. PRO Number (PRO#) – A unique number assigned by a motor freight carrier to identify a specific shipment. The
PRO Number will be separate and distinct from the Bill of Lading Number
3.19. Inbound Shipment Appointment Number (ISA) – Confirmation number accompanying an inbound delivery
appointment. Should be made available by the carrier upon arrival at Amazon facility as necessary
3.20. Electronic Data Interchange (EDI) – A method of transmitting data in formatted messages electronically
between Amazon, carriers, and shippers using the EDI standards X12
3.21. Freight Management Console (FMC) – The Amazon Logistics platform that allows the user access to obtain
visibility on scheduled loads that interact with Amazon facilities
Page | 4
3.22. Prepaid – (Amazon term equivalent is “TheyPay”) The consignor (shipper) pays the freight charges
3.23. Collect – (Amazon term equivalent is “WePay”) Amazon is responsible for paying the freight charges
4. Shipper Inbound Overview

4.1. All inbound freight deliveries to the FC, excluding Small Parcel, require an appointment. All inbound
appointments must be made online via Amazon’s Carrier Central site, as outlined in the Carrier Central User
Manual.
4.1.1. Prior to receipt of any load tenders, carrier should submit a login request at
https://carriercentral.amazon.com/ to ensure they have the ability to schedule appointments. This is
a one-time event, but it can take as long as one day to process. Please refer to the Carrier Central
User Manual for detailed instructions.
4.2. It is recommended that the carrier has a representative on each shift with access to Carrier Central and is
familiar with its features. This is so appointment changes can be performed as soon as required.
4.3. Tender process – Carriers should expect to receive the majority of inbound EDI 204 tenders from Amazon daily,
Monday through Friday by 1400 PST/PDT. The EDI 204 will contain (full breakdown of EDI 204s can be found in
Addendum F):
4.3.1. Assigned carrier including contact name and phone number
4.3.2. ARNs – There may be multiple ARNs contained within one EDI 204. These ARNs are to be used to
secure pickup appointments at shippers. ARNs are NOT to be split across different shipments
4.3.3. Routing Request Number – This is the number provided to the shipper when they route their freight
in Amazon’s system to be tendered to a carrier
4.3.4. Cargo Value – PO value associated with the freight being moved: Low (<$100k), Medium ($100k-
$250k), High ($250k-$1 MM) and Highest (>$1 MM)
4.3.5. Shipper Name and Address – If any discrepancy arises regarding accuracy of address, driver should
contact ROC per Addendum A to resolve
4.3.6. Freight Ready Date – The FRD will typically be the business day following receipt of the tender
4.3.7. PO #(s) – This is the identifier of our agreement for the amount of goods purchased from the shipper
4.3.8. Total Cartons
4.3.9. Total Pallets – The number of stacked versus unstacked pallets will be differentiated
4.3.10. Weight
4.3.11. Freight Class (for LTL and LTL consolidation shipments)
4.3.12. Destination FC
4.3.13. City and State of FC
4.3.14. VRID – If multiple ARNs are assigned to that VRID, they shall be shipped together.
4.4. Carriers are expected to communicate throughout the process via the appropriate means (i.e. EDI, Relay),
starting with accepting the tender. Expected EDI lifecycles for all ship modes can be found in Section 13, with the
exception of Small Parcel.
5. Truckload (TL)
5.1. Carriers must respond to all tenders via EDI 990/Relay with an “Accept” or “Reject” response within 2 hours of
receipt of a tender.
5.1.1. Carriers must maintain at least a 95% tender acceptance rate, based on a weekly average.
5.1.2. Whether accepting or rejecting, a response is required for every tender sent to carriers. (Reminder:
Amazon actively reviews rejections on an ongoing basis).
5.1.2..1. No response to a tender will be treated as a rejection and will be retendered to a new carrier.
5.1.2..2. Every rejection MUST include an accompanying rejection reason.
5.1.2..3. Under no circumstances will a carrier attempt to reject a tender that they have already
accepted.
Page | 5
5.1.3. Carriers should not initiate contact with the shipper to schedule pick up until a tender has been
received and accepted. Amazon will notify the shipper of carrier selection upon carrier’s acceptance
5.2. Carrier will secure capacity upon receipt of load tenders based on tendered pickup date and Carrier Central
delivery appointment availability.
5.2.1. If the carrier is not able to secure capacity for a shipment immediately, the load should be rejected.
Non-Relay carriers will also communicate the issue with ROC per Addendum A. This will initiate the
retender process of the load, no further communication is necessary.
5.2.2. If the load has already been accepted and the carrier is unable to secure capacity within 72 hours of
receiving the load tender or prior to 24 hours before the FRD, whichever is sooner, the carrier must
notify Amazon of the capacity issue by submitting a case to ROC per Addendum A. MMPM actively
reviews capacity issues by carrier/lane.
5.3. Within 2 hours of accepting the load tender, the carrier must submit an appointment request in Carrier Central.
Refer to the Carrier Central User Manual for specific details.
5.3.1. Carrier Requested Delivery Date (CRDD) should be calculated based on FRD plus transit time (solo
transit), see Section 5.12 for transit time strategy. The appointment confirmation, which will be
emailed and visible in Carrier Central, will contain the ISA # and appointment time.
5.3.2. Carriers requesting an appointment on Carrier Central will utilize Crystalview, a feature which allows
carriers to select a specific appointment time. The expectation is that the selected time will be the
earliest feasible appointment, closest to the CRDD, that can be completed.
5.3.3. Any change to CRDD must be done by editing the date, NOT creating a new appointment. Any
problems experienced during this process should be communicated to the ROC immediately per
Addendum A.
5.4. After receiving the appointment confirmation, the carrier should contact the shipper to arrange pick up based
on the delivery appointment time at the FC and transit time needed.
5.4.1. Scheduled pickups must be communicated to Amazon via EDI/Relay, as appropriate.
5.5. Upon arrival at the shipper, the load information provided in the original tender (# of pallets/packages, ARNs,
etc.) should be compared to the information provided on the BOL and the actual shipment loaded whenever
possible and access to the trailer is available.
5.5.1. The shipper will provide the carrier with a physical copy of the BOL. The BOL is a legal document
which will be used for invoicing and must match what is being transported. Any discrepancies must
be immediately communicated to the ROC per Addendum A.
• All ARNs being transported must appear on the BOL and must be in typed format, NOT
handwritten.
5.5.2. If there is a discrepancy in the load quantity or content, the carrier must update the appointment
with the correct load information in Carrier Central.
5.5.3. If there is any damage noted, contact the ROC for further instruction on accepting the load.
5.5.4. Carriers are required to seal trailers and notate seal numbers prior to beginning transit to Amazon
facility. Refer to Section 11.9 for more information regarding the use of seals.
5.5.5. The carrier must remain on site to receive the shipment for at least 2 hours gate to gate, or until the
scheduled departure time, unless the shipper has informed the driver that the freight is not ready.
5.5.5..1. An effort should be made to talk to the shipper on site to verify freight not ready and
establish carrier’s presence. These details, specifically any personnel contacted, position they
hold, and name, should be included in cases made to ROC to clarify actions and establish the
nature of a possible TONU.
5.6. Any delays that may affect pickup must be communicated via appropriate means (i.e. EDI, Relay) with the
applicable delay reason code and inform the ROC as necessary. If the pickup appointment will not be met, the
carrier should immediately inform the shipper for rescheduling, if not rescheduled through Relay.
5.6.1. If pickup will be delayed by more than 72 business hours from the load tender, the ROC must be
contacted per Addendum A and Amazon will make the determination for the best course of action.
The load may be retendered based on the defect.
Page | 6
5.7. Every pickup attempt which does not result in a successful pickup must be accompanied by a new EDI 214
message with the appropriate reason code for the unsuccessful pickup.
5.8. If the carrier will be late for the delivery appointment, the ROC must be contacted per Addendum A so they can
inform the FC. The carrier may be directed to reschedule the appointment in Carrier Central.
5.8.1. Any delay must be accompanied by the appropriate delay reason code via EDI/Relay as appropriate.
5.8.2. If the driver arrives more than 30 minutes after appointment time without prior notification, the
appointment is liable to be cancelled by ROC/TOM. This will require a new appointment request to
be submitted in Carrier Central and may be used to evaluate performance.
5.8.3. To prevent NCNS, when any carrier knows they will be late to any appointment they must cut a case
to ROC per Addendum A.
5.8.4. If a reschedule/cancellation is done within 24 hours of an appointment, this will be considered a
carrier defect by the ROC and may result in suspension from Carrier Central. See Section 11 for more
details.
5.9. Driver must be prepared to provide their ISA # upon arrival at the FC gate. This is the primary reference number
for identifying shipper inbound loads upon arrival. The guard should be informed that the driver has an
appointment and the VRID should be made available to confirm appointment as necessary.
5.9.1. Carriers are permitted to perform drop loads according to their applicable agreement and terms.
5.9.2. Drop loads are permitted to be delivered based on the window communicated by IB Scheduling in
the external Quicksight provided when onboarded. This window may change based on site backlog
and yard constraints. If Amazon needs to reduce the drop window due to yard capacity, the previous
drop windows will be honored for 12 hours.
5.10. Standard unloading free time allowance for live loads is 2 hours per appointment.
5.10.1. Detention Accessorial: Assuming that the carrier has arrived at the destination at the scheduled
arrival time and following the 2 hours of free time, driver detention charges will begin accruing in
accordance with the carrier’s applicable agreement and must be approved by the ROC, see Section 14
for accessorial validation.
5.10.2. Loaded Trailer Dwell Accessorial: Trailer detention/dwell charges will be paid out in accordance with
the applicable carrier agreement. Relay and AF Partner rates for trailer dwell/detention accessorial
charges can be referenced on the Relay portal.
5.11. Dwelling Empty Trailer Tow Policy
5.11.1. A dwelling trailer is one not owned by Amazon which has no clear mechanism for removal from the
yard by the carrier.
5.11.2. Any dwelling trailer is liable to incur the following actions:
5.11.2..1. TOM team will request trailer removal within 1 hour of the trailer being emptied. This first
notice will inform the carrier that the trailer is empty and is expected to be removed within
72 hours.
5.11.2..2. If the equipment is not removed within 72 hours, the ROC/MMPM will escalate to the carrier
for immediate pick up.
5.11.2..3. If the equipment is not removed 48 hours after escalation, the ROC will give the TOM team
permission to tow the empty trailer from the yard. This action will be communicated to the
carrier and will include the company used for towing and the ETA for removal.
5.12. Transit Time Strategy: Our goal is to have a disruption and delay free transit whenever possible. We are fully
aware that at times shippers will not be able to meet their FRDs and FCs will not be able to accept delivery at the
CRDD, however we want to avoid creating extra transit time whenever possible. The variables involved in setting
the pickup and delivery appointments include:
5.12.1. Delivery appointment time requested by the carrier and accepted by the FC
• Initially the CRDD should always be equal to the FRD on the tender plus the calculated drive
time without adding additional time other than to accommodate for FC operating hours.
• FCs should accept the CRDD in the case of “Hot POs” (marked as such in the external
Quicksight). Notify ROC per Addendum A in the event this does not occur.
Page | 7
5.12.2. Pickup time at the shipper

• The expectation is that the freight will be ready for pickup by the agreed upon FRD by 0800 local
time AND within business hours (unless otherwise communicated).
• If a shipper is unable to accommodate the planned pickup that falls on/after the FRD or cannot
be reached, then ROC must be notified per Addendum A to assist in resolving the issue.
• Any attempts made at pickup or issues encountered should be promptly communicated to the
ROC and accompanied by the appropriate EDI message explaining the cause of the delay.
5.12.3. Transit Time
• TL transit time is measured from pickup at origin to actual drop off using a solo driver to drive
directly to the FC, including federally regulated breaks.
• It is our expectation that if a driver has to drive over a holiday weekend to make a direct transit
then they will do so. Additional time will not be added to accommodate driver’s personal plans.
• It is understood that delays may often be encountered that may extend transit time. It is
expected that any delays encountered that may have an effect on delivery will be promptly
communicated via EDI/Relay and the ROC will be contacted as necessary.
5.13. Balanced Carrier Scorecard
5.13.1. To evaluate TL carrier partners, Amazon uses a carrier scorecard that tracks key metrics to assess
overall carrier performance.
5.13.2. This scorecard is subject to change as Amazon improves processes and develops new metrics and
makes the scorecard more comprehensive. Future iterations will be communicated to carriers and
outlined in this section in the following update.
5.13.3. The scorecard is composed of four different metrics that carrier managers use to evaluate
performance on a week to week basis:
• ISA Compliance is measured by if the FC arrival of the load via EDI (X1_NS) is no later than 30
minutes from the Scheduled Arrival date/time.
• Rejections are calculated by dividing the total number of loads rejected (combination of
rejections via EDI 990, loads not accepted within 2 hours/expired, and all carrier controllable
cancellations based on timestamp of cancellation) by the total new tenders created for the
carrier in the same week.
• CARP compliance is based on carriers selecting the earliest provided delivery appointment in
Carrier Central for the delivery FC relative to the CRDD. Any carrier controllable appointment
pushes are considered defects.
• Average Days Pushed computes the number of days between the latest ISA date and the first
CRDD.
6. Intermodal (IM)
6.1. Carriers must respond to all tenders via EDI 990 with an “Accept” or “Reject” response within 2 hours of receipt
of a tender.
6.1.1. Carriers must maintain at least a 95% tender acceptance rate, based on a rolling 7 days average.
6.1.2..2. Every rejection MUST include an accompanying rejection reason.
accepted.
received and accepted. Amazon will notify the shipper of carrier selection upon carrier’s acceptance.
6.2. Carrier will secure capacity upon receipt of load tenders based on tendered pickup date and Carrier Central
delivery appointment availability.
Page | 8
6.2.1. If for any reason the carrier is not able to secure capacity for a shipment, the load should be rejected
immediately. Non-Relay carriers will also communicate with ROC per Addendum A. This will initiate
the retender process of the load, no further communication is necessary.
6.2.2. If the load has already been accepted and the carrier is unable to secure capacity within 72 hours of
receiving EDI load tender or prior to 24 hours before the FRD, whichever is sooner, then carrier must
notify Amazon of the capacity issue by submitting a case to ROC per Addendum A. Carrier
managers/MMPM actively reviews capacity issues by carrier/lane.
6.3. Once the tender has been accepted, the carrier must contact the shipper via email/phone to arrange for pickup.
6.3.1. Scheduled pickups must be communicated to Amazon.
be communicated to the ROC per Addendum A.
handwritten.
6.4.3. Carriers are required to seal trailers and notate seal numbers prior to beginning transit to Amazon
facility. Refer to Section 11.9 for more information regarding the use of seals.
6.5. Any delays that may affect pickup must be communicated via EDI immediately with the applicable delay reason
code and inform the ROC as necessary. If the pickup appointment will not be met, the carrier should
immediately inform the shipper for rescheduling.
6.6. Every pickup attempt which does not result in a successful pickup must be accompanied by an EDI 214 message
with the appropriate reason code for the unsuccessful pickup.
6.7. Once the load has been checked in at the rail yard gate, Carrier must submit an appointment request in Carrier
Central if not already done. Refer to the Carrier Central User Manual for specific details on scheduling
appointments.
6.7.1. Carrier Requested Delivery Date (CRDD) should be calculated based on FRD plus transit time, see
Section 6.12 for transit time strategy. The appointment confirmation, which will be emailed and
visible in Carrier Central, will contain the ISA # and appointment time.
6.7.2. Carriers will utilize Crystalview, a feature of Carrier Central, to select a specific appointment time. The
expectation is that the selected time will be the earliest feasible appointment, closest to the CRDD,
that can be completed.
Addendum A.
6.8.1. Any delay must be accompanied by the appropriate delay reason code via EDI 214.
6.8.2. If the driver arrives more than 1 hour after appointment time without prior notification, the
be submitted in Carrier Central and may be used to evaluate performance. The expectation is an on-
time delivery at least 95% of the time.
6.8.3. To prevent NCNS, ensure that any delivery reschedules are performed in Carrier Central greater than
24 hours prior to planned delivery.
6.8.4. If a reschedule/cancellation is done within 24 hours of an appointment, this will be considered a
defect by the ROC and may result in suspension from Carrier Central. See Section 11 for more details.
Page | 9
6.10. Standard unloading free time allowance for live unloads is 2 hours per appointment.
6.10.1. Loaded Trailer Dwell Accessorial: Trailer detention/dwell charges will be paid in accordance with the
applicable carrier agreement.
120 hours.
6.11.2..2. After 120 hours, carriers will be contacted to escalate the issue and inform them of next
steps for removal process.
• Initially the CRDD should always be equal to the pickup date plus the time spent in terminal
consolidation and on the road en route to the FC without adding additional time other than to
accommodate for FC operating hours.
• Carriers should utilize a combination of published rail times, current rail conditions, historical
travel time (4-8 weeks trailing data), and calculated travel time for a solo driver from rail yard to
destination with federally regulated breaks to determine total transit time. No additional buffer
time should be added into the transit time.
then they will do so. Additional time will not be added to accommodate driver’s personal plans
• It is understood that delays often are encountered that may extend transit time. It is expected
that delays encountered that may have an effect on delivery will be promptly communicated via
EDI 214 and the ROC will be contacted as necessary per Addendum A.
6.13. Lane Deprecation and Conversion
6.13.1. Amazon will give carriers 2-week lead time notice concerning any changes to a carrier’s lanes due to
deprecation or conversion whenever possible. There may be times due to operational constraints
where this lead time may be shortened.
6.13.2. Carriers are expected to remove any excess assets within 5 days of receiving notice of lane
deprecation/conversion.
• The ROC Equipment team will be monitoring carrier’s asset movement and will escalate any
issues where assets are not removed as outlined above.
Page | 10
7. Less-than-truckload (LTL)
7.1. Carriers should expect to receive LTL load tenders approximately 24 hours prior to FRD.
7.2. Carriers must respond to all tenders via EDI 990 with an “Accept” or “Reject” response within 4 hours of receipt
of a tender.
7.2.1. Carriers must maintain at least a 95% tender acceptance rate, based on a rolling 7 days average.
7.2.2..2. Every rejection MUST include an accompanying rejection reason code from the list in
Addendum G.
accepted.
received and accepted. Amazon will notify the shipper of carrier selection upon carrier’s acceptance.
7.3. Carrier will secure capacity upon receipt of load tenders based on tendered pickup date.
7.4. Carrier should contact shipper to arrange pickup immediately following acceptance of tender.
7.4.1. Scheduled pickups must be communicated to Amazon via EDI/Relay, as appropriate.
7.4.2. Shippers are expected to have shipments ready for pickup by 0800 local time AND within business
hours on scheduled pickup date.
be communicated to the ROC per Addendum A.
handwritten.
7.5.2. Loads should be picked up from shippers based on expected ARNs.
7.5.3. At a minimum, LTL carriers are required to seal trailers at destination terminal following
consolidation and notate seal numbers prior to beginning transit to Amazon facility. Refer to Section
11.9 for more information regarding the use of seals.
7.5.5. Shipments are NOT to be split at pickup for any reason. If this does occur due to unforeseen
circumstances, the ROC should be informed per Addendum A immediately upon determining the split
with a copy of the updated BOL. The submitted invoice should only include the transported ARNs.
7.5.6. The carrier should remain on site to receive the shipment for at least 30 minutes gate to gate, or until
scheduled departure time, unless the driver is informed that the freight will not be ready.
7.5.6..1. An effort should be made to talk to the shipper on site to verify freight not ready and
establish carrier’s presence. These details, specifically any personnel contacted, position they
hold, and name, should be included in cases made to ROC to clarify actions and establish the
nature of a possible TONU.
7.6. Any delays that may affect pickup must be communicated via appropriate means with the applicable delay
reason code (i.e. EDI, Relay) and inform the ROC as necessary. If the pickup appointment will not be met, the
carrier should immediately inform the shipper for rescheduling, if not rescheduled through Relay.
7.7. Every pickup attempt which does not result in a successful pickup must be accompanied by a new EDI 214
message with the appropriate reason code for the unsuccessful pickup.
Page | 11
7.7.1. If freight is not ready on first attempt, carrier will follow up with call for next available pick up. If
freight isn’t ready after 2nd attempt, and shipper has yet to provide a ready date for freight, carrier
will cut a case to ROC with all No Freight ARNs per Addendum A.
7.8. Carriers should request an appointment in Carrier Central for FC delivery no later than when the trailer has been
finalized with the applicable freight at the destination terminal. The requested delivery date should be within 24
hours of the request submission, unless this is not possible due to transit time. Refer to the Carrier Central User
Manual for specific details on scheduling appointments.
7.8.1. Carriers requesting an appointment on Carrier Central will utilize Crystalview, a feature which allows
carriers to select a specific appointment time. The expectation is that the selected time will be the
earliest feasible appointment, closest to the Carrier Requested Delivery Date (CRDD), that can be
completed.
Addendum A.
7.8.3. Carriers will ensure that all ARNs being delivered are entered on the Carrier Central appointment.
This will ensure maximum visibility and allow Amazon to correctly track shipments and carrier
performance.
7.9.1. This delay must be accompanied by the appropriate delay reason code via EDI/Relay as appropriate.
7.9.2. If the driver arrives more than 30 minutes after the appointment without prior notification, the
be submitted in Carrier Central.
7.9.3. To prevent NCNS, when any carrier knows they will be late to any appointment they must cut a case
to ROC per Addendum A.
7.9.4. Any delivery appointment that must be rescheduled/cancelled must be done immediately. Continual
poor performance and reschedules will risk removal from Carrier Central, see Section 11 for details.
7.11. Standard unloading free time allowance for live loads is 2 hours per appointment.
7.11.1. Detention Accessorial: Assuming that the carrier has arrived at the destination at the scheduled
arrival time and following the 2 hours of free time, driver detention charges will begin accruing in
accordance with the carrier’s applicable agreement and must be approved by the ROC, see Section 14
for accessorial validation.
7.11.2. Loaded Trailer Dwell Accessorial: Trailer detention/dwell charges will be paid out in accordance with
the applicable carrier agreement. Relay and AF Partner rates for trailer dwell/detention accessorial
charges can be referenced on the Relay portal.
7.12. Embargoes
7.12.1. Carriers must provide a minimum of three business days’ notice before enacting an embargo on an
Amazon FC/end zip. This notice must be made to your SCM via email.
7.12.1..1. Carriers must coordinate with the ROC to continue delivery of any product in their possession
at time of embargo. This may involve redirecting freight originally destined for an embargoed
location. Do not return freight to the shipper unless specifically instructed to do so.
7.12.2. Upon initiation of the embargo, carriers should reject loads for that lane via EDI 990 with the correct
rejection code (if carrier cannot reject tenders, they must reject manually via the ROC). Amazon
Page | 12
systems will take ~1-2 business days to completely halt tenders post-embargo.
7.12.3. The designated lane will remain turned off until the carrier notifies their SCM via email that the
embargo will stop and to restart automatic tenders.
72 hours.
7.13.2..2. If the equipment is not removed within 72 hours, the ROC/MMPM/SCM will escalate to the
carrier for immediate pickup.
7.13.2..3. If the equipment is not removed 48 hours after escalation, the ROC will give the TOM team
permission to tow the empty trailer from the yard. This action will be communicated to the
carrier and will include the company used for towing and the ETA for removal.
• Initially the CRDD should always be equal to the FRD on the tender plus the calculated drive
time without adding additional time other than to accommodate for FC operating hours.
7.14.2. Pickup time at the shipper
• The expectation is that the freight will be ready for pickup by the agreed upon FRD by 0800 local
time AND within business hours (unless otherwise communicated).
• If a shipper is unable to accommodate the planned pickup that falls on/after the FRD or cannot
be reached, then ROC must be notified per Addendum A to assist in resolving the issue.
• Any attempts made at pickup or issues encountered should be promptly communicated to the
ROC and accompanied by the appropriate EDI message explaining the cause of the delay.
• Should be calculated as the time for a solo driver to drive directly to the FC including federally
regulated breaks. No additional buffer time should be added into the transit time.
then they will do so. Additional time will not be added to accommodate driver’s personal plans.
• It is understood that delays may often be encountered that may extend transit time. It is
expected that any delays encountered that may have an effect on delivery will be promptly
communicated via EDI/Relay and the ROC will be contacted as necessary.
7.15. Balanced Carrier Scorecard
7.15.1. To evaluate LTL carrier partners, Amazon uses a carrier scorecard that tracks key metrics to assess
overall carrier performance.
7.15.2. This scorecard is subject to change as Amazon improves processes and develops new metrics. Future
iterations will be communicated to carriers and outlined in this section in the following update.
7.15.3. The scorecard is categorized by Performance and Signals with associated metrics in each section.
Performance metrics are weighted 70% of total score and Signals metrics are weighted 30% of total
score.
• OTPU is measured based on the total ARNs picked up on the vendor’s routed FRD/Total ARN on
that FRD. Pickup success will be dependent on Amazon’s receipt of the applicable EDI 214.
• CARP compliance is based on carriers selecting the earliest provided delivery appointment in
Carrier Central. Any carrier controllable appointment pushes are considered defects.
Page | 13
• An ISA defect is whenever a carrier adjusts the ISA with a late reschedule, late cancellation,
appointment duplication, inaccurate PO, or NCNS. For further explanation of ISA defects, refer
to Section 11.4.2.
• For signal definitions, refer to Section 13.5.1.
Category Metric Metric Weights Overall Weight
OTPU (Carrier Controllable only) 50%
Recovery Timeliness (Recovered within 3 days of FRD) 30%
Performance 70%
Appointment Execution (CARP Compliance) 10%
ISA Defects 10%
EDI Coverage 40%
Signals EDI Timeliness (Receipt with 4 hours) 40% 30%
EDI Defects 20%
Total Balanced Score 100%
8. Small Parcel (SP)

8.1. Once Amazon completes the purchase order process with the shipper, they will be informed that their shipment
is being transported via SP and would then arrange for pickup via the carrier’s applicable website. This will be
done using the Amazon account information.
8.1.1. The shipper will use the Amazon purchase order and ARNs for reference numbers when coordinating
with carriers.
8.1.2. The shipper will be utilizing Amazon’s 3rd party billing information on their accounts if they are a
WePay/Collect shipper.
8.2. Upon arrival at the shipper, the shipper will provide the carrier with a physical copy of the BOL. The load
information provided on the original tender (# of cartons/packages, ARNs, etc.) should be compared to the
information provided on the BOL and the actual shipment loaded.
8.2.1. All ARNs being transported must appear on the BOL and must be in typed format, NOT handwritten.
8.2.2. Shipping labels should have been affixed on all packages by the shipper. These labels should be
verified and match all expected information (i.e. destination).
8.3. Any delays that may delay pickup must be communicated immediately to the shipper.
8.4. While in transit and 24 hours prior to delivery, the carrier will send trailer ID/tracking IDs to Amazon via an EDI
214 message so that Amazon may secure an inbound delivery appointment for the carrier.
8.4.1. An ISA number will be created internally for the SP carrier.
8.5. Driver will check in upon arrival at gate to be appropriately directed for completion of delivery.
8.5.1. The load will be matched to the ISA upon entry to verify that the shipment has arrived as expected.
8.6. All small parcel trailers are set up to be utilized as a drop trailers upon arrival at destination FC.
8.6.1. Depending on the equipment used for the shipment, an unload may be executed as a live unload.
8.7. Loaded Trailer Dwell Accessorial: Trailer detention/dwell charges will be paid out in accordance with the
applicable carrier agreement.
9. Import Linehaul (Transload)
9.1. Amazon uses the services of a 3PL Transloader in order to cross dock imported goods targeted for our FCs from
ocean containers to surface equipment. Imports require drop trailers at origin and destination. Volume arrives
to several ports with transload services currently supplied by several providers:
Page | 14
DSFS – Damco – Santa Fe, CA TPCH – Trade Port – Charleston, SC

12801 Excelsior Drive 400 Long Point Rd
Santa Fe Spring, CA 90670 Mount Pleasant, SC 29464
TPSV– Trade Port – Savannah, GA GOAK – GSC – Oakland, CA

301 Little Hearst Pkwy 1599 Maritime Street, Building D512
Port Wentworth, GA 31407 Oakland, CA 94607
RSAV – Road One – Savannah, GA REWR – Road One – Flanders, NJ

115 Pinder Point Rd 703 Bartley-Chester Rd
Port Wentworth, GA 31407 Flanders, NJ 07836
DSEA – Damco – Sumner, WA DHOU – Damco – Houston, TX

14409 24th St. E. 500 Mesa Drive
Sumner, WA 98390 Houston, TX 77078
DSEB – Damco – Lakewood, WA RORF – Road One – Suffolk, VA

7530 150th ST SW 6601 Park Drive
Lakewood, WA 98439 Suffolk, VA 23435
BCVA – Damco – New Westminster, BC (CA)

549 Duncan Street
New Westminster, BC V3K5B6
9.2. Transload Operations

9.2.1. Transloader yards are open 24/7. The 3PL Transloader office hours are 0800 – 1700 local time,
Monday-Friday.
9.2.2. Carrier managers will complete a forecast every Thursday for the following week (Sunday-
Saturday) based on expected arrivals.
9.2.2..1. Imports volume is subject to allocation changes based on FC ability to receive. Lane level
volume will experience weekly changes in allocations driving changes in load volumes.
9.2.2..2. Forecast is calculated using cubic meters of incoming and pier side freight allocations to
quantify the number of trailers needed for each lane over the next few weeks. A
deferred allocation model is used, where final allocations for product are not locked in
until 5 days before vessel arrival.
9.2.2..3. Once completed, the forecast will be sent to carriers by EOD Thursday. Carriers are
expected to confirm their number of trailers by Friday 1100 PST/PDT for the next week.
9.2.3. Amazon requires this program to be quoted and executed with drop trailer pools at origin and
drop unloads at FCs.
9.2.3..1. Trailer Pool Requirement Calculations
• IM (2.5x requirement): Total forecast vol./operational days (usually 5 days)*2.5
• TL (4x requirement): Total forecast vol./operational days (usually 5 days)*4
• 33% empty ratio is expected to be maintained at site to allow for fluid transloader
operations with empties.
• Carriers will be informed daily of deficits from CBM reports at transload sites where they
have lanes by MMPM. Carriers must provide turn plans daily by 1000 EST. MMPM will
provide a template, which will be updated as lanes change via Route Guide.
9.2.3..2. Carriers are required to provide empty trailer capacity following the addition of new
lanes/transload sites after the bid process and Route Guide updates. The trailer pool
requirement must be provided by the Sunday before the new Route Guide is in effect.
Page | 15
• New Route Guides are sent by email from strategy team the Friday before the lane
change.
9.2.4. Trailer pool increases/decreases based on the agreed upon volume forecast are due in place by
Sunday.
9.2.4..1. For empty trailer removal above pool requirement, carriers must escalate the situation
to their MMPM, who will get approval from the Amazon Global Mile team.
9.2.5. A detailed communication will be sent daily from transloaders to carriers providing an update on
equipment and loading status for equipment onsite.
9.3. Once a transloader has completed loading a trailer, a routing request will be submitted to Amazon. Amazon
will then create an ARN for the load and will be followed by an EDI 204 load tender to carrier.
9.3.1. Load tenders must be accepted via EDI 990 within 2 hours. After 2 hours, the tender will time
out and will be retendered. Auto accept functionally should be turned on for this business
segment.
9.4. Delivery appointments should be requested in Carrier Central immediately after accepting a load tender.
The appointment must be requested within 4 hours of accepting the tender.
9.4.1. Carrier is responsible for setting up an import specific SCAC (in the format IMPXX, with last two
letters being the first two letters of actual SCAC), to be used only for imports.
9.4.1..1. Carrier may only use the Imports SCAC to secure an appointment for Imports loads. A
new account must be created in Carrier Central with a new SCAC to execute any other
types of load.
9.4.2. Delivery requests in Carrier Central MUST Include the following: Use of Imports SCAC (IMPXX),
Freight Type = TL, Load Type = Not-Palletized, Clamp Truck = Yes, Trailer Number (not
mandatory), Comments “Import Load, Drop Unload”, ARN, PRO Number, BOL Number
(Transloader BOL, NOT VRID), Carton Counts, All PO’s
9.4.2..1. Failure to correctly include all information will lead to appointment push, and habitual
noncompliance will warrant potential carrier removal from program.
9.4.3. Carriers requesting an appointment on Carrier Central will utilize Crystalview, a feature which
allows them to select a specific appointment time. The expectation is that the selected time will
be the earliest feasible appointment, closest to the CRDD, that can be completed.
Addendum A.
9.4.5. Delivery appointments should be scheduled based on FRD plus transit time. Expected transit
time is calculated based on the FRD included in the tender. Transit time strategy for OTR loads
should be calculated in accordance with Section 5.12 (TL Transit Time Strategy).
9.4.6. Due to FC capacity constraints, appointments may be pushed and loads can dwell over 24 hours
at transload sites. Carriers may experience trailers dwelling at FCs during peak volume if there is
limited capacity to unload. Escalations can be made to MMPM for long dwellings cases.
9.5. The expectation is that loaded trailers will be pulled by carriers within 24 hours of receiving the tender from
the transloader.
9.5.1. The ROC will contact carriers if any loaded trailers are dwelling past 24 hours once tendered.
9.5.2. If Amazon scheduling issues prevent pickup within 72 hours from receiving the tender, cut a case
to ROC and include the ISA # along with desired time for delivery.
9.6. Any delays that are encountered en route to pick up or delivery should be communicated immediately.
9.6.1. All delays should be accompanied by the appropriate EDI message with the applicable delay code and
a case created with ROC as appropriate.
9.6.2. Pickup delays should be communicated with a new ETA for arrival if the carrier will be delayed
outside the 24 hours following the acceptance of the load tender.
9.7. Driver must be prepared to provide an ISA number upon arrival at gate. This is the primary reference number for
identifying shipper inbound loads upon arrival.
9.8. Communications procedure:
Page | 16
9.8.1. Throughout transit, EDI 214 status updates should be sent for any change of status and no less
than 4 times per day.
9.8.2. In case of emergencies, Amazon ROC should be immediately contacted per Addendum A.
9.9. Embargoes
9.9.1. Carriers must provide a minimum of three business days’ notice before enacting an embargo on any
lane. Carrier will escalate embargoes, with expected duration, to MMPM via email or in OTR carrier
chime room. Upon initiation of the embargo, carriers should stop accepting tenders from that lane.
• Less than 14-day embargo - if a receiving FC is in the Route Guide for the carrier the load
will be redirected. If receiving FC is not in Route Guide, the carrier will need to provide
a rate to MMPM for approval to execute the load.
• At least 14-day embargo - MMPM will partner with Amazon Global Mile team to close
out the lane.
9.9.2. The embargoed lane will remain turned off until the carrier notifies their MMPM via email that the
embargo will stop. At that point, MMPM will escalate the lane to be added back.
10. Warehouse Transfers (WT)

10.1. It is our expectation that carriers assigned as a primary lane owner will accept all tenders offered to them.
Rejecting a load that is expected to be accepted is considered a service failure and will affect a carrier’s overall
performance rating.
10.2. WT loads are scheduled on a weekly basis with Proactive Additional loads and Ad Hocs scheduled on a less
frequent basis.
10.2.1. Weekly Schedules – Schedules are created on Wednesday afternoon for the following Sunday –
Saturday period. Schedules are sent to carriers both through email and via EDI 204.
• It is very important that carriers compare their emailed schedule to the received 204 tenders.
The emailed schedule is always considered the Master Schedule and if a 204 tender for a load
that is listed on the emailed schedule is not received, then raise a case to the ROC Scheduling
team to advise on the discrepancy.
• Carriers can also verify the schedule by logging into Amazon Logistics and verifying using FMC.
10.2.2. Proactive Additions – As the forecast changes throughout the week, you may receive additional loads
to your schedule. Proactive Additions are loads that are added to your schedule at least 24 hrs.
before scheduled arrival time at shipper. You will receive an email notifying you of the loads and
follow-on EDI 204 tenders.
• Proactive additions are NOT considered ad hocs and carriers are expected to cover these
additional loads. It will be considered a service failure if gone uncovered. If you cannot cover
the load, you will need to raise a case to ROC informing Amazon that you do not have coverage
as soon as possible so secondary capacity can be secured.
10.2.3. Ad Hocs – Primary carriers are expected to support based on their agreement and have 1 hour to
offer capacity for the load before ROC begins evaluating secondary carriers and presenting the load
for bid (primary carriers can still bid past the first hour).
• The only exception to this rule is if the ad hoc load is needed within 1 hour or the primary carrier
loses capacity on the lane.
10.2.4. The transit times used to schedule WT loads only allow for direct non-stop service. Solo drivers may
be used only if no layovers are anticipated. Otherwise team or non-stop relay service is required.
10.3. Arrival at Pick Up
10.3.1. Drivers must provide the VRID upon arrival at the FC. When carriers show up at a building they must
get the load ID confirmed immediately by a representative at that FC. There is no excuse for a carrier
showing up at an FC and not confirming the load number.
10.3.2. Drivers should only be given a single Load ID pertaining to their specific load. Under no circumstances
should drivers show up with multiple Load IDs and select which load to transport.
Page | 17
10.3.3. When a carrier presents the FC with a VRID that the FC cannot confirm, the driver should
immediately contact their dispatch and stay onsite as they can confirm the load with the ROC. The
driver must remain onsite while ROC and Dispatch confirm the load.
10.3.4. The carrier will be provided with a physical copy of the BOL. The BOL is a legal document which will
be used for invoicing and must match what is being transported. Any discrepancies must be
communicated to the ROC.
10.4. Drivers must arrive at or before the scheduled arrival time found on the schedule or the load tender. This
should not be confused with the scheduled pull time. The tender may show both, however this does not
indicate an arrival window and should not be interpreted as such.
10.4.1. Example: The tender may indicate a 1300 arrival time and a 1400 pull time. This does not that the
driver can arrive between 1300 and 1400. The driver is expected to arrive by 1300.
10.5. FCs have an additional 30 minutes allowance after the pull time to complete paperwork and release the trailer
to the driver. Drivers should be prepared to wait up to 30 minutes after the scheduled pull time to be released.
10.5.1. The carrier should notify ROC through late truck reporting on FMC if not released within 30 minutes
after the scheduled pull time. Ensure you include the following in the case:
• Lane
• Scheduled Pull Time
• Load ID
• If the delay will affect the scheduled delivery time
• Any known information regarding the reason for the delay and estimated time of departure
10.6. All WT loads using a subcarrier will need to have the subcarrier assignment made 24 hours prior to pull time.
Subcarriers can be updated in bulk using AWS or one load at a time in FMC.
10.6.1. To bulk upload – Subcarrier assignments need to be uploaded via AWS in the following folder:
Carriers/SCAC/Output/Subcarrier by 1600 PST/PDT daily for loads scheduled to depart after 1600
PST/PDT the following day.
10.6.2. The subcarrier report must be sent in an Excel CSV file in the below format:
Load # Subcarrier
ABC Trucking xxxxxxxxx
XYZ Trucking xxxxxxxxx
10.6.3. To update subcarrier one load at a time – In FMC, search for the load ID you want to update. Once
you find the load, click on the hyperlink in the subcarrier column and fill in the blank subcarrier field
once the Add/Change Sub Carrier window pops up.
10.7. Arrival at Delivery
10.7.1. When arriving at an Amazon facility, drivers must check in with their dispatch and send the
appropriate EDI/Relay delivery message.
10.7.2. If there is a delay at the facility gate, the time of arrival should be the time the line was entered.
10.7.3. If the driver arrives and the facility is closed, the driver must check in with their dispatch and contact
ROC per Addendum A to inform them of the closure. ROC will confirm hours and advise when to re-
deliver.
10.7.4. Drivers must get a signature on the BOL at delivery, including date and time of delivery. Any overages,
shortages, or damages must be noted on the BOL.
10.8. Communications
10.8.1. All WT trips are expected to communicate the same EDI/Relay messages that would be expected for a
standard inbound TL shipment (Section 13 for EDI).
10.8.2. The only message not expected from the carrier would be to inform Amazon of securing a pickup
appointment (EDI XA), since it is on the load tender.
Page | 18
11. General Information (all business types)
11.1. On Time Performance – Arriving on time is critical to our operations and service commitments to our customers.
Amazon actively tracks on-time performance and uses it to evaluate carrier performance. The following are a
few of the root causes considered carrier controllable defects regarding on-time performance (full list can be
found in Section 13):
11.1.1. Dispatch error
11.1.2. Capacity issue – no equipment/drivers available
11.1.3. Medical (to include Covid related issues)
11.1.4. If Amazon fails to receive a delay reason code, this will be considered as a carrier controllable defect
until remedied
11.2. Load/Trailer Quality –The following standards of vehicle condition are required on all Amazon Loads:
11.2.1. The vehicle floor must be well maintained and free from obstructions and damage, such as holes.
11.2.2. The vehicle must be water tight, clean and free of strong odors, especially when delivering food and
healthcare products. All dunnage and nails should be removed prior to entering premises.
11.2.3. The vehicle must be able to withstand the weight and height of a 13’ 6” powered industrial truck (or
forklift) to offload freight.
11.2.4. It is expected that trailers with uneven or corrugated flooring, such as found on refrigerated trailers,
will not be used and will absolutely not be floor loaded. Any floor loaded shipment arriving at an FC
in this condition may be refused.
11.2.5. Load Bars/Tension Straps – Tension straps must not be allowed to hang freely and must be firmly
fixed to the vehicle so that they present no danger to staff while ensuring accessibility to the load.
11.2.5..1. The final pallets placed on a trailer must be secured by tension straps/load bars in order to
prevent freight from falling when doors are opened.
11.2.5..2. Load bars, tension straps, air pillows, and/or diamond corrugated shims must be used to
secure any double stacked pallets that may shift or are next to a large void of space.
11.2.6. All tandems will be towards the rear position when dropped on property.
11.2.7. All doors must be able to swing freely and carrier must have all securement chains/hooks for doors.
11.2.8. Trailer repairs need to be done immediately or the trailer replaced to avoid disruption to trailer
pools. Certain repairs can be done on site, but welding will not be conducted nor will hot work
permits be issued.
11.3. Refusals – A trailer, shipment, or portion of a shipment is subject to refusal at the FC if associates are unable to
safely unload the trailer or verify the contents of the shipment. Any refusals can be reported to the ROC per
Addendum A. Common reasons for freight refusals include, but are not limited to:
11.3.1. Pallets shifting in transit
11.3.2. Pallets/products stacked in a manner that prevents the FC from safely unloading the product
11.3.3. Over-sized floor loaded product that exceeds 100 lbs. (mech lift) and cannot be unloaded by clamp
11.4. Carrier Central and ISA Considerations
11.4.1. Duplicate ISAs – There can only be one ISA per load from the creation of one CRDD. If a delivery
appointment must be changed then the CRDD should be edited, a second CRDD should NOT be
created.
11.4.2. Appointment Defects – Amazon tracks several different appointment defects:
• No Call, No Show (NCNS) – A scheduled delivery that does not occur or occurs after scheduled
arrival time with no prior notification, regardless of reason
• Late Cancellation – An appointment that the carrier cancels 24 hrs. or less before scheduled
arrival time, regardless of reason
• Late Reschedule – An appointment that the carrier reschedules 24 hrs. or less before the
scheduled arrival time, regardless of reason
• Duplicate/Inaccurate PO – A delivery scheduled using PO information that has already been
delivered and Amazon has received in full OR is inaccurate/misleading
Page | 19
• Placeholding – The initial PO(s) used to secure an Appointment is/are removed 24 hours or less
before the Scheduled Arrival Time or missing on receipt
• PO Manifest Accuracy – The number of POs on the Appointment (Carrier-entered) and received
by Amazon against the sum of (i) the total number of POs on the Appointment (Carrier-entered)
received, (ii) the number of POs not on the Appointment (Carrier-entered) but received, and (iii)
the number of POs on the appointment (Carrier-entered) but missing on receipt
• Unit/Carton Count Manifest Accuracy – The number of units/cartons Amazon receives against
the Appointment (Carrier-entered) units/cartons expected
11.4.3. Amazon will continually assess carrier’s ability to comply with Carrier Central guidelines outlined in
the Use Policy by evaluating the percentage of appointments that result in a defect associated with
the carrier’s SCAC, i.e. the Defect Rate.
11.4.3..1. The defect rate includes appointments made by the carrier or by a supplier on the carrier’s
behalf.
11.4.3..2. Carriers that do not adhere to the Carrier Central Use Policy or have high defect rates are
liable to be suspended from Carrier Central.
11.4.4. All carriers with on Carrier Central must have a registered USDOT number with FMCSA, and the SCAC
registered to the USDOT number with the Legal company name matching in NMFTA’s system.
11.5. No Freight – Loads that experience multiple FNRs are liable to be canceled by Amazon. The carrier will be
informed if this action is taken.
11.6. Redirects – Mainly exist in two use cases:
11.6.1. Upstream Redirects – The shipment is reconsigned up until it departs the origin terminal. Attention
will be focused to attempting redirects prior to tender.
11.6.2. Downstream Redirects – When an FC is experiencing significant push, redirects provide a lever to
reduce FC push and free trailers taken up with pushed shipments.
11.6.3. In all redirects, the destination FC on the PO will need to be changed. The Inbound War Room will
create a case in which the carrier will provide rates for the reconsignment. Charges will be reviewed
and the POs will be changed with a redirect VRID provided to the new FC based on the received rates.
Please refer to your contract for pricing guidelines.
11.6.3..1. Response is expected within 24 hours. Prompt responses are critical to properly executing
redirects, so timely feedback is appreciated when the redirect case is initiated.
11.7. Cancelled Orders
11.7.1. When Amazon or the shipper cancels an order, the carrier is required to send the appropriate
cancellation DP code to override any previous delay codes. Carriers must also delete any ISAs tied to
the order. If load is Shipper Cancelled, the carrier must cut a case to the ROC as well for resolution.
11.7.2. There will be times where loads may be cancelled that were already picked up, whether that is due to
a missing check-in signal or BOL in Amazon’s system. If a load is accidentally cancelled by Amazon and
subsequently picked up, the carrier will be required to provide a BOL for the load to Amazon either
through Relay or a case per Addendum A so the load can be retendered to that carrier.
11.7.3. If any invoice is submitted with a cancelled VRID due to such occurrences as incidental transport of a
load that was cancelled but still loaded, the invoice will be rejected and short paid $0. The carrier
should follow up with the ROC to obtain a new VRID for the shipment if transported. The follow-on
invoice must contain a new invoice number and the new VRID provided by the ROC.
11.8. Wrong Carrier – If you arrive for a load and find that a non-tendered carrier has picked up the load you were
tendered, create a case with the ROC per Addendum A for resolution.
11.9. Load Securement - Restraints and seals are necessary on every load.
11.9.1. Prior to loading an empty trailer:
• Live Load – Drivers need to provide at least 2 straps or load bars to the shipper.
• Drop Load – Drivers need to ensure at least 2 straps or load bars are in the trailer before
dropping the trailer.
• If the shipper refuses to act to properly secure the load, the carrier should notify Amazon ROC
immediately and note the exception on the BOL prior to any movement.
Page | 20
11.9.2. All Amazon loads should be secured with seals once en route to Amazon facility and all seals shall
meet the following conditions:
11.9.2..1. All seals must be ISO 17712 compliant and meet the following criteria:
11.9.2..2. Strong and durable against weather, chemical action, and undetectable tampering.
11.9.2..3. Must be easy to apply and seal.
11.9.2..4. Permanently and uniquely marked/numbered, and marked with an easily identifiable
manufacturer’s logo.
11.9.3. All TL shipments, high-value shipments (high or highest as noted in tender), and shipments traveling
more than 250 miles from origin to destination must receive a high-security bolt seal, with seal
number notated on BOL.
11.9.4. Carriers must ensure that seal numbers are recorded on the BOL/manifest and accompanied by a
signature. Upon delivery, FC will match seal number to the documentation and if there is a mismatch
the load may be rejected.
11.9.5. Drivers will not cut seals once enroute to Amazon facility and must leave seals intact during transit to
and upon arrival at Amazon facilities. Amazon’s TOM team are responsible for cutting/removing
seals upon driver’s arrival at an Amazon facility.
11.9.6. For no reason should a seal be broken in transit once the seal has been applied and is en route to the
Amazon facility.
11.9.6..1. If a seal is broken for reasons outside of the carrier’s control, a case shall be created per
Addendum A to receive further guidance and inform all concerned parties.
11.10. Security
11.10.1. A secure yard must be fully-fenced on all sides with monitored entrance/exit points and 24/7 remote
monitoring with regularly scheduled live sweeps.
11.10.1..1. Amazon loads are expected to be monitored entering and exiting the yard and checked to
make sure the proper agents are pulling the loads from the secure yard.
11.10.2. Load value as defined below are included in the load tenders (found in segment L11 labelled ZZ).
Carriers must carry the appropriate insurance for the load to accept the applicable tender.
• Low: less than $100k
• Medium: $100k to $250k
• High: >$250k to $1 MM
• Highest: > $1 MM
11.10.3. High Value Loads – In addition to any mutually agreed upon standards, carrier must also comply with
these requirements for all services involving loads specifically identified as High/Highest value:
• Team drivers are required and at least one driver must remain with the load at all times.
• Tractor must be equipped with GPS tracking and must provide electronic updates.
• No stops allowed within 200 miles of pick up and 200 miles of delivery.
11.10.4. If a trailer must be left unattended, it must be parked in a secure yard as described in Section 11.9.1
11.10.5. Security/Safety at Check-In
11.10.5..1. Check-ins will only be conducted at the guard shack while the driver is in their truck. At no
point should a driver leave their truck unattended or approach a guard shack on foot, this is
considered a safety violation.
11.10.5..2. Amazon will never approach a driver outside of an Amazon facility or request they leave their
truck unattended to check in.
• If anyone, especially someone identifying as an Amazon employee, approaches you
outside of an Amazon site, remain in your truck until inside the Amazon yard,
continue to follow all safety protocols, and contact the ROC.
• If at any point a driver is approached, feel threatened, or witness concerning
behavior, contact law enforcement (call 911). Once law enforcement is engaged,
contact the ROC to inform them of the situation.
11.11. In rare instances, a load may need to be trans-loaded from one trailer to another en route. In these cases, our
expectations are as follows:
Page | 21
11.11.1. An emergency trans-load requires a 3rd party not directly involved in transportation of the shipment
(carrier representative other than the driver, a storage facility representative, etc.) on-site while the
trans-load is taking place. The 3rd party must validate the following:
• Original seal was taken off.
• Unit count is the same once the trans-load is complete.
• New seal is secured and recorded on BOL once trans-load is complete.
• 3rd party monitor must have name and company recorded in BOL.
11.12. Carrier Holidays
11.12.1. Carriers must update their observed holidays on an annual basis for the upcoming year no later than
November 30 by providing those dates to your applicable MMPM/SCM via email. Holidays include
any day that the carrier will be unable to pick up/deliver freight. Changes to the current year’s
holiday schedule must be communicated immediately to your MMPM/SCM.
11.12.2. For any regional holidays not observed by the entire fleet, it is the responsibility of the carrier to
reject applicable tenders immediately.
11.13. Other Expectations:
11.13.1. Carriers must follow Amazon Yard Rules when picking up and delivering at all Amazon facilities (See
Addendum E for list of yard rules).
11.13.2. Driver decorum – Drivers are to maintain a professional and courteous attitude towards Amazon FC
employees, customers and other service providers at all times. Failure to do so may result in the
driver being barred from Amazon loads.
11.13.3. Any damage to driver property or Amazon property must be reported immediately to ship clerk for
documentation and resolution.
11.13.4. Driver Safety – Carriers are expected to ensure the safety of their drivers at all times. This includes
ensuring safe conditions and driver welfare, i.e. if driver reports inability to drive due to lack of sleep
or other reason, then they are taken off the road even if they are within their regulatory drive hours.
11.13.5. Concerning vendors with multiple properties in the same region: To prevent any complication with
pickup locations, each vendor location is expected to have a unique account in the carrier’s internal
system to correctly match the pickup address on incoming tenders.
• This is to prevent all loads for a vendor routing carrier to a singular address on file resulting in a
false Freight Not Ready or warehouses with no knowledge of shipments.
12. Base Rates and Lane Ownership

12.1. Amazon rate requests for primary lanes and subsequent awards will be handled via email. Carriers should
maintain copies of all email correspondence related to rates for their records.
12.2. Amazon will consider rate adjustments on a quarterly basis for all given carrier and lane combination.
12.2.1. Mid-quarter rate adjustments will not be considered from any carriers. Lane ownership based on
provided rates will not change outside of designated bidding periods.
12.2.2. Lane ownership throughout the quarter will continue to be evaluated based on performance.
12.3. It is expected that primary lane owners will accept all loads tendered to them.
12.3.1. Rejection capabilities will be based on the carrier’s agreement and require immediate notification to
Amazon and communication with the ROC team when necessary. Rejections will impact the carrier’s
performance score.
12.3.2. Lane pricing should reflect the commitment needed to handle all the loads in a lane.
12.4. Amazon is licensed for CzarLite International North America 1/10/2011 for all Intra US and cross border
shipments. For Intra Canada, Amazon is licensed for CzarLite Intra Canada 10/22/2018.
12.5. All miles are based off the version of PC Miler Amazon is using at the given time, and will be confirmed when an
award is made. Carrier must invoice Amazon based off these miles. Any mileage discrepancy shall be
communicated to Amazon before submitting invoices whenever possible and addressed before accepting the
award.
12.5.1. All mileage amounts will be rounded to the nearest tenth of a mile and the minimum mileage
Page | 22
amount to be awarded will be 1.0 miles.

12.5.2. Amazon may, with written notice, update the version of PC Miler being used. There will be no
compensation adjustments for any awards prior to the effective date of the update.
12.6. Periodically lanes will be modified, added or eliminated. At times carriers may be taken off of assigned lanes
with little to no notice (every effort will be made to give at least one-week advance notice).
13. EDI
13.1. Any carriers transmitting signals via API will be expected to continue to do so in accordance with the conditions
agreed upon with Amazon.
13.2. EDI 204 messages are used as the motor carrier load tender and they initiate the process of transporting a
shipment with a selected carrier.
13.2.1. EDI 990 messages (response to a load tender) are expected in response to receipt of any load tender
by the carrier.
13.2.2. A detailed breakdown of EDI 204 messages can be found in Addendum F.
Unique Program Identifiers 204 tenders
Mode EDI B207 Notifier
Domestic Inbound Truckload A
Warehouse transfer H
Vendor Returns N/A. Based on PO
Inbound Consolidation (TL) C
Import Linehaul I
13.3. If a given EDI message requires input for payment terms and the shipment contains ARNs as an identifier, the
payment terms MUST be identified as collect. ARNs will only be assigned for WePay/collect shipments.
13.4. EDI 214 messages are the primary method for carriers to communicate shipment status to Amazon. Prior to
contacting carriers for shipment status, Amazon will review the most recent status messages provided by the
carrier to prevent inefficient communications, as well as provide the most accurate picture of our transportation
network.
13.4.1. This guide provides carriers with an explanation of when 214 messages are expected, as well as what
exception codes Amazon expects to see in the 214 messages and when they are appropriate.
13.4.2. In order for these messages to be effective, it is imperative that all shipment status changes are sent
as close to the event as possible. Stale status updates will be of little use. The status message should
always include the actual time the data was gathered or the status event occurred, as well as an
updated ETA if appropriate.
13.4.3. All data in a given 214 is expected to come from the truck carrying the freight via electronic means.
Manual updates are not preferred and considered a last resort, but all updates must be done as
quickly and accurately as possible, regardless of means.
13.4.4. If the carrier is able to communicate GPS data to Amazon for a shipment via 214 messaging, it should
be sent. This will increase visibility and convey a clear picture of carrier actions while assisting in case
resolution, e.g. reported Freight Not Ready events.
13.4.5. For shipments that reschedule the original pickup date, regardless if this is due to missed pickup or
offline communication, the new date must be sent to Amazon in all subsequent 214 messages
utilizing the G62*LP*DATE*TIME segment. This will ensure carrier’s metrics are properly tracked.
Page | 23
• The applicable defect code for the delay shall be sent with the first reschedule date transmission
to explain the cause of the reschedule.
13.4.6. All 214 messages are required to include a pallet/carton count for the associated shipment.
• The pallet/carton count will be communicated using the SDQ*CT*ZZ*ZZ*COUNT (Cartons) and
SDQ*PL*ZZ*ZZ*COUNT (Pallets) segments, as applicable. Carriers may input a value of zero for
either cartons or pallets when necessary.
• Amazon requires either a pallet count or carton count, but both values are preferred.
• If at any point the pallet count changes, the new number of pallets should be reflected in all
following 214 messages.
13.5. EDI Metrics
13.5.1. Shipment visibility is a top concern for Amazon, due to its ability to enable smooth operations
between all parties of the shipping process. There are 3 core metrics and applicable SLAs used to
monitor/evaluate carrier performance as it relates to the EDI messaging, especially 214 messages:
• Signal Compliance – This will evaluate the carrier’s ability to transmit all expected messages
throughout the applicable EDI lifecycle. The most important messages will be the ones regarding
pickup and delivery, especially delays. Carriers will be expected to maintain 100% coverage of
expected signals.
• Signal Latency – Delayed signals provide little use once received. The time from event to signal
receipt will be tracked to evaluate performance. Carriers are expected to transmit messages
within 4 hours of the trigger event, however Amazon strives to receive real-time
communications from carriers to maximize performance.
• Signal/Defect Code Accuracy – Any delay must have a 214 message sent regarding the delayed
pickup/delivery and must be accompanied by the proper defect code. This is highly important
for visibility and establishing the cause of delays, so Amazon can improve processes. Any
messages without a DP/DD delay code will be considered a Carrier Controllable defect. 100% of
delayed events are expected to possess the appropriate DP/DD defect code.
• All three of these metrics are regularly reviewed/reported upon and are critical for determining
the usability of the signals received.
13.6. EDI 214 Expected Shipment Lifecycle
13.6.1. Below are the messages that we expect to receive on every shipment for the specified freight type
(TL, LTL, Intermodal, LTL Consolidation with Linehaul TL, LTL Consolidation with Intermodal).
13.6.2. For shipments that remain in a single status for an extended period of time, the previous status
message should be repeated at minimum every 4 hours.
13.6.3. Included below after the lifecycles, there is a list of exception codes that apply to all freight types
(with an additional list of rail delay codes). These exceptions are split into reasons for delayed pickup
and for delayed delivery.
Page | 24
TL - required shipment lifecycle 214 status messages

Status Reason
Status Definition Amazon Status Description
Code Code
XB NS Shipment Acknowledged Until such time that we initiate 997 messages, the XB 214 will
be your acknowledgement and acceptance of the 204 tender.
AG P1 Estimated Delivery Used to indicate that a drop off appointment request has been
made, include initial CRDD and the time of the request.
X9 NA Delivery Appointment Secured Use this status to indicate that you have received confirmation
on This Date and/or Time of the delivery appointment and the date/time of that delivery.
XA NA Pickup Appointment Secured Use this status to indicate that you have successfully scheduled
on This Date and/or Time a pickup appointment and the date/time of that pickup.
ZP NS En Route to Pickup Location This status should be transmitted when the trip begins for the
driver. This typically is when the driver departs his terminal to
proceed to the pickup location.
X3 NS Arrived at Pickup Location Upon arriving at the pickup location, but prior to checking in.
Typically, upon arrival at the guard shack.
CP NS Completed Loading at Pickup Upon completing the pickup. Sent when trailer is loaded and
Location trailer doors closed.
AF NS Carrier Departed Pick-up This status is distinct from the CP status. Must be sent when
location with shipment driver departs from the location with load. This is a distinct
signal to evaluate time from load completion to departure.
X6 NS En Route to Delivery Location Sent immediately after departure from pickup location and
repeated throughout the entire transit to the delivery location.
Should be sent every 4 hours if no change in status.
X1 NS Arrived at Delivery Location Upon arriving at the delivery location. If there is a delay at the
facility gate, the time should be the time the line/queue was
entered.
D1* NS Completed Unloading at To be sent when trailer is fully unloaded - Applicable for live
Delivery Location unloads only
S1* NS Trailer spotted at Consignee’s Trailer has been dropped for unloading - Applicable for drop
Location trailers only.
CD NS Carrier Departed Delivery Gate time departure following completion of drop/unload -
Location Applicable for all load types, live or drop
*S1 NS and D1 NS are mutually exclusive
Page | 25
LTL - required shipment lifecycle 214 status message

Status Reason Standard Status
Amazon Status Description
Code Code Interpretation
XA NA Pickup Appointment Secured Use this status to indicate that you have received confirmation
on This Date and/or Time on a pickup appointment and the date/time of that pickup. If
you do not need a pickup appointment, transmit this
immediately after the XB.
ZP NS En Route to Pickup Location This status should be transmitted when the truck has been
dispatched to the pickup location.
AF NS Carrier Departed Pick-up This status is distinct from the CP status. Must be sent when
X6 AM En Route to Carrier Cross Dock Shipment is en route to the local pickup cross dock terminal
Terminal
X4 AM Arrived at Carrier Cross Dock Shipment has left the local pickup terminal – Used for all cross
Terminal docks except final cross dock
P1 AM Departed Carrier Cross Dock Shipment has left the local pickup terminal - Used for all cross
X6 NS En Route to Final Cross Dock Used to indicate transit to the delivery terminal location. In
Location transit from the delivery terminal to the FC should utilize the
OD NS message
X4 AG Arrived at Final Cross Dock Shipment has arrived at the local final cross dock terminal -
Location Only used at the delivery terminal
AV P1 Available for Delivery At final cross dock terminal and FC delivery appointment has
been requested.
Z7 NA FC Delivery appointment is set Delivery appointment confirmation received.
OD NS Out for Delivery Sent when departing from final cross dock terminal for delivery
to FC.
facility gate, the time should be the time the line/queue was
entered.
D1* NS Completed Unloading at To be sent when trailer is fully unloaded - Applicable for live
Delivery Location unloads only
S1* NS Trailer spotted at Consignee’s Trailer has been dropped for unloading - Applicable for drop
Location trailers only.
Page | 26
Intermodal - required shipment lifecycle 214 status messages

XA NA Pickup Appointment Secured Use this status to indicate that you have successfully scheduled
AF NS Carrier Departed Pickup This status is distinct from the CP status. Must be sent when
X6 AJ En Route to Delivery Location Used for dray from pickup location to rail ramp. Should be sent
immediately following departure from pickup location.
I1 NS In-Gate at Rail Yard Arrival at the rail ramp
AG P1 Estimated Delivery Used to indicate that a drop off appointment request has been
made, include initial CRDD and the time of the request.
X9 NA Delivery Appointment Secured Use this status to indicate that you have received confirmation
on This Date and/or Time of the delivery appointment and the date/time of that delivery.
RL NS Rail Departure from Origin Train has departed from origin ramp with shipment - Should be
Intermodal Ramp activated by Rail EDI 322 message
X6 NS En Route to Delivery Location On the rail and in transit to delivery location (rail section only)
AR NS Rail Arrival at Destination Train has arrived at destination ramp with shipment - Should be
OA NS Out-Gate at Rail Yard Carrier has taken possession of shipment from rail and
departed the ramp location en route to FC
X6 AG En Route to Delivery Location Dray from Rail ramp to delivery location
facility gate, the time should be the time the line / queue was
entered.
S1* NS Trailer spotted at Consignee’s To be sent when trailer is fully unloaded - Applicable for live
Location unloads only
D1* NS Completed Unloading at Trailer has been dropped for unloading - Applicable for drop
Delivery Location trailers only.
Page | 27
LTL Consolidation with Linehaul TL - required shipment lifecycle 214 status messages
Status Reason
Status Definition Amazon Status Description
Code Code
XA NA Pick-up Appointment Secured Use this status to indicate that you have successfully scheduled
X6 AM En Route to Carrier Cross Dock Shipment is en route to the local pickup cross dock terminal
Terminal
X6 NS En Route to Delivery Location Shipment is transiting between cross docks - Used for all cross
docks except final cross dock
X6 AZ En Route to Final Carrier Cross Shipment is en route to final cross dock/consolidation Facility
Dock/ “Next Carrier” Facility
X4 AZ Arrived at Final Carrier Cross Shipment has arrived at the local final cross dock terminal -
Dock/ “Next Carrier” Facility Only used at the delivery terminal
R1 NS Received Shipment from Indicates linehaul TL carrier has taken shipment as a
Previous Carrier consolidated load
P1 AZ Departure from “Next Carrier” Indicates shipment has departed Consolidation Facility on Line
Facility haul
X6 NS En Route to Delivery Location Repeated throughout the entire transit to the first delivery
location.
facility gate, the time should be the time the line / queue was
entered.
D1* NS Trailer spotted at Consignee’s To be sent when trailer is fully unloaded - Applicable for live
S1* NS Completed Unloading at Trailer has been dropped for unloading - Applicable for drop
*S1 NS and D1 NS are mutually exclusive.
Page | 28
LTL Consolidation with IM - required shipment lifecycle 214 status messages

XA NA Pick-up Appointment Secured Use this status to indicate that you have successfully scheduled
driver. This typically is when the driver departs his terminal.
X6 AZ En Route to Final Carrier Cross Shipment is en route to final cross dock/consolidation Facility
Dock/ “Next Carrier” Facility
X4 AZ Arrived at Final Carrier Cross Shipment has arrived at the local final cross dock terminal -
Dock/ “Next Carrier” Facility Only used at the delivery terminal
R1 NS Received Shipment from Indicates linehaul IM carrier has taken shipment as a
Previous Carrier consolidated load
P1 AZ Departure from “Next Carrier” Indicates shipment has departed Consolidation Facility on Line
Facility haul
X6 AJ En Route to Delivery Location Used for dray from pickup location to rail ramp. Should be sent
immediately following departure from pickup location.
I1 NS In-Gate at Rail Yard Arrival at the rail ramp
RL NS Rail Departure from Origin Train has departed from origin ramp with shipment - Should be
X6 NS En Route to Delivery Location On the rail and in transit to delivery location (rail section only)
AR NS Rail Arrival at Destination Train has arrived at destination ramp with shipment - Should be
OA NS Out-Gate at Rail Yard Carrier has taken possession of shipment from rail and
departed the ramp location en route to FC
X6 AG En Route to Delivery Location Dray from Rail ramp to delivery location
gate, the time should be the time the line/queue was entered.
D1* NS Trailer spotted at Consignee’s To be sent when trailer is fully unloaded - Applicable for live
S1* NS Completed Unloading at Trailer has been dropped for unloading - Applicable for drop
*S1 NS and D1 NS are mutually exclusive.
Page | 29
13.7. Exceptions
13.7.1. Below are the exceptions for all freight types. Exception messages should be sent to indicate
applicable delays and should immediately be followed by a new 214 status message from the
appropriate lifecycle list.
13.7.1..1. Example: A TL shipment is en route to delivery and breaks down. The carrier should transmit
a DP AI message (mechanical issue) and then immediately resume transmitting X6 NS with
the new ETA.
13.7.2. Shipments that arrive late without an exception message will be viewed as a service failure. For
purposes of review, messages without a DP/DD code will be considered a Carrier Controllable defect.
INBOUND DELAYED PICKUP EDI MESSAGES

DP AG Amazon Controllable: Carrier Central website crashes, or is unable to accept the appointment
Delivery Appointment request. This message should not be used if the carrier is having
Portal Issue problems with accessing the internet.
Example:
When trying to submit a CRDD Request, the website continues to
timeout.
DP RR Amazon Controllable: Carrier did not receive either the EDI 204 Tender OR the Tender
Delay in Receiving Confirmation Email from Amazon
Tender Example:
1. The tender isn’t received in the carrier’s system until after FRD.
2. The tender/confirmation does not appear in the carrier’s system.
DP CA Amazon Controllable: This is only applicable for when the shipment was cancelled by Amazon.
Amazon Cancelled This message should not be used for rescheduled shipments.
Shipment Example:
Amazon cancelled the shipment prior to carrier picking up from the
shipper.
DP IC Amazon Controllable: FOR TL & IM SHIPMODES ONLY: Amazon did not send the ISA
No ISA Confirmation Confirmation.
Example:
Amazon never sent the ISA Confirmation.
DP FR Amazon Controllable: FOR TL & IM SHIPMODES ONLY: Amazon rescheduled the delivery
FC Rescheduled appointment at the FC.
Appointment Example:
The FC rescheduled a carrier’s delivery appointment for 2 days later, so
the carrier picked up from the shipper 2 days late.
DP TP Amazon Controllable: Amazon did not send accurate tender pick up information.
Incorrect Tender Example:
Pickup Information A tender was sent with the wrong pickup location.
DP BL Amazon Controllable: Carrier has stopped transporting to certain FCs due to a backlog of their
No Pickup Capacity loaded trailers at that specific site.
due to FC Backlogs Example:
Carrier has embargoed LAX9 due to trailer backlog.
DP SE Amazon Controllable: The carrier arrives at the shipper without the proper notification of any
Special Equipment special equipment needed to load and transport the shipment.
Required Example:
Shipper requires a lift gate to load shipment but carrier was not notified
and arrives without a lift gate.
Page | 30

DP CT Carrier Controllable: Carrier did not have the capacity to pick up the shipment.
Capacity Issue Example:
The carrier did not have enough drivers to pick up the load on time.
DP DE Carrier Controllable: Carrier did not provide accurate dispatch information.
Dispatch Error Example:
The carrier dispatched the truck to the wrong pick up address.
DP DR Carrier Controllable: A delay due to any issue that the driver had control over.
Driver Error Example:
1. The driver was delayed due to a speeding ticket.
2. The driver ran out of gas.
DP AI Carrier Controllable: Mechanical issues on equipment owned by the carrier.
Mechanical Issue Example:
The truck’s battery died.
DP SC Carrier Controllable: Delay was caused from the carrier not submitting a CRDD request to
Delay Submitting Amazon.
Delivery Appointment Example:
Request to Amazon A truckload carrier received the tender, but did not submit a CRDD
request until 4 days later.
DP PN Carrier Controllable: FOR LTL & NSXD SHIPMODES ONLY: Delay was caused from a pickup at
Previous Non-Amazon a previous non-Amazon shipper.
Load Delay Example:
The driver was delayed by a non-Amazon pick up shipper, thus the
driver’s next pick up from an Amazon shipper was delayed.
DP AE Carrier Controllable: Delay was caused by carrier arriving without the sufficient equipment
Additional Equipment required to complete the pickup.
Needed Example:
Carrier arrives without the requisite tension straps/load bars required.
DP DS Carrier Controllable: FOR LTL & NSXD CARRIERS ONLY: Delay was caused because the pickup
Non-Daily Service location was not serviced by the carrier daily.
Area Example:
Shipper was located in west Kansas and the LTL carrier only routed
through the pickup location 3 days a week.
DP AC Non-Controllable: Delay was caused from either a vehicle accident or an accident at the
Accident shipper’s pickup location.
Example:
The shipper ran a forklift into the carrier’s truck.
DP DO Non-Controllable: DOT Delay was caused from a DOT Inspection.
Inspection Example:
Conduct of a DOT Inspection delayed the carrier’s transit.
DP WR Non-Controllable: Delay was caused by weather conditions.
Weather Example:
The driver could not get to the shipper’s location due to a snow storm.
DP TR Non-Controllable: Delay was caused by traffic en route to the pickup location.
Traffic Example:
The driver was 3hrs late to the shipper due to significant traffic on
highway to facility.
Page | 31
DP MD Non-Controllable: Delay was caused by medical issues with the driver or an employee at
Medical the pickup location.
Example:
1. The driver had an unexpected medical emergency.
2. The driver contracted Covid-19
DP HO Non-Controllable: A load cannot be completed due to a closure on a holiday.
Holidays Example:
Carrier is scheduled for pickup on a holiday when they aren’t operating
or arrives at shipper for pickup and they are closed due to holiday.
DP AM Vendor Controllable: Shipper requests a different pickup time than scheduled in advance of
Vendor Requested the driver arriving at the pickup location. NOTE: Any offline reschedules
Pickup Reschedule should be communicated clearly to Amazon for tracking purposes.
Example:
The shipper requested the carrier pickup 2 days later than the original
pickup date.
DP DC Vendor Controllable: The shipper shipped the load with a different carrier.
Shipped Via Different Example:
Carrier The carrier arrived at the shipper’s facility to find that the shipment had
already been picked up by a different carrier.
DP VC Vendor Controllable: Shipper cancels the pickup in advance of the carrier arriving.
Vendor Cancelled Example:
Pickup The day before a pickup, the shipper cancels the pickup.
DP NF Vendor Controllable: The driver has arrived at the shipper and there is no freight for the
No Freight at Pickup driver to pickup or the shipper says the freight will be ready at another
time.
Example:
The carrier arrives at the pickup location, but there is no freight ready
for pickup.
DP VL Vendor Controllable: The shipper’s facility is closed when the driver arrives.
Vendor Closed Example:
The driver arrives to find out the shipper is only open 3 days a week and
is closed upon arrival.
DP LD Vendor Controllable: Shipper does not load the trailer on time.
Vendor Loading Delay Example:
The shipper takes 8hrs to load their pallets in the trailer, when the
carrier planned 1 hr.
DP VR Vendor Controllable: The shipper is unable to be prepared for pickup due to requiring 24hrs
Vendor Requires 24hr prior to a pickup appointment to be prepared.
Notice Example:
The carrier requests a same day pickup, but the shipper says they need
24hrs to schedule a pickup appointment.
DP VN Vendor Controllable: The shipper is unable to be prepared for pickup due to requiring 48hrs
Vendor Requires 48hr prior to a pickup appointment to be prepared.
Notice Example:
The carrier requests a same day pickup, but the shipper says they need
48hrs to schedule a pickup appointment.
Page | 32
DP VS Vendor Controllable: This message is only used when the shipper provides no response the
No Vendor Response carriers pickup requests
When Scheduling Example:
Pickup The shipper does not respond to the carrier’s emails and calls to
schedule a pickup appointment.
DP VV Vendor Controllable: FOR LTL & NSXD SHIPMODES ONLY: Delay was caused from a pickup at
Previous Amazon a previous Amazon shipper.
Vendor Load Delay Example:
The driver was delayed by a previous Amazon shipper, thus the driver’s
next pickup from an Amazon shipper was delayed.
DP SR Vendor Controllable: The shipper has loaded the drop trailer on site but does not promptly
No Trailer Swap arrange for pickup.
Requested Example:
Shipper requests pickup and new drop trailer 3 days after it was loaded.
DP PQ Vendor Controllable: Upon arrival at the shipper, the load is not in a quality to be shipped
Poor Load Quality due to conditions such as damage or poor preparation.
Example:
The driver arrives to a load with broken product or on broken pallets.
DP RD Vendor Controllable: FOR LTL & NSXD SHIPMODES ONLY: The carrier may receive freight for
Dry Run, No Freight at other customers but receives no Amazon freight when it was expected.
Pickup Example:
The shipper has a shipment ready for Company, Inc. but not the
expected Amazon shipment.
DP DT Vendor Controllable: Driver has waited the requisite time to receive a load from the shipper
Driver Time Exceeded, and the freight is still not ready.
No Freight at Pickup Example:
After waiting 30 min. gate to gate, the shipper stated they have not
completed pulling the full shipment for an LTL carrier.
INBOUND DELAYED DELIVERY EDI MESSAGES

DD CA Amazon Caused: This is only applicable for when the shipment was cancelled by Amazon.
Amazon Cancelled This message should not be used for rescheduled shipments.
Shipment Example:
Amazon cancelled the shipment prior to completion of transport.
DD CI Amazon Caused: The carrier submits a CRDD request, but the website will not accept one
CARP Portal Would or more of the ARNs.
Not Accept ARN Example:
The carrier tries to submit a CRDD Request, but the delivery
appointment portal will not accept one or more of the ARNs.
DD XF Amazon Caused: Shipment is late due to traffic upon arrival at the FC to get into the
Traffic Caused By FC yard.
Example:
The carrier waits in a mile of traffic to enter the FC.
DD CC Amazon Caused: Did Amazon did not send an ISA Confirmation.
Not Receive ISA Example:
Confirmation The carrier submitted a CRDD request, but never received an ISA.
Page | 33
DD BS Amazon Caused: Amazon did not accept the Freight at the FC. This code can only be used
Refused Freight once the driver is at the FC and has accessed the yard.
Example:
The FC did not accept the freight due to improper restraints.
DD FX Amazon Caused: Amazon redirects the shipment to another FC.
Freight Redirect Example:
The shipment was redirected to another FC due to the FC yard being
full, which added another day of transit time.
DD TT Amazon Caused: The ISA did not provide enough transit time for the carrier.
Insufficient Transit Example:
Times The carrier had an ISA for the next day, but the driver needed 4 days
transit time.
DD FD Amazon Caused: FC Prior to arriving at the FC, the ISA was rescheduled or deleted by
Deleted/Rescheduled Amazon.
Example:
2 days before arriving at an FC, the carrier receives a new ISA from the
FC for a new date.
DD AC Non-Controllable: Delay was caused from a vehicle accident or accident at the FC.
Accident Example:
Carrier’s truck was rear ended by a car.
DD DO Non-Controllable: DOT Delay was caused from a DOT Inspection.
Inspection Example:
Conduct of a DOT Inspection delayed the carrier’s arrival at the FC.
DD WR Non-Controllable: Delay was caused by weather conditions.
Weather Example:
The driver could not get to the FCs location due to a snow storm.
DD TR Non-Controllable: Delay was caused by traffic en route to the FC.
Traffic Example:
The driver was 8hrs late to the FC from traffic during transit, and the
time had rolled over to the next day.
DD BD Non-Controllable: The driver was delayed due to border inspections.
Border Delay Example:
When crossing into the US from Canada, the truck was delayed for 8hrs
because the border patrol inspected the truck.
DD MD Non-Controllable: Delay was caused by medical issues with the driver or an employee at
Medical the FC location.
Example:
The driver had a medical emergency.
DD AI Carrier Controllable: Mechanical issues on equipment owned by the carrier.
Mechanical Issues Example:
The truck had a flat tire.
DD CP Carrier Controllable: The carrier did not have available capacity to deliver the shipment on
Capacity time.
Example:
An LTL carrier did not have enough drivers for the 2nd leg of the
shipment.
Page | 34
DD IA Carrier Controllable: Carrier’s dispatcher did not provide accurate information to the driver.
Dispatch Error Example:
The carrier dispatched the truck to the wrong delivery address.
DD DR Carrier Controllable: A delay due to any issue that the driver had control over.
Driver error Example:
The driver was delayed due to a speeding ticket.
DD TD Carrier Controllable: FOR LTL & NSXD SHIPMODES ONLY. Delays at the cross dock outside of
Transit Delay the issues listed above.
Example:
The shipment was delayed at the cross-dock due to load movement.
DD VD Vendor Caused: Any shipper issue that caused a delivery delay.
Vendor Delay Example:
The shipper was late loading the trailers
Carrier Controllable: Rail Delays FOR IM SHIPMODE ONLY. For specific rail delay codes, refer to the Rail
Only Delayed Delivery EDI codes below
Page | 35
RAIL ONLY INBOUND DELAYED DELIVERY EDI MESSAGES

Carrier Controllable: Train failure such as derailment.
DD RA
Rail Accident
Carrier Controllable: Scheduled train cancelled due to low overall customer volume, among
DD RN
Rail Annulment other operational considerations.
Carrier Controllable: Not enough chassis to either pull from origin to rail ramp, or pull from
DD RC
Rail Capacity Chassis rail ramp to deliver to destination.
Carrier Controllable: Not enough containers in market to pull from origin.
DD RT Rail Capacity
Container
Carrier Controllable: Not enough railroad flatcars to pull containers from origin rail ramp to
DD RF
Rail Capacity Flatcar destination rail ramp.
Carrier Controllable: Heavy influx of trains on railroad lines resulting in waiting trains for
DD RI
Rail Congestion Line others to pass by.
Carrier Controllable: Heavy influx of trains delivering into or departing from railroad ramps,
DD RR
Rail Congestion Ramp resulting in waiting trains for others to pass by.
Carrier Controllable: Scheduled trains are combined due to low overall customer volume,
DD RG
Rail Consolidation among other operational considerations.
Carrier Controllable: Railroad has notified dray partner >2 hours after arrival of train for
DD RL
Rail Late Notification pickup to deliver to customer.
Carrier Controllable: Train is delayed without further reason. Only a valid code if requiring
DD RE
Rail Late Train further investigation with railroad.
Carrier Controllable: Railroad flatcar is set out as bad order and must be repaired before
DD RM Rail Mechanical being allowed to join another train.
Flatcar
Carrier Controllable: Locomotive failure such as engine burn or need for axle repair.
DD RO Rail Mechanical,
Locomotive
Carrier Controllable: Weather related incident where tracks are unstable due to water
DD RH
Rail Washout running under track ballast or other weather-related track issue.
Non-Controllable: Rail Load left on ground at facility for scheduled train. Generally due to
DD RS
Missouts influx of ramp in-gate volume and low prioritization of freight.
Non-Controllable: Rail Railroad union employees on strike.
DD RX
Strike
Non-Controllable: Rail Days rail ramps are closed due to union holidays.
DD RY
Holiday
Non-Controllable: Rail Train delayed due to maintenance needed on tracks because of heat
DD RW Maintenance of Way kinks, rail splits, ties, etc.
Page | 36
14. Invoice Process and Off-Manifest Resolution
14.1. EDI 210 - Invoices should be sent daily via the EDI pipeline. (See Addendum B for EDI details.)
14.2. Non-EDI invoices will only be accepted on a case by case basis. Please contact finance directly at trans-
invoicing@amazon.com for permission to submit non-EDI invoices.
14.3. All invoices must contain accurate invoice date based on the date that invoice was submitted.
14.4. Shipments that contain ARNs as identifiers MUST be identified as collect. ARNs will only be assigned for
WePay/collect shipments
14.5. All invoices must contain a valid account number mapped based on the program type. Account numbers will be
provided to you, reference Addendum B for format. If you do not have account numbers prior to billing please
contact trans-invoicing@amazon.com
14.6. All invoices must contain valid shipment reference numbers:
14.6.1. Inbound/Imports Linehaul:
• Tender ID – Included on the 204 tender. Neither Null or #NA will be accepted.
• PO Number – Sent in routing request email
• ISA number – Received as part of appointment notification after submitting request in Carrier
Central. Will need to use the ISA that the load was delivered with.
• ARN number – ARN included in 204 tender. There may be multiple ARNs received in a tender.
14.7. Consolidated Invoices – (Applicable for LTL) Carriers should create a Master BOL for every tender ID. All loads on
a particular tender ID, picked on a particular date, and shipped from the same origin to the same destination
should be consolidated on a single invoice number.
14.8. Carriers are requested to submit base rate/fuel invoices and accessorial charges on the first invoice and on a
single invoice for the most expedited payment.
14.9. Multiple invoices – For any load with multiple invoices, each invoice must have a unique invoice number. The
identifying numbers contained within the invoice shall remain the same.
14.9.1. Reused invoice numbers with different alphanumeric identifiers will not be accepted. The
supplemental invoices must have the same reference ID (load number/tender ID/VRID).
14.9.2. In the event that any accessorial takes longer than base rate/fuel charges, carriers may submit
separate invoices for base rate/fuel charges and accessorial charges but this will delay payment.
14.9.3. Any invoices that are being sent due to previously being short paid, the new invoice for the remining
amount must use the original invoice number with the suffix “BD”. This invoice shall only include the
amount due, NOT the full invoice value.
14.10. All invoices with correct shipment reference and amounts will be cleared and the payment will be sent out
based on the carrier’s payment terms. Amazon pays invoices based on receive date, not invoice date.
14.11. In the event of any invoice issues, Amazon will contact the carrier and may require them to submit supplemental
documentation of the charges.
14.12. Invoices with any issues are put “on-hold” and carriers are requested to provide applicable supplemental
documentation within 10 days corresponding to any email requests from Amazon to assist in controllership
teams turn around. Typical backup documentation includes:
• Email communication with Amazon showing approval for base rate/accessorial charges
• Proof of Delivery document (BOL) in case of canceled loads or split tenders
14.13. Amazon are not liable to pay any invoices that are submitted greater than 180 days after ship date.
14.13.1. Any invoices billed after 180 days will be disputed with the carrier. Based on carrier justification, the
invoice will either be short paid $0 or paid with business approval.
14.13.2. It should be made clear to Amazon if any delays were due to shipper or Amazon action.
14.14. Amazon will contact the carrier via email biweekly with a list of invoices that were flagged during audit or failed
for a given reason.
14.15. The following are typical issues that can result in payment delays:
14.15.1. Invalid Tender ID/shipment reference (Load ID, VRID, PO# or ISA number)
14.15.2. Invalid Account Number as applicable to respective business type.
Page | 37
14.15.3. Base rate variance/Fuel surcharge variance

• If the rates billed appear incorrect, Amazon will short pay the invoice based on the amount
Amazon deems correct for initial payment.
14.16. For any invoices that are being sent due to previously short paid invoices, as described above, the new invoice
for the remining amount must use the original invoice number and contain the suffix “BD”. These invoices
should only include the amount due, NOT the entire invoice value.
14.16.1. Cancelled Load
• If load indicates to Amazon that it was cancelled, however it was picked up and delivered by
carrier, the carrier will be required to contact the ROC per Addendum A and obtain a new VRID.
The delivered load will then be billed using the new VRID.
14.16.2. Split Shipments
• In the case that a split occurs, the original VRID cannot be used to bill both shipments.
• As soon as the carrier becomes aware that the tender has been split, the ROC should be
contacted immediately via emailing the appropriate email queue found in Addendum A with an
updated BOL so that a VRID can be assigned for the remaining portion of the shipment.
14.16.3. Invalid Tenders
• Invoices with Invalid tender ID’s would be purged directly. These will need to be rebilled with a
valid VRID using a different invoice number.
14.17. Accessorial Charges
14.17.1. Accessorial charges are limited only to those that are clearly outlined in the carrier’s current contract
or applicable agreement and use Amazon approved charge codes.
14.17.2. Accessorial charges must be invoiced under their appropriate charge code and not added to the base
charge. Failure to do so will result in purging or short payment.
14.17.2..1. If accessorial charges are sent on a separate invoice, they must not include base rate and fuel
surcharges.
14.17.2..2. Detention charges should be invoiced to one tender on a given ISA.
14.17.3. Certain accessorial charges must be validated upon submission to controllership team with required
documentation.
14.17.3..1. These events are covered in detail in the Carrier Invoice Manual but include detention fees.
14.17.3..2. For trailer detention/layover charges, a case must be raised as charges begin accruing.
14.17.3..3. TL carriers must submit accessorial approval requests to the Controllership team at cs-
edi@amazon.com with the subject line format: [VRID][SCAC] [CHARGE CODE][CHARGE
AMOUNT][CASE ID] and accompanied by any corresponding documentation/ROC cases.
14.17.3..4. IM carriers must submit accessorial approval requests to the Controllership team at pi-mm-
accessorial@amazon.com with the subject line format: [VRID][SCAC] [CHARGE
CODE][CHARGE AMOUNT][CASE ID] and accompanied by any corresponding documentation
or ROC cases. Operational assistance and cases can be raised at intermodal-cm-
accessorials@amazon.com.
14.17.3..5. US/CA LTL carriers must submit accessorial approval requests to the Invoicing/Controllership
team at pi-ltl-accessorial@amazon.com with subject line format: [VRID][SCAC][CHARGE
CODE][CHARGE AMOUNT][CASE ID] with timestamp information obtained by ROC
accompanied by any corresponding documentation or ROC cases.
14.17.3..6. Canadian carriers must submit accessorial approval requests to the Controllership team at
canadapayments@amazon.com with the subject line format: [VRID][SCAC] [CHARGE
CODE][CHARGE AMOUNT][CASE ID] and accompanied by any corresponding documentation
or ROC cases
14.17.3..7. Trailer detention charges must have a case submitted to the controllership team as soon as
charges begin accruing and must include scheduled appointment time, actual arrival time,
and actual depart time.
14.17.4. Carrier can submit invoices after the required information is sent to the controllership team, however
an accessorial may be denied during auditing as required.
Page | 38
14.17.5. Any accessorial charges submitted after 180 days of occurrence will be denied.
14.18. Aging Statements
14.18.1. Invoice statuses can be viewed on the AWS portal, which will be published on a weekly basis.
14.18.2. TL carriers are required to submit aging statements every month per Amazon emails. LTL/IM carriers
will NOT be required to submit an aging statement but must submit one if requested in emails sent
from Amazon.
14.18.3. Aging statements should be sent to trans-invoicing@amazon.com.
14.18.3..1. Aging statements must be submitted no later than 3 business days from the last day of the
month, with activity (based on ship date NOT invoice date) through close. A standard excel
statement template will be provided in the aging request email.
14.18.3..2. If you foresee any potential delays with submitting your statement to us by the deadline
given, please let us know ASAP and tell us what date you will be submitting the aging.
14.18.3..3. Do not alter the subject line of the email request and reply all in your response.
14.18.4. Aging Statements are not recognized as invoices and used internally only for reconciliation purposes.
Please make sure all invoices are submitted via EDI 210.
14.18.4..1. Please include information on loads in transit and loads not yet invoiced
14.18.5. Amazon prioritizes payment of past due invoices based on their presence on an aging statement. Any
past due invoices missing from the aging statement may not be properly prioritized.
14.18.6. Please include the account numbers and account description in your aging statement.
14.18.7. Ensure that there are no duplicate invoice numbers in the Aging statement.
14.18.8. If you foresee any delays with submitting your statement by the deadline given, please communicate
the delay ASAP and the date by which it will be submitted.
14.18.8..1. Carriers who consistently are late sending aging statements or do not send statements may
have their account put on hold.
14.18.9. Retain all email communication regarding ad-hoc rate or accessorial approvals as needed for future
documentation purposes.
14.18.10. Remittances for payments will be sent for every invoice paid. Remittances will be sent to an email
address you specify. If you need to change the email address, please send an email to trans-
invoicing@amazon.com with the request.
14.18.10..1. If you do not receive remittance details please email trans-invoicing@amazon.com with
payment amount, payment number, and payment received date.
14.18.11. Any changes in the bank account information need to be provided to trans-invoicing@amazon.com at
least three weeks in advance.
14.19. All issues regarding invoicing should be addressed to trans-invoicing@amazon.com and escalations sent to
MMPM/carrier manager and trans-finance@amazon.com
14.19.1. For TL/IM invoice dispute issues, emails containing applicable documentation should be sent to mm-
disputes@amazon.com.
14.20. Credit Notes & Balance Dues
14.20.1. Prior to sending any credit notes or balance due invoices please email trans-invoicing@amazon.com
for confirmation.
14.20.2. Credit notes should be submitted via EDI unless you have received approval to send it otherwise
14.21. Metrics and Reporting
14.21.1. Aging Reports will be published on a weekly basis to Carriers’ respective folders in AWS. The files will
be available under the location: SCAC >> Input >> Weekly >> Invoice Aging Reports.
Page | 39
Addendum A – Case Management and Resolution
1. Relay app users are expected to submit a case/contact Amazon through the Relay app. This will ensure real time
response and resolution.
2. For all non-Relay app carriers, use the following steps below for issue resolution:
2.1. Carriers Steps:
2.1.1.Submit support cases through FMC.
2.1.2.If the carrier does not receive the correct support, consider direct email based on the issues below.
2.1.2.1. Ensure that your SCAC is included in the subject line of the email.
2.1.3.Any issue that still has not been resolved should be brought to the attention of the carrier’s MMPM/SCM.
3. Available Email Queues:

• roc-ib-na-carrier-missed-pickup@amazon.com – This queue is dedicated to carrier missed pickup support and
freight-not-ready occurrences.
• roc-ib-na-split-shipments@amazon.com – For communication shipments being split in any manner or if non-
tendered/cancelled freight was received. Splits must be communicated immediately to enable follow on billing.
• noc-na-misships@amazon.com – Reporting any cases of a misship regarding Amazon.
• noc-na-ib-late-trucks@amazon.com – To be used when carrier is running late to delivery appointment (contact
IB Scheduling team in Section 3 for assistance).
• toc-ib-na-scheduling@amazon.com – Any issues related to appointment portal or scheduling adjustments. Also
used to report unloading delays at FC.
• toc-ib-na-po-bol-mismatch@amazon.com – For PO request for any re-open and FC flipping support. This will
allow carriers to reserve ISA for delivery or to address issue of PO not being accepted in appointment portal.
• toc-ib-na-pod-drm@amazon.com – Used for POD [E-BOL] request.
• toc-ib-na-freight-refusals@amazon.com – In the case that an FC refuses the carrier’s load (safety issues, wrong
sort type, etc.).
• noc-na-ib-guard-shack-rejections@amazon.com – For cases where the driver is rejected at the guard shack for
any reason, such as ISA issues.
• toc-ib-na-other-issues@amazon.com – A generic queue to be used when the carrier did not receive the
appropriate support through FMC or no other email queue fits carrier’s problem. This queue will only act to
confirm routing/tender information, forward carriers to the correct support, and resolve issues that do not have
their own queue.
4. Amazon Freight Operations DM Shipper Support: If any issues remain unresolved and are pending carrier
action/information, Amazon associates may reach out to carriers through a phone call in an attempt to resolve
cases.
4.1. The only information that will be communicated from Amazon to the carrier will include their first name and
last initial/team, vendor information, and shipment identification details (e.g. PRO #, ISA, etc.). Any other
information requested may not be given and associates’ full names/personal identifiable information will NOT
be given out.
4.2. This final attempt at case resolution is highly dependent on carriers maintaining accurate contact information
with Amazon. All contact information that should be used by Amazon for case resolution should be kept up to
date with their SCM/MMPM on a monthly basis and upon any changes.
IMPORTANT: Amazon is in the process of eliminating direct email queues and will be shifting non-Relay app resolution
solely to support cases submitted through FMC. Once this occurs, it will be appropriately updated in this manual.
Page | 40
Addendum B – EDI 210 Invoice Guide
Less Than Truckload

Reference X12 210 Invoice Corresponding X12
Reference Note
Description element 204 element
In all cases, Tender ID should be sent.
B303 element from B204 element from
TENDERID Tender ID Note: Please ensure to populate
the B2 segment B2 segment
Consignee address at package level.
In all detention invoices, ISA number or
Appointment ID
B303 element from B204 element from should be sent as Tender ID.
TENDERID (Only Detention
the B2 segment B2 segment Note: This should be done only for
Invoices)
detention invoices
ARN must be populated to N9*BX
segment.
L1101 element
Amazon Reference N902 when N901 = If no EDI 204, manual ARN # must be
ARN when L1102 = BX in
Number BX in Loop 0463 same as provided by ROC.
Loop 0300
Note: Send all ARNs that are included in
the tender.
L1101 element If carrier didn’t obtain the Appointment
N902 when N901 =
ISA Appointment ID when L1102 = AO in ID, N9*AO segment will not need to be
AO in Loop 0463
Loop 0300 populated on the X12 210 invoice
PO must be populated to SPO1 element
on the X12 210 invoice.
Inventory PO - A letter followed by 7
Purchase Order SPO01 element in OID02 element in numbers, example L1234567.
PO
Number Loop 0465 Loop 0350 Non-Inventory PO - Starts with 1000 or
1001 (US), 3000 or 3001 (CA), example
1000444556.
Note: Send all POs in Tender ID.
Carrier Assigned N902 when N901 = PRO must be populated to N9*CN
PRO
Tracking ID CN in Loop 0463 segment
B306 Invoices must contain valid dates:
(Invoice/billing) - Invoice date: Invoice is submitted
Date
POD01 (Delivery) - Delivery: Load is delivered
G6202 (Ship) - Ship: Date of shipping
Appropriate program All invoices must contain valid account #
Account # N104
account # based on program.
If carrier didn’t obtain the BOL, N9*BM
N902 when N901 =
BOL Bill of Lading segment will not need to be populated
BM in Loop 0463
on the X12 210 invoice
N902 when N901 = For Vendor Return shipment, VRET must
VRET Vendor Return ID
RZ in Loop 0463 be populated to N9*RZ segment
Weight
Freight Class
From Zip
To Zip
Page | 41
TL Inbound/Vendor Return
Reference Note
There is NO TENDERID for manual
routing, B303 element will not need to
be populated with any value in this case.
B303 element from B204 element from
TENDERID Tender ID In all other cases, Tender ID should be
the B2 segment B2 segment
sent.
Note: Please ensure to populate
segment.
L1101 element
Loop 0300
the tender.
N902 when N901 =
AO in Loop 0463
Loop 0300 populated on the X12 210 invoice.
on the X12 210 invoice.
Inventory PO - A letter followed by 7
Purchase Order SPO01 element in OID02 element in numbers, example L1234567.
PO
Number Loop 0465 Loop 0350 Non-Inventory PO - Starts with 1000 or
1001 (US), 3000 or 3001 (CA), example
1000444556.
Note: Send all POs in Tender ID.
PRO
Date
Account # N104
N902 when N901 =
BM in Loop 0463
Distance from
Miles SDQ04
source to destination
From Zip Zip code of pickup N403
To Zip Zip of drop N403
Page | 42
TL Warehouse Transfers
Reference Note
There is NO TENDERID for manual
routing, B303 element will not need to
be populated with any value in this case.
Tender ID/Load B303 element from B204 element from In all other cases, Tender Id should be
TENDERID
Number the B2 segment B2 segment sent.
For TL WT Tender Id = Load Id
Note: Please ensure to populate
L1101 element
N902 when N901 =
ISA Appointment ID when L1102 = AO in Does not apply for WT. Not required.
AO in Loop 0463
Loop 0300
L1101 element
Amazon Reference N902 when N901 = ARN must be populated to N9*BX
Number BX in Loop 0463 segment
Loop 0300
PRO
N902 when N901 =
BM in Loop 0463
Date
Account # N104
Distance from
Miles SDQ04
source to destination
From Zip Zip code of pickup N403
To Zip Zip of drop N403
N902 when N901 = Only TL carriers are required providing
QY in Loop 0463 this reference. The possible values are
following:
1) SOLO – N9*QY*SOLO
2) TEAM – N9*QY*TEAM
LOADTYPE Load Type
3) RELAY – N9*QY*RELAY
• SOLO means single driver

• TEAM mean a team of drivers
• RELAY means shipment delivery
involves multiple drivers
Page | 43
Intermodal
Reference Note
In the case of manual tenders, mention
tender ID as ‘MT_<case id>_<load #>.
Tender ID/VRID should be same as in EDI
B303 element from B204 element from 214.
TENDERID Tender ID
the B2 segment B2 segment For consolidated loads, enter VRID as
given by ROC.
For imports, enter tender ID provided in
Carrier AWS S3 folder.
segment.
L1101 element
Loop 0300
the tender.
N902 when N901 =
AO in Loop 0463
Loop 0300 populated on the X12 210 invoice.
Purchase Order SPO01 element in OID02 element in
PO on the X12 210 invoice.
Number Loop 0465 Loop 0350
Note: Send all PO #’s in Tender ID.
PRO must be populated to N9*CN
Carrier Assigned N902 when N901 = segment
PRO
Tracking ID CN in Loop 0463 Note: Send PRO # corresponding to
tender ID.
Date
Account # N104
N902 when N901 =
BM in Loop 0463
Miles
From Zip
To Zip
Page | 44
Example of X12 210 Invoice with Amazon requirements and the corresponding X12 204 Load Tender:
X12 210 Invoice (inbound) with Amazon
Corresponding X12 204 Load Tender
Requirements
ST*210*259460001~ ST*204*0001
B3**002068250*366036*CC**20100908*8003**2010
B2** CARRIER_SCAC**366036**CC
0918*035*CARRIER_SCAC*20100908~
ITD*01~ B2A*00
N9*2F*002068250~ L11*LOW*ZZ
G62*11*20100908~ N7**0*********TF
N1*SH*CARRIER_NAME*25*449776-0004~ S5*1*CL*348*L***51*E
N3*ABC ROAD~ L11*328560681*BX
N4*SEATTLE*WA*98105~ G62*37*20100908*I*0200
LX*1~ G62*38*20100908*K*0200
L5*1*BASE CHARGE~ LAD*PLT*0
L1*1*155.09*PH*53816****400~ LAD*CTN*51
N1*SH*Handi-Craft Company*ZZ*DRDJ963116 LAD*UNT*0
N3*4433 Fyler Avenue N1*SH*Handi-Craft Company*ZZ*DRDJ963116
N4*St. Louis*MO*63116*US N3*4433 Fyler Avenue
N1*CN*AMAZON.COM WHITESTOWN
N4*St. Louis*MO*63116*US
FC*ZZ*IND146075
N3*4255 Anson Boulevard G61*DC*Mona Willard*TE*314-773-2979
N4*Whitestown*IN*46075*US G61*DC*Karen Hendricks*TE*314-773-2979
CD3*G*348**0*SI~ G61*DC*Mona Willard*FX*314-773-9273
N9*BX*328560681*ARN~ OID*000066351276*N8799510**UN*0
N9*CN*002068250*PRO~ S5*2*CU*348*L***51*E
N9*AO*45269062*ISA~ L11*328560681*BX
N9*ACD*125~ G62*53*20100920*G*0300
POD*20100918**CARRIER_SCAC~ G62*54*20100920*L*0300
G62*11*20100908~ LAD*PLT*0
SPO*N8799510**CT*51~ LAD*CTN*51
SDQ*DM*ZZ*SM*487~ LAD*UNT*0
LX*2~ N1*CN*AMAZON.COM WHITESTOWN FC*ZZ*IND146075
L5*2*DISCOUNT~ N3*4255 Anson Boulevard
L1*2*0.874*CT*-47062****DSC~ N4*Whitestown*IN*46075*US
G61*DC*IND1 RECEIVING DEPARTMENT*EM*ind1-
LX*3~
receiveclerk@amazon.com
L5*3*FUEL SURCHARGE~ OID*000066351276*N8799510**UN*0
L1*3*0.185*CT*1249****FUE~ SE*32*0001
L3*348*G***8003******1~
SE*32*259460001~
Page | 45
Account Numbers:
Mode US Account Number CA Account Number MX Account Number
Domestic Inbound <SCAC>VNIB <SCAC>VNIBCA <SCAC>VNIBMX
Inbound LTL <SCAC>AMZNLTLUS <SCAC>AMZNLTLCA <SCAC>AMZNLTLMX
Warehouse Transfer <SCAC>WHTR <SCAC>WHTR <SCAC>WHTRMX
Vendor Returns (TL) <SCAC>VNRT <SCAC>VNRTCA <SCAC>VNRTMX
Vendor Returns (LTL) <SCAC>AMZNVRETUS <SCAC>AMZNVRETCA <SCAC>AMZNVRETMX
IB Consolidation <SCAC>IBCN <SCAC>IBCNCA <SCAC>IBCNMX
Import Linehaul <SCAC>IMLH <SCAC>IMLHCA <SCAC>IMLHMX
Charge Codes:
X12 210 Charge CODE DESCRIPTION
400 Base Charge
DSC Base Discount
FUE Fuel Surcharge
295_FUE Fuel Surcharge Discount
Page | 46
Addendum C – Reference Number Table
Reference Numbers IBLH IBLH - M WT IPLH CLH V-RET Non-INV

Load # x x x x
Tender ID x x x x
BOL# x x x x
ARN x x
ISA x x x x
PO# x x x x
VR# x
PRO# x x x x x x x
Notes
IBLH - M: Manually tendered shipper inbound loads are assigned a "manual ARN" by ROC, this number is actually the
ticket number associated with the load and should be included in the ARN and Tender ID field of the 210 invoice but
should not be used in Carrier Central.
WT, Non-INV: These types are scheduled in FMC
VRET: Manually tendered loads
Definitions
IBLH Inbound Linehaul - 204 tendered
IBLH - M Inbound Linehaul - manually tendered
WT Warehouse Transfers
IPHL Import Linehaul
CLH Consolidated Linehaul
V-RET Vendor Returns
Non-INV Non-Inventory
Shipment Term used to describe the movement of any piece, carton, pallet or group of pallets from a
single origin to a single destination
Load Term used to describe the movement of trailer form origin(s) to destination(s). May contain
multiple shipments in a single load
Load # Received either via 204 tender or via email from ROC
Tender ID EDI system generated number. Only available on loads tendered via EDI. Equals Load
Number on WT 204 tenders.
BOL# Bill of Lading: Shipper supplied number - can also be referred to as the manifest number
ARN Amazon generated number for each shipment - may have multiple shipments on a single
load
ISA Amazon delivery appointment portal generated appointment number - should only have one
ISA per delivery to FC
PO# Purchase Order #: Amazon generated number representing a purchase of inventory.
Inventory on a single PO can be transported over multiple shipments or loads
VR# Vendor Return #: Amazon generated number given to inventory shipment being sent back to
shippers
PRO# Carrier generated number - typically used to describe a single load
Page | 47
Addendum D - AWS S3 Carrier Portal
Welcome to Amazon Web Services! This guide will provide instructions to access your S3 account on the AWS
Management Console.
Definitions:
• S3: Simple Storage Solution.
• AWS Management Console: A simple web services interface that can be used to store and retrieve data.
• Bucket: A bucket is a container for directories.
• Directory: A directory is a container for files.
Login Information:
Username Password Console login link
4 digit SCAC Will be sent by Amazon’s BI team to carrier https://889496872030.signin.aws.amazon.com/console
separately when AWS account is created
Process:
• Sign in to AWS Management Console using the login link and the provided credentials:
• Click the S3 option in the services menu in the upper right-hand side of the Console:
• From the Buckets window, click the ‘na--carriers’ bucket
• Double-Click the directory with your SCAC code. Your available files will be located in your directory.
1) Note that after clicking on na--carriers folder, check for your user id by scrolling down rather than searching by
typing the user name. Observed that in few cases it results in an error while searching for the folder.
• To download a file, right-click the file and choose Download:
• To upload a file, click the upload button from the Objects and Folders window:
• From the Upload window, click Add Files and choose a file to upload. Click Start Upload to add the file to your
directory.
Carriers can reach out to Controllership if they do not possess an AWS account or are unable to access it. For any
questions, please contact MMPM.
Page | 48
Addendum E – Yard Safety Rules
• Only connect to a trailer with a Green exterior dock light.

o DO NOT hook to any trailer with a RED dock light
• Drivers must wear a safety vest and close toed shoes whenever in the yard and outside their vehicles
• Drivers are responsible for opening and closing side-hinged style trailer doors upon arrival and departure from
dock. Do not remove the tamper seal until instructed to do so by an Amazon Fulfillment representative.
• Drivers will surrender their keys for all box trucks or vans (trucks that cannot detach from the trailer) that are to
be loaded or unloaded by Amazon personnel.
• Drivers shall not hook up to their trailer until directed by Amazon personnel. Tractor must be completely
unhooked and at least 6 ft away from trailer after docking.
• Drivers must wait in the driver area in the building or in their cab >6 ft away from the trailer. Drivers may wait in
their cab or in designated tractor parking
• No idling or smoking in the trailer yard unless in a designated area.
• Trailers 28 ft or less require 2 jack stands. Amazon personnel are responsible for placing and removing jack
stands.
• Trailers that do not engage to the dock lock will have a glad lock or king pin applied. Amazon personnel are
responsible for applying and removing these devices.
• Drivers are responsible for placing wheel chock(s) upon arrival and removing wheel chock(s) from the trailer
prior to departure.
Note: Additional site-specific safety rules can be found on the R4D app for Relay users. Non-Relay carriers will find site-
specific safety rules posted upon arrival at the site.
FAILURE TO COMPLY WITH YARD SAFETY RULES WILL RESULT IN REFUSAL OF LOAD OR PICK-UP AND A REPORT TO
YOUR DISPATCHER.
In the event of an emergency or severe weather, please follow the guidance of Amazon personnel.
Page | 49
Addendum F – EDI X12-204
EDI X12- 204

204 Motor Carrier Load Tender - Version 4010
Introduction
This document details the specifications for implementing the Motor Carrier Load Tender (204) transaction with Amazon.com. The 204
transaction is partnered with two additional transactions, the Shipment Status Message (214) and the Load Tender Acknowledgement (990).
Amazon.com is in compliance with the 4010 X12 Standards for Motor Carrier Load Tender.
Amazon.com Amazon Usage

This guide will clearly outline and define the structure and content of the 204 that Amazon.com will be sending to our trading partners.
Benefits
The 204 will allow you, the trading partner, to create a return 214 document that will accept a shipment and allow us to track orders and their
estimated delivery times into our DC or outbound to our customer’s final destination. With better tracking information we can better service our
customer’s needs.
Specific Instructions for 204

Please make sure you have filled out and returned an Amazon.com EDI Carrier Survey. If you have not received a copy of the survey, please
notify your Amazon contact.
Amazon.com sends a 204 to the carrier, with critical shipment information including load reference identification, window required for shipping,
pickup, and drop off destinations. A carrier is expected to send back a 214 that will provide Amazon.com specific information on the shipment
including pro-number, shipment status codes, date and time of shipment/delivery. The ability to send back a stop code in the L11 is
mandatory for those carriers doing multiple stops.
Timing is critical. A 990, which accepts the load request, must be generated within 90 minutes of our sending the 204 transaction. If you
cannot generate a 990 document, returning a 214 will be fine as acceptance of the load, but please let us know that this is the procedure you
will follow, as it will require our approval.
Definitions:
Every segment/element is classified as one of the following:
• M / Mandatory – M element/segment (Mandatory segments are highlighted in yellow).

• O/ Optional – Can use element/segment. It often simplifies the document for both parties if the optional segments/elements are not
utilized.
• C / Conditional – Use is dependent on other elements/segments. For example, if element 06 is a qualifier then the item that was
being qualified/defined must follow in element 07. You cannot have one without the other.
• R – Amazon Recommended.
“Req” - Represents the X12 standard requirement.

Amazon Usage: Deviations from standard are clearly noted.
204 Motor Carrier Load Tender
Functional Group= SM
Page | 50
This Draft Standard for Trial Use contains the format and establishes the data contents of the Motor Carrier Load Tender Transaction
Set (204) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to allow
shippers or other interested parties to offer (tender) a shipment to a full load (truckload) motor carrier including detailed scheduling,
equipment requirements, commodities, and shipping instructions pertinent to a load tender. It is not to be used to provide a motor
carrier with data relative to a Less-than-Truckload bill of lading, pick-up notification, or manifest.
Not Defined:
Pos Id Segment Name Req Max Use Repeat Notes Amazon Usage
ISA Interchange Control M 1 M
Header
GS Functional Group Header M 1 M
Heading:
010 ST Transaction Set Header M 1 M
020 B2 Beginning Segment for M 1 M
Shipment Information
Transaction
030 B2A Set Purpose M 1 M
080 L11 Business Instructions and O 50 M
Reference Number
090 G62 Date/Time O 1 N1/090 M
100 MS3 Interline Information O 1 M
LOOP ID - 0200 10
200 N7 Equipment Details O 1 M
Detail:
LOOP ID - 0300 999
010 S5 Stop Off Details M 1 M
020 L11 Business Instructions and O 50 M
Reference Number
030 G62 Date/Time O 2 N2/030 M
050 LAD Lading Detail O 999 N2/050 M
LOOP ID - 0310 1
070 N1 Name O 1 M
090 N3 Address Information O 2 M
100 N4 Geographic Location O 1 M
120 G61 Contact O 3 R
LOOP ID - 0350 999 N2/150L

150 OID Order Identification Detail O 1 N2/150 M
Summary:
010 L3 Total Weight and Charges O 1 M
020 SE Transaction Set Trailer M 1 M
Not Defined:
GE Functional Group Trailer M 1 M
IEA Interchange Control Trailer M 1 M
Notes:
1/090 Segment G62 in header is used to convey the must-respond-by date and time when responding to a 204
Page | 51
transaction.
2/030 Use G62 segment either in loop 0300 or loop 0350, but not both.
2/050 Use LAD segment either in loop 0300 or loop 0350, but not both.
2/140L The G61 segment contains the person or company to be contacted by the carrier in case of emergency.
2/140 The G61 segment contains the person or company to be contacted by the carrier in case of emergency.
2/150L Use loop 0350 for conveying seller's order/invoice level detail or buyer's purchase order level detail. If not
using order level detail, this loop should not be used.
Interchange Control Header

ISA
Pos: Max: 1
Not Defined - Mandatory
Loop: N/A Elements: 16
User Option (Amazon Usage): M
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Element Summary:
Ref Id Element Name Req Type Min/Max Amazon Usage

ISA01 I01 Authorization Information Qualifier M ID 2/2 M
Description: Code to identify the type of information in the Authorization Information
All valid standard codes are used.
ISA02 I02 Authorization Information M AN 10/10 M
Description: 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)
ISA03 I03 Security Information Qualifier M ID 2/2 M
Description: Code to identify the type of information in the Security Information
ISA04 I04 Security Information M AN 10/10 M
Description: 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)
ISA05 I05 Interchange ID Qualifier M ID 2/2 M
Description: Qualifier to designate the system/method of code structure used to designate the
sender or receiver ID element being qualified
ISA06 I06 Interchange Sender ID M AN 15/15 M
Description: 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
ISA07 I05 Interchange ID Qualifier M ID 2/2 M
Description: Qualifier to designate the system/method of code structure used to designate the
sender or receiver ID element being qualified
ISA08 I07 Interchange Receiver ID M AN 15/15 M
Description: 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
Page | 52
ID to route data to them

ISA09 I08 Interchange Date M DT 6/6 M
Description: Date of the interchange
ISA10 I09 Interchange Time M TM 4/4 M
Description: Time of the interchange
ISA11 I10 Interchange Control Standards Identifier M ID 1/1 M
Description: Code to identify the agency responsible for the control standard used by the
message that is enclosed by the interchange header and trailer
ISA12 I11 Interchange Control Version Number M ID 5/5 M
Description: Code specifying the version number of the interchange control segments
ISA13 I12 Interchange Control Number M N0 9/9 M
Description: A control number assigned by the interchange sender
ISA14 I13 Acknowledgment Requested M ID 1/1 M
Description: Code sent by the sender to request an interchange acknowledgment (TA1)
ISA15 I14 Amazon Usage Indicator M ID 1/1 M
Description: Code to indicate whether data enclosed by this interchange envelope is test,
production or information
ISA16 I15 Component Element Separator M 1/1 M
Description: 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
Functional Group Header

GS
Pos: Max: 1
Not Defined - Mandatory
To indicate the beginning of a functional group and to provide control information
Element Summary:

GS01 479 Functional Identifier Code M ID 2/2 M
Description: Code identifying a group of application related transaction sets
Code Name
SM Motor Carrier Load Tender (204)
GS02 142 Application Sender's Code M AN 2/15 M
Description: Code identifying party sending transmission; codes agreed to by trading partners
GS03 124 Application Receiver's Code M AN 2/15 M
Description: Code identifying party receiving transmission; codes agreed to by trading
Page | 53
partners
GS04 373 Date M DT 8/8 M
Description: Date expressed as CCYYMMDD
GS05 337 Time M TM 4/8 M
Description: 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)
GS06 28 Group Control Number M N0 1/9 M
Description: Assigned number originated and maintained by the sender
GS07 455 Responsible Agency Code M ID 1/2 M
Description: Code identifying the issuer of the standard; this code is used in conjunction with
Data Element 480
GS08 480 Version / Release / Industry Identifier Code M AN 1/12 M
Description: Code indicating the version, release, subrelease, and industry identifier of the
EDI standard being O, 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
Code Name
004010 Draft 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.
Transaction Set Header

ST
Pos: 010 Max: 1
Heading - Mandatory
To indicate the start of a transaction set and to assign a control number
Element Summary:

ST01 143 Transaction Set Identifier Code M ID 3/3 M
Description: Code uniquely identifying a Transaction Set
Page | 54
ST02 329 Transaction Set Control Number M AN 4/9 M

Description: Identifying control number that must be unique within the transaction set
functional group assigned by the originator for a transaction set
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).
B2 Beginning Segment for Shipment Pos: 020 Max: 1

Heading - Mandatory
Information Transaction Loop: N/A Elements: 12
To transmit basic data relating to shipment information
Element Summary:
B202 140 Standard Carrier Alpha Code O ID 2/4 O

Description: Standard Carrier Alpha Code
B204 145 Shipment Identification Number O AN 1/30 M
Description: Identification number assigned to the shipment by the shipper that uniquely
identifies the shipment from origin to ultimate destination and is not subject to modification;
(Does not contain blanks or special characters)
Amazon Usage:
Load ID/ VRID
B206 146 Shipment Method of Payment M ID 2/2 M

Description: Code identifying payment terms for transportation charges
Code Name
CC Collect
PP Prepaid
Prepaid for Warehouse Transfer and Outbound Linehaul only
B207 147 Shipment Qualifier O ID 1/2 O

Description: Code identifying payment terms for transportation charges
Code Name (Amazon defined)
A Inbound Ad Hoc
D Inbound Imm
H Warehouse Transfer
I Inbound Import
Amazon Usage: Shipment Qualifier is a Min 1/Max 2 ID.
Semantics:
Page | 55
1. B202 contains the Standard Carrier Alpha Code (SCAC) of the carrier that will receive the bill of lading.
Comments:
1. B202 is mandatory for transaction set 204.
Pos: 030 Max: 1

B2A Set Purpose Heading - Mandatory
To allow for positive identification of transaction set purpose
Element Summary:

B2A01 353 Transaction Set Purpose Code M ID 2/2 M
Description: Code identifying purpose of transaction set
Code Name
00 Original
01 Cancellation
Amazon Usage: Subsequent 204’s should be considered a replacement.
**04 Change
**NOT USED
B2A02 346 Application Type O AN 2/2 O

Description: Code identifying an application
Amazon Usage: P=Production; B2A02 will be “P “.
Example:
B2A*00*P ~
Note the blank space following the “P”.
L11 Business Instructions and Reference Pos: 080 Max: 50

Heading - Optional
Number Loop: N/A Elements: 3
To specify instructions in this business relationship or a reference number
Element Summary:

L1101 127 Reference Identification X AN 1/30 O
Description: Reference information as defined for a particular Transaction Set or as specified
by the Reference Identification Qualifier
Amazon Usage: Load Value
L1102 128 Reference Identification Qualifier X ID 2/3 O
Page | 56
Description: Code qualifying the Reference Identification

Code Name
KD Transloader of Load Tender Carrier/SCAC
ZZ Load Value (LOW, MEDIUM)
L1103 352 Description X AN 1/80 O
Description: A free-form description to clarify the related data elements and their content
This element will be populated with rate tier when qualifier is ZZ
Syntax Rules:
1. R0103 - At least one of L1101 or L1103 is required.
2. P0102 - If either L1101 or L1102 is present, then the other is required.
AMAZON Trans EDI Notes:

The L11 segment will also be used to notify Transloader of Load Tender Carrier/SCAC using the qualifier KD.
Example:
Passing in X.12 doc in L11 segment with KD qualifier:
L11.01 LoadTenderCarrierSCAC
L11.02 Qualifier – KD
L11.03 LoadTenderCarrierName
Example: L11*SCAC*KD* CarrierName~

Example: L11*AMZN*KD* AMAZON~
Pos: 090 Max: 1

G62 Date/Time Heading - Optional
To specify pertinent dates and times
Element Summary:

G6201 432 Date Qualifier X ID 2/2 O
Description: Code specifying type of date
Code Name
64 Must Response By
G6202 373 Date X DT 8/8 O
G6203 176 Time Qualifier X ID 1/2 O
Description: Code specifying the reported time
Code Name
1 Must Respond By
G6204 337 Time X TM 4/8 O
Page | 57
Syntax Rules:
1. R0103 - At least one of G6201 or G6203 is required.
2. P0102 - If either G6201 or G6202 is present, then the other is required.
Pos: 100 Max: 1

MS3 Interline Information Heading - Optional
To identify the interline carrier and relevant data
Element Summary:

MS301 140 Standard Carrier Alpha Code M ID 2/4 M
Description: Standard Carrier Alpha Code
MS302 133 Routing Sequence Code M ID 1/2 M
Description: Code describing the relationship of a carrier to a specific shipment movement
MS304 91 Transportation Method/Type Code O ID 1/2 O
Description: Code specifying the method or type of transportation for the shipment
Semantics:
1. MS301 is the Standard Carrier Alpha Code (SCAC) of the interline carrier.
Pos: 200 Repeat: 10

Loop 0200 Optional
Loop: 0200 Elements: N/A
To identify the equipment
Loop Summary:
Pos Id Segment Name Req Max Use Repeat Amazon Usage

200 N7 Equipment Details O 1 M
Page | 58
Pos: 200 Max: 1

N7 Equipment Details Heading - Optional
Loop: 0200 Elements: 24
To identify the equipment
Element Summary:
N702 207 Equipment Number M AN 1/10 M

Description: Sequencing or serial part of an equipment unit's identifying number (pure numeric
form for equipment number is preferred)
Amazon Usage: This number will always be transmitted as “0” (zero)
N711 40 Equipment Description Code O ID 2/2 O
Description: Code identifying type of equipment used for shipment
Code Name
CN Container
HV High Cube Van
RT Controlled Temperature Trailer (Reefar)
TF Trailer, Dry Freight
TV Truck, Van
VE Vessel, Ocean
N715 567 Equipment Length O N0 4/5 O
Description: Length (in feet and inches) of equipment ordered or used to transport shipment
Amazon Usage: Format is FFFII; where FFF is feet and II is inches; the range for II is 00
through 11.
Pos: 010 Repeat: 999

Loop 0300 Mandatory
To specify stop-off detail reference numbers and stop reason
Loop Summary:

010 S5 Stop Off Details M 1 M
020 L11 Business Instructions and Reference O 50 M
Number
030 G62 Date/Time O 2 M
050 LAD Lading Detail O 999 M
070 Loop 0310 O 1 M
150 Loop 0350 O 999 M
Page | 59
Pos: 010 Max: 1

S5 Stop Off Details Detail - Mandatory
To specify stop-off detail reference numbers and stop reason
Element Summary:

S501 165 Stop Sequence Number M N0 1/3 M
Description: Identifying number for the specific stop and the sequence in which the stop is to
be performed
S502 163 Stop Reason Code M ID 2/2 M
Description: Code specifying the reason for the stop
Code Name
CL Complete Load
CU Complete Unload
PL Part Load
PU Part Unload
S503 81 Weight X R 1/10 O
Description: Numeric value of weight
S504 188 Weight Unit Code X ID 1/1 O
Description: Code specifying the weight unit
Code Name
L Pounds
S505 382 Number of Units Shipped X R 1/10 O
Description: Numeric value of units shipped in manufacturer's shipping units for a line item or
transaction set
S506 355 Unit or Basis for Measurement Code X ID 2/2 O
Description: Code specifying the units in which a value is being expressed, or manner in
which a measurement has been taken
Code Name
PL Pallet/Unit Load
S507 183 Volume X R 1/8 O
Description: Value of volumetric measure
S508 184 Volume Unit Qualifier X ID 1/1 O
Description: Code identifying the volume unit
Code Name
E Cubic Feet
Syntax Rules:
1. P0304 - If either S503 or S504 is present, then the other is required.
Page | 60
L11 Business Instructions and Reference Pos: 020 Max: 50

Detail - Optional
Number Loop: 0300 Elements: 3
To specify instructions in this business relationship or a reference number
Element Summary:

L1101 127 Reference Identification X AN 1/30 O
L1102 128 Reference Identification Qualifier X ID 2/3 M
Description: Code qualifying the Reference Identification
Code Name
AO Appointment ID (a.k.a. ISA Number)
BX Amazon Reference Number (a.k.a. ARN)
CN Pro Reference Number
Syntax Rules:
1. R0103 - At least one of L1101 or L1103 is required.
Pos: 030 Max: 2

G62 Date/Time Detail - Optional
To specify pertinent dates and times
Element Summary:

G6201 432 Date Qualifier X ID 2/2 M
Description: Code specifying type of date
Code Name
37 Ship Not Before Date
38 Ship Not Later Than Date
53 Deliver Not Before Date
54 Deliver No Later Than Date
G6202 373 Date X DT 8/8 M
G6203 176 Time Qualifier X ID 1/2 M
Description: Code specifying the reported time
Page | 61
Code Name
I Earliest Requested Pickup Time
K Latest Requested Pickup Time
G Earliest Requested Deliver Time
L Latest Requested Deliver Time
G6204 337 Time X TM 4/8 M
Syntax Rules:
1. R0103 - At least one of G6201 or G6203 is required.
Pos: 050 Max: 999

LAD Lading Detail Detail - Optional
To transmit detailed lading data pertinent to a pickup or delivery
Element Summary:

LAD01 211 Packaging Form Code X ID 3/3 M
Description: Code for packaging form of the lading quantity
Code Name
PLT Pallet
CTN Carton
UNT Unit
LAD02 80 Lading Quantity X N0 1/7 M
Description: Number of units (pieces) of the lading commodity
Syntax Rules:
1. P0102 - If either LAD01 or LAD02 is present, then the other is required.
Pos: 070 Repeat: 1

Loop 0310 Optional
To identify a party by type of organization, name, and code
Page | 62
Loop Summary:

070 N1 Name O 1 M
090 N3 Address Information O 2 M
100 N4 Geographic Location O 1 M
120 G61 Contact O 3 R
Pos: 070 Max: 1

N1 Name Detail - Optional
To identify a party by type of organization, name, and code
Element Summary:

N101 98 Entity Identifier Code M ID 2/3 M
Description: Code identifying an organizational entity, a physical location, property or an
individual
Code Name
SH Shipper; will always be sent.
CN Consignee; will be sent per shipper business type.
N102 93 Name X AN 1/60 O
Description: Free-form name
N103 66 Identification Code Qualifier X ID 1/2 O
Description: Code designating the system/method of code structure used for Identification
Code (67)
Code Name
ZZ Mutually Defined
N104 67 Identification Code X AN 2/80 O
Description: Code identifying a party or other code
Syntax Rules:
1. R0203 - At least one of N102 or N103 is required.
2. P0304 - If either N103 or N104 is present, then the other is 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.
Page | 63
Pos: 090 Max: 2

N3 Address Information Detail - Optional
To specify the location of the named party
Element Summary:

N301 166 Address Information M AN 1/55 M
Description: Address information
N302 166 Address Information O AN 1/55 O
Description: Address information
Pos: 100 Max: 1

N4 Geographic Location Detail - Optional
To specify the geographic place of the named party
Element Summary:

N401 19 City Name O AN 2/30 O
Description: Free-form text for city name
N402 156 State or Province Code O ID 2/2 O
Description: Code (Standard State/Province) as defined by appropriate government agency
N403 116 Postal Code O ID 3/15 O
Description: Code defining international postal zone code excluding punctuation and blanks
(zip code for United States)
N404 26 Country Code O ID 2/3 O
Description: Code identifying the country
Syntax Rules:
1. C0605 - If N406 is present, then N405 is required.
Comments:
1. A combination of either N401 through N404 may be adequate to specify a location.
2. N402 is required only if city name (N401) is in the U.S. or Canada.
Page | 64
Pos: 120 Max: 3

G61 Contact Detail - Optional
User Option (Amazon Usage): R
To identify a person or office to whom communications should be directed
Element Summary:

G6101 366 Contact Function Code M ID 2/2 M
Description: Code identifying the major duty or responsibility of the person or group named
Code Name
SH Shipper
DC Distribution Center
G6102 93 Name M AN 1/60 M
Description: Free-form name
G6103 365 Communication Number Qualifier X ID 2/2 O
Description: Code identifying the type of communication number
Code Name
TE Telephone
FX Fax
EM Email
G6104 364 Communication Number X AN 1/80 O
Description: Complete communications number including country or area code when
applicable
Syntax Rules:
Comments:
1. G6103 qualifies G6104.
Pos: 150 Repeat: 999

Loop 0350 Optional
To specify order identification detail
Loop Summary:

150 OID Order Identification Detail O 1 M
Page | 65
Pos: 150 Max: 1

OID Order Identification Detail Detail - Optional
To specify order identification detail
Element Summary:

OID01 127 Reference Identification X AN 1/30 M
Amazon Usage: Routing ID
OID02 324 Purchase Order Number X AN 1/22 M
Description: Identifying number for Purchase Order assigned by the originator/purchaser
OID04 355 Unit or Basis for Measurement Code X ID 2/2 O
Description: Code specifying the units in which a value is being expressed, or manner in
which a measurement has been taken
Code Name
PL Pallet/Unit Load
UN Unit
OID05 380 Quantity X R 1/15 O
Description: Numeric value of quantity
OID06 188 Weight Unit Code X ID 1/1 O
Description: Code specifying the weight unit
Code Name
L Pounds
OID07 81 Weight X R 1/10 O
Description: Numeric value of weight
OID08 184 Volume Unit Qualifier X ID 1/1 O
Description: Code identifying the volume unit
Code Name
E Cubic Feet
OID09 183 Volume X R 1/8 O
Description: Value of volumetric measure
Syntax Rules:
1. R0102 - At least one of OID01 or OID02 is required.
3. P0405 - If either OID04 or OID05 is present, then the other is required.
Semantics:
Page | 66
1. OID01 is the seller's order identification number.
Pos: 010 Max: 1

L3 Total Weight and Charges Summary - Optional
To specify the total shipment in terms of weight, volume, rates, charges, advances, and prepaid amounts applicable to one or more line
items
Element Summary:

L303 60 Freight Rate X R 1/9 O
Description: Rate that applies to the specific commodity
L304 122 Rate/Value Qualifier X ID 2/2 O
Description: Code qualifying how to extend charges or interpret value
L305 58 Charge O N2 1/12 O
Description: For a line item: freight or special charge; for the total invoice: the total charges --
expressed in the standard monetary denomination for the currency specified
Amazon Usage: Total charges
Syntax Rules:
Semantics:
1. L305 is the total charges.
Pos: 020 Max: 1

SE Transaction Set Trailer Summary - Mandatory
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending
(SE) segments)
Element Summary:

SE01 96 Number of Included Segments M N0 1/10 M
Description: Total number of segments included in a transaction set including ST and SE
segments
SE02 329 Transaction Set Control Number M AN 4/9 M
Page | 67
Description: Identifying control number that must be unique within the transaction set
functional group assigned by the originator for a transaction set
Comments:
1. SE is the last segment of each transaction set.
Pos: Max: 1
GE Functional Group Trailer Not Defined - Mandatory
To indicate the end of a functional group and to provide control information
Element Summary:

GE01 97 Number of Transaction Sets Included M N0 1/6 M
Description: Total number of transaction sets included in the functional group or interchange
(transmission) group terminated by the trailer containing this data element
GE02 28 Group Control Number M N0 1/9 M
Description: Assigned number originated and maintained by the sender
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.
Pos: Max: 1
IEA Interchange Control Trailer Not Defined - Mandatory
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Element Summary:

IEA01 I16 Number of Included Functional Groups M N0 1/5 M
Description: A count of the number of functional groups included in an interchange
IEA02 I12 Interchange Control Number M N0 9/9 M
Description: A control number assigned by the interchange sender
Page | 68
Addendum G – LTL Rejection Reason List
Rejection Standard Status

Reason Code Interpretation
Inability to execute tender was caused by extreme weather conditions.
WTH Weather Example:
The driver could not get to the shipper’s location due to a blizzard.
Continual poor vendor operations have created a situation where the carrier
Vendor Facility cannot pick up the freight.
VFD
Delay Example:
Vendor refuses to palletize freight and insists on floor loading.
Carrier did not have enough tractors to pick up the shipment.
CPT Tractor Capacity Example:
The carrier had no trailers on-site to execute the tender.
Carrier agreed to complete more loads than they can execute.
Over Agreed
CPU Example:
Capacity
The carrier agreed to 5 more loads than they can provide trailers for.
Tenders received by carrier exceed the forecasted amount expected.
Not in Forecast/No Example:
NFC
Capacity The carrier allotted a specific number of trailers to Amazon loads and then
Amazon requested more than that amount.
Mechanical issues on equipment owned by the carrier.
Mechanical
EQR Example:
Breakdown
The trailer’s doors cannot be shut.
Mechanical issues on tractor owned by the carrier.
Mechanical
EQU Example:
Breakdown Tractor
The truck’s battery died.
Carrier receives a tender for a lane that they do not service.
Lane Assignment Example:
LAI
Incorrect The carrier received a tender with a destination that the carrier does not provide
services to.
Carrier does not have enough drivers to accept any more tenders.
DRS Driver Shortage Example:
The carrier has lost drivers and therefore cannot execute any more loads.
Carrier cannot accept the tender due to errors by the dispatcher.
Example:
DSP Dispatch Error
The dispatcher incorrectly assigned trailers for use and cannot accept tender due
to wrong driver type or no HOS remaining.
Carrier cannot accept load due to a reason within their control that is not listed
Carrier Controllable elsewhere on this list.
CCR
Reasons Example:
The carrier doesn’t have the required equipment available.
Amazon changes the load schedule and no longer needs this tender.
Amazon Schedule
ASC Example:
Change
Amazon informs the carrier the tender is no longer required and can be rejected.
Amazon facility backlog is delaying receipt of loads.
Amazon Facility
AFD Example:
Delay
Carrier cannot deliver to certain facility due to backlog delaying delivery.
Page | 69

WePay Ops Manual NAAmazon

Uploaded by

Copyright:

Available Formats

You might also like

WePay Ops Manual NAAmazon

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

WePay Ops Manual NAAmazon

Uploaded by

Copyright:

Available Formats

Carrier Manual

Requirements & Expectations

Effective Date: May 12, 2023

2. New Programs & Recent Additions

4. Shipper Inbound Overview

5.12.2. Pickup time at the shipper

8. Small Parcel (SP)

9. Import Linehaul (Transload)

DSFS – Damco – Santa Fe, CA TPCH – Trade Port – Charleston, SC

TPSV– Trade Port – Savannah, GA GOAK – GSC – Oakland, CA

RSAV – Road One – Savannah, GA REWR – Road One – Flanders, NJ

DSEA – Damco – Sumner, WA DHOU – Damco – Houston, TX

DSEB – Damco – Lakewood, WA RORF – Road One – Suffolk, VA

BCVA – Damco – New Westminster, BC (CA)

9.2. Transload Operations

10. Warehouse Transfers (WT)

11. General Information (all business types)

12. Base Rates and Lane Ownership

amount to be awarded will be 1.0 miles.

Unique Program Identifiers 204 tenders

Mode EDI B207 Notifier

Domestic Inbound Truckload A

Vendor Returns N/A. Based on PO

Inbound Consolidation (TL) C

TL - required shipment lifecycle 214 status messages

LTL - required shipment lifecycle 214 status message

Intermodal - required shipment lifecycle 214 status messages

LTL Consolidation with IM - required shipment lifecycle 214 status messages

INBOUND DELAYED PICKUP EDI MESSAGES

Status Reason Standard Status

INBOUND DELAYED DELIVERY EDI MESSAGES

RAIL ONLY INBOUND DELAYED DELIVERY EDI MESSAGES

14. Invoice Process and Off-Manifest Resolution

14.15.3. Base rate variance/Fuel surcharge variance

Addendum A – Case Management and Resolution

3. Available Email Queues:

Addendum B – EDI 210 Invoice Guide

Less Than Truckload

• SOLO means single driver

Addendum C – Reference Number Table

Reference Numbers IBLH IBLH - M WT IPLH CLH V-RET Non-INV

Addendum D - AWS S3 Carrier Portal

• From the Buckets window, click the ‘na--carriers’ bucket

• To download a file, right-click the file and choose Download:

Addendum E – Yard Safety Rules

• Only connect to a trailer with a Green exterior dock light.

Addendum F – EDI X12-204

EDI X12- 204

Amazon.com Amazon Usage

Specific Instructions for 204

• M / Mandatory – M element/segment (Mandatory segments are highlighted in yellow).

“Req” - Represents the X12 standard requirement.

204 Motor Carrier Load Tender

LOOP ID - 0350 999 N2/150L

Interchange Control Header

User Option (Amazon Usage): M

Ref Id Element Name Req Type Min/Max Amazon Usage

Example: L11SCACKD* CarrierName~