THE SHORT ANSWER

Evaluate Odoo manufacturing by tracing a representative product from demand through materials, production, completion and delivery. Confirm the quantities, responsibilities and exceptions at each stage before selecting a configuration. The most useful demonstration uses your production logic and a deliberately imperfect scenario.

Describe what the factory actually makes

Begin with a few representative product families rather than the entire catalogue. Identify whether work follows a repeatable standard, customer-specific design or a mixture. Record components, units, expected quantities, production stages and the point at which a product is considered complete.

Odoo's manufacturing documentation describes product configuration using bills of materials and, when the relevant setting is enabled, operations associated with work centres. Those building blocks still need to be matched to the business's actual production rules and the selected software setup.

Prepare reliable production master data

Choose an owner for component identifiers, units, bills of materials and revision decisions. Separate a product change from an informal shop-floor substitution. If the same material appears under several names, resolve the identity problem before expecting planning or costing reports to explain it.

Include data that makes exceptions visible: supplier lead-time assumptions, minimum purchase quantities, expected scrap and the way partially completed work is tracked. Use values the team can justify and review rather than making a demonstration look efficient with idealized inputs.

Map the decisions between departments

Ask when sales may promise a delivery date, who may release production and how purchasing learns about a shortage. Agree what happens when a component arrives late or a quality issue prevents completion. A connected system cannot resolve an unanswered ownership question on its own.

  • Who approves a substitute component?
  • When is a production revision effective?
  • How is unfinished work identified at a reporting cutoff?
  • Who can adjust consumption or completed quantities?
  • What evidence is required before goods move to dispatch?

An illustrative acceptance test

Prepare a sample production order for ten finished units using an approved material list. Make one component short and require a documented decision before proceeding. Record the actual materials used, any rejected quantity and the usable output, following the configured workflow under evaluation.

The test passes when the process owner can reconcile starting materials, consumption, remaining stock and completed goods. If lot or serial tracking is required, also demonstrate the expected trace from an affected component to the relevant output. Treat this as a requirement to verify, not an assumed capability in every setup.

Avoid a demonstration that hides difficult work

A clean make-to-order example may miss the conditions that dominate daily operations. Include rework, changed demand, partial production and a late supplier in the evaluation. Confirm whether each desired behaviour is standard, configuration, an additional app or custom work.

A common pitfall is importing a large product catalogue before agreeing on the production model. Pilot a representative family, let operators use the intended devices and collect discrepancies. Expand when the records, physical process and reporting tell a consistent story.

PUT THIS INTO PRACTICE

Apply this to your business.

Review your workflows, current systems and first-release requirements.

Request a business needs review

Common questions

What should a manufacturer bring to an Odoo discovery session?+

Bring representative products, bills of materials, production documents, exception examples and the reports used for operational decisions. Include production, purchasing, warehouse and finance owners so assumptions can be resolved together.

Can a successful demonstration prove the whole factory is ready?+

No. It validates the tested scenario. Build a coverage list of product families, production variations, equipment, permissions and exceptions, then agree which tests are required for the first release.

Sources & further reading

Product capabilities depend on the Odoo version, edition, subscription and configuration. Source documentation supports product facts; project checklists and scenarios are editorial guidance. Confirm current details before purchase.

Odoo 19 documentation: manufacturing product configuration ↗
KEEP EXPLORINGOdoo implementation in Canada: phases, roles and timelineOdoo customization: decide what is worth changingOdoo for distribution: make stock and commitments agree