You're a small manufacturer.
If you assemble gift boxes, pack subscription kits, build hampers, repackage bulk into retail units, or even just add a branded sticker to a shipped product, you're doing light manufacturing. Shopify "bundles" are pricing tricks. Xero ledgers don't track components. Once your finished goods consume parts, your tooling needs to know about both — or your stock numbers are fiction.
- Your gift boxes contain three to ten different SKUs you also sell separately.
- You ship a monthly subscription pack that's a different combination each cycle.
- You buy in bulk and repackage into retail units (e.g., 25kg sack → 50× 500g pouches).
- You receive components and assemble a finished good — even something as light as "branded sticker on supplied product."
- You can sell out of a kit because one component is short — but Shopify still says you have stock.
- Your true cost of goods for an assembled product is a guess that lives in someone's head.
A Bill of Materials, properly modelled.
In ERPNext, a Bill of Materials isn't a tag or a setting — it's a first-class document. You define the recipe once. Each time a finished good is assembled (a "Stock Manufacture entry"), the components decrement automatically. Stock-on-hand for the kit and for each underlying SKU stays in sync. And the cost basis for the finished good rolls up correctly from the components.
What this gets you in practice: when ribbon runs out, the system tells you the gift box can't be built — before a customer orders three of them. When you change the recipe (subscription pack content varies cycle to cycle), you version the BoM. When finance asks "what does this kit actually cost us?" — that number rolls up from real component costs, not a sticky note.
And once you have BoMs…
…the rest of ERPNext's manufacturing primitives become useful. Subcontracting for the parts you outsource (label printing, hand-finishing, fulfilment-house packing). Variance posting when actual yield differs from the recipe. Backflushing to consume components on a Work Order completion. Per-batch BoM when one supplier's lot has different yield than another's. None of this is exotic ERP territory — it's what manufacturing operations have always needed. The shift is doing it with open-source software that fits under your existing storefront and accounting tools, instead of a six-figure SaaS contract.
Most growing e-commerce businesses are quietly running a small manufacturing operation — and their tooling is in denial about it.
Other ways your tooling is showing the strain
More on the ScanMan stack.
Manufacturing primitives are one part of what ERPNext brings. Read on at scanman.co — the WMS, the open-source robotics positioning, and where it's all going.