For most FBA sellers, getting inventory "into Amazon" feels like sending a shipment into a black box. Something goes in, and eventually your dashboard shows stock available. But what actually happens between the truck arriving at the inbound dock and your listing showing "In Stock" is a multi-step process — and understanding it explains why things sometimes go wrong, and how to minimize the chances they do.
Amazon's inbound allocation logic is — by design — one of the most complex parts of its supply chain. It has to be. Unlike outbound fulfillment, which routes orders from existing inventory, inbound allocation must make decisions about where to put inventory before demand has materialized. It must simultaneously account for current sales velocity, fulfillment center capacity and fill levels, inter-facility transfer costs, upcoming inventory waves, and the time gap between when a shipment is registered and when it will physically be stowed.
The result is what the source material describes as a "dynamic-static" problem: decisions made about inventory that has already arrived are relatively straightforward; decisions about inventory still in transit require probabilistic modeling across dozens of variables. Getting this wrong has direct consequences — inventory placed in the wrong region increases fulfillment cost and hurts delivery speed for every order that requires it.
The inbound process begins when a truck arrives at the warehouse's inbound dock. For third-party sellers, the carrier must have been booked through Carrier Central — the scheduling system that links truck, shipment, FBA shipment number, and destination facility. Amazon's central dispatch team, based in Phoenix, coordinates inbound sequencing based on urgency: how quickly does this inventory need to reach sellable status?
The inbound dock at a receive center — carriers must pre-book through Carrier Central, arrive on schedule, and meet safety requirements before unloading begins.
Timing matters strictly. If a truck arrives late without prior notice, the appointment is automatically cancelled 30 minutes past the scheduled time. The carrier must rebook — and is flagged in Amazon's system. Repeated violations can result in the carrier losing receiving privileges. Sending inventory to the wrong facility triggers a violation record for both the carrier and the seller.
Safety checks happen before unloading begins. If the dock team identifies hazards — a trailer sitting too low, no cargo net, uneven flooring, boxes over 50 lb without weight markings — they have the right to refuse receipt. This is not bureaucracy; it protects the workers who will be physically handling the freight.
Once freight is unloaded, it passes through a PID scanner (known internally as a "dragon gate" — a multi-angle barcode scanner that simultaneously reads labels and weighs each carton). The system then routes each carton to one of six possible processing paths:
| Processing Path | What Triggers It | What Happens |
|---|---|---|
| Case Receive | Clean, single-SKU carton that matches system records | Fastest — entire box routed intact to outbound dock, no unpacking needed |
| Each Receive | Multi-unit carton requiring item-level scanning | Worker opens carton, scans each unit individually, places into tote assigned by indicator light |
| Prep | Items requiring bagging, wrapping, or re-labeling | Prep work completed first, then item rejoins Each Receive path |
| Problem Solve | System cannot identify item, or anomaly detected | Routed to specialist team; resolved manually — human error possible, complaints rarely successful |
| Sideline | Shipment arrived at wrong facility | Set aside until sufficient volume accumulates, then redirected to correct facility as a batch |
| Discard | No matching system record; seller account may be suspended | Worst outcome — item destroyed; common when account is banned mid-shipment |
The speed implication is significant. A clean, properly labeled, single-SKU case can move from unloading to outbound dock in under five minutes. A mixed-SKU carton with damaged labels, wrapped in excessive tape, can require Problem Solve → Prep → Each Receive, taking far longer — and increasing the risk of inventory errors that the seller has no effective recourse to dispute.
When Amazon's ONT8 receive center opened in Southern California, a large volume of Chinese seller freight arrived for the first time at a brand-new facility whose staff had not been prepared for the quality variance. Mixed-SKU cartons sealed with layers of yellow packing tape, unlabeled or mis-labeled items, broken barcodes — the combination nearly paralyzed the facility's processing capacity and sent shockwaves through the broader network.
That incident shaped receiving protocols for years. The lesson has not changed: the cleaner your freight, the faster it moves, the less human intervention touches it, and the lower your risk of inventory discrepancies.
One of the most practically important things to understand about the inbound process is the distinction between two inventory states that Amazon's platform displays differently:
The gap between these two states — which can span several days depending on transit time and fulfillment center workload — is when you are most vulnerable to the misleading appearance of stock that cannot yet be shipped on time.
Most inbound problems have preventable root causes. Based on what the receiving process rewards and penalizes, here are the highest-leverage things a seller can do:
The principle underlying all of these is the same: every time a human has to intervene in your inbound process, the risk of an error increases and the time to sellable status grows. Your goal is to make your freight invisible — the kind of shipment that moves through the system without triggering a single exception.