Bundles on the Floor: The Cash Your Sewing-Line WIP Holds

Every bundle sitting between the cutting room and the finishing table is cash you have already spent — on fabric, trims and the labour done so far — but cannot invoice until the garment ships. A single sewing line carrying three days of work-in-progress at a few hundred rupees of absorbed cost per piece can have several lakh rupees frozen on the floor at any moment. Halve the throughput time and you free roughly half that cash, permanently, while catching defects days earlier.

Owners watch their bank balance and their order book, but rarely the pile of bundles between operations — which is, quietly, one of the largest pools of working capital in the factory. This piece shows how to put a rupee figure on it, why it's cash and not just clutter, and how shrinking it pays twice. It's the third of three on the sewing floor, after what 1% of efficiency is worth and where your sewing minutes go.

By the Mama Editorial Team — we scope camera and floor-visibility projects for Indian factories. Last verified: 2 October 2026, against standard working-capital and lean-manufacturing definitions (WIP valuation at absorbed cost; Little's Law relating WIP, throughput and lead time). All ₹ figures are illustrative worked examples, not benchmarks.

Key takeaways

• WIP is spent-but-uninvoiced cash. Each in-process garment has absorbed fabric + trims + part of its labour, none of it yet recoverable.
• Value it simply: pieces in process × average absorbed cost per piece at its stage.
• WIP and throughput time move together (Little's Law): WIP ≈ daily output × days-in-process. Cut the days, cut the cash.
• The payoff is double: freed working capital and defects caught early, before a wrong operation repeats across a three-day pile.
• Fabric dominates garment cost, so apparel WIP is cash-heavy — frozen capital, not just floor congestion.

Why bundles are cash, not clutter

Trace one bundle. The fabric was bought and paid for. It was cut — labour spent. Trims were issued. As it moves down the line, each operation adds more paid labour. At no point in that journey can you send an invoice: the garment isn't finished, isn't inspected, isn't packed, isn't shipped. Every rupee in that bundle is money out with no money back yet — the textbook definition of working capital tied up in inventory.

Multiply by every bundle on the floor and you have a standing pool of cash you funded — from your own reserves or from a working-capital loan you pay interest on — that is doing nothing but sitting in half-made garments. In apparel the pool is unusually heavy because fabric is the largest single component of garment cost (commonly well over half), so even an in-process piece carries most of its material value already spent.

Putting a ₹ figure on it

The valuation is deliberately simple:

WIP value ≈ pieces in process × average absorbed cost per piece

• Pieces in process — count the bundles between the first sewing operation and finishing, times pieces per bundle. Or derive it from throughput (below).
• Absorbed cost per piece — fabric + trims already issued + the labour spent up to the average station. A mid-line piece has most of its fabric and trims plus part of its CM. Use a blended average across the line.

Worked example (illustrative)

One sewing line, 1,000 pieces/day output, garments spending 3 days in process from first operation to finishing.

• Pieces in process ≈ 1,000 × 3 = 3,000 pieces on the floor at any time.
• Average absorbed cost per in-process piece (illustrative): fabric + trims ₹260 + partial labour ₹40 = ₹300/piece.
• WIP value ≈ 3,000 × ₹300 = ₹9 lakh frozen on one line, continuously.

Now shorten throughput from 3 days to 1.5 days (better line balancing, smaller bundles, faster feeding):

• Pieces in process ≈ 1,000 × 1.5 = 1,500.
• WIP value ≈ ₹4.5 lakh — you've freed ₹4.5 lakh of working capital off this one line, for good.

If that cash was funded by a working-capital facility at, say, an illustrative 12% a year, the freed ₹4.5 lakh is also about ₹54,000/year of interest you stop paying — on a single line. Scale across a 10-line floor and the frozen pool, and the saving, move into the crores. All figures illustrative — plug in your own garment cost and throughput.

WIP and time are the same thing (Little's Law, in plain words)

There's a law behind the arithmetic, and it's worth naming because it tells you how to cut WIP:

WIP = Throughput (output rate) × Lead time (days in process)

At a fixed output rate, WIP and throughput time rise and fall together. You cannot cut the cash on the floor without cutting the time a garment spends crossing it — and vice versa. This is why "we'll just produce less WIP" is not a plan; the plan is to shorten the journey: balance the line so no station hoards bundles, shrink bundle sizes so work flows instead of pooling, and keep the line fed so pieces don't stall. The bundle-wait bucket in where your sewing minutes go and this frozen cash are two readings of the same problem.

The second payoff: defects caught before they multiply

Cash is only half the case. A long throughput time is also a quality time-bomb. If an operation is set wrong — a seam off-spec, a wrong interlining — a three-day WIP pile means three days of garments carry that fault before anyone at finishing notices. You then rework or scrap a mountain. A short, fast-flowing line surfaces the same mistake within hours, when only a few dozen pieces are affected. Shrinking WIP tightens your quality feedback loop at no extra cost — and late-discovered defects are a direct cause of the shipment slips covered in why your shipments slip.

How to measure your WIP today

1. Count it once, physically. Walk the line and count bundles between first operation and finishing × pieces per bundle. That's your pieces-in-process.
2. Or derive it: measure how long a marked bundle takes from entry to finishing (throughput time), multiply by daily output.
3. Blend an absorbed cost per in-process piece (fabric + trims + average partial labour).
4. Multiply for the standing ₹ value, and re-count monthly to see it move.
5. Watch where it pools. The station with the tallest bundle pile is your bottleneck; the one sitting empty is starved. Both point to line balance.

Seeing where bundles pile — and for how long

You can count WIP once by walking the floor, but the number you really want is dynamic: which station the bundles pile up at, how long each bundle sits before it's picked up, and how that shifts hour to hour and style to style. That dwell time is the throughput time driving the frozen cash — and it changes every time the line is re-balanced or a new style loads.

Mama watches the video from your floor cameras and each morning messages the owner, in plain language on WhatsApp, where work is pooling on the line and where the flow stalls — reported as flow between stations, not a judgement of operators. It runs on the cameras you already have, or we place our own.

For a read on your floor rather than an illustrative table: send a short walk-through video of your shop and we'll return where the bundles stack up and the hours leak, a camera plan to watch those points, and a proposal. If the freed capacity has you weighing more output, the third-shift ₹ case runs that math; for the Tirupur/knitwear context specifically, see textile factory cameras.

FAQ

How do I value my sewing-line WIP? Pieces in process × average absorbed cost per piece (fabric + trims already issued + partial labour). Count the bundles on the floor, or multiply daily output by throughput time in days.

Why does WIP matter if the garments will sell anyway? Because the cash is spent now and recovered only on shipment. Every day a garment sits in process is a day your money — often borrowed at interest — is locked up and earning nothing, and a day longer before a defect is caught.

How do I reduce WIP without cutting output? Shorten throughput time: balance the line, shrink bundle sizes, and keep stations fed so work flows instead of pooling. By Little's Law, less time-in-process means less cash-on-floor at the same output.

Does watching bundles mean monitoring workers? No. The useful signal is where work pools and how long it waits between operations — a line-balance and flow question, not a ranking of the people at the machines.