The Bundle System in Garment Production: Why It Still Dominates (And How to Digitize It)
Every garment factory in South Asia runs on bundles. You cut fabric into pieces, tie them together in stacks of 10 or 20, attach a ticket, and send them down the sewing line. This system was invented in the 1950s. Seventy years later, most factories still track these bundles with handwritten tickets and paper registers. I built an entire ERP around fixing this.
What Is the Bundle System (Without the Textbook Jargon)
Walk into any cut-make-trim factory in Kathmandu, Dhaka, or Tirupur and you will see the same thing: stacks of cut fabric pieces tied together with a paper slip on top. That is a bundle. It is the basic unit of work on a sewing floor — not the individual piece, not the full order, but a bundle of 10 or 20 identical pieces grouped by size, color, and component.
A single garment is made of multiple components. A polo shirt has a front panel, back panel, two sleeves, a collar, and a pocket. Each of those components gets cut separately and bundled separately. So one order of 400 polo shirts in 4 sizes and 3 colors does not move through the factory as 400 garments. It moves as hundreds of individual bundles — front bundles, back bundles, sleeve bundles, collar bundles — each flowing through different sewing operations before converging at assembly points.
The bundle ticket is the identity card of each bundle. In a traditional factory, it is a paper slip that records the lot number, style, size, color, piece count, and component type. The operator tears off a coupon from the ticket when she finishes working on that bundle. At the end of the day, someone collects the coupons, counts them, and calculates payment. That is the garment bundling process in its most basic form, and it has not fundamentally changed since the system was formalized in American garment factories in the 1950s.
The bundle system works because it is simple. An operator does not need to understand production planning or garment construction. She takes a bundle from the trolley, does her operation, puts it back, takes the next one. The bundle is self-contained — it carries its own identity, its own piece count, its own routing information. That simplicity is why it survived when other manufacturing systems came and went.
Progressive Bundle System vs the Alternatives
When people in the garment industry say "bundle system," they usually mean the Progressive Bundle System, or PBS. The word "progressive" just means bundles move forward through a sequence of operations — from cutting to the first sewing operation, then the next, then the next, until the garment is complete. Work-in-progress (WIP) accumulates between stations. That is the defining characteristic: bundles wait in queues between machines.
PBS dominates the CMT world. According to research published in the International Journal of Industrial Ergonomics and production engineering literature on ScienceDirect, the progressive bundle system remains the most widely used production system in apparel manufacturing globally. Estimates vary, but in South Asian CMT factories specifically, it is well above 90%. The reason is straightforward: it works with low-skill operators, requires minimal capital investment, and supervisors already know how to manage it.
But PBS is not the only option. Let me compare it honestly with the alternatives.
| System | How It Works | WIP Level | Capital Cost | Best For |
|---|---|---|---|---|
| Progressive Bundle (PBS) | Bundles move station to station, queue between operations | High | Low | CMT factories, 50-500 operators |
| Modular / Cellular | Team of 5-15 operators makes complete garments, minimal WIP | Very low | Low | High-variety, quick response |
| Unit Production System (UPS) | Overhead rail carries individual pieces between stations automatically | Very low | $50,000-200,000+ | Large factories, high volume |
| One-Piece Flow | Single garment moves through all operations without batching | Minimal | Medium (layout changes) | Lean environments, skilled teams |
Lean consultants will push you toward modular manufacturing or one-piece flow. And they are not wrong in theory. Lower WIP means faster throughput, fewer defects caught late, and less capital tied up in unfinished goods. The Toyota Production System proved this decades ago, and lean principles from Taiichi Ohno's work have transformed automotive and electronics manufacturing.
But garment manufacturing is not automotive. An operator on an overlock machine does one operation. Moving her to a modular cell where she does three operations requires cross-training that takes months. The operators resist it because their piece-rate earnings drop while they learn new skills. The supervisors resist it because they lose control of individual station output. The factory owner resists it because throughput drops 20-30% during the transition period.
My honest take: If you are running under 500 operators in a CMT setup, PBS is probably your best system. Do not let lean consultants tell you otherwise. Fix the tracking, fix the WIP visibility, fix the payment disputes — but do not throw away a production system that every operator on your floor already knows how to use. Digitize the bundle ticket, not the production system.
The Unit Production System deserves a mention because it is genuinely impressive. Companies like Eton Systems build overhead conveyor systems that transport individual garment pieces between workstations automatically. No bundles, no trolleys, no manual transport. But the price tag starts at $50,000 for a basic line and can exceed $200,000 for a full installation. For a factory in Nepal or Bangladesh making $1.50 per garment on CMT margins, that math does not work. PBS with digital tracking gives you 80% of the visibility benefit at 1% of the cost.
The Anatomy of a Bundle — Getting Specific
Let me show you exactly what a bundle looks like in our system. This is not a generic example. This is real data from our production floor.
Take a cutting order: Lot S27, Article 2233 (a men's casual shirt). The cutting room cuts 400 pieces across sizes S, M, L, XL in three colors: Red, Blue, and Black. The fabric is spread in layers, cut with a straight knife, and separated into components. The front panels go into one stack, backs into another, sleeves into their own stacks, and so on.
Each stack gets divided into bundles of 10 pieces. A bundle of 10 medium-size red front panels becomes:
- Lot: S27
- Article: 2233
- Size: M
- Color: RED
- Bundle ID: B001
- Component: FRONT (code: FRT)
- Quantity: 10 pieces
In a paper system, this information gets handwritten on a ticket and pinned to the bundle. In our system, it gets encoded into a QR code. Here is the actual JSON data structure stored in that QR label:
We use single-character keys to minimize the QR code size. A smaller QR code means fewer modules, which means it scans faster and prints smaller on the label. The entire payload is under 80 characters, which fits comfortably in a version 3 QR code — the kind that is about 2 cm square and scans reliably even on a cheap phone camera.
That 400-piece order generates roughly 180 bundles across all components, sizes, and colors. Each one gets a QR label printed on a TSC thermal printer. The labels take about 4 minutes to print for the entire lot. In the old paper system, writing 180 bundle tickets took the cutting master the better part of an hour, and his handwriting was not always legible by the time it reached the sewing floor.
Where Bundles Go Wrong
The bundle system works until it does not. And when it fails, it fails in the same predictable ways in every factory I have seen. These are not edge cases. These are daily occurrences that production managers have learned to live with — which is exactly why they persist.
Lost bundles
A bundle of 10 collar pieces falls behind a machine. Nobody notices for three days. When you find it, the operator who was supposed to sew it has moved to a different color. The collar pieces are now the wrong shade because they were from the first dye lot and the line has moved to the second. Ten collars wasted. Multiply this by a few times a month and you have a real cost problem that never shows up in any report because nobody tracks "bundles found behind machines."
Mismatched bundles
The cutting master labels a bundle as size L but it is actually size M. The operator does not check — why would she? She trusts the ticket. The mismatch is only discovered at assembly when the front panel does not match the back panel. By then, ten garments are wrong and someone has to trace back through the entire chain to figure out where the error happened. In a paper system, that trace is nearly impossible. In a digital system, you pull up the bundle ID and see every touch point in seconds.
Counting disputes
This is the one that causes the most friction on the floor. The operator says she finished 47 bundles today. The supervisor's tally shows 42. Five bundles of difference at NPR 4.50 per piece, 10 pieces per bundle — that is NPR 225 in disputed earnings. Not a fortune, but enough to start an argument that sours the entire shift. In a factory with 80 operators, these disputes happen daily. The supervisor does not have time for them. The operator feels cheated. Nobody wins.
The root cause is always the same: the paper ticket is a single point of truth with no backup. The coupon gets torn off, and that coupon is the only proof the work happened. If it falls on the floor, gets mixed into another operator's stack, or the supervisor miscounts at the end of the day, the data is lost. There is no audit trail, no timestamp, no second copy.
WIP buildup
Two hundred bundles sitting on a trolley between overlock and flatlock. The overlock station is running fast because the operator is skilled and motivated. The flatlock station has a new operator who is still learning. Nobody notices the pile growing until it is a physical obstacle in the aisle. By then, you have three days of WIP tied up in bundles that are not earning revenue.
WIP is inventory, and inventory is money. A garment industry benchmark from the Online Clothing Study notes that PBS factories typically carry 3-5 days of WIP between stations. Reducing that to 1-2 days through better visibility and line balancing can free up significant working capital — capital that a CMT factory operating on thin margins desperately needs.
Paper Ticket vs QR Label: An Honest Comparison
I sell QR-based tracking software, so let me be upfront about my bias. But I have also spent enough time on factory floors to know that paper is not stupid. It has real advantages that digital advocates like to ignore. Here is the honest comparison.
| Factor | Paper Bundle Ticket | QR Code Label |
|---|---|---|
| Cost per label | Essentially free (paper + pen) | Under $0.005 (thermal label + ribbon) |
| Works offline | Always | Yes, with offline-first software |
| Durability | Gets dirty, torn, lost, ink smudges | Survives oil, heat; 30% damage tolerance with error correction |
| Real-time tracking | Impossible — data enters system at end of day | Instant — every scan is a data point |
| Payment accuracy | Depends on coupon counting, frequent disputes | Automatic — scan = recorded piece count, zero disputes |
| WIP visibility | Requires physical floor walk to count trolleys | Live dashboard shows bundles at every station |
| Operator training | None needed | 5-10 minutes to learn scanning |
| Equipment needed | Nothing | Label printer ($200), smartphones (operators usually have them), WiFi |
| Audit trail | None — coupon is the only record | Complete — who, what, when, with timestamps |
| Dependency tracking | Manual — supervisor checks if components are ready | Automatic — system unlocks next operation when prerequisites are done |
Paper wins on two things: zero cost and zero training. If you have 10 operators and one style running continuously, paper is fine. The supervisor can keep it all in her head. But the moment you scale past 30-40 operators, multiple styles, and need to calculate payments accurately, paper falls apart. Not because it is bad technology — it was never technology to begin with. It is a manual system hitting the limits of human memory and manual counting.
How Digital Bundle Tracking Works in Practice
Let me walk through the actual workflow in Scan ERP. This is what happens every day on our factory floor.
Cutting room generates bundles and prints QR labels
The cutting master enters the lot details into the system: article, sizes, colors, quantities. The system generates bundle IDs for every component-size-color combination, creates the QR data, and sends the labels to a TSC thermal printer. 180 labels print in about 4 minutes. Each label gets pinned to its physical bundle. From this moment, the physical bundle and its digital twin exist in parallel.
Work pool is generated from the garment template
The system knows that article 2233 requires 7 sewing operations in a specific sequence with dependencies. It takes 180 bundles and creates 1,260 work assignments automatically. Each assignment knows which bundle it belongs to, which operation it represents, which machine type is needed, and which other assignments must be completed before it can start. The shoulder seam cannot begin until both front and back panels are done. The system enforces this.
Operator scans QR, system finds work, timer starts
The operator picks up a bundle, points her phone at the QR label. One second. The system decodes the QR, looks up the matching work assignment, verifies the operator's skill and machine type, and starts the work timer. One scan replaced writing the bundle number, operation name, start time, and piece count on a paper tally. Across 80 operators doing 25 bundles each per day, that is 2,000 manual recording steps eliminated daily.
Work completes, payment is recorded, dependencies unlock
When the operator finishes the bundle, she scans again. The system records the completion, calculates the piece-rate payment, writes it to her earnings diary, and checks if this completion unlocks any downstream operations. If Sunita just finished the front panel and Bikash already finished the back panel for the same garment, the "join shoulder" operation unlocks automatically. We call this component marriage. No supervisor intervention needed.
Supervisor monitors flow from his phone
The live dashboard shows exactly how many bundles are at each station, which operators are ahead or behind target, and where WIP is building up. When 15 bundles stack up at side-seam, the supervisor gets an alert on his phone before the pile becomes a physical problem. He reassigns operators, rebalances the line, and keeps production flowing. All based on real data, not a floor walk and a gut feeling.
End of month: payroll in 20 minutes
Every completed scan has been feeding into the operator's earnings diary all month. Piece rates, quality bonuses, efficiency adjustments — all calculated automatically. The accountant pulls the report and payroll is done. No coupon counting, no disputes, no three-day reconciliation marathon. Last month: zero payment disputes across the entire floor. That alone justified the system.
Bundle Size: The Optimization Nobody Talks About
How many pieces should go in a bundle? This sounds like a trivial question, but it has a direct impact on WIP, throughput, and even operator morale. I have experimented with different sizes and settled on a clear answer.
Small bundles (5-10 pieces)
- Less WIP between stations — each bundle moves faster through the line
- Faster feedback on quality issues — problems caught after 5 pieces, not 50
- More labels to print and more scans to perform
- More bundle handling time relative to sewing time
Large bundles (20-50 pieces)
- Fewer labels, fewer scans, less administrative overhead
- Operator spends more time sewing, less time picking up and putting down bundles
- Much higher WIP — a queue of 10 bundles at 50 pieces each is 500 pieces of inventory
- Quality issues hide longer — a defective stitch pattern repeats 50 times before anyone checks
Our choice: We use 10-piece bundles. It is the sweet spot for most sewing operations. Small enough to keep WIP manageable, large enough that operators are not constantly picking up and putting down bundles. The extra label printing cost is negligible — about NPR 0.50 per label. The WIP reduction and quality catch rate more than pay for it.
There is an exception for components with very fast cycle times, like button attach or bartack. For those operations, an operator might finish a 10-piece bundle in 3 minutes. The bundle handling time becomes a significant percentage of the total. In those cases, we sometimes use 20-piece bundles. But for mainstream sewing operations — overlock, flatlock, single needle — 10 is the number.
The Real Numbers
Here is what digital bundle tracking looks like after six months of production data from our floor.
That zero on payment disputes is not a marketing number. It is a real count from a real factory. When every piece of work is timestamped with the operator's ID, the bundle ID, and the operation, there is nothing to dispute. The data is the data. The operator can see her running total on her own phone throughout the day. The supervisor sees the same numbers. Disagreement requires one of them to argue with a database, and people tend not to do that.
What You Need to Get Started
If you are running a factory on paper bundle tickets and want to move to digital tracking, here is the minimum viable setup. I am not listing the ideal setup. I am listing what actually works with the least investment.
- A thermal label printer — TSC TE200 or equivalent. Around $200. Prints QR labels on rolls. The labels need to be thermal transfer (with ribbon), not direct thermal, because direct thermal labels turn black from heat and friction on the sewing floor.
- Smartphones — Any Android phone from the last 4-5 years with a working camera. Most operators in South Asian factories already have one. You do not need to buy 80 phones. You need WiFi and a web app.
- Reliable WiFi — One decent access point per floor section. The data per scan is under 1 KB, so bandwidth is not the issue. Reliability is. A dropped connection during a scan should not lose data — which is why the software must be offline-first.
- Tracking software that understands garments — Not generic warehouse barcode scanning. You need software that knows about components, operations, dependencies, and piece-rate payment. A general-purpose barcode app cannot handle garment marriage logic.
Total investment for a 50-operator floor: $500-800, not counting phones operators already own. Compare that with UPS systems at $50,000+ or RFID deployments at $15,000+ for hardware alone. The ROI from eliminating payment disputes, reducing lost bundles, and improving line balance typically pays back the investment within two months.
The Bundle System Is Not Going Anywhere
I have been in enough factories and read enough lean manufacturing literature to know that the bundle system catches criticism from production engineers and consultants. It creates WIP. It relies on batch thinking instead of flow thinking. It is the opposite of one-piece flow, which is the lean ideal.
All of that is true. And none of it matters for 90% of CMT factories operating today. The progressive bundle system works because it matches the reality of garment manufacturing: operators specialize in single operations, machine setups are fixed, and the entire piece-rate payment structure is built around counting completed bundles. You cannot rip out the foundation of a production system and replace it with one-piece flow over a weekend. It takes years of cultural change, cross-training investment, and a management team willing to absorb the transition cost.
What you can do — what I did — is take the existing system and make it visible. Replace the paper ticket with a QR label. Replace the coupon counting with a phone scan. Replace the end-of-day tally with a real-time dashboard. Replace the payment arguments with timestamped records.
The bundle system is not going anywhere. It is simple, it works, and every operator in South Asia knows how it runs. But the paper ticket attached to that bundle? That is the part that needs to evolve. When you replace paper with a QR code, you do not change the system — you just make it visible.
Ready to Digitize Your Bundle Tracking?
Scan ERP is built around the bundle system. QR labels, automatic work assignment, component marriage, piece-rate payments, and real-time WIP visibility — all designed for CMT factories running PBS.
Get a Free Demo