The connected apparel workflow map
The apparel workflow is twelve connected stages that carry a collection from line plan and open-to-buy through design, product development, assortment, buying, demand forecasting, size curves, purchase orders, production, allocation, and analytics. Each stage hands decisions and data to the next — and the seams between them are where most cost, delay, and error are created.
This map walks each stage in order: the decisions made, the teams involved, the data that must carry forward, the common handoff risk, and how an apparel operating system keeps the chain connected.
Quick answer
The end-to-end apparel workflow is a connected chain from line plan and OTB through design, product development, assortment, buy plan, demand forecasting, size curves, purchase orders, production and WIP, allocation, and analytics. The value is not in any single stage — it is in the handoffs between them staying connected.
// The twelve stages
01
Line Plan
- Decisions
- How many styles, in which categories and price tiers, to bring to the season — the shape and depth of the range before any product exists.
- Teams
- Merchandising, design leadership
- Carries forward
- Style count by category, price architecture, planned margin, and the seasonal calendar.
- Handoff risk
- The line plan lives in a separate file from the financial plan, so style intent and OTB drift apart before development even starts.
- Apparel OS
- Holds the line plan and OTB as one object, so the count and shape of the range stay reconciled to the dollars from day one.
02
OTB / Financial Plan
- Decisions
- How much can be bought by month, category, and channel — sales, margin, receipts, and inventory targets that fund the line plan.
- Teams
- Planning, finance
- Carries forward
- Open-to-buy by period, receipt flow, turn and margin targets, and beginning/ending inventory.
- Handoff risk
- OTB is set in a planning spreadsheet that buyers never see in their working files, so the buy quietly exceeds the plan.
- Apparel OS
- Buy decisions draft against live OTB, so remaining open-to-buy updates as styles are committed — no end-of-season surprise.
03
Visual Board / Design Direction
- Decisions
- The aesthetic point of view for the season — themes, color stories, key items, and how the range hangs together visually.
- Teams
- Design, merchandising
- Carries forward
- Color palettes, concept boards, key-item direction, and the editorial story behind the assortment.
- Handoff risk
- Visual direction sits in a presentation tool disconnected from the line list, so what is shown and what is planned diverge.
- Apparel OS
- Boards attach to the same line plan and product records, so visual intent and the planned range describe one assortment.
04
Product Development
- Decisions
- Which concepts become real styles — specs, materials, costing, sampling rounds, and the development critical path per style.
- Teams
- Design, product development, sourcing
- Carries forward
- Tech packs, bill of materials, target and quoted costs, sample status, and development milestones.
- Handoff risk
- Development data lives in PLM while the plan lives elsewhere, so cost and timeline changes never reach the planners who priced the range.
- Apparel OS
- Costing and development status sit on the same product record as the plan, so a cost or date slip is visible to planning immediately.
05
Assortment Planning
- Decisions
- The final set of styles, colorways, and depth by channel and door cluster — what carries the range and what fills it out.
- Teams
- Merchandising, planning
- Carries forward
- Style/colorway lineup, channel and cluster assortments, planned depth, and good-better-best structure.
- Handoff risk
- The assortment is rebuilt by hand from development and planning files, so the version buyers work from is already stale.
- Apparel OS
- The assortment is a view of the live product records and plan, so it reflects the current range without manual reassembly.
06
Buy Plan
- Decisions
- Unit buys by style, colorway, and size — translating the assortment and OTB into committed quantities and receipt timing.
- Teams
- Buying, planning
- Carries forward
- Buy quantities by SKU, vendor and order timing, landed cost, and the resulting receipt flow.
- Handoff risk
- The buy is keyed into a vendor spreadsheet detached from OTB, so it overshoots the plan and breaks the receipt flow.
- Apparel OS
- The buy is built against live OTB and the assortment, so units, dollars, and receipt timing stay reconciled as quantities change.
07
Demand Forecasting
- Decisions
- Expected sell-through by style, channel, and period — the demand signal that shapes depth, flow, and reorder posture.
- Teams
- Planning, analytics
- Carries forward
- Forecast units and sell-through curves by style and channel, plus the assumptions behind them.
- Handoff risk
- The forecast is produced in an isolated model, so when the buy or assortment changes the forecast is never re-run against it.
- Apparel OS
- Forecasts read from the same plan and history, so a change in the assortment or buy can be reflected in the demand view.
08
Size Curves
- Decisions
- How each style buy is split across the size run by channel and cluster — the size ratios applied to the buy and to allocation.
- Teams
- Planning, buying
- Carries forward
- Size ratios by style, category, and channel, applied consistently from buy through allocation.
- Handoff risk
- Size curves live in a one-off spreadsheet, so the curve used to buy differs from the curve used to allocate, breaking the size run.
- Apparel OS
- One set of size curves drives both the buy and allocation, so the size logic stays consistent across the workflow.
09
Purchase Orders
- Decisions
- Which orders are placed with which vendors — quantities, costs, ship windows, and terms committed to suppliers.
- Teams
- Buying, sourcing, operations
- Carries forward
- PO quantities and costs by SKU, vendor and ship-window commitments, and the link back to the buy plan.
- Handoff risk
- POs are raised in an ERP that never points back to the buy plan, so what was ordered and what was planned reconcile only after the fact.
- Apparel OS
- POs generate from the approved buy, so ordered units trace directly to the plan and remaining open-to-buy updates on issue.
10
Production / WIP
- Decisions
- How orders move through development, sampling, and manufacturing — managing the critical path and exceptions to protect in-store dates.
- Teams
- Sourcing, production, operations
- Carries forward
- WIP status by PO and milestone, revised ship dates, quantity and quality variances, and critical-path exceptions.
- Handoff risk
- Production status sits in vendor emails and trackers, so a factory slip becomes visible to planning only when goods are late.
- Apparel OS
- WIP status flows back to the same record as the buy and plan, so a slip surfaces as a planning exception while there is still time to act.
11
Allocation
- Decisions
- How received units are distributed across channels, doors, and clusters by size — the first placement and the basis for replenishment.
- Teams
- Allocation, planning
- Carries forward
- Allocation quantities by door and size, pack configurations, and the in-stock position by location.
- Handoff risk
- Allocation uses size curves and receipt data re-keyed from other systems, so the placement is built on numbers that no longer match.
- Apparel OS
- Allocation reads live receipts and the same size curves used to buy, so units land where the plan and demand expect them.
12
Analytics / Replanning
- Decisions
- How the season is performing and what to change in-season — reorders, markdowns, transfers, and the read-through into next season.
- Teams
- Planning, merchandising, analytics
- Carries forward
- Sell-through, margin and inventory actuals against plan, plus the lessons that seed the next line plan.
- Handoff risk
- Reporting is stitched together from exports of every prior system, so the read of the season is late and never fully reconciled.
- Apparel OS
- Actuals sit against the original plan on one record, so the in-season read is current and the next line plan starts from the truth.
// Why the seams matter
The handoffs are the workflow
Read down the map and a pattern repeats at every boundary: a number is re-keyed, a file is rebuilt, a version goes stale. The line plan and OTB drift apart; the size curve used to buy differs from the one used to allocate; a factory slip surfaces only when goods are late. None of these failures happen inside a stage — they happen in the handoff between stages. That is why connecting the workflow on one record matters more than optimizing any single stage in isolation. It is also the practical case behind running apparel on a connected system instead of disconnected spreadsheets.
Several of these stages have concrete math you can work directly — OTB, size curves, sell-through, and markdowns. The free retail-plan.com calculators let you model individual stages before connecting them end to end.
// Summary
- The apparel workflow runs as twelve connected stages from line plan and OTB through to in-season analytics and replanning.
- Each stage hands decisions and data to the next — line plan to development, assortment to buy, size curves to allocation — and the data must carry forward intact.
- Most cost, delay, and error are created at the seams between stages, where numbers are re-keyed, files are rebuilt, and versions go stale.
- An apparel operating system keeps the chain connected on one shared product record and plan, so a change in one stage surfaces in the others.
- Connecting the handoffs matters more than optimizing any single stage in isolation.
// Related resources
See it in RetailNorthstar →// See it in RetailNorthstar
See how the Apparel OS comes to life in RetailNorthstar — one connected workflow from line plan to production.
See this workflow in RetailNorthstar — the platform that runs all twelve stages on one connected product record and plan.