What kanban for FBA actually means
Kanban for FBA is the attempt to apply Toyota’s pull-based replenishment system to Amazon FBA inventory operations. In the original kanban method, downstream consumption (a unit sold or used) triggers an upstream replenishment signal via a physical card or electronic equivalent. The factory only produces what the next station has consumed. Inventory stays minimal because nothing moves until a real signal arrives.
The kanban model works beautifully when lead times are short and predictable, which is exactly the opposite of the typical Amazon FBA sourcing scenario. Most FBA products ship from Asia with 45-60 day production lead times plus 18-25 days of ocean freight plus 14-21 days of FBA receiving. Total: 75-105 days from PO to FBA-available. Try running pure kanban on that lead time and you stock out on day 30.
This is why kanban for FBA cannot be a copy-paste of textbook kanban. It has to be a hybrid: forecast-driven push for the long-haul supplier-to-port leg, and kanban-style pull for the short-haul port-to-FBA leg using AWD or a 3PL as the buffer.
The kanban card count calculation
For FBA, this formula only works for the buffer-to-FBA leg. The lead time L is the AWD or 3PL transfer time to FBA, typically 7-14 days, not the supplier lead time. The supplier-to-buffer leg still has to run on forecast-based push because the lead time is too long for kanban pull signals to reach back in time. You can read more about the underlying methodology on Wikipedia’s kanban entry.
Example: hybrid kanban for an FBA supplement brand
You sell a daily multivitamin at 150 bottles/day across 3 SKUs. Sourcing setup: supplier (China) to AWD takes 72 days total (forecast-based push, quarterly orders). AWD to FBA takes 10 days (kanban pull, weekly).
Card calculation for the AWD-to-FBA leg, using container size C = 100 bottles/case:
- Number of Kanban Cards = (150 x 10 x 1.20) ÷ 100 = 1,800 ÷ 100 = 18 cards
Each card represents 100 bottles in transit or queued for transfer. The 18-card buffer covers 12 days of demand including 20% safety factor. Whenever FBA inventory of an SKU drops by 100 bottles, you release a kanban signal to the AWD facility, which ships the next 100-bottle case.
Meanwhile, the supplier-to-AWD leg runs on a 72-day push cycle. You order 13,500 bottles per quarter (90 days x 150) plus a buffer based on demand forecasts. AWD holds 60-90 days of supply at any moment. The kanban for FBA portion only manages the last 10-day pull window where signals can travel fast enough to matter.
Why pure kanban fails for FBA
Toyota’s original kanban implementation used cards traveling between adjacent stations on a factory floor. The signal-to-replenishment cycle was minutes. Amazon FBA sellers operate at the opposite end of the lead-time spectrum.
Lead time math kills the pull signal. If a kanban card takes 75 days to trigger replenishment, by the time the signal reaches your supplier and the next batch arrives, demand has already shifted. You need forecasting and inventory buffer ahead of any kanban pull mechanism.
FBA restock limits override pull signals. Even if your kanban for FBA system says send 800 units, Amazon may only accept 400. The remaining 400 stay at the buffer location, and your card count assumptions break.
Cash flow conflicts with kanban orthodoxy. Kanban purists target near-zero buffer inventory. FBA sellers cannot afford to stock out during Q4. The right kanban for FBA approach accepts a 30-60 day buffer at AWD or 3PL because the cost of a stockout (lost Buy Box, ranking damage, missed sales) far exceeds the carrying cost.
Common mistakes
- Trying to run pure pull from supplier to FBA. The lead time is too long. Sellers who attempt this stock out repeatedly because consumption signals cannot reach back to Asia in time. Always use a hybrid push-pull model.
- Sizing kanban cards based on average demand. Average demand undersizes cards for peak weeks. Use the 80th-90th percentile of weekly demand for card sizing, then re-evaluate quarterly.
- Skipping the buffer location entirely. Kanban for FBA only works if you have a buffer (AWD, 3PL, or even a small dedicated portion of your home warehouse) between the long-lead-time supplier shipment and the short-lead-time FBA replenishment. Without that buffer, you are running open-loop forecast-only and calling it kanban.