Bill of Materials (BOM)
Understand how product structures connect planned quantities, controlled revisions and actual material consumption in regulated manufacturing.

On this page · 12 sections
- 1What a Bill of Materials defines
- 2BOM versus formula, recipe, routing and master record
- 3Single-level, multi-level and shared product structures
- 4BOM data model: definitions, identifiers and material events
- 5Revision control, effectivity and work-order locking
- 6From product definition to execution and human release
- 7Packaging BOMs: pack quantities and label identity
- 8Planning quantities, yield-adjusted costs and where-used queries
- 9Lot traceability: following actual material paths
- 10US regulatory mapping: product records and electronic controls
- 11System ownership, integrations and exception recovery
- 12Failure analysis, implementation checks and useful metrics
How does BOM apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01What a Bill of Materials defines
A bill of materials (BOM) defines the components and quantities needed to make a stated quantity of a product or intermediate. BOM and BoM are common abbreviations; product structure and parts list are related terms whose scope varies by organisation.
The quantity basis matters. Illustrative bases are one housing and two seals per pump, ingredient masses per 100 kg blend batch, or 12 bottles and one carton per case. Each line needs a component identifier, quantity and unit tied to that basis. Use maintained material master data for component identification.
These quantities support purchasing, material requirements planning and costing. Linking the selected BOM version to a production order in a manufacturing execution system gives execution a defined material reference.
Treat the BOM as the planned material definition, not as evidence of what was used. The actual lots and quantities consumed belong in the batch or production record, captured from material-use events at execution.
02BOM versus formula, recipe, routing and master record
These distinctions describe common manufacturing practice, not universal document names. Some systems use formula and recipe interchangeably; compare their fields and controlled scope, not just their titles.
| Term | Typical content | Definition basis | Connection to the BOM |
|---|---|---|---|
| BOM | Required components and quantities | Per unit, assembly or defined batch | Material structure |
| Formula | Quantitative process composition | Mass, volume or proportions | Process-material requirements |
| Recipe | Composition and processing instructions | Batch quantities and conditions | Instructions beyond the material list |
| Routing | Operations, resources and sequence | Operation and resource identifiers | Component lines may reference an operation |
| Master manufacturing record | Controlled reusable instructions and checks | Product and batch size | Component list within a broader instruction set |
| Executed batch record | Actual materials, actions, results and exceptions | One identified batch | Evidence of execution, not just planned requirements |
As a document-control practice, identify the applicable material-definition revision and instruction revision on the production order. Where revisions change independently, check that the selected pair is compatible: a substituted component may need different processing conditions even when its required quantity is unchanged.
For US drug batch records, 21 CFR 211.188(a) requires an accurate reproduction of the appropriate master production or control record, checked for accuracy, dated and signed. Assess that record's content rather than relying on whether software labels its source a BOM, formula or recipe.
03Single-level, multi-level and shared product structures
A single-level BOM lists a parent’s immediate components. A multi-level BOM expands assemblies or blends into their components. Discrete quantities commonly use counts; process quantities commonly use mass or volume. Density relates mass to volume; concentration describes constituent content and needs a stated basis, such as mass fraction.
Engineering, manufacturing and packaging structures are related views, not necessarily identical trees. An assembly may be built in stages, while one bulk blend may feed several pack configurations. Co-products need output relationships: they are products of a transformation, not components consumed beneath the main product.
Shared substructures form a directed graph rather than independent copies. Reject circular dependencies and make traversal limits explicit. If expansion stops at a depth limit, report an incomplete result rather than presenting a partial structure as complete. Quantity traversal is covered in the planning section below.
A phantom groups components for planning, usually without a separate production order or stock balance. A physical intermediate may instead be stored, sampled or transferred before the next operation. Decide whether that intermediate needs its own item and lot identity; flattening purchasing demand should not dictate the execution model. Its storage interval may warrant a hold-time study.
04BOM data model: definitions, identifiers and material events
A useful relational design separates reusable item identity, product definitions and lot-level execution. Govern identifiers through material master data, not description matching. The following model makes component occurrences and authorised outputs explicit so that input and output transactions can follow different validation rules.
| Entity | Key fields | Relationship |
|---|---|---|
| Item | item_id (PK), item_code, base_uom | Reusable material or product identity; one item can have many lots. |
| BOMVersion | bom_version_id (PK), output_item_id (FK) | Owns the component lines for one definition version. |
| BOMLine | bom_line_id (PK), bom_version_id (FK), component_item_id (FK) | Identifies one component occurrence within the definition. |
| WorkOrder | work_order_id (PK), bom_version_id (FK), snapshot_id | Connects production to its selected execution context. |
| ExecutionLine | execution_line_id (PK), work_order_id (FK), bom_line_id (FK), occurrence_path | Distinguishes expanded occurrences of definition lines. |
| OutputDefinition | output_definition_id (PK), work_order_id (FK), output_item_id (FK), authorization_ref | Identifies an authorised output item for the order, including any co-product. |
| Lot | lot_id (PK), item_id (FK), supplier_id, supplier_lot_code | Gives stock an internal identity while retaining supplier provenance. |
| MaterialEvent | event_id (PK), work_order_id (FK), execution_line_id (nullable FK), output_definition_id (nullable FK), lot_id (FK), reference_event_id (nullable FK) | Records a material transaction; event type determines which context links are required. |
PK means primary key; FK means foreign key. Extend BOMVersion with revision, basis_quantity, basis_uom, expected_yield_pct, status, effective_from, effective_to and site_scope. State whether its basis represents charged material or expected usable output. Expected yield is a planning assumption, not measured production. Selection and snapshot governance are covered in the revision-control section.
Extend BOMLine with sequence, quantity, uom, operation_id, critical_flag, tolerance_pct and referenced_subformula_version_id. Sequence orders the list; operation_id connects the requirement to a manufacturing operation. Define the tolerance’s reference quantity explicitly. Make the pair work_order_id and occurrence_path unique: the same definition line may appear through several expanded sub-formula paths.
Keep supplier_lot_code distinct from internal lot_id. A printed supplier code is not necessarily unique across suppliers or items, and multiple internal lots can share the same supplier, item and supplier code. Do not impose uniqueness on that combination without a business justification.
Extend MaterialEvent with event_type, quantity, uom, occurred_at, recorded_at, source_system and source_event_id. Store a positive quantity magnitude and define its inventory and consumption effects by event type. Separate activity time from entry time, and deduplicate imported events within the source’s identifier namespace.
| Event type | Required context | Semantic validation |
|---|---|---|
| Input issue, dispense or consumption | execution_line_id required; output_definition_id null | The line belongs to the order’s selected execution context. The lot’s item matches the component or an authorised alternate, with an approval reference. |
| Output receipt | output_definition_id required; execution_line_id null | The output definition belongs to the order. The lot’s item matches that authorised output, not an input component. |
| Unused-input return | reference_event_id points to the original issue or dispense | Retain that event’s order, execution occurrence, item and lot. Cap returns at its recorded unconsumed balance. |
| Full reversal | reference_event_id points to one original non-reversal event | Retain the target’s input or output context, quantity and unit; negate its effects. Permit only one full reversal of that event. |
Returns therefore inherit input-line context; reversals inherit whichever context their target required. An output reversal keeps the output definition and a null execution line. Record corrections through linked reversal and replacement entries rather than overwriting history. Foreign-key existence alone cannot detect a valid lot attached to the wrong operation or output.
Work order
Identify the batch and the BOM version selected for production.
- Product and batch number
- Planned batch size and unit
- Selected BOM revision
- Production dates
Approved BOM Revision
Check that the retrieved definition matches the work order and was approved for use when production began.
- Revision number
- Approval and effective dates
- Approver
- Batch quantity used as the BOM basis
Component Requirements
Check what each line calls for and open linked sub-formulas where a requirement needs further explanation.
- Material identity
- Required quantity and unit
- Quantity tolerance
- Linked sub-formula revision
- Permitted substitutions
Dispensing and Consumption Records
Compare planned requirements with materials actually charged, including returns and additional charges.
- Material and lot used
- Quantity weighed and unit
- Quantity charged or returned
- Operator and time
- Recorded difference from plan
Lot History
Trace a questioned input back to receipt and forward to the batches and outputs that used it.
- Internal lot number
- Supplier and supplier lot
- Receipt and material disposition
- Consuming batches
- Resulting intermediate and finished lots
Deviation and Correction Records
Challenge unexplained differences and check whether the evidence supports the reviewer's disposition.
- Affected component, lot and batch
- Original entry and corrected entry
- Reason for change
- Investigation and supporting evidence
- Reviewer decision and unresolved actions
05Revision control, effectivity and work-order locking
Revision identifies the definition; approval status tracks its review state; effectivity determines where and when it applies. An approved BOM may still be ineligible for a site, product variant, production date or batch size. Define effectivity rules, including date boundaries, size ranges and the controlling event—for example, scheduled production start. Check for overlapping candidates and gaps within each selection scope.
Use a documented lifecycle, such as draft, review, approval and retirement, retaining status and approval history. Suggested owners are formulation for composition, manufacturing engineering for processes, packaging engineering for packaging, and finance for costing. Quality and other designated approvers review within their remit. These responsibilities are configuration-management recommendations, not a universal workflow.
At the defined work-order locking point, preserve the selected revision, resolved child revisions, authorised output definitions and applicable instructions in an immutable execution snapshot. Pin child versions rather than resolving them again from a mutable “latest” pointer. Retain the applicable unit-conversion versions and rounding rules as well. Record later authorised amendments separately, linked to the original context, with their reason and approval. This preserves both what was initially authorised and what changed during execution.
Before activation, use change control to assess dependent structures, conversions, label identities, purchasing commitments and unreleased work orders. Record affected items, owners and disposition decisions. When a schedule or batch size changes, recheck applicability and document whether the locked definition remains authorised or needs an amendment; do not silently replace it.
06From product definition to execution and human release
A typical handoff starts with the product owner defining the output, batch basis and units. Reviewers check completeness and manufacturability. Planning selects the applicable definition using the controls above, calculates demand and checks capacity. Production records material movements and process results, then submits the batch record for review. Each handoff should identify its owner, acceptance criteria and unresolved exceptions.
Reservation allocates stock to demand; dispensing measures or separates material for an operation; consumption records actual use. Neither reservation nor dispensing alone proves incorporation. Reconcile staged quantities with consumption, unused returns, recorded losses and remaining staged stock, using the event relationships defined above. Output receipt records produced inventory rather than another component movement.
Treat planning readiness, material eligibility and batch disposition as separate decisions, rather than one “ready” flag. BOM approval establishes neither lot eligibility nor batch acceptance. The designated reviewer checks reconciliations, test results and unresolved exceptions against applicable acceptance criteria. A batch release checklist can organise that review. Returning unused material to inventory does not itself authorise reuse.
- DefineSet product, quantity basis, components and operations.
- ReviewCheck structure, conversions, packaging and applicability.
- LockPreserve the work order's selected definition.
- PlanCalculate demand and eligible material availability.
- ExecuteRecord identified lots and actual material events.
- ReconcileResolve differences, returns and missing evidence.
- DispositionSubmit the evidence for human review.
07Packaging BOMs: pack quantities and label identity
A packaging BOM connects bulk product to a filled unit, a saleable unit and a shipping case. In this example, the closed, labeled bottle is the saleable unit. Record containers, closures, labels, inserts and shippers against an explicit basis—per bottle or per case—to support bulk-to-pack traceability. State whether inserts are included rather than leaving their usage ambiguous.
Assume 2,400 saleable bottles, 60 tablets per bottle, 12 bottles per case, one bottle, closure and label per filled unit, one shipper per case, no inserts and no process loss. The plan produces 2,400 ÷ 12 = 200 cases.
| Item | Per case (units) | Planned consumption (units) |
|---|---|---|
| Tablets | 720 | 144,000 |
| Bottles | 12 | 2,400 |
| Closures | 12 | 2,400 |
| Labels | 12 | 2,400 |
| Shippers | 1 | 200 |
If labels are purchased only in packs of 250, ten packs provide 2,500 labels: 100 above planned consumption. Purchasing rounding changes the order quantity, not the packaging BOM’s usage of one label per bottle.
Control artwork revision, language, market and pack configuration as distinct attributes. Select the label item for the intended market and pack before calculating demand: a correct count does not establish correct identity. Use these attributes in label inspection.
08Planning quantities, yield-adjusted costs and where-used queries
Material requirements planning starts with gross component requirements from the applicable BOM. Net these against unreserved eligible stock plus scheduled receipts usable by the need date. Check site, quality status and remaining shelf life: arrival alone does not establish availability.
Quantity traversal across levels
Filter BOM explosion by site, effective date and applicable version; exclude unselected alternatives. For proportional lines, express each requirement per unit of usable parent output, converting charge-based definitions using their stated recovery once. Reconcile units, multiply ratios along each consuming path, then sum contributions and scale to the finished quantity. Deduplicating repeated item IDs loses demand. Calculate fixed-per-batch inputs from the number of batches rather than applying the proportional multiplier.
Worked case 2: charge, recovery and shortage
Assume a 100 kg reference charge contains 50 kg A, 30 kg B and 20 kg C, with 98% mass recovery for each component. The saleable target is 490 kg; no potency or moisture corrections apply. Required charge is 490 kg ÷ 0.98 = 500 kg: five times the reference charge.
| Component | Charge | Price | Material cost |
|---|---|---|---|
| A | 250 kg | USD 4/kg | USD 1,000 |
| B | 150 kg | USD 2/kg | USD 300 |
| C | 100 kg | USD 1/kg | USD 100 |
| Total | 500 kg | — | USD 1,400 |
Expected loss is 10 kg: 500 kg charged = 490 kg saleable + 10 kg lost. Material-only cost is USD 1,400 ÷ 490 kg ≈ USD 2.86/kg. This excludes labour, overhead, packaging, taxes and scrap credits.
For A, assume 80 kg eligible on hand before reservations, 30 kg reserved elsewhere and no scheduled receipts. Available stock is 80 − 30 = 50 kg; net shortage is 250 − 50 = 200 kg. Purchasing-pack rounding is excluded.
Keep component usage, manufacturing recovery and purchasing allowances separate. Recovery adjusts this charge once; do not divide the resulting quantities by 0.98 again. Any additional purchasing allowance needs a distinct, documented basis. Apply purchasing-pack rounding after calculating the net requirement, not at every intermediate multiplication.
Cost bases and reverse queries
Standard material cost uses defined quantities, expected recovery and standard prices. Actual material cost uses recorded consumption and the applicable inventory valuation method, divided by actual saleable output for unit cost. Co-product allocation requires an explicit costing policy; this example assumes one saleable output.
Reverse where-used queries identify parent definitions affected by a component or child-structure change. Preserve the same applicability filters and show the dependency path so an engineer can distinguish direct use from use through an intermediate. Use recorded genealogy, covered next, to investigate actual lot exposure.
09Lot traceability: following actual material paths
Build lot genealogy from the event relationships defined above. Backward tracing follows outputs to consumed inputs; forward tracing follows inputs downstream. Include intermediate transformations, blending, splitting and packaging transfers so the investigation does not stop at the first finished or bulk lot.
Assume W17 and W18 each require 100 kg of component A; all quantities below are actual consumption, with no returns. W17 consumes 60 kg from L1 and 40 kg from L2, producing F17. W18 consumes 25 kg from L2 and 75 kg from L3, producing F18. Each consumes 100 kg; L2 contributes 40 + 25 = 65 kg across these batches. A forward trace identifies F17 and F18 as investigation candidates, not a determined recall scope.
If homogeneously blended F17 is split into P17a and P17b, trace both packaging lots. Bulk-to-pack traceability needs recorded allocations between bulk and packaging outputs. The BOM alone cannot establish how much L2 reached either pack lot. More generally, shared work-order membership establishes association, not precise input allocation among co-products or time-separated outputs. Use finer allocation only where process evidence supports it; otherwise retain the broader candidate set.
Locate the failed relationship
| Symptom | Likely investigation point | Check |
|---|---|---|
| A dispensed lot disappears from genealogy | Execution capture | Determine whether consumption was recorded and linked to the correct occurrence. |
| The supplier’s lot cannot be found internally | Receiving identity mapping | Check the identifier relationships described in the data model. |
| Bulk is traceable but repacked stock is not | Downstream continuity | Find the missing bulk-to-output allocation or repacking event. |
| An alternate item is absent from exposure results | Query logic | Search actual consumed items, not only nominal BOM components. |
None of these symptoms alone proves that the BOM definition is wrong. Test both trace directions using known transactions, including authorised substitutions and corrected events. A mock recall exercise can reveal broken relationships that a successful single-lot lookup would miss.
10US regulatory mapping: product records and electronic controls
Using the record distinctions above, map BOM fields into the applicable controlled product record. This US mapping covers drugs, dietary supplements and covered finished-device operations; assess food, chemicals and other jurisdictions separately. The table separates binding requirements from practical implementation choices.
| Product and record | Binding requirement | Practical BOM connection |
|---|---|---|
| US drugs: master component identity | 21 CFR 211.186(b)(3) requires a complete component list with names or codes sufficiently specific to indicate any special quality characteristic. | Connect component identifiers to those characteristics in material master data. |
| US drugs: master quantities | 21 CFR 211.186(b)(4) requires each component's weight or measure using the same weight system. Reasonable dosage-form quantity variations may be permitted when justified in the master record. | Keep quantity and unit together; a configured tolerance does not itself provide technical justification. |
| US drugs: master instructions | 21 CFR 211.186(b)(9) requires complete manufacturing and control instructions, sampling and testing procedures, specifications, special notations and precautions. | Link the material definition to the instruction content identified above. |
| US drugs: actual batch evidence | 21 CFR 211.188(b)(3)–(4) requires identification of each component or in-process batch used and the weights and measures of components used. | Populate the batch record from actual material-use events. |
| US dietary supplements: formulation and size | 21 CFR 111.205(a) requires preparing and following a written master manufacturing record for each unique formulation manufactured and each batch size. | Connect formulation identity and batch-size context to the master manufacturing record. |
| US dietary supplements: component list | 21 CFR 111.210(b)–(c) requires the master manufacturing record to include a complete list of components to be used and an accurate statement of the weight or measure of each component. | Use the approved BOM revision as the source of that list and its quantities, and keep both under the same change control. |
For drug materials, 21 CFR 211.84(a) requires withholding each lot of components, drug product containers and closures from use until sampled, tested or examined as appropriate and released by the quality control unit. This provides the drug-specific basis for the quarantine gate discussed above.
Devices: current QMSR
FDA's QMSR overview explains that the rule became effective on February 2, 2026 and incorporates ISO 13485:2016 by reference. Use a current QMSR-to-ISO mapping when updating legacy product-record procedures.
For covered finished-device operations, 21 CFR 820.1(a) requires a quality management system appropriate for the manufacturer's specific devices. Map the product structure into that system according to the operations performed.
Electronic records: assess Part 11 applicability
For a manufacturing BOM, assess whether it serves as a record required by an applicable FDA predicate rule and is kept electronically. 21 CFR 11.1(b) states that Part 11 applies to records in electronic form that are created, modified, maintained, archived, retrieved, or transmitted under any records requirements set forth in agency regulations. A digital planning list that no predicate rule requires is not brought into scope merely by being electronic. The provision also covers electronic records submitted to FDA under the FD&C Act and the Public Health Service Act. Document the recordkeeping rule, any applicable exclusion, record format and responsible owner in document control.
11System ownership, integrations and exception recovery
Recommended integration practice: document authoritative owners and conflict rules before designing MES–ERP integration. An illustrative split assigns BOM revisions to product definition, demand to ERP, inventory movements to warehouse management, consumption to execution, and material disposition to quality; actual ownership varies.
Specify stable item, lot, order and BOM-line identifiers; revision and applicability; quantity basis and units; conversion version; source system and event identifier; occurrence and receipt timestamps. Reject name-only matching. Quarantine reused identifiers with conflicting payloads.
- Offline transaction: preserve its original identity and occurrence time; reconcile intervening movements and validate the referenced revision before posting.
- Delayed lot-status update: block affected use pending quality assessment, including earlier consumption and downstream batches where later findings change acceptability.
- Duplicate consumption: deduplicate by source system and event identifier; commit the inventory effect and deduplication record together so concurrent retries cannot double-post.
- Rejected revision: retain the last accepted definition for reference, flag affected orders, and confirm an authorized, applicable revision before restarting dependent execution.
Quarantine failed messages and preserve payloads. Reconcile source and destination before replay; retries must not create additional business effects. Correct posted material consumption using linked reversals or correction events, not silent overwrites. An acknowledgement proves only its agreed receipt or processing stage. Close recovery by comparing applied lot quantities, order links, genealogy links and movement balances.
12Failure analysis, implementation checks and useful metrics
Run these suggested local checks in a controlled test environment, with expected results agreed before execution. They are not regulatory thresholds. Investigate discrepancies through deviation handling.
| Symptom | Possible mechanism | Acceptance test and expected result |
|---|---|---|
| Wrong quantities | Basis or conversion error | Independently calculate component quantities from the declared batch basis, units and conversion factors. System quantities match those results after the specified rounding. |
| Obsolete packaging | Applicability error | Create new test orders immediately before, at and after each effective-date boundary. Every order selects the expected revision under the documented effectivity rule. |
| Circular dependency | Ancestor reference | Direct and indirect ancestor loops are rejected; valid shared substructures are accepted. |
| Missing consumption | Unposted events | Every independently evidenced lot-controlled consumption event has a genealogy link to the correct input lot and resulting batch, with matching quantity and unit. |
| Doubled consumption | Interface replay | Replay the same event ID. Only one posting exists; inventory and genealogy quantities remain unchanged after replay. |
| Unapproved substitution | Alternate-control bypass | Challenge ingredient verification with an unauthorised alternate. Its use is blocked and no consumption is posted; an otherwise eligible authorised alternate passes. |
Configuration go-live checks
Name owners in the configuration specification. Retrieve a test order's execution snapshot and confirm it matches the BOM version actually used. Complete a trace drill against a predetermined set of affected batches. After recovery, the same versions, consumption links and trace results remain retrievable.
Monthly metrics
Fix site/product scope, reporting cutoff and cohort: orders started that month. Report ratios; zero denominators are not applicable.
- Execution-snapshot coverage = cohort orders with retrievable snapshots of the BOM version actually used ÷ all cohort orders.
- Genealogy coverage = independently evidenced lot-controlled consumption events linked to input lots and resulting batches ÷ all such events for cohort orders. Include events missing from genealogy.
- BOM-caused shortage rate = cohort orders with shortages attributed by investigation to an applicable BOM error ÷ all cohort orders. Count each order once; exclude shortages caused solely by supplier or inventory failures.
Frequently asked questions
Q.Can one BOM support several pack sizes or selling markets without duplicating every component?+
Yes. A practical design separates the common bulk product from pack-specific structures containing containers, closures, labels and case quantities. Each selling configuration references the shared bulk item and selects a controlled packaging revision. Keep market eligibility, artwork revision and effective dates explicit rather than hiding them in item descriptions. Use material master data to distinguish configurations and bulk-to-pack traceability to connect their finished lots. If composition changes between markets, treat that as a formulation difference, not merely a packaging option.
Q.How should potency or moisture adjustments affect a planned component quantity?+
Keep the nominal requirement separate from the lot-specific calculated charge. Assuming a target of 9.5 kg active and an as-is assay of 95% by mass, the charge is 9.5 ÷ 0.95 = 10 kg. For a dry-basis assay, first establish the corresponding as-is concentration using the applicable moisture result; do not correct twice. Record the assay basis, calculation and any balancing adjustment. Distinguish an assay-adjusted charge from an intentional overage, and define the counter-balance excipient rule where applicable.
Q.Can an approved alternate material be used without revising the parent BOM?+
Potentially, if the controlled configuration already authorizes that alternate for the relevant product, operation and market. Supplier approval alone does not establish interchangeability. Define substitution scope, quantity conversion, specification compatibility and any additional checks before use. Record the actual alternate item and lot against the executed order. If the proposed substitution falls outside the existing authorization, route it through change control rather than editing a consumption line informally. Keep supplier risk management separate from approval of the product-specific substitution.
Q.When should rework have its own item identity or formula version?+
Distinguish rework from general material recovery. For devices within the U.S. QMSR's scope, 21 CFR 820.3(b) defines rework as action on nonconforming product to fulfill specified requirements in the medical device file before release for distribution. As data-model choices, use a separate item when material needs distinct specifications, storage conditions, permitted uses or valuation; use a controlled formula version for repeatable changes to inputs or instructions. A one-off disposition should retain its order-specific instructions. These identifiers do not authorize rework. Preserve originating lots, actual additions and nonconforming history in material genealogy.
Q.What should happen to an open work order when its selected BOM revision becomes obsolete?+
Do not silently replace its selected revision. Assess why the revision became obsolete, whether execution has started, and whether the change affects safety, specifications or packaging suitability. The disposition may be to continue under documented authorization, hold the order, or cancel and reissue it against the replacement revision. Preserve the original selection and decision history. Use recipe effective dating to control future selection and a recipe supersession log to explain the transition; neither alone resolves work already in progress.
Q.How can a shared premix be costed without double-counting ingredients or losing lot genealogy?+
Choose one costing boundary. If the parent consumes a stocked premix, its cost includes the premix's rolled-up ingredient and conversion costs; do not add those ingredients again as separate parent costs. Assuming no losses or other costs, 20 kg of premix valued at $6/kg contributes $120 to the parent batch. Retain the premix production record and link its consumed lots to each downstream batch. A planning BOM explosion can show underlying demand without creating duplicate inventory consumption transactions.
Q.Can a spreadsheet support a controlled BOM process, and where does it become difficult to manage?+
A spreadsheet can support a small, stable BOM process when ownership, revision approval, access, calculation checks and retained execution copies are deliberately controlled. Those controls alone do not establish suitability for a particular regulated record. Difficulty grows with concurrent editing, shared subassemblies, market variants and lot-specific adjustments. A saved workbook does not by itself show which revision an order used or who authorized a substitution. Evaluate whether document control can reliably preserve those relationships. Consider migration when maintaining cross-file consistency and reconstructing decisions becomes difficult to sustain.
Q.Which records should a manufacturer request from a contract packer to reconcile material use and finished lots?+
Agree the record package before packing begins. Request bulk lot receipts, packaging item and lot identities, artwork revisions, quantities issued and returned, rejects, destruction records, finished quantities, samples and remaining stock. Include executed packing instructions, line-clearance results, deviations and the mapping from bulk lots to finished lots. Reconcile each material in a consistent unit and investigate unexplained differences rather than assigning them automatically to scrap. Define these deliverables and review responsibilities within contract manufacturer management, including access to supporting records.
Primary sources
- 21 CFR 211.186 — Master production and control records
- 21 CFR 211.84 — Testing and approval or rejection of components
- 21 CFR 211.188 — Batch production and control records
- 21 CFR 111.205 — Dietary supplements: master manufacturing record requirement
- 21 CFR 820.1 — QMSR scope
- 21 CFR 820.3 — QMSR definitions
- 21 CFR 11.1 — Part 11 scope
- FDA: Quality Management System Regulation (QMSR) overview
Explore this topic
BOM sits inside 2 overlapping topic clusters in our glossary. Every neighbour is one click away.
Where each shop-floor system fits and what it owns vs the ERP above it.
Material requirements planning, BOM explosion, net requirements, scheduling and demand signals that drive what the floor makes next.
Want to see how BOM could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
