The starting point
Manufacturers can begin with a bounded production history that connects planned work, components, actual output and exceptions. Production orders and equipment-maintenance jobs describe different processes. Decide which process a proposed evaluator needs, then check the retained evidence and the authority to discuss it.
Build a useful inventory.
Describe categories and connections. Keep actual records in your own systems during the initial fit review.
| Illustrative category | Describe without exporting | First question |
|---|---|---|
| Production orders | Product family; route; component and operation links | Did the route change by plant or period? |
| Actual output | Quantity units; backorder and scrap coverage | Is completed quantity distinct from plan? |
| Quality follow-up | Finding, correction and review references | Does closure have supporting evidence? |
Scroll across to read all three columns.
Let the configured route explain the records.
Odoo’s two-step manufacturing documentation connects a production order with component picking and operations. It also explains that this route has no separate finished-product transfer, although inventory updates. A missing transfer row is therefore not automatically missing production. Ask the system owner which route each warehouse used and which evidence records actual output in the proposed period. The documentation is an example, not a VOID integration.
Bound the confidential process knowledge.
An inventory can describe assembly, rework or inspection categories without revealing recipes, tolerances, customer drawings or machine settings. Flag those dependencies rather than promising that deleting names preserves everything useful. Separate company-created records from subcontractor reports and supplied manuals. If the proposed question depends on a restricted drawing, the owner must resolve that scope before preparing a real sample.
Ask what would change the decision.
Confirm whether a prospective evaluator needs production exceptions, repair reasoning or quality outcomes. A coherent scope can be smaller than the factory archive. VOID starts with metadata and charges no upfront seller referral fee. Conditional receiving-program compensation is disclosed before the business approves a named recipient and exact introduction details. That approval does not release a sample or grant a license.
Hypothetical screening example
Illustration: proceed with one known route.
A fictional assembler retains a year of production orders from one warehouse, with component picks and recorded output. Older plants used undocumented configurations. Its owner describes the one-year route, excludes customer drawings and lists rework as a separate category. The wider archive remains outside the first scope until its meanings can be checked.
Next decision. Proceed to a metadata fit discussion for the defined route; hold the multi-plant history.
Questions before the next step.
Are maintenance work orders the same as production records?
No. A repair history explains equipment interventions; production records explain how goods were made. They need different units and evidence.
Does ERP access establish licensing authority?
It establishes access. The proposed use still needs the business’s rights, confidentiality and disclosure review before a sample.
Source notes
Software documentation describes possible record structures. It does not establish your retained history, rights or buyer acceptance.
Odoo 19.0 — two-step manufacturingOdoo · Checked 2026-10-11A manufacturing order connects components and operations. The two-step route records component picking without a separate finished-product transfer; manufacturing route settings vary by warehouse.