A recurring risk in fast-growing Amazon accounts is the inventory velocity trap: sales accelerate faster than replenishment cycles can keep pace, creating stockout risk even shortly after a large shipment arrives. This is compounded when inventory tracking sheets lag behind Seller Central's actual data, masking the true urgency of the situation.
The 5lb Black Beans SKU in the [1] account is a live example of this failure mode. Despite a recent large inbound shipment, only 267 units were on hand — less than one month of stock — against a monthly sales velocity of ~366 units. Without immediate action, a stockout was imminent.
The result: a team believes they have adequate stock, places a reorder on a normal schedule, and runs out before the new inventory arrives.
| Metric | Value |
|---|---|
| Units on hand (FBA) | 267 |
| Monthly sales velocity | ~366 units/month |
| Months of stock remaining | ~0.7 months |
| Recent large shipment? | Yes — but not fully reflected in tracking sheet |
The inventory sheet showed a discrepancy: a recent large shipment had been sent to FBA, but the available unit count did not reflect it. This pointed to one of two problems:
- The shipment was still in transit or in FBA receiving (not yet available).
- The tracking sheet macro had not been updated to account for the inbound.
Either way, the effective runway was under one month — a critical threshold requiring immediate escalation.
"We'll be out of stock before we can ship it again." — Mark Hope, weekly call 2025-10-29
Do not rely solely on the tracking sheet. Cross-reference with Seller Central directly:
- Reports → Fulfillment → Inventory Ledger: shows all units received, sold, and in transit by ASIN.
- Check Manage Shipments for any inbound shipments in "In Transit" or "Receiving" status and confirm their contents.
Runway (days) = (Units Available + Units Inbound) / Daily Velocity
Daily Velocity = Monthly Velocity / 30
If runway is under 45 days, treat as urgent. Under 30 days, treat as critical.
After reconciling with Seller Central, update the tracking sheet with:
- Corrected on-hand units
- Confirmed inbound units and expected arrival date
- Revised velocity based on the most recent 30-day period (not historical averages)
Any finished goods sitting at a 3PL or warehouse should be shipped to FBA immediately when a velocity crisis is identified. Do not wait for a full pallet — partial shipments are preferable to a stockout.
Manual spreadsheet macros updated daily are fragile. Consider:
- Pulling velocity data directly from Seller Central's Business Reports → Detail Page Sales and Traffic by ASIN
- Setting up automated reorder alerts when months-of-stock drops below a threshold (e.g., 2 months triggers review, 1 month triggers order)
Reorder points should account for the full replenishment cycle:
Reorder Point = (Lead Time in Days × Daily Velocity) + Safety Stock
Safety Stock = (Max Daily Velocity - Avg Daily Velocity) × Lead Time
For fast-growing SKUs, velocity can change dramatically month over month. A velocity figure from 60 days ago may be significantly understated.
The 5lb Black Beans were the most critical case, but the same review surfaced multiple other SKUs below 2 months of stock in the Cellarize account. Any account with accelerating overall sales (Cellarize was showing strong year-on-year growth) should be treated as high-risk for velocity-driven stockouts across the catalog, not just on the top SKU.