Five signals your factory WIP visibility has already broken
My position is simple: by the time a production manager says WIP visibility is a problem, it has been broken for about a season. The thing that convinced me was not a crisis call. It was watching a merchandiser at a mid-market womenswear brand walk me through her Monday ritual, which involved three WhatsApp threads, a shared Google sheet maintained by a sourcing coordinator in another time zone, and a PDF the factory sent on Friday that she had not opened yet.
What are the factory wip visibility signals apparel teams actually miss?
Factory WIP visibility, in apparel, is the ability for merchandising, production, and planning to see, at any moment, how many units of each style and color are at each stage (cut, sewn, finished, packed, shipped) against the plan and the ship window. That is the definition. The signals that it has broken are not alarms. They are small reporting habits that have quietly replaced the system of record.
In the vendor evaluations I sit through most weeks, the prospects who tell me production is “mostly fine” almost always describe one of the five patterns below when I ask them to walk me through last Tuesday. They do not frame these as problems. They frame them as how the work gets done. The tell is right there.
This is Breakpoint 2 of the 6 Breakpoints framework: production and supply execution drift from the plan. The drift is almost never caught at the moment it happens. It surfaces two or three weeks later when a ship window slips and finance asks why the air freight line went up again.
The five signals
One. WIP updates arrive as attachments. If the current state of production lives in a PDF, an Excel file, or a WhatsApp photo of a handwritten tally, you do not have WIP visibility. You have a weekly snapshot already stale by the time anyone opens it. The merchandiser cannot query it. The planner cannot reconcile it against the PO. Nobody can tell whether cut quantities match what was committed, because the committed number lives in a different file.
Two. Cut quantities quietly diverge from the PO and nobody flags it. A factory cuts 4,800 against a PO for 5,000 because the fabric roll came in short. On a well-run production record, the variance surfaces the day it happens and the merchandiser decides whether to accept the short, re-cut, or reallocate the demand. On a broken record, it only appears at pack-out, when the warehouse receives 4,760 and someone has to explain the gap to the wholesale account that was expecting 5,000 against a locked ship window.
Three. Sampling delays do not post against the critical path. The lab dip was late by nine days. The fit sample was late by six. Neither triggered a visible slip on the time-and-action calendar because the calendar is a static Gantt chart somebody rebuilds each season. The production manager knows. The merchandiser knows. The planner finds out when bulk is late and nobody can reconstruct where the days went. A production drift diagnostic usually surfaces these in the first ten minutes of the conversation.
Four. The ship window calculation lives in a spreadsheet. This one costs the most. If your ex-factory date, in-transit buffer, retailer ship window, and cancel date are reconciled in a spreadsheet one person maintains, you are one resignation away from missing a window you did not know was tight. Ship windows are the most operationally expensive date concept in apparel B2B, and they belong in the production record, bound to the PO, visible to the person loading the container.
Five. The production manager answers status questions by calling the factory. This is the most honest signal. If the only reliable way to know where a style is in production is a phone call, then everything upstream (the dashboards, the weekly reports, the status columns) is theater. The system of truth is the factory’s own tracker, which you cannot see.
The worked number nobody wants to run
For a wholesale plus DTC brand running a 3PL and roughly 40 to 60 active production POs at any time, our back-of-envelope on operations around this size is that roughly one full-time equivalent is effectively doing data plumbing between systems instead of analysis. In production specifically, that FTE’s time shows up as the merchandising coordinator who spends her Monday rebuilding the WIP view from attachments, the sourcing lead who reconciles cut quantities against POs by hand, and the planner who maintains the ship window spreadsheet. None of that work is analysis. All of it is recreating a record the operation does not have.
There is the real cost of broken WIP visibility. Not the missed window itself, which is visible and gets blamed on the factory. The quieter cost is the headcount burning on reconciliation that should be a byproduct of a shared production management record, not somebody’s job.
What I would do Monday morning in your seat
Stop asking the factory for a better WIP report. The report is not the problem. The problem is that merchandising, production, sourcing, and planning are each keeping their own version of the production record, and the factory’s weekly PDF is what the team uses to pretend those versions agree.
Pick one PO due to ship in the next six weeks. Write down, from memory, the cut quantity, the current sewn count, the ex-factory date, the ship window, and the last confirmed sample approval date. Then ask the three other people who touch that PO to do the same, independently, before lunch. Compare the five numbers at 2 PM. The gaps are your map. Run that exercise once and it will tell you more about where your production and sourcing operating model has drifted than another quarter of weekly status meetings. From there, the fix is architectural, not procedural: one record, written into by every role, with the ship window and the PO living in the same place as the WIP count.
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.
Ronnell writes about onboarding, adoption, and operational readiness for apparel brands moving to a connected platform. His articles focus on what it takes to go live with confidence and sustain strong execution across channels, warehouses, and teams. As Head of Customer Success and Onboarding at Uphance, he leads the implementation phases that turn a software signature into running operations. He writes about kickoff scoping, data migration, sandbox cutover, change management patterns, and the stakeholder alignment work that determines whether a connected platform actually changes how a brand runs, or just adds another login to the existing chaos.
