Build a stable property reference before merging customer contacts or importing past jobs. Keep billing entities, access contacts and service locations separate, then map open work and unbilled charges to the correct property. Reconcile active obligations and customer balances using the same cutover date, with ambiguous addresses reviewed rather than automatically merged.
Understand the decision
Apartment buildings can contain repeated unit labels, similarly named managers and invoices issued to different ownership entities over time. Historical contact changes should not detach a property's service history. The target structure must let staff find the right unit without exposing unrelated customers' records.
Work through the requirements
- Normalize building and unit references.
- Map contacts by their actual roles.
- Reconcile open jobs and unpaid invoices.
| Record or decision | Why it matters |
|---|---|
| Property cross-reference | Preserves building and unit identity. |
| Contact-role mapping | Separates access, approval and billing contacts. |
| Opening-work list | Identifies unfinished and unbilled obligations. |
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
Merging records because names or street addresses look similar can transfer obligations to the wrong customer. Review active properties individually and keep the source identity available when staff investigate a historical charge.
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 Plumbing contractors 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: field service materials and warehouse configuration ↗Odoo 19: sales quotations and invoicing methods ↗Odoo 19: helpdesk after-sales workflows ↗