Amazon Fulfillment Centers are among the most document-strict receiving operations in logistics. A pallet that arrives with a mismatched BOL number, a missing shipment ID, or a quantity discrepancy between the packing list and the carton labels will be refused, held, or received against you - triggering claims, delays, and the kind of seller account performance hits that take weeks to recover from. For prep centers, getting the freight document stack right is not optional; it is the core operational competency that differentiates professional operations from those that lose clients over preventable dock rejections.
This guide covers the complete FBA freight document stack, Amazon's specific BOL requirements, how document requirements change across shipping modes, the prep center workflow from receiving through shipment, and where automation pays off at scale.
Every LTL or FTL shipment to an Amazon FC requires a specific set of documents. Missing any one of them creates a receiving problem. Here is what you need for every shipment:
For imports or shipments involving cross-border movement, add a commercial invoice and packing list formatted to customs standards. For any regulated or hazardous products, add the appropriate declaration. The base stack above covers domestic LTL and FTL shipments under the standard FBA inbound program.
This is where most errors originate. Amazon's BOL requirements are more specific than a standard carrier BOL, and Seller Central's shipment workflow generates the shipment IDs and reference numbers that must appear on the BOL exactly as shown - no paraphrasing, no abbreviating.
FBA[XXXXXXXX], generated in Seller Central when you create the inbound shipment. This must appear on the BOL as a reference number.Critical: The shipment ID on your BOL must match the shipment ID in Amazon's appointment system exactly. A single character difference - a missing leading zero, a lowercase letter where uppercase is expected - can cause a receiving rejection that routes your pallet to an unscheduled queue, adding days to your receiving timeline.
Amazon's Partnered Carrier Program (PCP) allows sellers to ship LTL through Amazon-negotiated UPS rates, with the cost deducted from their seller account. Non-partnered shipping means you arrange your own carrier - typically a freight broker or direct carrier relationship.
For partnered carrier LTL shipments, Amazon generates the BOL for you within Seller Central. You download the pre-populated BOL, hand it to the driver at pickup, and the shipment reference numbers are automatically reconciled. Document errors are dramatically reduced because Amazon controls the BOL template. The trade-off is less flexibility on rates, carriers, and pickup timing.
For non-partnered LTL and FTL shipments, you generate the BOL yourself - or your prep center generates it on behalf of the seller. This is where document errors spike. The BOL must contain all the Amazon-required reference fields, formatted correctly, and the carrier needs a copy for their records that matches what Amazon expects to see at the dock. If you are running non-partnered shipments at any volume, this is the workflow that benefits most from document generation automation. Our guide on generating BOLs via REST API walks through exactly how to structure this workflow programmatically.
Amazon FCs expect standard GMA (Grocery Manufacturers Association) pallets: 48 inches by 40 inches. Pallet weight must not exceed 1,500 pounds. Height - including the pallet itself - must not exceed 72 inches for standard stacking; some FCs allow up to 98 inches for floor-loaded trailers designated for high-bay storage, but this is FC-specific and must be confirmed in advance.
Pallets must be stable, shrink-wrapped from bottom to top, and not overhanging the pallet deck edges by more than 2 inches on any side. The reason this matters for documentation: your BOL pallet count must reflect actual pallet count, and if Amazon's receiving team counts a different number of pallets than your BOL states, the receiving discrepancy triggers a manual review that can hold your inventory for several days.
Floor-loaded trailers (cartons stacked directly on the trailer floor without pallets) are accepted at some FCs for certain product categories, but they require a separate process. The BOL should note "floor loaded" and include a carton count instead of a pallet count. Amazon's receiving team will unload and palletize, which adds time and can result in carton damage claims. For high-value inventory, palletized shipments are nearly always the better choice, even if they cost more in prep labor.
Amazon uses a carrier appointment scheduling system - either Carrier Central (for carriers to schedule directly) or Seller Central's appointment request tool (for sellers to initiate). The appointment is tied to the shipment ID and a specific carrier SCAC code or carrier identifier.
When the driver arrives at the FC, the receiving team pulls up the appointment by the shipment ID and carrier information. They then compare the BOL the driver presents against the appointment record. If the BOL shipment ID does not match the appointment record, or if the carrier listed on the BOL is different from the carrier who booked the appointment, the load will not be received at that door - it gets sent to the yard for manual processing, which adds unpredictable delay.
The operational rule is: finalize your BOL with the shipment ID and carrier information before booking the appointment, not after. Changing carriers after booking an appointment requires canceling and re-booking, and many FCs have limited appointment availability, so last-minute changes can push your delivery out by days.
These are the most frequent causes of dock refusals and receiving holds, categorized by their document root cause:
| Rejection Reason | Document Root Cause | Prevention |
|---|---|---|
| Shipment ID not on BOL | BOL template missing Amazon reference fields | Use Amazon-compliant BOL template |
| Shipment ID mismatch | Typo in shipment ID on BOL or appointment | Auto-populate from Seller Central data |
| Wrong delivery address format | Using street address instead of Amazon FC code format | Copy address exactly from Seller Central |
| Quantity mismatch (BOL vs packing list) | Manually entered carton counts diverged | Generate BOL and packing list from same data source |
| Missing pallet labels | Labels not printed or fell off in transit | Apply 4 labels per pallet, shrink wrap over labels |
| Carton labels facing wrong direction | Labels applied to non-visible pallet face | Label all four carton faces on outermost layer |
| Carrier not matching appointment | Carrier changed after appointment booked | Finalize carrier before booking appointment |
| Overweight pallets | Weight not calculated before palletizing | Weigh pallets before building; max 1,500 lbs |
Small parcel (UPS, FedEx, partnered UPS through Amazon) does not require a BOL. Each carton has its own tracking label. The main document is the packing list in Seller Central, and your primary concern is that carton labels are applied correctly and scannable. Document failure mode here is misapplied labels or labels not registered in the shipment plan.
LTL shipments require the full document stack described above. This is the most common mode for prep centers shipping palletized FBA inventory and the most document-intensive. The BOL is the central document, and everything else - pallet labels, packing list, appointment confirmation - must reconcile against it.
FTL shipments follow the same document requirements as LTL with a few additions: the BOL should note "full truckload" and include the trailer number. Amazon may require a seal number to be noted on the BOL for certain high-value FTL loads. The appointment process for FTL at Amazon FCs typically involves a dedicated dock door reserved for the full trailer, and the BOL must specify the correct FC dock designation.
For the specific LTL documentation requirements that apply regardless of the Amazon context, see our LTL shipment documentation checklist.
A well-run prep center handles FBA freight documentation as an integrated step in the workflow, not an afterthought. Here is the standard sequence:
Steps 6 and 7 are where document errors cluster. When prep centers do these steps manually - pulling the shipment ID from Seller Central, typing it into a Word BOL template, and manually entering carton counts - transcription errors are almost guaranteed at high volume.
A prep center processing 50 or more FBA shipments per week is spending significant staff time on document creation and correction. Here is a realistic time accounting for manual document generation:
At 50 shipments per week, that is 15-24 hours per week in document creation alone - before errors. With a 3-5% dock rejection rate from document issues (common in manual operations), that is 1-3 rejections per week each costing 30-60 minutes to resolve plus any financial penalties from appointment no-shows or re-delivery fees.
API-generated documents, populated directly from Seller Central export data or a prep center's WMS, reduce creation time to seconds and eliminate transcription errors entirely. At 50 shipments per week, the ROI on document automation is usually positive within the first month of implementation. At 200+ shipments per week, it becomes one of the highest-leverage operational improvements available.
The FreightDoc API supports Amazon-compliant BOL generation with configurable fields for shipment ID, reference numbers, and the specific address format Amazon FCs expect. You can integrate it directly into your prep center's WMS or dispatch workflow and have documents generated automatically at the point of shipment creation.
If you are shipping inventory into Amazon's Canadian or European FCs from the United States, you need a commercial invoice (or pro forma invoice for non-sale shipments) in addition to the standard FBA document stack. This document is required for customs clearance and must include:
Amazon does not accept shipments through Canadian or EU customs on behalf of the seller - the seller or their customs broker handles import clearance. The BOL for the cross-border leg must reference the customs entry number once it is assigned, and the delivery to the Amazon FC only happens after customs release. Document errors at the customs stage can hold inventory for days or weeks.
Amazon's receiving speed depends on scanners being able to read labels at each stage of the receiving process. Label placement failures are among the most preventable causes of receiving delays.
Carton labels: Applied to one face of each carton, in the upper right quadrant, on a flat surface (not over tape, seams, or graphics). Labels must be fully legible - no wrinkles, no folds, no coverage by shrink wrap. For palletized shipments, ensure the outermost carton layer has labels on the pallet-facing side so they can be scanned after unwrapping.
Pallet labels: Amazon-generated pallet labels from Seller Central should be applied to all four sides of each pallet, in the center at approximately eye height (roughly 3-4 feet from the floor). Applying labels under the shrink wrap is acceptable; over the top layer of shrink wrap is better since it survives handling without the wrap being cut.
One practical tip from high-volume prep centers: laminate or use laser-printed labels rather than thermal inkjet for pallet labels. Thermal inkjet labels fade in humid or cold environments, and Amazon cold-storage FCs and cross-dock facilities can degrade label readability during a single transit.
FBA freight documentation is a precision exercise. Every field on the BOL, every label placement decision, every pallet count on the packing list has a corresponding check at the Amazon FC. The prep centers that operate at scale without constant dock rejections are the ones that have built systematic, automated document generation workflows - not ones that rely on staff manually entering shipment IDs into Word templates. The investment in getting documentation right pays back in faster receiving, cleaner seller account metrics, and the kind of client retention that comes from never causing a delay.
FreightDoc generates BOL, rate confirmations, carrier packets, and customs docs via API - in under 2 seconds.
Join the Waitlist