Library · Stock / inventory · How to run this
Fullstack campus restock wait is not ShipBob FC restock wait
Return units on a Fullstack campus restock window stay unsellable for restock days while demand/day keeps moving. Multiply restock days by demand/day for lag demand. FS restock cover gap = max(0, lag demand − return units).
Pair: Returns restock lag on Stock. FC twin: ShipBob restock lag. Dock twin: restock-back.
What you type
Return units — Campus return units still in Fullstack restock (not sellable yet).
Restock days — Written lag days until those campus returns become sellable again.
Demand / day — Sellable demand units per day for that SKU on the same campus cut.
FS restock cover gap = max(0, restock days × demand/day − return units). A wide FS restock cover gap usually means putaway delay on that campus — chase that dock; never invent an FS restock cover-gap chip.
What not to do
Do not invent an FS restock cover gap. Do not pour a ShipBob or ShipMonk restock-lag export into Fullstack fields. Do not fold restock-back % or damage-claim counts into cover-gap fields. Do not blend campuses when one dock owns the stuck returns.
Related: Stock, ShipBob restock lag, restock-back, receiving is not sellable.
Procedure
- Type return units, restock days, and demand/day.
- Read FS restock cover gap.
- Chase campus restock putaway when FS restock cover gap is material.
Failure modes
- Inventing an FS restock cover gap.
- Dumping a ShipBob or ShipMonk restock-lag file into Fullstack fields.
- Folding restock-back % counts into cover-gap fields.
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
- FS restock cover gap
- max(0, restock days × demand per day − return units in restock).
Work with us — We run this job on your accounts. Services
FAQ
- Is this ShipBob returns restock lag?
- ShipBob prices FC stuck returns. [Returns restock lag](/manuals/shipbob-returns-restock-lag) stays on ShipBob. Campus counts never leave Fullstack here.
- Is this Fullstack returns-restock rate?
- Dock-cleared share vs cover gap. [Returns-restock rate](/manuals/fullstack-returns-restock-rate) is dock-cleared ÷ dock-received. Here lag demand races return units still in restock.
- What FS restock cover gap should I invent?
- None. Enter return units, restock lag days, and demand units per day from the same Fullstack campus restock export.