A factory may have a lengthy item file while the implementation team still cannot determine the components needed for a particular output quantity. Material names do not explain whether a quantity applies to one unit or a batch, or which product version uses it. Make those meanings explainable and reviewable before entering ERP data.
The task is not converting every factory document at once. Start with a limited product family reviewed by production, inventory and the data approver. Prepare a representative sample so the implementer understands what to configure and what needs cleanup or a decision before expansion.
One product reveals many questions
Imagine a fictional workshop assembling a desk file holder from one ready-made base, two dividers and four fasteners. These are teaching quantities describing data, not design or manufacturing instructions for a real product. The workshop offers two colors, with one component potentially changing by color while the remaining parts stay the same.
Identify the product code, unit and differences between variants. State whether the bill of materials describes one holder or a defined batch. Where materials are bought in packs but consumed individually, prepare approved units and conversions. Do not leave the implementer to assume “box” means the same quantity for every item.
A pack of four connected sheets
| Sheet | Prepare | Review |
|---|---|---|
| Product card | Code, description, unit, variants and usage status. | Do codes identify the intended products? |
| Bill of materials | Product, base output quantity, components, quantities and units. | Is component quantity understood per output quantity? |
| Operations route | Operations, sequence, resource or work center and time definition. | Is time per batch or unit, and what is its source? |
| Version and approval | Version, effective date, reviewer and change owner. | Which version does the production-order test use? |
Connect sheets with identifiers rather than similar names. Mark unresolved fields and assign completion owners. An unknown value should not become zero simply because an import file expects a number. Ask the implementer for an appropriate way to test scope without concealing missing information.
Separate components from work steps
A bill of materials describes required components and quantities; an operations route describes work and resources. Odoo 19 documentation presents these elements with component, operation and work-center settings. This helps organize information but does not mean filling fields produces a correct operating plan.
In the example, assembly, inspection and packing can be described from actual workshop practice, including what each records. If timing is required, distinguish approved estimates from actual measurements and specify whether setup or waiting is included. Do not invent numbers to make a planning screen look complete. State the sample's limits.
Agree what waste and substitution mean
You may need planned quantities, actual consumption and unusable quantities recorded separately. Ask the process owner how they differ, who approves variance reasons and how the selected solution represents them. This article supplies neither a standard waste percentage nor an industrial costing method; those need organizational data and appropriate specialists.
If substitute components are permitted, do not leave them only in free-text descriptions. Define when substitution is allowed, who approves it and how it affects the version or order. Ask what standard functionality covers and what needs manual procedure, configuration or development rather than assuming every substitution operates automatically.
Versioning preserves the test's meaning
Microsoft Dynamics documentation explains that BOM version validity can relate to product, period, quantity and site, with approval and activation concepts. Those product settings are not universal ERP requirements. They remind the buyer to identify which version belongs to which case.
If the fastener count changes in the example, the team should know which order tested the old version and which uses the new one. Request a review method before applying changes and an explanation of effects on existing orders under supported capabilities and approved policy. An external file change without an updated reference makes comparison ambiguous.
A readiness test before entering the rest of the factory
Prepare a test order with a known output quantity, then review components, units, the correct variant, operations and version. Include missing data and an approved different component, and inspect what the user sees. The process owner should review outcomes before large imports or extensive customization intended to compensate for unresolved data.
For broader scope, read the manufacturing ERP guide; for migration evidence, read the migration reconciliation report. When requesting manufacturing ERP implementation from Nextwave, send the four sheets and sample so discovery begins with a product that can be understood and checked.
Data organization sources
The Odoo 19 bill of materials documentation source and Microsoft BOM and version guide were opened on 3 November 2026. They support the stated concepts; the example is neither engineering advice nor evidence of results for a client factory.
