What FBA transfer is designed to do
FBA transfer is the controlled hand-off between your ocean or air first-leg shipment and Amazon fulfillment centers. Freight lands in the United States, is received at a Zistone warehouse, counted, put away, labeled to Amazon's current inbound plan, and then dispatched on a booked delivery appointment. Zistone International operates seven processing centers across the US East, Central, and West. The network exists so sellers can absorb schedule variance, labeling errors, weight-limit issues, and appointment congestion inside a warehouse they can see - not on a yard where a refused trailer becomes an emergency.
Direct-to-Amazon looks simpler until a carton mark, appointment, or dimensional weight is wrong. Then the shipment is rescheduled, refused, or billed for detention. Transfer is not an extra touch for its own sake. It is a quality gate: receive the container or LCL lot cleanly, correct the label and carton data, then present Amazon with a shipment that matches the ASN. Sellers who treat transfer as a buffer, rather than as last-minute salvage, consistently see more stable check-in and fewer stranded pallets.
Why seven warehouses beat a single coastal shed
East Coast buildings serve New York, New Jersey, Pennsylvania and nearby FC clusters. Central sites cover Midwest and South-Central demand, including lanes toward Chicago and Dallas. West Coast sites sit close to Los Angeles and other Pacific gateways so boxes can move from terminal to putaway without a transcontinental dray. All seven sites share one WMS language: inventory, exceptions, and tracking numbers are visible in the same way, so operations teams do not reconcile six different spreadsheets.
Proximity cuts live miles and appointment conflict. In peak season, cargo can be drayed into Zistone, processed, and held until Amazon capacity opens, instead of idling at the port. Multi-node sellers can split one ocean container by SKU or carton count across regions, then book each FC separately. That turns "one all-or-nothing appointment" into a managed rollout. Inter-warehouse balance is possible, but the cheaper design is to inbound to the right coast the first time.
LCL and FCL inbound, including mixed SKUs
We receive both less-than-container and full-container loads. FCL units are pulled by drayage, unstuffed, and checked against bill of lading, packing list, and carton marks. LCL lots are segregated by house bill so freight is not mixed across customers. Multi-SKU pallets, small single-SKU lots, and multi-bill containers are all in scope. Damage, moisture, and shortage are photographed at receipt so insurance or the first-leg carrier can be notified immediately - not after Amazon declines the freight.
Putaway is typically one to two business days. Once cartons are on the system, available units can be used to create transfer orders. Speed never outranks count accuracy: a fast but wrong putaway produces mislabeled FC shipments and a second, more expensive move. Urgent replenishment can be prioritized by agreement, still with SKU-level verification before any FBA label is applied.
The operating sequence
The standard path is: unload and count → putaway (1-2 business days) → WMS visibility → transfer order from seller or ERP → FBA labels issued by email (self-provided labels accepted for pickup accounts) → apply labels against physical SKUs → outbound against the appointment (target within 24 hours when documents and slots are ready) → automatic tracking updates → exception follow-up → FC check-in. Each node has an owner so freight does not sit in an unnamed "somewhere in the building" state.
Labeling is the quality-critical step. Warehouse codes, FNSKUs, and carton weights must match the Amazon plan. Over-taping old marks, using the wrong FC, or covering scannable barcodes are common failure modes we train against. Self-pickup customers receive a time window and a piece-count handoff. For delivered freight, outbound follows the appointed carrier and reference number, then the tracking ID is written back for in-transit visibility.
Visibility, pickup, and exceptions
Competitive transfer is an information product as much as a labor product. Inbound, on-hand, staged, in-transit, and delivered statuses reduce email ping-pong. Marketing and replenishment can plan against real inventory instead of estimated ETA. Exceptions - damage, short, label mismatch, failed appointment - are ticketed until there is a disposition: relabel, rebook, return, or a claims pack.
The 24-hour outbound target assumes complete labels and a valid appointment. If Amazon slots tighten, freight stays in the building and appointments roll, rather than accruing yard fees. For seasonal spikes, prepare labels and FC plans three to seven days ahead and use the warehouse as a planned buffer, not a panic room. Transfer works when it is scheduled into the supply chain, not bolted on after the vessel docks.
Who should use FBA transfer - and how it connects to other services
Transfer fits sellers who need regional FC injection after ocean or air arrival; brands that want US-side label QA; teams whose direct appointments are unreliable; and accounts splitting one container across multiple FCs. Residual units can later move into dropshipping. Amazon removals can flow into relabel or repair. The same seven-site map supports the full loop of inbound, transfer, sell, and return.
Before sailing, share SKU lists, carton counts, gross weights, cubes, and intended FCs so we can pre-position labor. Combined with Zistone booking and last-mile drayage, transfer becomes a managed node rather than a surprise. Contact us to decide East versus West inbound for your mix.