SupplyGrid · Glossary Definition

Level Code

A level code in manufacturing inventory planning, commonly called Low-Level Code (LLC), is a numeric field that identifies the lowest BOM level at which a component appears. MRP uses it to sequence requirement explosions, consolidating all dependent demand before netting stock and preventing duplicate planning across assemblies.

On the shop floor, low-level code controls the order in which dependent demand is calculated during an MRP explosion. When a shared raw material or subassembly sits at different depths in multiple product structures, the system assigns its deepest occurrence and waits until all higher-level parents have been exploded. This timing is what makes receiving release timing, raw-material reservation, kitting, picklist generation, and inventory pegging trustworthy: the planner sees the true net requirement only after every source of demand is known. In a discrete manufacturing environment with high variant assemblies, a stale LLC can cause material to be kitted too early or shortages to surface at line side. In warehousing, it also affects putaway and replenishment signals because stock is reserved against the correct demand horizon. Keeping the code recalculated after any engineering BOM change ensures the planning run stays accurate and exception messages remain meaningful.

Operational Failure Matrix
Risk LevelOperational Pitfall Description
⚠️ Warning 1Duplicate demand and phantom shortages: A stale low-level code after a BOM edit lets the same component be planned at the wrong level, generating repeated gross requirements and artificial stockouts. The result is excess expedite messages, duplicate requisitions, or double reservations against different parent orders.
⚠️ Warning 2Late pegging on shared components: When a part appears in multiple assemblies but its level code is not recalculated, MRP nets it before all higher-level demand is known. That creates under-allocation and a late stockout at issue time despite sufficient inventory in the earlier run.
⚠️ Warning 3Inaccurate planning performance and exception noise: If low-level codes are not refreshed after engineering changes, the MRP engine processes items out of sequence, increasing run time and exception chatter. In practice, this bottlenecks planning, delays purchase signal generation, and skews material availability dates.
Technical FAQs
Is level code the same as BOM level?

In MRP usage, yes, it is the lowest BOM level where the item appears, not merely the first level encountered. This deepest occurrence determines the planning sequence.

Why must MRP process a component at its lowest occurrence across all parents?

Because net requirements can only be calculated after every parent structure that can generate demand has been exploded. Deferring to the deepest level consolidates all dependent demand in one pass and avoids duplicate planning.

What happens if two BOM branches use the same part at different depths?

The low-level code is set to the deepest occurrence, and planning is deferred to that level. This ensures all demand is consolidated once and prevents premature or duplicate material requirements.

Software that works like your best tools.

This Glossary is maintained by Ryxen — focused software tools that solve specific operational friction points for Canadian small businesses. No ERP bloat, no per-user pricing, no demo calls.