Each store gets its own draft order. Sized for its own demand.
Stokk treats every location as a first-class entity, not an afterthought of central purchasing. Store managers see a draft they can review and edit — not a blank spreadsheet.
| SKU | On hand | Suggest | Cover |
|---|---|---|---|
| RC-AD-3KG | 4 | 12 | 21d |
| WH-CHK-400 | 0 | 24 | — |
| KONG-CL-M | 11 | 6 | 30d |
| TFS-SAL-12K | 2 | 8 | 14d |
| LMP-OAK-2 | 9 | 0 | 62d |
Sits on top of your ERP. Reads stock, writes transactions, never duplicates the source of truth.
One central plan can't size every store correctly.
When central buying sets one rate for the network, fast stores stock out and slow stores sit on stock. Lateral transfers don't happen because nobody can see both sides at once. Store managers stop trusting the plan.
- Per-location velocity, lead time and capacity
- Lateral transfer suggestions when one store is dry and another overstocked
- Tablet-friendly grid for the back office
- Per-store min/max and case-multiple respect
- Store overrides feed back into next week's plan
Capabilities, in plain language.
Per-store sizing
Each store has its own velocity, lead time and replenishment cycle. Stokk drafts an order tuned to the store, not the network.
Lateral transfers
When one store is overstocked and another is dry, Stokk suggests the transfer before it suggests a fresh PO.
Drafts ready every Monday
No blank-page Mondays. Store managers open a draft, edit four lines instead of building 280, and confirm.
Tablet-friendly grid
The back office runs on tablets — Stokk's grid is built for it. Fast keyboard nav, clean touch targets, no spreadsheet rage.
Multi-tier networks
DC → store, store → store, supplier → DC. All in one model, all sized consistently.
Confirmation flow
Each store confirms its own draft. Stokk learns from every override and explains the changes that mattered.
How replenishment looks across the network.
Two angles: when Stokk catches a lateral transfer opportunity, and how the back office sees every store's draft at once.
Berlin is sitting on 142 days of cover; Hamburg drops below safety stock in 8 days. Lateral transfer is €420 cheaper than a fresh PO and beats lead time by 10 days.
- Reykjavík312confirmed
- Berlin284drafted
- Hamburg198drafted
- Stockholm241confirmed
- Oslo174open
- Copenhagen209drafted
The numbers Stokk customers report after the first cycle.
After the first full ordering cycle, lost-sale events on A-classified items roughly halve.
Buyers stop building proposals from scratch. The Brief lands; they review and approve.
Stokk's per-store sizing and lateral transfers free cash that was sitting on a pallet.
Continuous, offline-capable counts replace the once-a-year shutdown count.
Replenishment that learns from every store override.
When a store manager edits the suggested quantity, Stokk doesn't just accept it — it remembers. Patterns in overrides become input to the next forecast cycle, captured per store and per SKU.
The result is a system that gets more accurate the longer your team uses it, instead of a static rule engine that calcifies the day it ships.
How AI gets used here
Decisions stay explainable. Every recommendation has a written reason and a human approval step. Your data isn't used to train shared models. Claude's prompts are scoped per request.
Plays nicely with the systems you already pay for.
Common questions about this module.
Can we lock down what stores can edit?
Yes. Per-role access controls let buyers limit how far a store can override quantities or add new lines. Default is review-and-confirm with audit log.
Does Stokk handle case multiples and pallet rounding?
Yes. Per-supplier and per-SKU case sizes are respected. Stokk rounds intelligently against demand, not blindly upward.
What if our DC is also a store?
Common. Stokk models hybrid locations. The DC sees its own replenishment from suppliers; downstream stores see their replenishment from the DC.
Other parts of the operating system.
See Replenishment on your data.
A 20-minute demo on your ERP, your SKUs, your stores. We do the work; you decide if it earns its place in your operating system.