Product 4 of 5 ยท Allocate and replenish
Stock where it sells, before the size runs out.
SeasonTail sets the first allocation and every weekly replenishment and transfer by store and size, so the run stays whole where customers are buying.
| Size | Units | From | To | Why |
|---|---|---|---|---|
| M | 12 | Denver, Cherry Creek | Chicago, Loop | Chicago sells M twice as fast |
| S | 8 | Portland, Pearl | Miami, Brickell | Miami has 1.5 weeks of S left |
| XL | 6 | Miami, Brickell | Denver, Cherry Creek | XL unsold in Miami since week 3 |
What goes wrong today.
Allocated by store grade, not by size
An A store gets more of everything, including the sizes it never sells.
Replenishment that reacts too late
Min and max triggers fire once a size is already gone. The store loses the sale and the week.
Transfers nobody trusts
Moving stock between stores is judged by hand, so it happens too rarely, too late, or where it costs more than it earns.
What allocate and replenish does.
First allocation
Each store's opening stock by size, from its own size curve and expected sales for the first weeks.
Warehouse holdback
How much to keep back for later, and for which stores, so the units go where the season proves they sell.
Weekly replenishment by size
Orders from the warehouse sized to each store's sales rate and lead time, before a size runs out.
Store-to-store transfers
Moves suggested only where the margin they protect covers the cost of shipping and handling.
Size-run protection
Broken runs consolidated into fewer stores, so more stores keep a full run and fewer are left with odd sizes.
Your constraints
Store capacity, presentation minimums, shipping days and carton quantities are built in.
From your data to a decision you can check.
Every recommendation shows its reasons. Planners adjust and approve before anything is sent.
Reads
- Daily or weekly sales and stock by store and size
- Warehouse stock and inbound purchase orders
- Store capacity and presentation rules
- Shipping days and costs
Decides
- Opening stock by store and size
- Weekly replenishment orders
- Transfers between stores
Sends
- Allocations and replenishment to your warehouse or allocation system
- Transfer lists to stores
- Sell-through by size back to pricing
One model behind every decision.
Allocate and replenish reads from the same season model as the other four decisions. Use it on its own, and every one you add later starts with what it has learned.
How the platform fits togetherKeep your stack. Add allocate and replenish.
Allocate and replenish works on its own, next to the systems you already use. Add the other decisions when you're ready: they read from the same season model, so each one starts with everything the last one learned.
See how it fits together- Works with what you run
- Exports from your merchandising, ERP and allocation systems are enough to start. Decisions go back in the formats those systems already take.
- Planners stay in charge
- Every recommendation shows its reasons. Planners adjust and approve, and nothing leaves until they do.
- Your data stays yours
- It is used to plan your season, and never shown to another retailer.
Questions about allocate and replenish.
We already have an allocation system. Do we need to replace it?
No. SeasonTail can send its quantities to the system you use today, which keeps running the warehouse and store orders.
How often does it run?
As often as your data arrives: daily or weekly. Most teams review replenishment on their usual weekly rhythm.
Does it account for the cost of a transfer?
Yes. A transfer is only suggested when the margin it protects is larger than what it costs to move the stock.
See allocate and replenish on your own season.
Bring one category's sales and stock. We'll show you what SeasonTail would decide, and why.