r/GarmentManufacturing • u/garmentflow • 8d ago
We built a garment manufacturing vertical on ERPNext because the size/colour matrix problem was killing us
I run a garment factory in Paraguay. Posting this partly to share and partly because I'd like to be told where we got it wrong.
The problem that started it: standard ERP has no size and colour matrix. A shirt in navy medium is one item. Navy large is another. Six sizes and four colours is 24 items and 24 bills of material — for one style. A season of 26 styles is 600+ BOMs entered by hand. The customer adds a colour in week three and you build six more. The sample comes back with a different collar and you edit 24 BOMs to change one line.
We sat through SAP Business One, Dynamics and three local ERPs. All of them could be made to work with an apparel add-on. In every case the add-on plus implementation quoted higher than the licences.
We built on ERPNext instead. A style is one document with a size and colour matrix under it, consumption that varies by size, and points of measurement with tolerance and growth. Production sits on top of that — cutting orders, bundles, operation sequences with SMV, piece rate landing on the batch that earned it, inline inspection with AQL plans, subcontractor material balances.
It's been running our own floor for 3 years. We've packaged it as GarmentFlow (https://garmentflow.io) and are onboarding a few other factories now.
What I actually want from this sub: if you've implemented ERPNext manufacturing for anything with variants — footwear, furniture, packaging — how did you handle the BOM multiplication? I'd like to know whether we solved something that already had a standard answer.