Activewear operations: fabric commitments, knit lead times, and colorway sprawl
It is 7:40 AM on a Tuesday and the production lead at a mid-market activewear brand is on WhatsApp with a knit mill in Portugal. The mill is asking for a final colorway split on 4,200 kilos of a recycled poly-spandex jersey that was booked in greige eleven weeks ago. Design added two new colors to the drop last Thursday. Merch pulled one color after a sell-in call on Friday. The production plan in the spreadsheet still shows the original six colors. The mill wants an answer by end of day Lisbon time or the dye slot moves to the following week, which pushes the finished fabric past the cut date, which pushes the drop. Nobody has told finance that the greige is already paid for regardless.
What does activewear brand fabric commitments operations actually mean?
Activewear brand fabric commitments operations is the discipline of managing the gap between when a performance-fabric brand commits money and capacity to a knit mill and when that fabric becomes finished goods against a specific style, size, and colorway. In cotton-woven categories, the mill and the cut-and-sew factory are often the same vendor, and fabric moves through as part of a bundled quote. In activewear, they are almost never the same. The knit mill books yarn, knits greige, and holds it. The dye house takes greige to finished fabric in specific colors. The cut-and-sew factory takes finished fabric to garments. Each hop has its own lead time, minimum, and failure mode, and the brand carries the liability across all three.
That structural difference is why activewear production plans drift harder than woven plans. The commitment to buy 4,200 kilos of greige happens before the assortment is locked, before wholesale sell-in is complete, and often before the DTC drop calendar is finalized. Every downstream decision, add a color, drop a size, shift a launch, has to reconcile against a fabric pool that was sized months earlier for a different plan.
Why knit lead times punish assortment changes
A typical performance-knit lead time for a mid-market brand runs 12 to 16 weeks from yarn booking to finished, tested, and shipped fabric. Break that down and the flex points are narrow. Yarn spinning and delivery to the knit mill is 3 to 5 weeks. Knitting greige is 2 to 3 weeks depending on machine gauge and available capacity. Wet processing, dye, and finish is 3 to 4 weeks including QA. Testing for shrinkage, colorfastness, and stretch recovery is another week. Ocean freight adds 4 to 6 weeks if the finished fabric ships internationally to the cut-and-sew factory.
Inside that window, the only reversible decisions are dye color and dye lot size, and only up until the greige is committed to the dye house. Everything upstream, yarn count, knit construction, greige quantity, is locked. From the fit calls I run with prospects each week, the pattern that comes up most often is a merch team that thinks they still have flexibility in month three because “the fabric isn’t dyed yet,” without understanding that the total greige pool is already fixed. You can rebalance colors inside the pool. You cannot grow the pool.
This is BP2 territory in the 6 Breakpoints framework: production and supply execution drifting from the plan. The plan said six colors at defined ratios. The actual execution is a moving target of color adds, color drops, and ratio shifts, all fighting for shares of a fixed greige commitment. Without a system that ties fabric commitments to styles and colorways as a live ledger, the drift stays invisible until the mill sends the invoice for the unallocated greige.
How does colorway sprawl inflate the buy?
Colorway sprawl is the single largest driver of fabric liability in activewear, and it compounds silently. Consider a core legging in one fabric quality. Year one launches with 4 colors. Year two the line planning meeting adds 2 seasonal colors and keeps all 4 core colors. Year three, 2 more seasonal colors plus a collaboration exclusive. The style is now offered in 9 colors. Dye minimums for performance knits typically run 300 to 500 kilos per color per lot. At the low end, offering 9 colors means committing 2,700 kilos of finished fabric to that one style before a single unit sells.
Now layer on sizes. If the brand runs XXS through XXL, that is 7 sizes. Nine colors times seven sizes is 63 SKUs from one style. Each SKU has its own demand curve, its own oversell risk, and its own end-of-season markdown exposure. The math gets worse when the same base fabric is used across a legging, a short, and a bra. The dye lot is shared, but the finished fabric has to be split across three cutting plans with different consumption per unit.
The POV I hold across the comparison conversations that come up in this category is simple: activewear brands should cap active colorways per style per season based on fabric commitment math, not based on what design wants to show. Fewer colors, deeper by size, is almost always the right answer for the operations team and the finance team. Merch will resist. The fabric ledger has to win that argument with numbers, not opinions.
What breaks when the fabric ledger lives in spreadsheets?
At the $15M revenue band, the pattern is consistent. Fabric commitments live in one spreadsheet maintained by production. Style-level BOMs live in a PLM or another spreadsheet maintained by design. Colorway assortments live in the line plan maintained by merch. Actual mill invoices live in accounting. None of these systems talk to each other in real time. The reconciliation happens manually, usually by the production lead, and usually late at night before a mill call.
That reconciliation eats hours. Back-of-envelope for a brand this size, the operations team spends 6 to 9 hours a week reconciling inventory positions across Shopify, the 3PL, and wholesale commitments. Add fabric reconciliation on top and you are describing one full-time person doing nothing but data plumbing. When a system is missing, a person becomes the system, and people miss things. Missed reconciliation shows up as a 2 to 3 percent oversell rate at peak on finished goods, because the committed-but-unshipped wholesale pool was not netted against DTC availability. It also shows up as unallocated greige sitting in a mill warehouse in Portugal that nobody has decided what to do with.
The structural weakness here is that fabric is treated as a purchase rather than a planned resource. A purchase is a line item on an invoice. A planned resource is a pool that gets drawn down against specific styles, colorways, and production orders, with visibility into what is committed, what is available, and what is orphaned. Getting to the second model requires connected production and sourcing execution where fabric commitments, purchase orders, and style BOMs share the same underlying data.
When do knit constructions become an operations problem instead of a design decision?
Design teams pick knit constructions for hand, drape, compression, and moisture management. Operations teams inherit the consequences: minimum knit runs, machine gauge availability, and finish compatibility. A brand that runs 4 base fabrics can consolidate greige commitments across styles. A brand that runs 14 base fabrics, because every new style added a new construction, cannot. Each fabric quality has its own minimum commitment, its own lead time, and its own liability line.
The knit construction proliferation problem usually starts small. A new style needs slightly heavier compression, so design specifies a new yarn count. A collaboration wants a specific texture, so a new knit structure gets developed. Two years later the fabric library has 14 qualities, half of which are used in one or two styles. The knit mill is now running short batches at higher unit costs, lead times are longer because small orders get scheduled around large ones, and the fabric ledger has 14 rows instead of 4.
The operational rule I would defend here: no new base fabric quality enters the line unless it is planned across at least 3 styles or 1,500 units of committed demand. Below that threshold, force the design intent onto an existing fabric or a close variant. This is not a creative constraint, it is a fabric commitments constraint. The brands that stay disciplined on the fabric library are the ones whose production plans still resemble reality at week 12.
How should activewear brands sequence commitments against sell-in?
The sequencing problem is where wholesale-heavy activewear brands get squeezed hardest. Wholesale sell-in for a spring drop typically closes in September. Mill commitments for that spring drop have to happen in July or August to hit January delivery. That means the brand is committing greige quantities before it knows what wholesale will actually order. DTC forecasts are similarly speculative that far out.
The operational answer is a tiered commitment structure. Commit greige at the fabric-quality level based on a conservative aggregate forecast across all styles that share the fabric. Delay the color split until dye-house commitment, which is typically 6 to 8 weeks before finished fabric ships. Delay the style-and-size split until cut planning, which is typically 4 to 6 weeks before garment ship. Each stage narrows the commitment as more real demand data arrives.
This works only if the system can hold aggregate commitments at the fabric level and progressively resolve them into style, color, and size allocations as decisions get made. In practice, most brands running spreadsheets commit at the SKU level too early because that is what the spreadsheet forces them to do. The spreadsheet does not have a concept of “unallocated greige waiting for color decision.” The system either knows the SKU or it does not. That is why the production drift diagnostic surfaces this pattern early: brands committing at SKU-level three months out are always drifting by month two.
What does the fabric ledger actually need to track?
A functioning fabric ledger for an activewear brand tracks seven things per fabric commitment. Fabric quality identifier and specification. Total greige quantity committed and unit of measure. Committed dye colors and quantities per color, including the unallocated pool. Style and colorway allocations against each color pool. Mill and dye house lead times and current status. Purchase order references and payment terms. Finished fabric arrivals against expected quantities, including yield loss and rejects.
Each of these has to be queryable against the production plan and the sales order book. When merch asks “can we add a tenth color to the core legging,” the answer should be visible in under a minute: yes, there are 380 kilos of unallocated greige in the current commitment, dye-house minimum is 300 kilos, dye slot is available in three weeks, adds 4 weeks to that color’s delivery. Or: no, greige is fully allocated, adding a color requires a new commitment with a 14-week lead time.
That kind of answer is not achievable in a spreadsheet at any scale beyond one fabric and three colors. It requires a production management system where fabric commitments are first-class objects tied to styles, purchase orders, and finished goods inventory. Everything else is a workaround that costs the brand hours of manual reconciliation and, worse, the credibility of production commitments to sales and merch.
What activewear operators should do this quarter
The question this post answers, whether fabric commitments and colorway sprawl are actually the load-bearing problem in an activewear brand’s operations, is usually yes for brands in the $10M to $20M zone. The symptoms show up as missed drop dates, unallocated fabric on mill invoices, and a production lead who is exhausted by Thursday. The diagnosis is that the plan and the execution have drifted, and the drift is invisible because the fabric ledger, the BOM, and the assortment plan live in different files.
For a production or operations lead reading this: audit the last three fabric commitments against actual finished fabric usage. Compute the orphaned greige and the color-level over-commit. Count the base fabric qualities in active production and the average styles per quality. If orphaned greige is more than 8 percent of committed volume, or if more than a third of your fabric qualities are used in fewer than three styles, the fabric commitments layer is where the operational cost is compounding. That is a BP2 problem, and it does not solve itself with a better spreadsheet.
Where is your operation on the 6 Breakpoints curve?
The assessment scores your apparel operation across all six breakpoints (product data, production, inventory truth, order flow, warehouse execution, reporting) and identifies which one is hurting you most.
Frequently asked questions
Where this fits in the Uphance platform
Shubham writes about evaluating ERP fit, assessing operational complexity, and how apparel brands can tell whether their current systems are helping or holding them back. As a Solutions Consultant at Uphance, he runs discovery conversations and fit assessments for apparel brands moving off patchwork stacks of PLM, PIM, inventory, and B2B tools. His articles cover ERP selection, vendor RFPs, comparison frameworks, and the operational signals that tell a brand it has outgrown spreadsheets and point solutions. He focuses on how mid-market apparel teams evaluate connected platforms against the cost of staying with what they have.
Saurabh writes about integrations, data consistency, and how apparel brands connect the commerce, logistics, finance, and operational systems their business depends on. As Engineering Manager for Integrations at Uphance, he leads the team that builds and operates the EDI, API, and connector layer between apparel ERPs and the rest of the stack: Shopify, QuickBooks, Xero, Amazon, 3PL platforms, and retailer trading partners. His articles cover EDI transaction sets (850, 856, 810, 940, 945), integration architecture, sync reliability, retailer compliance, and the failure modes that surface when connected systems drift apart between trading partners.
