---
title: Inventory Velocity Crisis & Replenishment Planning
type: article
created: '2025-10-29'
updated: '2025-10-29'
source_docs:
- raw/2025-10-29-weekly-call-w-gilbert-97690098.md
tags:
- inventory
- amazon
- replenishment
- velocity
- fba
- cellarize
- operations
layer: 2
client_source: null
industry_context: null
transferable: true
---

# Inventory Velocity Crisis & Replenishment Planning

## Overview

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 [[wiki/clients/cellarize/_index|Cellarize]] 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 Velocity Trap: How It Happens

1. **Sales accelerate** beyond initial projections (often driven by successful PPC, organic rank gains, or seasonal demand).
2. **Replenishment lead times** (production → warehouse → FBA inbound processing) remain fixed — often 4–8 weeks or more.
3. **Inventory sheets** are updated manually or on a lag, so the apparent "months of stock" figure is stale by the time it's reviewed.
4. **Inbound shipments** may be in transit or in FBA receiving, not yet reflected in available inventory counts, creating a false sense of security.

The result: a team believes they have adequate stock, places a reorder on a normal schedule, and runs out before the new inventory arrives.

---

## Case Example: Cellarize 5lb Black Beans (October 2025)

| 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

---

## Warning Signs to Watch For

- Any SKU showing **< 1 month of stock** on the inventory sheet
- A large inbound shipment that **doesn't appear** in available inventory within expected processing time
- Monthly velocity that has **increased significantly** since the last reorder was placed
- Inventory sheet "months remaining" figures that haven't been reconciled against Seller Central's **Inventory Ledger report**

---

## Recommended Response Protocol

### 1. Verify the True Inventory Position
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.

### 2. Calculate Realistic Runway
```
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.

### 3. Escalate Immediately
- Contact the production/supply contact (e.g., Carly for Cellarize) to initiate a reorder.
- Confirm lead time from order to FBA-available and compare against runway.
- If lead time exceeds runway, consider expedited shipping or partial shipments.

### 4. Update the Velocity Sheet
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)

### 5. Send Inventory to FBA Promptly
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.

---

## Structural Fixes

### Automate Velocity Tracking
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)

### Build in Replenishment Lead Time Buffers
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
```

### Review Velocity Monthly, Not Quarterly
For fast-growing SKUs, velocity can change dramatically month over month. A velocity figure from 60 days ago may be significantly understated.

---

## Related Situations in This Account

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.

---

## Action Items (from 2025-10-29 call)

- [ ] Reconcile 5lb Black Beans inbound shipment via Seller Central Inventory Ledger; update velocity sheet (@Gilbert)
- [ ] Call Carly to initiate black beans reorder based on confirmed inventory data (@Gilbert)
- [ ] Send 5lb Black Beans to FBA immediately (@Gilbert)
- [ ] Review all SKUs below 2 months of stock and assess reorder urgency (@Gilbert)

---

## Related Articles

- [[wiki/clients/cellarize/_index|Cellarize Client Overview]]
- [[wiki/knowledge/ecommerce-strategy/amazon-ppc-margin-optimization|Amazon PPC Margin Optimization]]