How should an FBM seller pilot Multi-Location Inventory?
Start with a small group of stable SKUs and warehouses, enable the required shipping automation, transmit location-level inventory through one controlled method, and compare promised versus actual delivery. Expand only when feed accuracy, routing, cancellation, late-shipment, and contribution thresholds hold through normal exceptions.
Amazon currently makes Multi-Location Inventory available to eligible US merchant-fulfilled operations using supported Seller Central, feed, API, or integration methods. It uses location-level stock with Shipping Settings Automation to calculate delivery promises from relevant stocked locations; current public guidance excludes FBA inventory.
Prepare each fulfillment location
- Location identifier, address, operating calendar, cutoff, handling time, carrier services, capacity, and backup owner.
- SKU mapping, usable quantity, reserved stock, safety buffer, damaged units, inbound units, and update frequency.
- System of record, feed or integrator, timestamp, retry behavior, duplicate protection, and reconciliation report.
- Shipping template, automation setting, service coverage, pickup reliability, and holiday exceptions.
- Outage, oversell, late pickup, split order, warehouse closure, and manual fallback procedure.
Test inventory accuracy before faster promises
Run shadow comparisons between physical sellable stock, the warehouse system, the outbound location feed, and Amazon's visible quantity. Test sales, cancellations, returns, transfers, damaged stock, and simultaneous orders before reducing buffers.
A faster customer promise is safe only when the selected warehouse can pick, pack, hand off, and track the order within the configured schedule. Keep a location-specific buffer until latency and exception behavior are proven.
Measure the pilot by warehouse and SKU
- Inventory-feed success, data age, oversells, suppressed offers, manual corrections, and unexplained quantity differences.
- Promised versus actual delivery, handling compliance, on-time shipment, valid tracking, cancellations, and customer contacts.
- Carrier, zone, expedited-shipping, split-order, labor, software, and exception cost per delivered order.
- Conversion and contribution compared with a similar pre-pilot or control period.
- Root cause, corrective owner, verification, and expansion decision for every material exception.
Keep an immediate rollback path
Pause expansion or restore a conservative manual promise when inventory updates become stale, a location closes, carrier performance degrades, or cancellation and late-shipment signals exceed the pilot threshold. Do not rely on automation while its source inventory is incomplete.
Participation, supported update methods, shipping-template limits, eligible inventory, settings, and program behavior can change. Verify the current Multi-Location Inventory page, Seller Central configuration, API documentation, and integrator support before launch or architecture changes.