Knowledge base
Stream restock cutoff escalation process
A repeatable workflow for deciding what to do when a live-commerce replenishment wave is about to miss or has already missed its stream cutoff.
Trigger scenarios
- A replenishment request is likely to miss the stream release window
- The team needs a repeatable recovery path before the next live session starts
1. Confirm which cutoff failed first
Check whether the first miss happened at approval, warehouse release, or stream-priority handoff.
- Evidence required: Request timestamp
- Evidence required: Cutoff rule
- Evidence required: Release status
2. Choose the smallest recovery wave
Release the smallest replenishment action that protects the next live window before expanding to larger manual recovery.
- Evidence required: Recovery-wave decision
- Evidence required: Priority SKU list
3. Record the new cutoff owner
Assign one owner for the next timing decision so repeated misses do not recur in the next session.
- Evidence required: Owner note
- Evidence required: Next-cutoff checklist
Common mistakes
- Escalating inventory quantity before confirming the real failure was timing ownership
- Running emergency replenishment without assigning the next cutoff owner
Audience
Live-commerce operations teams coordinating stream and warehouse replenishment windows