Excel vs a system: when spreadsheets stop working for apparel

Let's say up front what software vendors usually won't: if you have a dozen styles or fewer and you handle everything yourself, you don't need any system. Excel, a Google Sheet and a couple of chats with the factory are an adequate toolkit at this stage. Discipline matters more than software.

This article is about how to recognise the moment when spreadsheets start costing more than a system does. And what PLM actually is, explained without the buzzwords.

What a "healthy" Excel stage looks like

One person keeps the whole collection in their head. A file called Styles_2026.xlsx with tabs, a folder of tech specs, a chat with the factory. Things change rarely, there are two or three people involved, and the cost of a mistake is modest. Everything is under control, because the controller is a single head, and it's yours.

Problems don't start because of the volume of data. They start because of the number of hands and the speed of change.

Six signals you've outgrown spreadsheets

1. You've had a "version incident." The factory sewed from an old file. Or a manager sent out a price list with last year's costing. If this has happened even once, it will happen more often from here: the number of copies grows faster than the number of people in the process.

2. More than two people are involved. A designer, a buyer and a marketplace manager have appeared, and your single Excel file has turned into four ("I made my own copy so it's easier for me"). The question "where's the current version?" starts eating an hour a day. The most common scenario: you edit a cell in your file while the buyer edits their copy at the same time, and by evening the two versions diverge and nobody remembers which one is right.

3. 30+ active SKUs. The number past which "keeping it in your head" stops working, even for very capable heads. The symptom: you open your own spreadsheet and aren't sure whether a row is still current. Another one: someone sorted a range without including the neighbouring column, and sizes drifted out of sync with style numbers. A BOM row with the lining was deleted along with a filter, and you only noticed it at goods-in.

4. You learn the costing after the batch is ordered. If margin is calculated "later, once all the invoices arrive," every batch is a lottery. (How to calculate it before ordering is a topic in its own right.)

5. Compliance and labelling have become a separate job. At 30-100 SKUs, the manual cycle of generating labels, printing them, matching them to sizes and reconciling the paperwork eats 5-10 hours a week, and that's exactly where mismatches are born, because the product data lives in one file and the labels live in another tool.

6. You can't take two weeks off. The bus test: if the process grinds to a halt without your head, you don't have a process, you have you. That's fine for a hobby and dangerous for a business that's growing.

Two signals or more: it's time to look at a system. Zero or one: close this tab and get back to work, you're doing fine.

What PLM is, in plain terms

PLM (product lifecycle management) is not "another spreadsheet, but in a browser." It rests on three principles:

One record, one truth. Each style has a single record: tech pack, materials, sizes, colours, costing, status. Everyone looks at the same one. Versions change inside it, with a history of who changed what.
The process is built into the data. A style isn't "somewhere in production," it's at a specific stage: sketch → sample → approved → order → shipment. Overdue items show up on a dashboard instead of surfacing on a Friday evening.
External participants work in the same place. The factory sees the current tech pack and marks off stages in its own portal, rather than receiving PDFs across ten chats.

Inventory and accounting systems answer the question "what do I have and where is it": stock levels, purchasing, sales. PLM answers the question "what am I creating and what state is it in": styles, tech packs, samples, factories, costing before the batch. They aren't competitors but a before and after: PLM ends where the batch is received into the warehouse, and the accounting system takes over from there.

What to demand of any system (not just ours)

If you're going to shop around, put the candidates through this checklist:

Can you start yourselves in an evening, with no "implementation project" and no call with a sales team?
Is a tech pack with a size grid and tolerances a native object, or is it "attach a PDF"?
Is there a factory portal? Are factory seats free? (Paying per factory is a dead-end model.)
Is costing calculated from the BOM and quotes, or is it a "type in a number" field?
Does it integrate with your reality: marketplaces, your ERP/accounting system?
How does it handle compliance and labelling? (Spoiler: for most, it doesn't.)
What does it cost at your scale, and is the pricing public at all?

And the key test: take one of your own real styles and set it up in the system end to end on a trial. Don't look at the demo data, it always looks pretty. Watch how long it took you and where you got stuck.

The honest bottom line

Excel is a great tool that you need to outgrow at the right time. "The right time" isn't a revenue figure, it's the moment when version chaos starts costing real money: a batch sewn from an old file, a delivery delayed by a labelling slip-up, a margin surprise. It usually happens somewhere between 30 and 100 SKUs and the second or third person on the team. If you have 10 styles and a steady pair of hands, a system will only add work. Don't buy it out of anxiety, buy it out of a specific pain.

Recognised yourself in two signals or more? Add up the cost of your chaos over the last six months: multiply incidents by what they cost, then add the hours of routine work at your own rate. Compare that with the price of a system. From there, the decision is made by arithmetic.

From PLMflow. We build PLM for exactly this transition: get started yourself in an evening, tech packs with tolerances, a free factory portal, costing and margin before the batch is ordered, marketplace prices in the style record, and compliance handling from the same record soon. Try it on one of your own styles →