The Hidden Complexity of BOMs in Apparel and Footwear

The Hidden Complexity of BOMs in Apparel and Footwear

Nov 16, 2026 · Look Cloud

In most industries, a bill of materials is a recipe. A product needs these components in these quantities, and that is it.

In apparel and footwear, the recipe changes with every color and every size. A navy jacket uses navy thread and a navy zipper, while the black version uses black ones. A size 45 shoe needs more leather than a size 36, and a different sole mold. Multiply that by hundreds of styles per season, and the BOM becomes one of the hardest pieces of data to keep right, and one of the most expensive to get wrong.

01

Five sources of complexity

BOM Structure · Variables
  • Color-dependent components. Fabric, thread, trims, zippers and labels change with each colorway. Some components follow the garment color, others stay the same across all colors, and some combine contrasting colors.
  • Size-dependent consumption. Larger sizes use more fabric or leather. In footwear, soles, lasts, insoles and boxes often change by size or size range.
  • Multiple levels. A shoe is assembled from semi-finished parts: an upper made of leather, lining and reinforcements, plus a sole unit. Each level has its own BOM, its own operations and sometimes its own supplier.
  • Operations and external processes. Cutting, stitching, embroidery, printing, washing or lasting are part of how the product is made. Many happen in outside workshops that need to receive the right materials.
  • Prepacks. Products are often sold or shipped in prepacks: a carton with a fixed size curve. The prepack itself is a BOM of SKUs, which sits on top of every SKU’s own BOM.
02

Example: one sneaker, many BOMs

Multi-SKU BOMs · Footwear

Take a single sneaker style offered in 4 colors and 10 sizes.

Each of the 40 SKUs needs its own bill of materials, pulling the right leather color, the right sole for its size range and the right box. The upper and the sole unit have their own BOMs one level down. Add a prepack, and there is yet another level on top. One style on the designer’s screen easily becomes more than 40 BOMs in the ERP.

Sneaker BOM: One style, three parts
03

Why generic ERP struggles

ERP Limitations · Workarounds

ERP systems like SAP Business One or Acumatica handle BOMs well, one item at a time. They expect each SKU’s BOM to be created and maintained individually. That leaves fashion companies with three bad options:

  • Build every BOM by hand. Slow, repetitive and full of copy-paste errors, such as a black zipper on a navy jacket.
  • Use one generic BOM per style. Simple, but material requirements and costs are wrong for every color and size, and purchasing has to correct them in spreadsheets.
  • Skip the BOM in the ERP. Production is managed outside the system, so material planning, costing and stock are never accurate.

And every change made during development, such as a new trim, a different fabric or an updated consumption, has to be repeated across dozens of BOMs.

04

How Look manages it: define once, generate everywhere

Look Cloud · ERP Automation

Look Cloud treats the BOM the way designers and product developers think about it: at style level, with rules for color and size.

  • One style BOM. The product developer builds a single BOM for the style, as part of the techpack, listing every material, trim and operation.
  • Color and size rules. Each line says how it behaves: follows the garment color, uses a fixed color, or maps to a specific color per colorway. Consumption can vary by size or size range.
  • Multi-level structure. Semi-finished parts such as uppers and sole units keep their own BOMs and operations, including those done by outside workshops.
  • Automatic ERP BOMs. When the style is released, Look generates the BOM for every SKU and creates it in SAP Business One, SAP S/4HANA or Acumatica. For prepacks, Look creates the prepack BOM with its size curve.
  • Changes in one place. Updating a material in the style BOM updates every SKU-level BOM, so the ERP stays in sync with development.

The result: Accurate material requirements, correct costing by color and size, and production orders that pull the right components, without anyone maintaining hundreds of BOMs by hand.

Struggling with BOMs in your ERP? Contact Argentis Systems to see how Look Cloud manages apparel and footwear BOMs with your own styles.