Every Odoo database accumulates duplicate contacts. A salesperson types a lead that already exists, a support agent creates a "new" customer who is really an old one under a different spelling, and an import drops in the same company twice. Odoo core does almost nothing to stop this at the point of entry: res.partner has no meaningful uniqueness constraint on email, phone, or VAT, and the standard UI only surfaces a soft name-based suggestion on some flows. The result is fragmented customer history, invoices and sales orders scattered across twin records, broken deduplication in mailings, and hours of manual merging after the damage is done.

This is a productized service, not an off-the-shelf download. ECOSIRE builds a Duplicate Contact Details Alert module tailored to your matching policy and installs it into your Odoo 17.0, 18.0, or 19.0 database. Technically, we add an @api.onchange layer and server-side @api.constrains guards on res.partner so a duplicate is caught both interactively (a warning banner as the user types) and defensively (blocked or flagged on save, including via the XML-RPC/JSON-RPC API and imports). Matching runs over the fields you choose — email, phone, mobile, vat, normalized name, or a composite key — with configurable normalization (case-folding, whitespace and punctuation stripping, E.164 phone normalization, domain-only email comparison). Detected candidates are shown inline in the form view (OWL/QWeb) with a one-click jump to the existing partner, and every near-miss can be logged for later review.

Because it is built for you, the behavior is a policy decision, not a fixed opinion. We can make the alert advisory (warn but allow), enforcing (ValidationError that blocks the save), or role-differentiated via ir.model.access.csv and record rules — for example, agents get a hard block while data-quality managers can override with a logged reason. We scope company-level behavior explicitly: in multi-company databases the match can be tenant-isolated or shared, and we respect company_id and record-rule visibility so the check never leaks contacts across companies the user cannot see. Optional extras include a scheduled ir.cron sweep that reports existing duplicates already in the database, a QWeb report of duplicate clusters, and an automated action to tag suspected twins.

Delivery is build-to-order. After a short scoping call we confirm the exact fields, normalization rules, enforcement mode, and Odoo edition (Community vs Enterprise), then build on a staging copy of your database, run UAT with your team, and deploy with a rollback plan. Typical delivery is 2-4 weeks from confirmed scope. You receive the full module source in a git repository — __manifest__.py, models, views, security, and tests — so you are never locked to us. Pricing starts from $249 (indicative, single-company base scope); additional matching fields, multi-company isolation, custom normalization for localized phone/VAT formats, existing-data cleanup, and cross-model checks (e.g. leads or vendors) increase the quoted scope.