Allocation of stock across stores
Splits an incoming run across stores in proportion to their sales taking existing stock and capacity into account, keeping part at the warehouse for replenishment.
At a glance
- What question does it answer?
- How to split an incoming run across stores and how much to keep at the warehouse.
- What data is needed?
- Quantity to allocate, warehouse reserve and weeks in the sales period.
- How to read the result?
- Look at cover after allocation in weeks: it should be roughly equal across stores. “Stores under-supplied” are those where need exceeds what was allocated because of the reserve or capacity. Example on the default values: 3,000 units arrive with a 20% warehouse reserve: 2,400 go to stores and 600 stay in the warehouse. Stock after distribution is about 8.4 weeks of sales in every store and one store gets less than it needs. If a store receives less because of capacity, enlarge the reserve or send the rest online. Next: “Does moving stock between stores pay back” and “Reorder from early sales”.
Why and how to reason
Splitting a run equally between stores is unreasonable: where goods sell faster they will run out sooner. So the guide is the store’s share of sales. But one must not forget that stores already hold something. The idea is that after distribution the stores' stock is equal in weeks of sales, so that no one is “richer” than the others.
For that, a store’s desired stock = share of sales x (run to distribute + current stock of all stores). Need = desired stock - what already lies there (and not more than capacity). If needs exceed the available goods, they are reduced proportionally. Part of the run is kept in the warehouse for replenishment.
Example. Run 3,000, reserve 20% = 600 in the warehouse, 2,400 to stores. Store stock 1,880. The Central store accounts for 4,200 of 13,300 sales, which is 31.6%: desired stock 0.316 x (2,400 + 1,880), about 1,352, on the shelf 420, so the shipment is about 931. Post-distribution stock in all stores is about 8.4 weeks.
When to use it
It fits when a run arrives or before a season, to decide how much to send to each point. Suitable for a network with several stores and online. Assumption: past weeks' sales reflect future demand. For a new point with no history set manually. It does not replace size allocation: distribute quantity first, then sizes. Revisit the split when a store changes format.
How to read the result
Check whether “stock after distribution” in weeks is equal across stores: the minimum and maximum in the example are close (8.36 and 8.37). Stores with undersupply hit capacity or a shortage of goods: the decision is a different split or an additional run. Warehouse leftover allows topping up bestsellers. Check that you did not deprive a weak store of assortment that must always be on display. Decision: confirm the split, revisit capacities, decide what to deliver during the season. It is worth checking the largest and smallest stores manually: the calculation gives an average, while you know local specifics.
Common mistakes
The usual mistakes: using sales for different periods across stores; not accounting for a store that was out of sales for renovation; ignoring capacity; sending everything to strong stores and leaving weak ones without a display. Also: not leaving a reserve in the warehouse. Also: ignoring logistics constraints.
What data is needed?
- Quantity to allocate, warehouse reserve and weeks in the sales period.
- By store: sales for the period, current stock and capacity (optional).
- Where to take it: the quantity to distribute from the goods receipt or delivery plan (WMS, 1C); sales and stock by store from the goods movement report for the sales period; capacity from the store layout and the merchandiser. Set the warehouse reserve by the replenishment lead time.
Inputs
| Field | Unit | Value in the example | Meaning |
|---|---|---|---|
| Units to allocate | units | 3,000 | How many units arrive for allocation across stores; part stays at the warehouse as the reserve. |
| Keep at the warehouse for replenishment | % | 20 | A reserve for stores’ top-ups once sales show. |
| Weeks in the sales period | weeks | 26 | Used to show cover in weeks of sales. |
How it is calculated
| Step | Formula |
|---|---|
| Desired store stock | Sales share × (allocatable + current stock of all stores) |
| Need | Desired stock − current (capped at capacity) |
| Allocate | Need, scaled down proportionally if it exceeds what is available |
Worked numbers
Default values from the app; in the interactive version you enter your own.
- Allocated to stores
- 2,400 units
- Kept at warehouse
- 600 unitsThe reserve plus what did not fit by capacity.
- Cover after allocation, min
- 8.4 weeks
- Cover after allocation, max
- 8.4 weeks
- Stores under-supplied
- 1Need exceeds what was allocated because of the reserve or capacity.
Split by store
| Store | Sales share | Stock now | Allocate | Cover after, weeks |
|---|---|---|---|---|
| Central mall | 32 % | 420 | 931 | 8.4 |
| High street | 20 % | 380 | 457 | 8.4 |
| Suburban mall | 11 % | 260 | 223 | 8.4 |
| Outlet | 14 % | 520 | 91 | 8.4 |
| Online store | 23 % | 300 | 698 | 8.4 |
Of 3,000 units, 2,400 go to stores and 600 stay at the warehouse for replenishment. The split follows sales share: make sure a new store without history is not left without stock and adjust by hand.
Nuances and limits
- Allocation by sales share does not know promotions and a store’s role: adjust by hand, especially for new stores without history.
- A new store with no sales history would get nothing: enter analog-based sales for it by hand.
- Distribution by sales share does not know about promotions or the store’s role: adjust after the calculation.