Define a shared order contract covering product identifiers, quantity units, dimensions, finish and project references. Validate incoming data before accepting it as a production instruction. The integration should report ambiguous units or missing specifications to an owner and distinguish a customer revision from a duplicate transmission of the same approved order.
Understand the decision
In a hypothetical dealer feed, one customer sends quantities as packs while another sends pieces. A revised order arrives with the same reference but a changed length and delivery date. Without explicit mapping and version handling, the interface could overstate demand or create an unintended second production commitment for the project.
Work through the requirements
- Map each dealer’s product and quantity conventions.
- Validate required project specifications before acceptance.
- Define revision, cancellation and duplicate handling.
| Record or decision | Why it matters |
|---|---|
| Dealer mapping | Connect codes and units to internal records. |
| Order version | Identify accepted specifications and changes. |
| Import exception | Assign missing or ambiguous information. |
What would a passing test show?
Use these hypothetical cases in a demonstration. Mark the evidence you have reviewed, then download the checklist. Selections stay in this tab.
Watch for this failure
An order feed that imports successfully may still contain the wrong commercial meaning. Test realistic dealer examples, including revisions and mixed units, before allowing imported orders to reserve material or trigger production without a human review.
Continue the evaluation
This example defines what to verify, rather than promising a particular Odoo feature. Keep a record of the demonstrated result, configuration, unresolved gaps and person who accepts it.
Read the wider implementation guideBring your workflow to the conversation.
Discuss requirements for Building products manufacturing in a business needs review. Start with your current systems, the handoff that fails and the result you need to prove.
Sources & scope
The linked product documentation is a starting point for validating your chosen version, edition, apps and hosting. The scenarios and acceptance criteria are editorial planning guidance, not customer case studies or a guarantee of built-in functionality. See how this library is prepared.
Odoo 19: manufacturing product configuration ↗Odoo 19: lot numbers ↗Odoo 19: quality control points ↗Odoo 19: vendor pricelists ↗