Every new style a textile mill launches passes through the same silent test: does the tech pack the design team drew match the fabric the sourcing team bought, the fit the pattern maker cut, and the trims the merchandiser confirmed? On paper the answer is always yes. On the floor, a launch typically absorbs three to six sample iterations, one or two fabric substitutions, and at least one last-minute trim change — and every one becomes an on-time-delivery risk if the record doesn’t catch up. A launch-readiness checklist is the discipline that separates smooth first cutting from bulk that ships two weeks late with the wrong buttons.
iFactory / Textile product launch readiness
Every New Style, Every Gate Cleared — Before Bulk Cutting Starts
A launch-readiness checklist that lives inside the PLM, enforces gate-by-gate signoff (tech pack, fabric, fit, PP sample), and flags the missing document, missing approval, or missing trim before it becomes a delay.
Tech pack locked
BOM · trims · specs
Gate 1
Fabric approved
GSM · shrinkage · fastness
Gate 2
Fit sample signed
3 rounds max · size set
Gate 3
PP sample cleared
Ready to cut bulk
Go
20–30
active styles = PLM tipping point
3 rounds
typical fit sample cycle
4 gates
tech pack → PP sample
The Problem on the Floor
A textile launch runs on four gates. The tech pack has to be locked with a complete BOM, trim callouts, size specs, and grade rules. The fabric has to be tested and approved for GSM, shrinkage, colorfastness, and hand feel. The fit sample has to close in three rounds or fewer with the size set signed off. And the pre-production sample has to clear the buyer’s review before bulk cutting. When any gate slips silently — a trim substitution nobody documented, a fabric lot 12 GSM heavier than approved, a fit comment lost between merchandiser and pattern maker — the failure surfaces at the PP review or on the cutting table. By then the reorder is two weeks late.
Where the Record Actually Breaks
Launch data is scattered by design — different teams own different pieces, and the pieces don’t talk to each other. The gaps look predictable when you name them.
Email + attachments
Tech pack revisions circulated as PDF attachments across email threads. Nobody knows which version the factory received or which the sample was cut from.
Shared drive
Fit comments, trim images, and approval notes live in a shared drive with vague file names. Two people cut different bulk orders from two different revisions.
Sample room log
Fit-session decisions recorded on paper in the sample room. Signoffs happen in person and never make it into the digital record.
Nowhere at all
Last-minute buyer changes come in on WhatsApp — a color update, a stitch spec change — and never enter the tech pack. The bulk gets cut against the old spec.
What Good Looks Like on the Line
A working launch-readiness system is not another spreadsheet. It is the gate discipline built into how the tech pack, fabric approval, and sample cycle live inside the PLM — so a style cannot advance to the next stage until the previous one is signed and documented.
Live Tech Pack
Version-controlled tech pack with BOM, size specs, grade rules, stitching, trims, and packaging — one source of truth, every revision timestamped and attributed.
One version, one truth
Fabric Signoff
Fabric approval tied to lab-tested GSM, shrinkage, colorfastness, and hand-feel results. No fabric enters cutting without the approval record and the test attachments.
Test-backed approval
Fit-Cycle Discipline
Fit sample rounds capped and gated — each round captures fit comments, images, and named signoff before the next sample is cut. Three rounds is the target, not seven.
Bounded rounds
PP Sample Gate
PP sample review as the final go/no-go. Buyer comments captured against the specific sample photo, changes routed back to the tech pack, cutting released only on green.
Green = cut bulk
How iFactory AI Fits
iFactory AI sits as an overlay on the PLM you already run — Centric, Bamboo Rose, PTC FlexPLM, or a spreadsheet-based system — and adds the launch-readiness discipline without replacing what works.
Gate Enforcement
Overlay Layer
Each launch gate configured to require named signoff and specified attachments before a style can move forward. No silent progression.
Revision Log
PLM + Overlay
Every tech pack change captured with user, timestamp, and reason. The specific revision the sample was cut from is the specific revision on record.
Test-Result Link
LIMS + PLM
Fabric lab results linked directly to the fabric approval record — no separate spreadsheet, no walking a PDF from lab to merchandiser.
Buyer Change Capture
Overlay Layer
Last-minute buyer changes (email, WhatsApp, phone) captured into the launch record with the affected gate flagged for re-signoff.
Pick one style your team launched in the last quarter. Ask which tech pack revision the bulk was cut against and whether every buyer change made it into that revision. If the answer takes a phone call, the record is behind the reality. Book a launch readiness review — we’ll audit one live style.
12-Week Rollout on One Line
One product line, one season, twelve weeks. The pilot is scoped to prove that gate discipline holds up under real launch pressure — not to prove that checklists exist.
Weeks 1–2
Line & Data Baseline
Pick one product line. Map the current launch process end to end. Baseline: sample rounds per style, tech-pack revision count, gate slippage frequency.
Weeks 3–4
Gate Configuration
Configure the four launch gates with named signoff paths, required attachments, and re-signoff triggers. Team walks through a mock launch together.
Weeks 5–8
Live on One Line
First season styles launched with gate enforcement active. Every gate signoff captured, every buyer change routed back to the tech pack.
Weeks 9–12
Cycle-Time Match
Twelve-week window closes. Compare sample rounds, revision count, and on-time launch rate against the pre-pilot baseline. Rollout plan sized to the delta.
Who Owns the KPI
Launch readiness crosses design, sourcing, sample room, merchandising, and production. Each function needs its own KPI or the discipline dies at the handoff.
Design Lead
Tech-pack revisions post gate 1
Owns the tech-pack lock — rising post-gate revisions signal that the specs weren’t complete when the gate opened.
Sourcing / Merchandiser
Fabric substitutions post gate 2
Owns fabric integrity — a substitution after gate 2 is a supply-chain fail that has to route back through fabric approval, not slip through.
Sample Room Head
Fit rounds per style (target ≤3)
Owns the fit cycle — every round beyond three is cost, delay, and a signal that the fit brief wasn’t clear enough at kickoff.
Production Head
On-time bulk cutting release %
Owns the outcome — how many styles hit their bulk cutting date on schedule. The number the entire launch discipline exists to protect.
FAQ
We already use a PLM — do we need another system on top of it?
Not another system, an overlay. iFactory AI reads from your existing PLM, adds the gate discipline that most PLMs let you skip, and writes back so the PLM remains the source of truth. If your PLM lets a style advance to bulk cutting without a signed PP sample record — most do — the overlay is the enforcement layer that fixes that gap without replacing your investment.
Book a demo to see the overlay running against your PLM.
How does it handle last-minute buyer changes that arrive on WhatsApp?
Every launch has these — a color update, a stitch spec change, a trim swap that comes in three days before cutting. The overlay captures the change (screenshot, message paste, or email forward), attaches it to the specific style and specific gate, and requires re-signoff on the affected gates. The cutting release is blocked until the re-signoff clears. This is not process overhead — it is the record that saves the reorder when the buyer later asks why bulk shipped with the previous spec.
What if we manage some styles on spreadsheets and some on the PLM?
Most mills do — high-volume commercial styles on the PLM, private-label and small-batch styles on spreadsheets. The overlay works across both. Spreadsheet-managed styles are ingested at the launch-gate points; PLM-managed styles integrate through the API. The dashboard shows both together, so the production head sees one launch pipeline instead of two, and the on-time cutting metric is unified.
Stop launching bulk against yesterday’s tech pack.
See Gate Discipline on One of Your Own Live Launches
Bring one product line, its current launch pipeline, and one style that missed its cutting date last season. We’ll show the gate enforcement, revision log, and buyer-change capture live — and quantify where the gates slipped.
