Apparel Bill of Materials: Build and Reconcile a Production BOM

A garment order can have enough buttons in total and still be short of the right colour, because the combined quantity hides which variants are available. It can also have the correct elastic length on a costing sheet while the purchase order uses rolls with a different yield. A bill of materials must preserve these details as the product moves from design to purchasing and production.

An apparel bill of materials, or BOM, lists the materials and parts needed for a defined garment. It connects each item to its use, quantity and version. A useful BOM lets the team explain where every requirement came from and recalculate it when the order changes.

This guide builds that control around a hypothetical order for 3,600 woven shorts. The quantities and allowances are teaching assumptions. A real order needs approved product data, trial results and supplier terms.

Decide what the BOM is describing

Start by naming the parent product: the garment or assembly the list will produce. State whether quantities apply to one garment, one dozen, one pack or another basis. Put that basis in a visible field.

A BOM for one garment describes the product, while a material requirement for an entire order applies that description to the quantities being made. The order calculation multiplies use by the required size and colour quantities, then handles agreed allowances and purchasing rules.

Microsoft's production BOM documentation describes components and subassemblies linked to a parent item. The useful principle for apparel is that a row needs a defined relationship to the garment. A list of supplier names and prices alone cannot provide it.

Include fabrics, linings, interlinings, sewing thread, closures, labels and other parts that the design requires. Define how packing materials will be handled. Some teams keep them in the same BOM; others use a linked packing BOM. Either method can work if there is no missing or double-counted requirement.

Keep manufacturing services distinct from physical materials. Embroidery work may be priced as a service, while its backing and thread may be supplied by the embroiderer. State who provides those inputs. Otherwise, both the factory and subcontractor may order them, or neither may do so.

Make assemblies and packing quantities explicit

A purchased assembly may contain several parts that do not need separate purchase rows. A complete zipper, for example, can include its slider and stops. If these are already included in the supplied unit, adding separate quantities for them would overstate what the factory must buy.

The technical file can still describe those parts, provided it distinguishes details that define the assembly from items that the factory must obtain and fit. If the factory buys zipper chain and sliders separately, the BOM needs a different structure that reflects that work.

Packing creates another change of basis. Suppose the shorts are packed twelve garments to a carton, with one divider in each carton. For 3,600 garments in full cartons, the net need is 3,600 ÷ 12 = 300 cartons and 300 dividers. It is not 3,600 dividers. A mixed-size pack rule may need its own table rather than a simple division.

Include buyer-supplied components in the physical requirement even when the factory does not purchase them. Their purchasing cost may be zero to the factory, but production still needs the correct quantity. Record ownership and supply responsibility in separate fields so a price filter cannot make a needed item disappear.

Use identities that survive a change of supplier description

Give each controlled item an internal code linked to the supplier's reference, then add the material, colour and key size or construction details needed to identify it. The description should help a person recognise the item, while the code keeps the record stable.

“Black zipper” is incomplete. The order may use several lengths, opening types or sliders. A correct quantity against a vague item name still leaves purchasing free to select the wrong product.

Keep the garment variant separate from the component variant: navy and stone garments might share one black elastic even though they require different zipper colours. The elastic can remain one shared material, while the zippers retain their separate identities. Do not create duplicate stock identities merely because the parent garment colour differs.

Conversely, do not merge items that only look similar. Two buttons with the same diameter can differ in finish, material or approved use. An approved alternate should have a controlled link to the primary item, not be hidden inside a general description.

If the customer uses GS1 identifiers, follow the agreed allocation rules. The GS1 GTIN Management Standard treats style, colour and size variations in its apparel example as distinct products. An internal component code and a trade-item GTIN serve different purposes. Map them clearly where both are used.

Build rows that explain the quantity

A practical BOM row needs enough data to support selection and calculation. The following fields can be adapted to the business, but the underlying questions should be answered.

Separate colour and size fields where that makes filtering clearer. Avoid burying several rules in a long remark such as “use A except for large navy and all tall sizes.” A small variant table is easier to verify.

The CLO-SET BOM documentation shows an apparel system managing information by colourway, grade and version. A spreadsheet can use the same basic discipline. The important point is that each combination receives the correct data when it is exported or changed.

Do not put a guessed value into a production BOM without marking its status. An early estimate can support a first quotation. It must be replaced or approved on a stated basis before people rely on it for bulk purchasing.

Start the order calculation with a reconciled size split

The example order has two colours and three sizes. Its approved quantities are as follows.

Check that the row totals and column totals both add to 3,600 before multiplying any material use, because a copied grand total cannot reveal a missing or duplicated variant. This reconciliation tests the size-colour split that drives the component calculation.

Now identify which components share the same use across the order. Assume every garment needs one main label, two sewn buttons and one matching spare button. The spare is part of the delivered product, so it belongs in net product use. It is not a waste allowance.

Main-label requirement = 3,600 × 1 = 3,600 labels.

Total net button requirement = 3,600 × 3 = 10,800 buttons.

Assume each colour uses its own button shade. The navy and stone requirements are therefore 5,400 buttons each. Purchasing a combined 10,800 without the shade split would lose essential information.

A size label creates another split. If its design is the same for both colours, net requirements are 1,200 S labels, 1,600 M labels and 800 L labels. Check whether the size is printed on a separate label or combined with another label before adding both rows.

Calculate size-dependent materials from the actual mix

Suppose the shorts use one cut piece of elastic in the back waistband. For this example, the approved cut lengths are 0.28 m for S, 0.30 m for M and 0.32 m for L. These are material cut lengths, not the finished waist measurement or a general rule for elastic design.

Net material requirement = sum of each variant's garment quantity × its material use.

For the elastic:

Net requirement = (1,200 × 0.28) + (1,600 × 0.30) + (800 × 0.32) = 1,072 m.

The order-weighted average is 1,072 ÷ 3,600 = about 0.29778 m per garment. It describes this particular size mix, so using it as a permanent product-BOM value would carry one order's assumptions into later orders with different quantities.

Using 0.30 m for every size would produce 1,080 m, which is 8 m above the calculated net need. Another size mix could make the same shortcut understate the requirement. The direction of the error depends on the order.

Keep enough precision in the underlying data. Round only at an agreed stage. Rounding the average too early and multiplying it back across a large order can create a difference that nobody can explain from the component rows.

State the allowance convention before applying it

The phrase “add 5% wastage” is incomplete unless everyone agrees what the percentage means. Two common calculations use different denominators.

If the allowance is an extra percentage of net need:

Planned input = net need × (1 + extra allowance rate).

If the loss is a fraction of input and the usable yield is known:

Planned input = net need ÷ usable yield.

For a net requirement of 1,000 units, adding 5% gives 1,050 units. A 5% loss of input means 95% yield, so the calculation is 1,000 ÷ 0.95 = 1,052.63 units before rounding.

The two answers differ because one percentage adds to the net requirement, while the other describes the share of purchased input that remains usable. Oracle's BOM guidance describes component yield using the second approach: component use divided by yield. Check how the actual planning system handles its fields before entering an allowance.

For the shorts example, assume the agreed elastic allowance is an extra 2% of net use. This allowance covers defined cutting and handling needs that are not already included in the cut lengths.

Planned elastic input = 1,072 × 1.02 = 1,093.44 m.

The 21.44 m difference is the planned extra amount, which reserves material for the stated needs without proving that this much waste will occur. Keep actual use and loss records so future allowances can be reviewed against evidence.

Do not add the same loss twice. If a fabric consumption figure already includes marker loss, adding another marker-loss percentage over it inflates demand. Record what each usage figure includes before applying order-level extras.

Convert into the supplier's selling unit

The BOM may use pieces or metres while the supplier sells bags, gross units, rolls or cartons. Keep the base unit and purchase unit distinct. Record the conversion for the exact item and pack being quoted.

Microsoft's unit-of-measure guidance explains the relationship between a base unit and alternate purchase or production units. The same issue exists outside an ERP system. “One box” is not a reliable quantity unless the box contents are defined.

Assume each button shade in the example needs an extra 3% over net use. The supplier sells each shade in packs of 144 buttons, with no split packs.

Planned need per shade = 5,400 × 1.03 = 5,562 buttons.

Packs per shade = 5,562 ÷ 144 = 38.625 packs.

Round up to 39 packs per shade.

Purchased buttons per shade = 39 × 144 = 5,616 buttons.

Pack-rounding surplus per shade = 5,616 − 5,562 = 54 buttons.

For both shades, purchase 78 packs, containing 11,232 buttons. That includes 324 buttons from the 3% allowance and 108 from pack rounding above the total net need of 10,800.

Keep those causes separate so a later review does not call all 432 extra buttons “waste” when some may remain as usable stock. Their treatment depends on ownership, buyer rules and future approved demand.

Round each non-interchangeable variant on its own. A spare navy button does not cover a stone-button shortage merely because the grand total is sufficient.

Match the price unit to the quantity unit

The same conversion matters when the BOM carries prices. Assume the quoted button price is US$7.20 per pack of 144, before any other charges. The price per button is 7.20 ÷ 144 = US$0.05. Multiplying the piece count by the pack price would produce a large error.

For the 78 packs above, the purchase value is 78 × 7.20 = US$561.60. Net product use alone is worth 10,800 × 0.05 = US$540.00 on this limited basis. The US$21.60 difference relates to the 432 buttons added through allowance and pack rounding.

Keep both figures labelled, since neither represents the complete delivered material cost when freight, duties or other charges must also be paid. The example checks the BOM's unit relationship; it does not set an accounting rule for surplus stock.

Deduct stock only when it is genuinely available

An order requirement is not always the quantity to buy, because the factory may already hold approved stock of the same item or have incoming supply allocated to the order. These supply records affect purchasing without changing what enters each garment.

Check identity and status before deducting either. Stock reserved for another order is not free stock. A roll on quality hold is not ready to cover a released requirement. A supplier's promise is different from a confirmed receipt.

For the elastic example, assume 60 m of matching, approved stock is available and allocated to these shorts. There are no other open receipts for the order. The supplier sells full 50 m rolls.

Additional length before pack rounding = 1,093.44 − 60 = 1,033.44 m.

Rolls to buy = 1,033.44 ÷ 50 = 20.6688, rounded up to 21 rolls.

New purchase = 21 × 50 = 1,050 m.

Total available after receipt = 1,050 + 60 = 1,110 m.

Planned surplus = 1,110 − 1,093.44 = 16.56 m.

This calculation assumes each roll provides its stated usable length, so different supplier packing or length terms require a revised conversion and a check of the received quantity. The ApparelDiary guide to usable supplier lead time explains why received material and usable material are different planning states.

Do not hide stock deductions inside the product's use-per-garment field. The shorts still need the same elastic length even when some supply comes from existing stock. Product use and supply availability must remain separate.

Handle fabric and thread with a clear basis

Fabric use often depends on the approved pattern, size mix, usable width and layout. A single metre-per-garment value may be an early estimate, a marker result or an allowance-loaded purchasing figure. Label which one it is.

When the basis changes, recalculate the affected requirement. A new usable width can alter the layout result even if every finished measurement stays the same. Do not carry an old fabric consumption into a new width without checking it.

Thread needs similar care. State whether the estimate covers all seams, colour changes, normal handling loss and any special operation. Keep the length unit consistent with the cone's labelled yield. The ApparelDiary sewing-thread consumption guide develops the length and cone-order calculations in detail.

For both materials, preserve the source calculation or trial reference so a reviewer can reproduce the total even when the BOM contains only the approved result. This keeps detailed engineering work accessible without forcing every purchasing user to navigate the whole worksheet.

Keep alternate materials controlled

An alternate is a defined option that has been assessed for a stated use. It is not a blank permission to buy something similar when the main item is late.

Record the alternate code, supplier, use quantity and any changed conditions. An alternate elastic may need a different cut length to achieve the agreed garment result, which makes a one-for-one substitution unreliable until that use has been validated.

Keep the approval state visible. A proposed alternate can be listed for review while remaining blocked for purchasing or use. State the exact permission so procurement does not interpret its presence in a spreadsheet as approval.

If the alternate replaces the primary item for part of an order, identify the affected units or lots. The material requirement should show which version applies to each portion. Do not sum both primary and alternate rows as though both enter every garment.

Use the same discipline for buyer-nominated materials. A nominated source still needs the correct reference, variant, use quantity and supply scope. Nomination alone does not make a row complete.

Recalculate changes only for the units they affect

A BOM revision needs both a change description and an effective scope that identifies whether it applies to the next sample, a new order or part of existing work. A date alone may be insufficient when old and new versions are being made at the same time.

Oracle's effective-date documentation illustrates the need for clear start and end boundaries. For an apparel order, pair those boundaries with the order or lot identity that staff can trace.

Suppose the technical team increases the size M elastic cut length from 0.30 to 0.31 m. The approved change affects 900 garments that have not yet received their elastic. The remaining size M units keep the earlier version under a recorded decision.

Extra net elastic = 900 × (0.31 − 0.30) = 9 m.

With the same extra 2% convention, the added planned input is 9 × 1.02 = 9.18 m. Compare that change with the remaining usable supply before placing another order. Do not automatically apply it to all 1,600 size M garments.

Keep the earlier use and consumption records intact. Overwriting history would make the original purchase and issued quantities appear wrong, even though they followed the valid requirement at the time.

Check the file that purchasing actually receives

A correct master record can still produce a faulty export if the selected colours, sizes or versions do not cover the work being released. Open the actual file and check its contents. A filter left on one colour can remove half an order without changing the visible column headings.

Check a few rows all the way from the source record to the exported quantity. Include a shared component, a size-dependent component and an approved alternate. Confirm that units, decimal places and approval notes remain visible. Look for duplicate rows caused by copying an assembly into more than one section.

Do not assume that linked data updates itself. The CLO-SET BOM guide states that changes to linked trim-file versions are not reflected in its tech pack automatically. Other tools may use different rules. Test the behaviour that matters in the system being used.

Save the released export with its version and issue date. When a correction follows, name the file it replaces and tell the affected teams. That makes it possible to establish which data supported a purchase instead of relying on the latest file in a shared folder.

Reconcile the BOM through the real garment

Before release, compare the list with the approved sample and construction instructions. Trace the garment from outer fabric to closures, internal support, labels and packing. Check small items that are easy to miss, such as a spare button or a protective packing insert.

Then reconcile the mathematics. Each size-colour quantity must link to a valid product version. Every use figure needs a unit. Allowances need a stated basis. Purchase packs must convert back to a sensible base-unit total.

Ask purchasing to check supplier pack sizes and quality staff to check approval references. Ask the sample room to confirm that listed components match the garment they made. These reviews test different parts of the same record.

Finally, keep the BOM connected to actual changes during production. A good list is not merely complete on the day it is created. It remains clear about the product, the units affected and the evidence behind each quantity as the order develops.

References

• Microsoft Learn: production BOM structure, quantities and versions.

• CLO-SET: BOM information by colourway, grade and version.

• GS1: GTIN Management Standard.

• Oracle: bills of material and component yield.

• Microsoft Learn: base and alternate units of measure.

• Oracle: component effective-date fields.