Tracking Work-in-Progress Across Multiple Apparel Factories

It is Tuesday morning and the production coordinator has four browser tabs open. One is a spreadsheet from the Portugal knitwear vendor last updated Friday. One is a WhatsApp thread with the Istanbul denim factory where the last message is a photo of a fabric roll. One is an email from the India woven shirt supplier confirming that lab dips were approved, which he already knew. One is the internal PO tracker, which shows twelve styles in production and no field for which factory is actually running them. The Nordstrom ship window opens in nineteen days. Three of those twelve styles are on that PO. He does not know if any of them are cut.

What does it mean to track work in progress factories in apparel?

To track work in progress factories, or track WIP across a multi-vendor production base, means holding a live, shared record of where every style and every PO line sits against its critical path, across every factory in the supply chain, at any point in time. It is not a weekly status call. It is not a spreadsheet that someone updates on Friday. It is a system where the factory records the milestone (fabric in, cut complete, sewing 50 percent, QC passed, packed) and the brand sees it the same day, with the ship window and any dependent orders visible in the same view.

Most brands in the $5M to $100M band do not have this. They have a production tracker that a coordinator maintains by asking people questions. That is not tracking. That is a person doing data entry against a moving target, and the target lies.

Why does WIP visibility break at three factories?

One factory is a relationship. Two factories is a spreadsheet. Three factories is a job. Somewhere between the second and the fourth vendor, the production coordinator’s calendar fills with status calls and the tracker starts to drift from reality within 48 hours of every update.

The objections I hear most often in evaluations come from production leads who insist their spreadsheet works fine. When I ask how they know a milestone has slipped, the answer is always the same: the factory tells them, usually late, usually by email, usually after the buffer is gone. That is not a tracking system. That is a notification system that only fires when it is too late to act.

This is Breakpoint 2 of the 6 Breakpoints of Apparel Operations: production execution drifts from the plan, and the plan stops being useful. The symptoms are predictable. Ship windows are missed because a fabric delay in week three was not flagged until week seven. Wholesale orders get cancelled because the retailer’s cancel date passes before the brand knows the goods are late. Air freight budgets balloon because every delay becomes an emergency. And the production coordinator quietly becomes a full-time expediter.

What are the actual data points you need to track?

A WIP tracking system that survives contact with three or more factories has to hold, per PO line, at minimum:

• The critical path milestones for that style (tech pack approved, fabric ordered, fabric received, lab dip approved, bulk cut, sewing start, sewing complete, QC, packed, shipped)
• The planned date and the actual date for each milestone
• The factory responsible and the internal owner
• The material commitments tied to that PO (fabric lot, trims, labels) and their status
• The downstream wholesale or DTC commitment (which retailer, which ship window, which drop)
• The exception state: on track, at risk, slipped, recovered

The critical piece most brands miss is the last one. Downstream commitment. If the coordinator cannot see that PO-4471 feeds a Nordstrom start-ship of October 12, then a two-week fabric delay looks like a two-week fabric delay. It is not. It is a cancelled order.

How is this different from a project management tool?

Across the comparison conversations I have run this quarter, a recurring pattern is that brands try to solve WIP tracking with Asana, Monday, Airtable, or ClickUp. It does not work, and the reason it does not work is architectural.

A project management tool tracks tasks. Apparel production tracks PO lines against a bill of materials against a critical path against a ship window against a retailer compliance calendar. The PO line is not a task. It is a linked object with a fabric commitment, a size run, a factory allocation, a landed cost, and a downstream sales order. When the fabric slips, everything downstream has to recalculate. Asana does not recalculate. It just shows a red dot.

Spreadsheets have the same problem in a different shape. They hold the data but nothing recalculates, nothing links to inventory, nothing warns you that the delay just broke your allocation to a wholesale account. For a $15M brand running wholesale, DTC, and 3PL, the manual reconciliation cost is roughly 6 to 9 hours a week just to keep inventory and orders honest. WIP tracking adds another layer on top of that, and it is where most of the emergency phone calls originate.

What does a working WIP system look like inside the operations stack?

WIP tracking cannot sit in a silo. If it did, it would just be a nicer spreadsheet. The point is that the production record connects to product data upstream (the tech pack, the BOM, the approved samples) and to inventory and orders downstream (the incoming goods, the allocated wholesale POs, the DTC pre-orders).

The architecture that works looks like this. Product data (PIM/PLM) holds the style, the tech pack, the BOM, and the critical path template. When a PO is issued to a factory, the critical path instantiates against that PO with real dates. The factory has a portal or a shared view where they update milestone completion. The system flags slippage automatically against the planned dates and against the downstream ship window. Inventory shows incoming stock with a confidence date that reflects the current WIP state, not the original PO date. Orders can be allocated against incoming stock with a warning if the WIP is slipping.

This is what running product data, production, inventory, and orders in one connected system actually means in practice. Not a dashboard. A chain of dependencies that recalculates when reality changes.

Why the Illustrator connection matters upstream

WIP tracking depends on the tech pack being right. If the factory is producing against an outdated spec, the goods will be rejected at QC and the milestone that mattered is not sewing complete, it is rework. The tech pack has to be the single version of truth, and it has to update when the designer updates the artwork.

Uphance PLM has a bidirectional Adobe Illustrator plugin, which means designers work in Illustrator and the flats, artwork, colorways, and specs sync both ways onto the tech pack. When a colorway changes, the factory sees it. When a spec is revised, the version is captured. That upstream discipline is what makes WIP tracking downstream honest. Direct Illustrator plugins are otherwise a feature of enterprise PLM at Centric or PTC price points; bringing it to the mid-market matters because the alternative, in most $10M to $20M brands, is emailed PDF tech packs and a comments column in a spreadsheet.

When should you stop tracking WIP in spreadsheets?

Here is a defensible line. If you are running production across three or more factories, or if a single missed ship window in the last twelve months cost you more than the annual cost of an operations platform, you are past the spreadsheet threshold. The predictable breakpoint zone for apparel operations sits at $10M to $20M in revenue, and WIP fragmentation is one of the first breakpoints to bite because production complexity scales faster than headcount.

A POV worth stating plainly: if you are missing more than one wholesale ship window per season because of production visibility, the tracker is the problem, not the factory. Factories miss dates. That is not going away. What has to change is your ability to see the slip four weeks out instead of four days out.

What are the operational anti-patterns to watch for?

A few patterns show up repeatedly in evaluations that indicate the WIP system has already broken:

• The production coordinator’s calendar has more than three recurring status calls per week with individual factories
• Milestone updates in the tracker are batched (Monday morning refresh) rather than event-driven
• The tracker does not show the downstream ship window on the same row as the WIP state
• Slippage is discovered by the sales team, not the production team, when a wholesale account asks about their PO
• Air freight is used more than twice a season to recover a delay that could have been caught earlier

If three or more of these are true, the diagnosis is not that the coordinator needs to try harder. The diagnosis is Breakpoint 2, and the fix is architectural.

How do factories actually update WIP without adding friction?

The realistic answer is that factory-side adoption is the hardest part of any WIP tracking rollout. A factory manager in Istanbul is not going to log into your beautiful web app three times a day. What works is a low-friction interface: a shared portal view of open POs for that factory, mobile-accessible, with milestone updates that take one tap, and email or WhatsApp fallbacks for factories that will not use anything else.

The reason this works is that the burden of translation moves from the coordinator to the system. The factory updates in whatever channel they will actually use. The system consolidates. The coordinator stops being a data-entry clerk and becomes an exception manager, which is what the role should have been in the first place.

What about small runs, sampling, and reorders?

WIP tracking is not just for bulk production. Sampling has its own critical path (first proto, fit sample, size set, PP sample, TOP) and its own slippage patterns. Reorders compress the timeline and often use different factories or different fabric lots, which means the WIP record has to distinguish between an original PO and a reorder against the same style.

This is where lightweight tracking falls apart, because sampling and reorders together often represent more transactions than bulk POs, even though the volume is smaller. If your tracker cannot hold both a size set milestone and a reorder PO for the same style without breaking, it is not a tracker.

What this means for an apparel operations team

Tracking WIP across multiple factories is not a reporting problem. It is a data model problem. The tracker has to hold the PO line, the critical path, the milestone events, the material commitments, and the downstream ship window in the same record, and it has to update when any of them change. A spreadsheet cannot do this. A project management tool cannot do this. A production module that connects to product data upstream and inventory and orders downstream can.

The practical test is whether your production coordinator spends more time asking questions or answering them. If it is the former, the system is not working, and every missed ship window is a symptom of the same underlying breakpoint. Fix the architecture and the status calls disappear on their own.

The cost of not fixing it is quiet but constant. Cancelled wholesale orders. Air freight bills. A coordinator who leaves because the job is untenable. And a production plan that everyone in the company has stopped believing.