Material requirement planning

Every window is a different product.

34 1/2" × 60" · inside mount · blackout ivory

Change that measurement by one eighth of an inch and the fabric cut, the tube length, the price and the purchase order all move with it. That is why a bill of materials for made-to-measure has to be a set of formulas, not a list of parts — and why generic manufacturing software never quite fits your factory.

34 1/2"

Why generic ERP does not fit

Your ERP thinks a shade
is a part number.

Every manufacturing system on the market assumes a fixed bill of materials: this product, these parts, these quantities. That assumption holds for almost every industry — and it collapses the moment two windows in the same house are different sizes.

What generic MRP expects

A fixed parts list

One product code, one recipe. To quote a second size you create a second product. A plant offering roller shades from 22 to 96 inches in eighth-inch increments would need 593 product codes for one fabric — before options.

SKU RS-3450-BO-IVR fabric 2.08 yd tube 1 ea hem bar 1 ea clutch 1 ea
What made-to-measure needs

A parametric bill of materials

One product, evaluated per line. The deductions, allowances and counts are rules a workroom edits — not code a developer rewrites. Every quote, cut list and material requirement follows automatically.

fabric_cut_W = ordered_W − 1 3/8" tube_cut = fabric_cut_W + 1/8" hem_bar_cut = fabric_cut_W − 1/8" roll_up = 2.5 × π × tube_OD fabric_drop = drop + roll_up + 3"

That single difference is why vertical products exist in this category at all, and it is the thing this prototype is built around. Everything below runs on it.

The golden thread

One measurement, followed
all the way to a purchase order.

Six screens, one engine. The figures beside each step are computed live from the same order book the prototype runs on — nothing here is a screenshot.

Domain rules

The things software written
for other industries misses.

None of these are edge cases. Every one of them costs a workroom money every week, and every one is implemented and visible in the prototype.

What it finds

Three numbers most workrooms
cannot see at all today.

Measured on the prototype's seeded order book — 148 orders, 585 lines, one quarter of trading.

What is in the prototype

Nineteen working screens.
Four real engines.

Built as a proof of concept: no backend, no database, nothing persists. But the imperial arithmetic, the parametric BOM for all six product families, the MRP engine and the nesting optimiser are working implementations, verified against hand-worked industry examples.