Prompt
How do I set up a replenishment planning system for store-level ordering with short shelf life products?
Latest observation
Setting up replenishment planning for store-level ordering with short shelf-life products is mostly about balancing service level, freshness, waste, and store workload. The right design usually combines a good forecasting model, inventory policy, and operational constraints like delivery cadence and minimum order quantities.
1) Define the planning objective
For short shelf-life items, the goal is usually not “minimize stockouts only,” but:
- Maintain target in-stock/service level
- Minimize spoilage and write-offs
- Keep inventory within freshness limits
- Fit store ordering and receiving capacity
A good starting KPI set is:
- Fill rate / service level
- Waste %
- Days of supply
- Forecast accuracy
- Expired inventory value
- Order adherence / manual overrides
2) Segment products
Not all items should be planned the same way. Split products by:
- Shelf life: very short, short, moderate
- Demand pattern: stable, seasonal, intermittent, promotional
- Handling: ambient, chilled, frozen
- Order frequency: daily, 2–3x/week, weekly
- Criticality: high-volume staples vs. niche items
For example:
- Daily fresh items: bread, milk, salads → very tight ordering, often manual-assisted
- Short shelf-life packaged items: ready meals, juices → forecast + coverage policy
- Longer-life perishables: yogurt, cheese → standard replenishment with freshness checks
3) Build a demand forecast at store-item level
Store-level replenishment depends on a forecast that reflects local demand.
Forecast inputs
- Historical sales by store-item-day
- Day of week patterns
- Seasonality and holidays
- Promotions and price changes
- Weather/local events if relevant
- Store attributes (size, format, demographics)
- Substitution effects and stockout history
Important
Adjust sales history for:
- Stockouts: otherwise demand is understated
- Promotions: separate baseline vs. uplift
- New items: use analogs or hierarchy-based forecasting
For short shelf-life items, use a short-horizon forecast:
- Daily or intra-week
- Rolling horizon: next 1–7 days depending on lead time and delivery frequency
4) Choose the replenishment logic
A practical approach is to order to a target inventory position that accounts for:
- Forecast demand over lead time
- Safety stock
- Shelf-life limit
- Minimum display/pack constraints
Basic formula
Order quantity = Target inventory position − Current inventory position
Where target inventory position might be:
Forecast demand during lead time + safety stock + presentation stock
But for short shelf-life items, add freshness controls:
- Do not order beyond what can sell before expiry
- Cap order quantity by remaining shelf-life capacity
- Consider on-hand age profile, not just total units
5) Add shelf-life-aware inventory rules
This is the core difference from normal replenishment.
Use age-bucket inventory
Track inventory by age or remaining shelf life:
- Today’s receipt
- 1 day old
- 2 days old
- etc.
Then prioritize:
- Sell oldest stock first
- Order only enough new stock to meet demand before expiry
Common policies
- Max days of cover: e.g., never exceed 2–3 days on hand
- Max age on receipt: reject or reduce ordering if product will expire too soon
- FEFO: First Expired, First Out
- Dynamic order cap: based on sell-through rate and remaining shelf life
6) Model lead time and delivery frequency
For perishables, lead time is critical.
You need to know:
- Store ordering cutoff times
- Warehouse picking time
- Transport time
- Delivery frequency by store
Example:
- If a store gets deliveries Monday, Wednesday, Friday, then on Monday the order should cover demand until Wednesday arrival, not a full week.
Short shelf-life planning often works best with:
- Daily or frequent ordering
- Tight order windows
- Automated suggested orders with store override
7) Include service-level and waste tradeoffs
Different items should have different service targets.
Example:
- High-traffic staple: 98% service level
- Moderate perishables: 95%
- Highly volatile fresh item: lower target if waste cost is high
A useful approach is to optimize:
Total cost = stockout cost + holding cost + waste cost + ordering cost
For short shelf-life items, waste cost is often much larger than regular carrying cost.
8) Use constrained replenishment rules
Store ordering usually needs practical guardrails:
- Minimum order quantity
- Case pack size
- Pallet/carton constraints
- Store capacity limits
- Supplier constraints
- Temperature zone capacity
- Labor constraints for receiving and stocking
The system should suggest orders that are:
- Feasible
- Easy to execute
- Not overloaded with tiny fragmented quantities
9) Design exception management
Not everything should be fully automated.
Set up alerts for:
- Forecast errors
- Sudden demand spikes
- Inventory near expiry
- Missed deliveries
- Promotion anomalies
- New item launches
- Negative on-hand / shrink issues
Allow planners or store managers to review:
- High-risk items
- Very low forecast confidence
- Items approaching expiry
- Items with repeated stockouts or waste
10) Start simple, then improve
A good phased rollout:
Phase 1: Rule-based replenishment
- Days of cover rules
- Basic safety stock
- FEFO
- Manual review for exceptions
Phase 2: Forecast-driven replenishment
- Store-item forecasts
- Dynamic safety stock
- Age-aware inventory
- Promotion adjustments
Phase 3: Optimization / ML
- Probabilistic forecasting
- Order optimization with waste costs
- Store clustering
- Automated exception prioritization
11) Data you’ll need
Minimum data set:
- Sales history by store-item-day
- On-hand inventory
- Receipts and transfers
- Product shelf life
- Lead time and delivery schedule
- Pack sizes and MOQ
- Promotions/prices
- Stockout flags
- Waste/expiry records
Better data:
- Inventory age/lot tracking
- Display stock vs backroom stock
- Weather and local events
- Substitute relationships
- Shrink and spoilage causes
12) A practical order calculation framework
For each store-item:
- Forecast demand for the replenishment horizon
- Determine inventory age and usable stock
- Subtract expected sell-through of existing stock before expiry
- Add safety stock based on forecast uncertainty
- Apply constraints:
- pack size
- MOQ
- max shelf-life coverage
- store capacity
- Produce suggested order quantity
13) Key success factors
This kind of system works well when:
- Forecasts are good at store-item level
- Inventory age is visible
- Delivery cadence matches demand variability
- Store staff trust the suggested order
- Exceptions are actively managed
- Waste and stockout KPIs are reviewed together
14) Recommended implementation architecture
Typical setup:
- Demand forecasting engine
- Inventory and expiry tracking
- Replenishment policy engine
- Constraint/feasibility layer
- Store order interface
- Analytics dashboard for KPIs and exceptions
If you want, I can also give you:
- a simple replenishment formula template,
- a data model/schema for the system, or
- a step-by-step implementation plan in Excel, SQL, or Python.