Customers and trading partners
Registered office, outlets and delivery points sit under one partner with one payment term and one credit limit. Sales per partner then reflect that customer's real business rather than three fragments of it.
Consider a baby-gear webshop based in Celje that also sells wholesale. A single pushchair offered in three colours appears in Metakocka as nine unrelated items, and two of the inactive ones still show up on Ceneje.si. A retailer from Maribor is on file twice, with two different payment terms, because sales keyed it in once and accounts a second time. A third of the catalogue has no weight or dimensions, so parcel locker labels keep needing manual correction. None of it was deliberate; ten people have been adding entries for five years, each under their own deadline. Master data management sorts the tangle out. Together we choose the entry that stays, map the others onto it, agree who may create a new customer or product, and define which fields can never be left blank. We work remotely, through secured access to your software or on exported files. Your team approves every merge before anything changes.
We never try to fix everything in one go. The first job is finding the error that costs you most, and that is where the work begins.
Registered office, outlets and delivery points sit under one partner with one payment term and one credit limit. Sales per partner then reflect that customer's real business rather than three fragments of it.
Colours, sizes and editions turn into variants of a single product. Your webshop, Ceneje.si and the shelf label are all fed from one place.
Full company name, address and VAT identification number must be correct, otherwise the recipient rejects an eSLOG 2.0 e-invoice or returns it for correction. We verify them and tighten data entry so the problem stays fixed.
A new IBAN is only recorded once it has been confirmed through a separate channel you already trust and signed off by two staff. A fake “our bank has changed” message cannot quietly turn into a payment.
Every item must carry a barcode, weight, dimensions and pack quantity. Labels for Pošta Slovenije, GLS or DPD print correctly, and export items also hold the commodity code and origin.
Each retired code keeps a pointer to its replacement, so historic invoices, reports and integrations carry on working once the tidy-up is finished.
Inactive webshop accounts are treated according to your retention rules and GDPR. Anything linked to bookkeeping records is held for as long as the law demands; whether to erase is for you and your accountant to decide.
Every phase finishes with an output for you to approve. Nothing changes in the system until you do.
A random sample of several hundred entries shows which mistakes appear and how frequently, giving you a quick sense of scale.
We name a responsible person for each list and write down required fields, naming conventions and who is allowed to add entries.
Merge proposals come to you as a spreadsheet, the owner ticks them off, and we apply them after taking a fresh backup. We stay clear of month-end.
Required fields and user rights are configured in your business software, and a brief monthly report lists any new entries with faults.
Without an owner, records decay within six months. Cleaning is a one-off job; keeping order is not. If nobody is responsible for the customer list, a few months later it will be full of duplicates again, because someone in a rush created a new customer instead of searching for the existing one. So every project names a person who approves new records and receives the monthly quality report. It is not a new job, just a few minutes a week.
For each field we agree in advance which source wins: the delivery address might belong to sales, the payment term to accounts. Where no rule exists yet we propose one, and the list owner on your side makes the call. After that it applies to every merge alike.
Not necessarily. Sizing the problem and preparing merge proposals can be done on exported files, with your colleague or system administrator entering the changes. Direct access makes things faster, but the choice is yours.
It depends on the number of entries and on how quickly your team approves proposals. With a few thousand products and customers it is typically a few weeks of work spread over several rounds; you get a firmer estimate after the sizing step.
We see customer entries because the work requires it, and that is covered by a data processing agreement. Wherever possible we use exports in which names and contact details are masked.
After sizing the problem you receive an estimate of hours. Our rate is €50 per hour plus VAT, and a fixed price is possible once the scope is clear. Small and mid-sized firms rarely need dedicated master data software, so licence costs usually do not arise.
Tell us briefly which report never reconciles and which lists cause the most confusion. Our first step is to size the problem with you.
Enquiry received
An engineer will write back no later than the following working day. Faults that leave your staff unable to work are always looked at first.
No town by that name here. Check the letters, or settle for the nearest larger place. Our engineers work only over the internet, so Kočevje and Koper get precisely the same treatment.