Library · Stock / inventory · How to run this
Batch release lag strands demand dollars
A batch stuck past the written release clock leaves demand dollars stranded. Type lag days and daily demand $. Stranded $ = lag days x daily demand $.
Pair: Batch release lag on Stock. Stability: stability hold. CoA: CoA release hold.
What you type
Lag days - calendar days past the written batch release date (or promised ship-ready date).
Daily demand $ - contribution or net demand dollars per day waiting on that batch / SKU.
Stranded $ = lag x daily demand. Pull release forward or cut ads when stranded $ is material - do not invent a lag chip.
What not to do
Do not invent lag days. Do not fold stability testing into this post-release lag. Do not treat dock-received as released. Do not average every SKU when one batch owns the hole.
Related: Stock, stability hold, CoA release hold, lot release vs ads.
Procedure
- Type lag days from the batch calendar.
- Type daily demand $ on that SKU.
- Pull release forward or cut ads when stranded $ is material.
Failure modes
- Inventing lag days.
- Folding stability testing into post-release lag.
- Treating dock-received as released.
Worked example
None on this page yet. When one lands it will be a real case: what broke, the number, and what changed. Not a composite.
Glossary
- Batch release stranded $
- Lag days past written release × daily demand $ waiting on that batch.
Work with us — We run this job on your accounts. Services
FAQ
- Is this stability hold days?
- Related Vitaquest clock. [Stability hold](/manuals/vitaquest-stability-hold-days) is testing days before release. This page is lag after the written release date vs demand $.
- Is this CoA release hold?
- Related QA gate. [CoA release hold](/manuals/coa-release-hold) is CoA not signed. This page is batch release lag days times daily demand $.
- What stranded $ should I invent?
- None. Type lag days from the batch calendar and daily demand $ from the SKU window.