Most of the software conversation around manufacturing ERP goes to dashboards, reporting and integrations. The part that actually decides whether production runs on time is far less glamorous: a structured list of exactly what goes into what you build, and a set of calculations that turns that list into a purchasing plan.
TL;DR
- A bill of materials is the definitive list of every component, sub-assembly and quantity needed to build one unit of a finished product.
- MRP takes that list, checks it against what’s already in stock, and works backward from your delivery date to tell you what to order and when.
- Multi-level BOMs, where an assembly is itself built from smaller assemblies, are where manual spreadsheets tend to fall apart first.
- MRP is a planning function. ERP is what happens when that planning function is connected to purchasing, inventory and finance rather than sitting in isolation.
- Blue Lotus 360 handles multi-level BOMs and MRP calculations natively, so production planning updates the moment stock or demand changes.
What a bill of materials actually is
Take something straightforward, a wooden dining chair. To build one, you need four legs, a seat panel, a backrest, sixteen screws, a specific quantity of wood glue, and a tin of finish. That list, with exact quantities against exact components, is the bill of materials. Nothing exotic about it conceptually, it’s a recipe.
Where it gets more involved is when a product isn’t built from raw components directly, but from sub-assemblies that are themselves built from other components. A chair leg might be its own mini bill of materials: a length of turned wood, a rubber foot, a fixing bracket. That’s a multi-level BOM, and it’s the normal state of affairs for anything beyond the simplest products.
The accuracy of this list matters more than it looks like it should. Get a quantity wrong, or leave out a sub-component, and everything downstream, purchasing, costing, scheduling, inherits that mistake.
From bill of materials to a purchasing plan
A BOM on its own doesn’t tell you when to order anything. That’s where material requirements planning, or MRP, takes over.
Say you’ve got an order for fifty chairs due in six weeks. MRP starts by calculating the gross requirement: fifty chairs means two hundred legs, fifty seats, fifty backrests, eight hundred screws, and so on, multiplying the BOM quantities up across the order.
It then nets that figure against what you actually have. If you’ve already got sixty legs in stock from a previous batch, you only need to source a hundred and forty more, not two hundred. This step alone is where a lot of manual planning quietly falls apart, since it relies on stock figures actually being accurate at the moment of calculation, not from a count done three weeks ago.
Finally, MRP works backward from the six-week deadline, factoring in how long each component actually takes to arrive or produce, to tell you exactly when each order needs to go out. If your legs take two weeks to source but your screws are available same-day, those two purchase orders shouldn’t be raised on the same date. Time-phased, backward-scheduled ordering is what stops materials sitting idle in a warehouse for a month, or worse, arriving a week after they were needed.
Where this genuinely breaks without proper software
Spreadsheets can hold a bill of materials for a simple, single-level product without much trouble. The problems start compounding once real manufacturing complexity enters the picture.
Multi-level structures get unwieldy fast. Once a product has sub-assemblies that are themselves built from other sub-assemblies, tracking accurate quantities through several layers in a spreadsheet becomes genuinely error-prone. One wrong formula reference and the whole material plan is quietly wrong.
Engineering changes don’t propagate cleanly. A component gets swapped, a supplier changes a part number, a design gets revised, and now there are two versions of the same BOM floating around, one in the spreadsheet someone’s working from, one in whatever the original design intended. Nobody’s malicious here, it’s just how version control fails without a system enforcing it.
Stock figures go stale between the plan and the purchase order. MRP only nets correctly against inventory that’s actually accurate at calculation time. If your stock count was last updated a fortnight ago, the “net requirement” the spreadsheet spits out is built on a number that’s already wrong.
None of these are exotic edge cases. They’re the normal operating conditions of any manufacturer building more than a handful of simple products, which is most manufacturers.
MRP, MRP II and ERP: not quite the same thing
Worth being precise about this distinction, since the terms get used loosely. MRP, in its original and narrowest sense, is materials planning only: what do we need, and when. MRP II extended that to include capacity, labour and machine scheduling alongside materials, connecting the “what do we need” question to “can we actually make it with the people and equipment we’ve got.”
ERP is the layer above both: MRP or MRP II sitting inside a system that’s also handling finance, procurement, inventory and sales, so a material shortage flagged by planning immediately connects to a purchase order, a supplier record, and a cost that flows through to your accounts, rather than sitting as an isolated calculation someone has to manually action elsewhere.
For most growing manufacturers, the practical question isn’t which of these three terms technically applies. It’s whether material planning lives inside the same system as everything else it needs to talk to, or whether it’s an island that someone has to bridge by hand.
Where Blue Lotus 360 fits in
Blue Lotus 360 handles multi-level BOMs and MRP calculations as core manufacturing functionality, not an add-on module bolted onto general accounting software. Stock netting runs against live inventory data rather than a snapshot from last week, engineering changes to a BOM update the plan immediately rather than needing to be manually re-keyed, and a flagged shortage connects straight through to a purchase order without someone bridging the gap between two disconnected systems.
If BOM accuracy or material planning is currently a spreadsheet exercise someone dreads every week, a demo is a reasonable way to see what that same process looks like running natively inside the platform.
FAQ Section
What’s the difference between a single-level and multi-level BOM?
A single-level BOM lists only the direct components of a finished product. A multi-level BOM goes deeper, showing that some of those components are themselves assemblies built from further components, which is how most real manufactured products are actually structured.
Does MRP replace the need for a production schedule?
No, they work together. A master production schedule defines what needs to be built and by when. MRP takes that schedule and works out the material side: what’s needed, in what quantity, and when it has to be ordered to meet it.
Is MRP only useful for large manufacturers?
No. Even a small manufacturer building a modest range of products benefits from accurate netting against stock and time-phased ordering. The complexity that makes spreadsheets unreliable, multi-level BOMs, engineering changes, stock accuracy, shows up at fairly modest scale, not just at large volume.
What happens if BOM data is wrong?
Every calculation downstream inherits the error. Wrong quantities lead to under-ordering or over-ordering materials, inaccurate costing, and schedules built on numbers that don’t reflect what’s actually needed to build the product.
