Assortment & range planning
A range built inside its budget.
Options and units by category, against approved OTB. Overspend shows while you build, not after the buy.
Counts drift once the file is emailed.
The range is a workbook. Price points are agreed in a meeting, written nowhere. Nobody can see whether the range spends its OTB.
Option depth comes with its reasons.
Recommended counts per category use historical productivity, newness and sell-through, logic attached. You set the target; the variance stays visible.
FORGE · OPTION ARCHITECTURE
The depth behind the range.
Lakefashion · H2 2027 · Illustrative plan
| Category | Recommended | Target | Variance |
|---|---|---|---|
| 55 | 0 | ||
| 80 | 0 | ||
| 34 | 0 | ||
| 59 | 0 |
Select a category for its rationale. Adjust targets to explore the mix.
Budget use shows while the range builds.
Previews and validation run pre-submission. Targets, actuals, variances and OTB by category, subcategory and store catch the overrun as it happens.
FORGE · CATEGORY OPEN-TO-BUY
Every option has a budget.
Lakefashion · H2 2027 · Illustrative plan
| Category | Budget | Actuals | On order | OTB |
|---|---|---|---|---|
| Blouses | $180k | $112k | $42k | $26k |
| Dresses | $260k | $184k | $61k | $15k |
| Jackets | $140k | $98k | $28k | $14k |
| Bags | $100k | $63k | $22k | $15k |
$70k unallocated. OTB = budget − actuals − on order. All values at cost.
Last year’s actuals sit beside this year’s.
Prior-year benchmarks live in the option plan, so options compare with what sold. Carry forward brings the learning.
FORGE · PRIOR-YEAR BENCHMARKS
Build on what sold.
Lakefashion · H2 2027 · Illustrative plan
| Category | 2026 options | Sell-through | 2027 plan |
|---|---|---|---|
| Blouses | 51 | 78% | 55 |
| Dresses | 64 | 84% | 80 |
| Jackets | 27 | 81% | 34 |
| Bags | 55 | 72% | 59 |
Approval sends the range to purchasing.
Signed-off size recommendations pass into the option plan. Orders come from it with quantities, costs and dates. Nothing is retyped.
FORGE · ALLOCATION · PO SELECTION
From range to ready.
Lakefashion · H1 2028 · Illustrative plan
| Style / colour | Units | Unit cost | Delivery |
|---|---|---|---|
| 1,774 | $24 | 12 Feb | |
| 152 | $18 | 12 Feb | |
| 548 | $22 | 19 Feb |
Interactive example. No purchase order is sent to a supplier.
Newness has a column of its own.
Continuity, seasonal and fashion each get a share of the options, so the mix is a figure, not a feeling.
| Category | Continuity | Seasonal | Fashion |
|---|---|---|---|
| Knitwear | options | options | options |
| Denim | options | options | options |
| Outerwear | options | options | options |
| Footwear | options | options | options |
Each cell holds options, units and a price.
yukti drafts styles into the range.
Accept an option and it becomes a new style for forge to cost. You approve, or let it run.
Five pages border this one.
Upstream and downstream.
Every screen here belongs to core.
Budgets, WSSI, OTB, ranges and sizes, one workspace. This page is the range part.
Questions, answered.
Can we keep our hierarchy and retail calendar?
Yes. Your own hierarchy and fiscal periods.
Can buyers override the recommended option counts?
Yes. You set the target; the variance stays visible.
Does the range know the budget?
Yes. Previews run against OTB before submission.
How does the approved range reach our ERP?
Purchase orders come from the range plan and reach your ERP.
Does this replace our PLM?
No. forge or your PLM holds the product. The range holds the decision.
Proof on the range you’re building.
Free 6-week POC on your own data, no contract. Live in 12 to 15 weeks, end to end.