Rebalancing
Rebalancingsurfaces suggested store↔store transfers. The classic situation: one store sits on six months of cover for a SKU, another is stocked out, and the next PO won't land for weeks. Moving the stock sideways between stores is the right answer.
What this is and isn't
This is store ↔ store only. Warehouse → store replenishment is handled by Replenishment; that flow runs on a weekly cycle and is unaffected by Rebalancing.
Stokk's job stops at “approved”. The actual picking, shipping, and receiving happens in Talning. Once Talning has shipped and DK has synced, the resulting stock movements arrive back in Stokk through the same channel regular DK transfers do — the inventory grid and chart pick them up automatically.
Plan a trip
The page is a planner, not a suggestion list. You start with the trip in mind: “we're driving from Krossmói to Spöng on Wednesday — what should go on the truck?”
Pick a From store and a To store at the top. The grid below fills with every SKU with stock at the source, joined with the destination's stock and target. Sort, filter, and resize like any other Stokk grid.
Tick the SKUs you want to ship and click a quantity to edit it inline. Editing a quantity also ticks the row — the buyer decision is one motion. The toolbar shows the live total (“3 SKUs · 24 units”). Hit Approve trip to record the lot as one transfer order. Re-approve more SKUs on the same From → To later in the day and they fold into the existing order rather than creating a duplicate.
The ★ suggestions
Some rows are starred — those are the heuristic's picks:
- FROM-store has stock above its target (excess);
- TO-store has shortage of at least 4 units;
- FROM is not selling the SKU faster than TO — never move from a fast-mover to a slow location;
- The warehouse can't cover the gap — if there's enough at the warehouse, the SKU rides the regular Replenishment cycle instead;
- The same (SKU, FROM, TO) wasn't already approved in the last 14 days.
The natural target is min_display + safety + rate × review_period — the same formula the PO suggestion uses. The Suggestions only toggle in the toolbar defaults to on; uncheck it to see every SKU at the source so you can add off-list items (display changes, brand rotations, damaged returns).
The Details panel
Select a row and click Details (or press d) to open a chart panel docked at the bottom of the page. The chart shows the source store's stock and sales history so you can visually confirm there's real excess — not a one-week spike that's about to sell down. Switch to TOvia the location dropdown in the chart toolbar to see the destination's history.
The Approved tab
One card per approved trip, with its SKU lines underneath. This is the list you hand to Talning. Click Export CSV to download it in a paste-friendly format.
Once Talning has actually shipped a trip (and DK has synced the stock movements back to Stokk), click Mark done on the card. If you change your mind before Talning processes, click Cancel — the candidate becomes available for re-suggestion immediately.
When to run it
Once a week, before transfer day. The list is recomputed live from the latest stock snapshot, so don't worry about scheduling — open the page when you're ready.