Ask a founder how much fabric a 300-unit production run needs and you'll usually get a pause, a WhatsApp message to the factory, and an answer that's right to within "roughly." A bill of materials replaces that pause with arithmetic. It's the recipe for one unit of your product — every component, every quantity, every gram of waste — and once it exists, questions like "what do I buy?", "what does this cost me?", and "can I even make 300?" become calculations instead of conversations. This guide builds a complete BOM from scratch and shows everything it unlocks.
Key takeaways
- A BOM is the recipe for one unit: components, quantities, units of measure, and waste allowances.
- Multiply the BOM by a production quantity, subtract materials on hand, and the shortfall is your purchase order — no guessing.
- Waste allowances (3-5% on cut fabric is typical) belong in the BOM, not in someone's head.
- Size variants S-XL should share one BOM with per-size overrides, not four separate ones that drift apart.
- The same BOM that drives purchasing also gives you your true unit cost — and shows when a price rise quietly eats your margin.
What a bill of materials actually is
A bill of materials is a structured list of everything required to produce one sellable unit, with three attributes per line: the component, the quantity per unit in a stated unit of measure, and a waste allowance reflecting how the real world differs from the drawing. Packaging belongs on the list too — a kurta without its polybag and carton allocation can't ship, so those are materials, not afterthoughts.
Get the units of measure right and half the future errors disappear. Buy fabric in metres and consume it in metres; if thread arrives in 5,000 m cones but the BOM thinks in metres used, record the conversion once, in the BOM, rather than re-deriving it in every purchase discussion. Mixed units — a BOM in metres and a stock register in kilograms — are the quiet cause of most "we ordered enough, how are we short?" mysteries.
Here's a complete, honest BOM for a cotton kurta, including costs so we can use it for the rollup later:
| Component | Qty per unit | Waste | Effective qty | Unit cost | Cost per kurta |
|---|---|---|---|---|---|
| Cotton fabric | 1.8 m | 4% | 1.872 m | ₹140/m | ₹262.08 |
| Buttons | 5 pcs | 2% | 5.1 pcs | ₹3/pc | ₹15.30 |
| Sewing thread | 120 m | 5% | 126 m | ₹0.04/m | ₹5.04 |
| Labels (brand + care) | 2 pcs | 2% | 2.04 pcs | ₹4/pc | ₹8.16 |
| Polybag | 1 pc | 2% | 1.02 pcs | ₹6/pc | ₹6.12 |
| Shipping carton (1 per 24 units) | 0.042 pc | — | 0.042 pc | ₹60/pc | ₹2.52 |
| Materials total | ₹299.22 |
Two details worth noticing. The carton line shows how shared packaging works: one carton holds 24 kurtas, so each kurta carries 1/24th of a carton. And the "effective qty" column is where the waste allowance does its work — you cut 1.872 m of fabric to end up with 1.8 m in the garment.
Single-level vs. multi-level BOMs
The kurta above is a single-level BOM: one flat list, finished product at the top, raw materials below. For most D2C brands, this is all you need.
A multi-level BOM nests sub-assemblies. Imagine a festive gift set containing a candle, a diffuser, and a gift box. The gift set's BOM lists "1× candle" — and the candle has its own BOM of wax, wick, fragrance oil, and jar. Multi-level structures earn their complexity when you produce and stock the sub-assembly independently: you make candles in bulk, hold them as inventory, and assemble gift sets from that stock. If you never stock the intermediate item separately, flatten it — every extra level is another thing to keep accurate.
The practical rule: start single-level; go multi-level only when a sub-assembly has its own production schedule and its own stock count.
Handling variants: one BOM, not five
Here's a mistake that quietly doubles maintenance work: creating a separate BOM for every size. The kurta comes in S, M, L, and XL — same fabric, same buttons, same labels. Four independent BOMs means four places to update when the button supplier changes, and four chances for them to disagree six months from now.
The better pattern is one BOM per product, shared across variants, with overrides where consumption genuinely differs. An XL might take 2.0 m of fabric against the S's 1.65 m — that's a per-size quantity override on the fabric line, not a new document. Everything else stays shared. This is exactly how Honey Shelf models BOMs: variants inherit the product's recipe, and you adjust only the lines that change. It also matches how plans should count SKUs — S through XL of one design is one product to manage, not four.
Waste and scrap allowances: plan for reality
No cutting table converts 100% of fabric into garments. Pattern layouts leave offcuts, some pieces fail QC, thread breaks and gets rewound. If your BOM says 1.8 m and reality consumes 1.87 m, then on a 500-unit run you'll be 35 metres short — discovered, inevitably, mid-run.
Waste allowances make the BOM tell the truth. Typical starting points: 3-5% on cut fabric, 1-2% on discrete components like buttons and jars, more for processes with real rejection rates (printing, dyeing, glass). But the honest method isn't a rule of thumb — it's your own data. After a few runs, compare materials issued to the factory against units produced, and set each component's allowance from actuals. If your fabric waste is consistently 7%, a 4% allowance is a polite fiction that costs you a mid-run shortage every time.
From BOM to purchase order: the shortfall calculation
This is where a BOM stops being documentation and starts being operations. Planning a 300-unit run of the kurta? The material requirement is the BOM times 300, and the purchase order is whatever you don't already have:
The same arithmetic answers the reverse question, which saves runs from stalling: given what's on hand, what's the largest run I can start today? With 210 m of fabric and an effective consumption of 1.872 m per unit, you can cut 112 kurtas right now while the fabric PO is in transit — instead of waiting three weeks to start anything at all. Run the shortfall calculation on every line and you have a complete, supplier-ready purchase list in minutes — buttons and thread from one supplier, fabric from another, each with its own lead time. In Honey Shelf's 6-stage pipeline this is the "Buy Materials" stage: the moment you draft a production order, the system explodes the BOM, nets it against material stock, and auto-drafts the POs for the shortfall. No spreadsheet, no forgotten thread order stalling a finished batch of cut fabric. How this fits into a full production calendar is covered in our guide to production planning for small manufacturers.
Costing rollup: what a unit really costs
The same table that drives purchasing also answers the margin question. Sum the cost column and the kurta's materials cost is ₹299.22. Add labour (say ₹110 per piece CMT) and per-unit overheads like job-work transport, and you have a true unit cost of roughly ₹430 — against a ₹1,499 selling price, a materials-and-making margin you can actually defend in a pricing discussion.
The rollup matters most when it moves. If cotton goes from ₹140 to ₹158 a metre, your unit cost silently rises by ₹33.70 — about 2.2 points of margin on this product. A live BOM recalculates that the day the new price lands; a static costing sheet from last year tells you at the annual review, eleven months too late. This is also the foundation for metrics like inventory turnover, which depend on knowing your true cost of goods sold.
Common BOM mistakes
- Leaving packaging out. Polybags, tags, inserts, and cartons are materials. Brands that omit them under-order them constantly — and nothing ships without them.
- No waste allowance. The BOM describes the ideal; production happens in the real. Every cut-material line needs an allowance based on actuals.
- Per-size BOM copies. Four documents that must be updated in lockstep never are. One BOM, per-variant overrides.
- Stale costs. A BOM with last year's prices produces this year's margin surprises. Update component costs when supplier invoices change — or use a system that does it on receipt.
- The BOM lives in one person's head. If material math depends on your production manager's memory, their holiday is a supply-chain event. Write it down where the whole team — and your software — can use it. This matters double if you work with external factories; see our notes on contract manufacturing in India.
Start with your bestseller
You don't need to BOM your whole catalogue this week. Pick your top product, list every component with honest quantities and waste, and run the shortfall calculation before your next production order. The first time a PO comes out of arithmetic instead of memory — correct, complete, and ten minutes after the production decision — the rest of the catalogue will follow on its own.