Treat a replacement fabric lot as a controlled production decision when shade consistency matters. Identify affected garments, remaining usable fabric and the customer’s acceptance criteria before mixing material. The plan should show which bundles may continue, which require a new allocation and whether a separate sample or customer approval is needed.
Understand the decision
In a sample order, one roll is shorter than its supplier label indicates. Another delivery has enough fabric but a visibly different shade. Combining the rolls might meet total quantity while producing mismatched panels or inconsistent garments within a customer’s planned assortment for a single store launch.
Work through the requirements
- Measure the remaining approved fabric by lot.
- Identify affected cut bundles and garment variants.
- Approve a shade allocation or revised delivery plan.
| Record or decision | Why it matters |
|---|---|
| Fabric lot record | Identify material and shade grouping. |
| Bundle allocation | Connect cut work with its material. |
| Exception approval | Document the accepted replacement decision. |
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
Fabric with the same purchasing code may not be interchangeable for a particular order. A shortage workflow should preserve the reason for accepting a substitute, rather than silently treating all received material as equivalent available stock.
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 ↗