Measuring the present state
We export customers, suppliers and articles, then count: likely duplicates, empty mandatory fields, spelling variants of one name, inconsistent units of measure.
Service · Data and analytics
Master data management
A report is never better than the records feeding it. In a trading company, after a few years, the same wholesaler exists four times in the ERP, one article carries two codes because it once arrived by the box and once by the unit, and the online shop creates a fresh customer for every guest order. We put all of that back in order, then we set the rules that stop the mess from returning six months later.
Identities
checked against public registers
Duplicates
found and then merged
Owner
named for every register
Quality
one report every month
Where this service reaches
The software matters least here. What matters is that one person owns each register and that the rules are written plainly enough for a new joiner to follow without asking.
Checking business partners
Company identities are compared with public business registers and VAT numbers with the European validation service. A correct record matters all the more now that invoices leave in electronic form.
Articles and codes
Consistent naming, barcodes, units and packaging factors. We link your internal codes to the listings published on marketplaces, often through a feed tool such as Lengow or Shoppingfeed.
Merging duplicates
Redundant records are brought together so that accounting documents, payments and sales history afterwards point at the right entry, with no orphaned lines left behind.
Creation rules
How a name and an address are written, which fields are mandatory, and above all who is allowed to create a customer or an article in the system.
Private customers and GDPR
We identify consumer accounts inactive beyond your retention period so you can delete or anonymise them in agreement with your DPO.
The way an engagement runs
The assessment is short. The clean-up is deliberately spread over time so that neither current sales nor the monthly accounting close are disturbed.
01
Assessment
Through secure remote access, or from an export, we count the errors and show which of them distort your reports the most.
02
Rules
Conventions are written with the people who create records every day, in sales and in the warehouse, not only with managers.
03
Clean-up
Active customers and selling articles first, the archive last. Every merge is approved by the owner of the register concerned.
04
Keeping it up
Checks at the moment of creation and a monthly quality report stop standards from slipping as soon as attention moves elsewhere.
The most expensive duplicate hides among your articles, not your customers. When one product carries two codes, stock splits between them, and the marketplace listing attached to the first shows nothing available while a full pallet waits in the warehouse. That error costs sales every day and appears in no financial statement: nobody looks for it, because nothing reports what was never sold.
Questions and answers
From haste and from integrations, almost every time. A salesperson cannot find the customer because the search used an abbreviated name, so a new record appears. The online shop pushes every guest order across as a new partner. Searching by company identifier, pulling details automatically from public sources and configuring the integration properly removes most of the problem.
Finding the suspicious pairs can, and it saves a great deal of time. The merge itself deserves human approval. Two companies with almost identical names are sometimes a parent and its subsidiary, with separate tax identities, and joining them mixes payments that are very hard to separate afterwards.
Rarely below two hundred and fifty staff. Written rules, entry validation inside Sage, Cegid, EBP or Odoo and a regular quality report handle the bulk of it. A dedicated tool earns its keep once several applications must share the same records in real time and none of them can act as the single reference.
That is almost always the most neglected part. We show how many accounts have gone unused for years, and you decide with your DPO what gets deleted or anonymised. Accounting documents are left alone: they fall under a retention duty of their own, separate from managing a customer list.
Put your records back in order
Tell us which reports fail to add up and which lists look cluttered. We start by measuring how large the problem really is.
When we are around
Weekdays, 8:00 to 18:00 CET; answers land inside one working day
Weekdays, 8:00 to 18:00 CET; answers land inside one working day
Talking it through
A call on Teams or Google Meet, whenever writing is not enough
A call on Teams or Google Meet, whenever writing is not enough
Message received
An answer follows inside one working day. Report an outage that is stopping people working and it moves ahead of everything else.
- Anything unclear gets asked. Where a figure needs detail we do not have, expect an e-mail or an offer of a short call on Teams or Google Meet.
- A proposal follows. What is covered, the figure in euros excluding VAT, and a start date that will hold. Nothing hides beneath an asterisk.
- Then it is your call. The proposal sits in your inbox for as long as you need. Query any line of it, and decide once you are satisfied.