Assign technical design ownership separately from the ownership of sellable product identifiers. Agree how approved styles, sizes, colours and revisions move between design tools, Odoo and sales channels. The integration should preserve stable identifiers while making an approved construction change visible without accidentally creating duplicate products or rewriting historical order specifications.
Understand the decision
In a hypothetical workflow, a designer updates pocket construction in a technical pack while the online store changes a colour’s display name. Both changes arrive during an active production run. The business needs to distinguish a marketing label edit from a manufacturing revision with material or assembly consequences.
Work through the requirements
- Name the owner of each product field.
- Map stable variants independently of display names.
- Require approval before manufacturing revisions become active.
| Record or decision | Why it matters |
|---|---|
| Field ownership map | Assign design and commerce responsibilities. |
| Variant mapping | Connect stable identifiers across systems. |
| Revision event | Record approved construction changes. |
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
Using a visible product name as the integration key makes ordinary merchandising edits risky. Preserve stable identifiers and define effective revisions, especially when old and new construction versions must coexist during a transition between production runs.
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 Apparel 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 ↗