Record the installed component and its source separately from the originally proposed part. Review technical suitability through the responsible process and commercial changes through the agreed customer decision. If the asset returns with a related fault, link the new investigation to the earlier repair without automatically classifying every cost as warranty or new revenue.
Understand the decision
A delayed component may lead to an alternative supplier or a refurbished replacement. The workshop also needs to distinguish unused stock, removed components and customer-owned parts. Accurate repair history depends on recording what was actually fitted and which unresolved condition remains after the intervention.
Work through the requirements
- Record actual installed and removed parts.
- Review substitution and charging decisions.
- Link return investigations to previous work.
| Record or decision | Why it matters |
|---|---|
| Component record | Shows what was fitted to the asset. |
| Substitution approval | Preserves technical and commercial decision references. |
| Return investigation | Connects the repeat fault to repair history. |
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
A warranty checkbox cannot determine contractual coverage or the cause of a repeated fault. Preserve the evidence and responsible decision before adjusting charges, while keeping the actual workshop effort visible for operational and cost 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 Equipment repair businesses 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: processing repair orders ↗Odoo 19: helpdesk after-sales workflows ↗Odoo 19: sales quotations and invoicing methods ↗