Product 2 of 5 ยท Assort and buy
The right range in each store, bought to the right depth.
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.
| Style | Role | Stores | Units | Sell-through |
|---|---|---|---|---|
| Rib crew tee | Core | 142 | 18,400 | 88% |
| Linen camp shirt | Fashion | 96 | 7,200 | 81% |
| Wrap midi dress | Fashion | 88 | 5,100 | 76% |
| Merino cardigan | Core | 120 | 9,600 | 84% |
What goes wrong today.
Every store gets the same range
A small mall store and a flagship carry the same styles in the same colors, and the small store's shelf fills with what its customers never buy.
Depth decided by feel
Too shallow and a winner sells out by week four. Too deep and it's the first style on the markdown rail.
The tail shows up after the order
What a range will leave behind is only visible once it's on the shelf, when nothing can be done about it but discount.
What assort and buy does.
Store grades and clusters
Stores grouped by what they actually sell, by category and price point, not only by total sales volume.
A range for each cluster
Which styles and colors go to which stores, within each store's space and presentation minimums.
Buy depth by style
Units to buy for every style, with the expected sell-through and the units likely left at season end shown beside each one.
New styles forecast from similar ones
A style with no history is forecast from past styles that share its attributes: category, fabric, fit, price and color family.
Core and fashion treated differently
Core styles are bought for replenishment. Fashion styles are bought once, to sell through by a set exit date.
Checked against open-to-buy
Every change to the range shows its effect on the budget, so the buy closes on plan.
From your data to a decision you can check.
Every recommendation shows its reasons. Planners adjust and approve before anything is sent.
Reads
- Sales history by style, store and attribute
- Product attributes for new and carry-over styles
- Store space and presentation rules
- Open-to-buy from the season plan
Decides
- Which styles each store carries
- Units to buy by style and color
- Expected sell-through and leftover per style
Sends
- The range plan to your product lifecycle or merchandising system
- Buy quantities for purchase orders
- Store counts per style to size and pack
One model behind every decision.
Assort and buy 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 assort and buy.
Assort and buy 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 assort and buy.
Does it choose the products we design or source?
No. Your merchants choose the products. SeasonTail decides where they go and how many to buy, and shows the consequence of each choice.
How are brand-new styles handled?
From their attributes. SeasonTail finds past styles with the same category, fabric, fit, price and color family, and forecasts from how those sold in each store.
Can we lock a style into every store?
Yes. Must-have styles, minimum presentations and store exclusions are rules the range is built around.
See assort and buy on your own season.
Bring one category's sales and stock. We'll show you what SeasonTail would decide, and why.