DataCleaner Pro · FOR DOLIBARR

Find duplicate customers.
Merge them without losing anything.

DataCleaner Pro scans third parties and contacts, scores each pair with an explained reason, shows exactly what a merge will move, then merges in one transaction with an audit trail. It also merges contacts, which Dolibarr itself cannot do.

Dolibarr 20 → 24PHP 7.4 – 8.2Version 1.0.0€129 excl. VATOn Dolistore

DataCleaner Pro — module for Dolibarr
Explained scoresMerge previewContact mergeAudit trail
YOUR DAILY WORKFLOW

What changes once the module is active.

01

Duplicates you can trust

Names, VAT numbers, e-mails, phones and addresses are normalised (legal forms, accents, phone formats) before comparison. Each pair shows its criteria, weights and points; two different VAT numbers dismiss a pair, and the “very likely” level requires a strong identifier.

02

Nothing merged blind

The review screen compares the two cards field by field with the number of invoices, orders, contacts and documents on each side. The merge preview names the recommended master, the field conflicts and the totals after merge. Nothing is ever merged automatically.

03

Contacts and documents kept

Third parties are merged through the core mechanism, after copying the absorbed party’s documents, which the native merge loses on Dolibarr 21 to 24. Contacts, which Dolibarr cannot merge, are relinked with their keys deduplicated, or the merge is blocked if an unknown table references them.

The dashboard — Dolibarr
Actual module interface in Dolibarr · Demonstration data. Click to enlarge.
INSIDE THE MODULE

The dashboard

Data health score, duplicates to review with the very likely count, third parties and contacts in the entity, merges recorded. Module state (tables, version, fingerprints up to date, last scan) and the duplicate table by type and confidence. Buttons: compute fingerprints, run a scan.

Browse all screens →

Know exactly what happens.

WorkflowTriggerResult in Dolibarr
Fingerprints“Compute fingerprints” button, then automatically on each create or updateNormalised fingerprint per third party and contact (name, e-mail, all phones, VAT number, address, postcode, city, country).
Scan“Run a scan” button or the scheduled task (off by default)Candidate pairs blocked in the database, scored criterion by criterion, classed very likely, possible or low confidence.
Review“Review” on a pairField-by-field comparison, linked object counts, score breakdown; decide “Not a duplicate”, “Ignore” or “Prepare merge”.
MergeConfirmation box on the merge previewDocuments copied, core merge for third parties or module merge for contacts, in a transaction, with an audit snapshot written beforehand.
PreventionCreating a third party or contact in DolibarrWarning when the new record looks like an existing one, with “open the existing one” or “create anyway”; optional block on an already used VAT number.
Data healthData quality pageScore across four axes (duplicates, completeness, validity, consistency) and ten findings such as invalid e-mails or missing country.

Before you choose.

Why does the score say 100 % for two records with different names?

Because the criteria are weighted: the same VAT number, phone and e-mail outweigh a name written differently. The review screen shows each criterion with its similarity, weight and points, and the field comparison marks what is equal and what differs.

Does Dolibarr already merge third parties?

Yes, from the third party card. DataCleaner finds the pairs, explains them, previews the result and then calls the core merge. On Dolibarr 21 to 24 the native merge deletes the absorbed party’s document directory before moving it; the module copies the documents first, a setting kept on by default.

And contacts?

Dolibarr has no contact merge at all. The module relinks the known tables (events, categories, document contacts, mailings, notifications…), deduplicates conflicting keys, offers a hook for third-party modules and refuses the merge if a table it does not know references the contact.

Can I run it on a large base?

Candidate pairs are built in the database by blocking keys, in batches, rather than comparing every record with every other. The documented test run on 20,000 third parties computed fingerprints in 15 s and scanned in 47 s with 33 MB of memory.

What is stored and for how long?

Fingerprints, candidate pairs, scan runs and merge audit snapshots, in six module tables. Snapshots hold personal data, so a retention in days is configurable and the purge task removes older ones. Fingerprints and pairs disappear with their source record.

Can the module stop duplicates from being created?

When a user creates a third party or contact that looks like an existing one, a warning offers to open the existing record or to create anyway. An option blocks creation when the VAT number is already used.

NEXT STEP

Get the module on Dolistore.

€129 excl. VAT · one-time purchase · version 1.0.0

Dolistore is the official Dolibarr marketplace: purchase, download and invoicing happen there. You receive the module archive, French and English translations, e-mail support at support@arcchester.com and the updates published on Dolistore.

Price as published on Dolistore on 9 October 2026; the listing shows the current price and conditions. Dolibarr 20 → 24 · PHP 7.4 – 8.2.