Start with assets physically in custody, their customer ownership and the current decision or repair stage. Reconcile parts allocated to each job, approved estimates and unbilled work separately from customer balances. Preserve serial and source references so historical repairs remain traceable without creating duplicate assets or fresh obligations for completed jobs.
Understand the decision
A workshop may hold equipment awaiting customer approval, completed units awaiting collection and dismantled units awaiting components. A customer balance alone cannot describe those responsibilities. Perform a physical-to-record check at cutover and document any unit whose owner, condition or next action cannot yet be established.
Work through the requirements
- Count customer assets physically in custody.
- Match parts and approvals to jobs.
- Reconcile unbilled work and customer balances.
| Record or decision | Why it matters |
|---|---|
| Custody reconciliation | Connects physical assets to responsible customers. |
| Repair opening sheet | States stage, approval and remaining work. |
| Parts allocation map | Shows job-specific component commitments. |
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
Migrating only open invoices overlooks customer equipment still sitting in the workshop. Reconcile physical custody with operational and financial records, and assign every unmatched unit an owner before the new system becomes authoritative.
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 ↗