The platform
One season model. Five decisions.
Your data feeds one model of demand. The model drives every planning decision. Each week's results go back into the model, so the next decision starts from what just happened.
- 1 · Data
Your season, in one place
Sales, stock, products, stores and supplier pack rules from the systems you already run, cleaned and joined by store, style and size.
- Sales and stock
- Products and stores
- Supplier packs
- 2 · Season model
One model of demand
Demand by store, size and week, including the sales lost when a size was missing. Every decision reads from it.
- Store-level demand
- Lost sales
- Size curves
- 3 · Decisions
Five decisions, one season
From the first forecast to the last markdown. Use all five, or start with the one you need.
Every week, what sold and what didn't goes back into the model. The next decision starts from what just happened.
Why one model matters.
Most retailers plan each decision in its own tool or spreadsheet, from its own version of demand. The end of season pays for the gaps between them.
Decisions that agree
The buy, the size split, the allocation and the markdown all start from the same demand by store and size. They stop contradicting each other.
Lost sales counted once, used everywhere
Demand hidden by sell-outs is estimated in the model, so every decision plans for what customers came for, not only what they could find.
Each decision teaches the next
What a style needed to clear informs next season's buy depth. Where a run broke informs next season's size curve.
A week in the loop.
- 1
New sales and stock arrive
Daily or weekly files, or direct connections, from the systems you already run.
- 2
The model updates
Demand by store, size and week is re-estimated with what just sold, and what couldn't.
- 3
Decisions are proposed
Replenishment, transfers, reforecasts and price changes, each with the reasons behind it.
- 4
Planners approve, results flow back
Approved decisions go to your systems. What they achieve becomes next week's data.
Five decisions, from the first forecast to the last markdown.
- 1
Forecast and plan
SeasonTail forecasts demand by store, channel and week, and turns it into the sales, margin and inventory budgets your season is bought against.
Explore forecast and plan - 2
Assort and buy
SeasonTail decides which styles each store carries and how many units to buy of each, with the cost of the season's tail already in the numbers.
Explore assort and buy - 3
Size and pack
SeasonTail decides how each buy splits across sizes and stores, and how it ships in packs, so every store keeps a sellable run of sizes until the season ends.
Explore size and pack - 4
Allocate and replenish
SeasonTail sets the first allocation and every weekly replenishment and transfer by store and size, so the run stays whole where customers are buying.
Explore allocate and replenish - 5
Price and promote
SeasonTail decides when, where and how deep to cut price, and which promotions earn their cost, store by store, with the stock each store has left.
Explore price and promote
Keep your stack. Add one decision.
You don't have to replace a system to start. Pick the decision that costs you most, often size and pack, where the tail is easiest to see. Each one you add reads from the same season model, so it 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.
See your own season in SeasonTail.
Bring one category's sales and stock. We'll show you where its tail is today.