Apparel product lifecycle is the sequence from concept to clearance. Most brands describe it as five or six stages; in practice it is seven, and the seventh (end-of-life) is the one most often unmanaged. Each stage produces data the next stage consumes, and the failure mode at scale is not stage-by-stage execution; it is data not flowing cleanly between stages.
This post is a working operator’s view of what happens at each stage, where the data lives, and where most brands lose visibility.
The seven stages
| Stage | Owner | Duration | Primary system | Key output |
|---|---|---|---|---|
| Concept | Design / merchandising | 1 to 3 months | Mood boards, trend reports | Style brief |
| Design | Design / technical design | 1 to 2 months | Illustrator, PLM | Initial tech pack |
| Sample | Technical design / factory | 2 to 4 months | PLM, factory portal | Approved production sample |
| Approval | Production / brand leadership | 1 to 2 weeks | PLM, approval log | Locked spec |
| Production | Production / sourcing / factory | 2 to 5 months | ERP, factory PO system | Finished goods |
| Distribution | Operations / sales / warehouse | Ongoing through season | OMS, WMS, channels | Sales |
| End-of-life | Merchandising / finance | 4 to 8 weeks at season end | Reporting, markdown system | Markdown plan or carryover |
The full lifecycle from concept to in-store is 6 to 18 months. Wholesale-led brands sit at the long end (12 to 18 months); DTC-led brands compress (6 to 9 months); fast fashion compresses further.
Stage 1: Concept
What happens: The design and merchandising teams identify what the brand will produce for an upcoming season. Inputs include trend research, prior-season sell-through, customer feedback, and brand strategy. Outputs are style briefs (one per planned style) and an assortment plan (the full season catalog).
Where data lives: Mood boards, trend reports, sales reports, merchandising plans. This is the most fragmented stage; data lives in separate documents and is not yet structured.
Common failures: Concept decisions made without prior-season sell-through data because reporting is too slow. Trend assumptions repeated season after season because no one tests them. Assortment too broad (too many SKUs) because no one is enforcing depth-versus-breadth tradeoffs.
Stage 2: Design
What happens: Designers translate concept briefs into actual garments. Sketches turn into flat technical drawings. Initial fabric and trim selections are made. The first version of the tech pack is created.
Where data lives: Illustrator, design files, early-version tech packs. PLM if the brand is on it; PDFs and shared drives if not.
Common failures: Tech packs created in PDF format and never structured. Material selections made before supplier confirmation. Costing impact of design decisions not visible until the sample comes back from the factory expensive.
Stage 3: Sample iteration
What happens: The factory builds prototypes against the tech pack. The brand reviews each sample, marks corrections, and the factory revises. A typical sample cycle runs three to five iterations: first sample → fit sample 1 → fit sample 2 → pre-production sample → production sample.
Where data lives: PLM (or shared tech pack files), photo annotations, factory communication. This is the most communication-intensive stage; every sample produces a round of comments.
Common failures: Version drift (the factory builds against an older tech pack version); ambiguous specs (the factory makes assumptions and the sample comes back wrong); sample cycle bloat (four cycles when one should suffice because comments are not specific enough).
Stage 4: Approval
What happens: The production sample is approved by the brand. Approval locks the spec; production proceeds against the locked spec; deviations from the locked spec are change orders, not assumed.
Where data lives: PLM approval log, signed approval forms, locked tech pack version.
Common failures: Approval is verbal, not documented. Approval is conditional (“approved if you change the trim color”) and the conditions are forgotten. Approval is granted by one person and the production team works against a different version because the approval did not propagate.
Stage 5: Production
What happens: The factory produces bulk against the locked tech pack. The brand issues a production PO with quantity, ship date, target FOB. The factory builds, the brand inspects (typically pre-shipment), and finished goods ship to the brand’s warehouse.
Where data lives: ERP production orders, factory invoices, inspection reports, shipping documents.
Common failures: Production-to-plan variance because production receipts post late or partial. Cost variance because factory invoices reflect different costs than the tech pack BOM. Quality issues that should have been caught at sample but slipped through because the sample-to-bulk gap was too wide.
This is the structural ground of Breakpoint 2 (production drift) in the 6 Breakpoints framework.
Stage 6: Distribution
What happens: Finished goods enter inventory. The brand allocates across channels (wholesale, DTC, marketplace, dropship), ships to customers, and tracks sell-through.
Where data lives: OMS (orders), WMS (warehouse), channel platforms (Shopify, Amazon, marketplaces), inventory ledger.
Common failures: Inventory drift across channels (oversells). Allocation conflicts between wholesale and DTC. Slow channel data leading to slow reorder decisions.
Stage 7: End-of-life
What happens: At season end, every style has remaining inventory. The brand decides per style: mark down to clear, send to off-price channel, send to outlet, donate, or carry over to next year. Each decision has financial and operational consequences.
Where data lives: Sell-through reports, inventory aging reports, markdown system, off-price channel agreements.
Common failures: End-of-life decisions made on slow data (last month’s sell-through, not last week’s). No clear owner for the decision. Carryover inventory drains warehouse capacity through the next season. Off-price channel terms not optimized.
End-of-life is the most unmanaged stage at most apparel brands. It happens to the inventory; it is rarely an explicit decision.
The cross-stage data flow problem
The lifecycle works when data flows between stages without manual re-entry:
- Concept → Design: assortment plan flows to design briefs.
- Design → Sample: tech pack edits flow to factory automatically.
- Sample → Approval: sample comments and approvals are tracked in one document.
- Approval → Production: locked tech pack feeds the production PO.
- Production → Distribution: production receipts post to inventory in real time.
- Distribution → End-of-life: sell-through data feeds markdown decisions.
Each arrow is a potential break. Brands managing the lifecycle in disconnected systems experience breaks at every arrow:
| Arrow | Break |
|---|---|
| Concept → Design | Assortment plan in spreadsheet, design briefs in shared drive; no link |
| Design → Sample | Tech pack PDF emailed to factory; revisions are new emails |
| Sample → Approval | Approval is verbal; no log; production team works from different version |
| Approval → Production | PO created manually from tech pack data; transcription errors |
| Production → Distribution | Receipts post to spreadsheet; inventory updates lag 24 to 72 hours |
| Distribution → End-of-life | Sell-through report manually built from channel exports |
A connected platform compresses the lifecycle by 20 to 40 percent because each handoff is automatic rather than manual.
What “connected” actually means
A connected apparel lifecycle system has four properties:
- Single source of truth per data class. Tech packs in one system; inventory in one ledger; orders in one OMS. Other systems read from these; nothing is duplicated.
- Live data flow between stages. When the tech pack changes, the costing updates. When production receives, the inventory ledger updates. When markdown is decided, channel feeds update.
- Stage gating with audit trail. Sample approvals are explicit and timestamped. Production cannot start without approval. Markdown cannot post without merchandising sign-off.
- Reporting that crosses stages. Sell-through can roll up to design (which fabrics sold best), to sourcing (which factories produced fastest), to merchandising (which categories underperformed). The cross-stage rollup is what turns operational data into strategic decisions.
Most brands have one or two of the four. The brands that have all four are typically running on apparel-specific platforms; brands on generic ERP plus generic ecommerce typically have one source of truth (financial), one weak handoff (production to inventory), and no real cross-stage reporting.
Operational signals that lifecycle management is breaking
Five symptoms that the lifecycle is held together by manual effort:
- Sample iteration regularly exceeds 4 cycles per style.
- Production-to-plan variance is consistently above 5 percent.
- Tech pack BOM and factory invoices disagree by more than 5 percent regularly.
- Markdown timing is consistently late (slow data leads to late decisions).
- End-of-life inventory carries forward for multiple seasons.
Each is a signal that the data is not flowing cleanly across stages.
Related reading
- PLM software for apparel
- Mastering the tech pack
- Apparel supply chain
- Production management
- The 6 Breakpoints framework
Which stage of your lifecycle is hurting you most right now?
Sample loops, production drift, end-of-life carryover, slow markdown decisions: each is a signal of a structural break between stages. The 6 Breakpoints Assessment is a 12-question diagnostic that identifies which break is hurting you most.