A 40 style capsule collection usually dies in the same place: week six, somewhere between the first sample and the factory approval email nobody answered.
Ask any product developer at a mid sized brand what eats their week and you will not hear “design.” You will hear tech packs, WhatsApp threads with a factory in Tirupur, and a size chart that exists in four versions across three laptops. The design is done. The business is stuck. That gap between a finished sketch and a shipped garment is where most apparel margins quietly evaporate, and it costs far more than most founders want to admit.
The fix is not more meetings. It is getting every style into one shared record that designers, buyers, and vendors all read from. That is the short version of plm for apparel, and once you see the leaks it plugs, the spreadsheet habit gets hard to defend.
What actually goes wrong in the middle
Here is the pattern I have watched across small and mid sized brands: a style gets approved in a group chat, the tech pack gets updated on someone’s desktop, the factory works from the version they were emailed two weeks ago, and the first bulk order comes back with the wrong placement on the chest print.
Nobody is lazy. The information simply lives in too many places. A sample comment sits in an email thread. A fabric substitution gets decided over a phone call. A measurement change gets written on a paper spec sheet that never makes it back to the master file.
Every one of those gaps has a cost. Sometimes it is a rework charge. Sometimes it is a two week delay that pushes your drop past the season. And sometimes it is a whole run of product you cannot sell at full price.
The leak is never one big mistake. It is forty small ones that never show up on a single invoice.
Four places your margin disappears
If you want to know whether your process is bleeding, look at these four spots. Every apparel team I have talked to loses money in at least two of them.
- Sample rounds that drag. Each extra sample cycle burns fabric, freight, and weeks. Teams that track comments in one place typically cut at least one full round.
- Version confusion at the factory. If a vendor can open two documents and see two different specs, you are gambling on which one they build from.
- Costing that gets rebuilt from scratch. When fabric prices, trim costs, and labor rates live in separate files, every quote becomes a fresh research project.
- Approvals with no paper trail. “I thought you signed off” is the most expensive sentence in apparel production.
None of these are design problems. They are information problems, and information problems have boring, fixable answers.
Why spreadsheets stop working around style fifty
Spreadsheets are genuinely great for the first season. You can hold twelve styles, a fabric list, and a rough cost sheet in one file and it feels manageable.
Then you add a second category. Then a second factory. Then a licensee, a wholesale account that wants custom labeling, and a sustainability questionnaire from a retailer. Suddenly the same workbook has nineteen tabs and one person who understands it.
That person becomes a bottleneck. They go on vacation and the collection stalls. They leave the company and institutional knowledge walks out with them. I have seen brands pay real money to freelance consultants purely to reconstruct what used to be in someone’s head.
The spreadsheet is not the problem. The problem is that it only works while one person remembers how it works.
The one record approach, and what it changes
The alternative is a single product record per style, where the sketch, the tech pack, the bill of materials, the sample comments, and the cost all point to the same source of truth. When a measurement changes, it changes once. When a vendor opens the style, they see the current version, not the version from three emails ago.
That sounds obvious written down. In practice it requires a few habits to stick:
- Every style gets a record before the first sample. No exceptions for “small” styles, because those are the ones that slip through.
- Comments go in the record, not in chat. If a decision matters to production, it belongs with the product.
- Vendors work from the live version. No PDF attachments, no version numbers in filenames.
- Costing updates when inputs change. Fabric price moves, margin recalculates.
- Approvals are timestamped. Who approved what, and when, in one line.
You can run steps two through five on a shared drive with disciplined naming, honestly. It works for smaller brands. It just stops working the moment you have more than a handful of people touching the same styles.
Where apparel fits in a bigger manufacturing story
Apparel is not unique in this. Manufacturers across every category have spent decades moving from paper based tracking to digital records, and the pattern is always the same: the product gets more complex, the coordination cost rises, and the paperwork becomes the bottleneck.
You can see the same arc in how product lifecycle management evolved from aerospace and automotive engineering into consumer goods. Fashion came late to it because collections move fast and the industry rewards improvisation. That is changing, partly because retail buyers now expect traceability and partly because the margins are too thin to absorb avoidable rework.
Small apparel businesses are also a bigger slice of the economy than most people assume. According to the U.S. Census Bureau, firms with fewer than 500 employees account for the overwhelming majority of employer businesses in the country, and apparel is no exception. When you are one of those firms, a two week delay is not an inconvenience. It is a cash flow event.
A simple audit you can run this week
Before you buy any software, spend an afternoon finding out how bad it actually is. Pick five styles that are mid development and answer these questions for each one:
| Question | What a bad answer looks like |
|---|---|
| Where is the current tech pack? | Two people point to two different files |
| What was the last sample comment? | Someone has to search an email thread |
| Who approved the last revision? | Nobody can say with certainty |
| What is the current unit cost? | The number lives in a separate spreadsheet |
| Can the factory see the latest version? | They have a PDF from last month |
If you get three or more bad answers out of five styles, your process is the problem, not your team. That is genuinely good news, because process is the cheaper of the two to fix.
Choosing what to do next
You have three realistic paths. Keep the current setup and accept the rework. Tighten your spreadsheets and naming conventions, which buys you maybe another season or two. Or move product data into a dedicated system that holds everything in one place.
I would push most growing brands toward the third option once they cross roughly thirty active styles per season or start working with more than two factories. Below that line, better discipline often costs less than a platform.
The U.S. Small Business Administration makes a related point that applies here: for a small firm, operational efficiency is usually a survival question, not a luxury. In apparel, the operational leak is almost always the same one, hiding in the space between a good design and a factory that never quite got the right version of it.
So run the audit. Count your bad answers. If the number surprises you, you already know what the next move is, and it probably is not hiring another coordinator to hold it all together.






