Dealer and account hierarchy
Head office, branches and delivery points hang under one parent account. Credit limit, payment terms and discount are defined once, and turnover per dealer finally means what it says.
Consider a furniture maker in Kayseri selling through some forty dealers across Turkey. One sofa set, offered in three colours and two fabrics, is scattered across more than thirty stock cards in Netsis, several of them inactive yet still orderable. Some dealers exist twice, once as head office and once as a branch, with a credit limit set on one card and blank on the other. Dimensions sent to Trendyol disagree with those in the ERP, so the courier bills a desi difference every month. Nobody did any of this on purpose; over ten years, different people in different hurries simply opened cards. Master data work untangles that history. It settles which record survives, which ones get folded into it, who is allowed to create new cards and which details a card cannot be saved without. Apply handles the whole job remotely, through secure access to your system or on exported files, and the final say always rests with your own staff.
Not every company has dirt in the same fields. We look first at which errors come back to you as invoices, courier charges or unpaid balances, and prioritise from there.
Head office, branches and delivery points hang under one parent account. Credit limit, payment terms and discount are defined once, and turnover per dealer finally means what it says.
Options like colour, size and fabric become variants of a single parent product. The marketplace listing, the picker on your website and the shelf label in the warehouse all draw on the same logic.
Tax number, tax office and e-Fatura registration status complete and current. Get this wrong and the document is issued under the wrong scenario, and cancelling and reissuing it is tiresome for both sides.
An IBAN change is applied only after confirmation over a second channel you already knew about and approval by two people. A fake our bank details have changed email does not become a payment order.
Barcode, units per carton, weight and desi are mandatory on every stock card. Your shipping integration prints the right label and the end-of-month desi surcharge stops being a surprise. Exporters keep the GTIP code and country of origin on the same card.
The link between every retired code and the code that replaced it is kept. Historic invoices, reports and integrations carry on working after the clean-up.
Guest accounts with no activity for years are set aside in a separate list for review under your KVKK retention and destruction policy. Records tied to bookkeeping stay for the statutory period, and destruction is decided by you and your mali müşavir.
Each stage ends with a deliverable and a sign-off. No record is touched without approval.
A few hundred randomly chosen cards reveal which kinds of errors occur and how often. The real size of the problem becomes visible quickly.
For each card type we document mandatory fields, naming conventions, who may create cards and what counts as a duplicate, then submit it to your team for approval.
Proposed merges are listed in a spreadsheet, the responsible person approves them, and they are applied after a fresh backup. Weeks that fall on month-end close are left untouched.
Mandatory fields and permissions are configured in the ERP, and a short monthly quality report reviews every newly opened card.
Spotting a duplicate is easy; deciding which copy is right is the hard part. A dealer's address may be freshest in the web shop, the tax details correct in the ERP and the contact person up to date in a sales rep's spreadsheet. So for every field we write down which source wins, and merges follow that rule. Without it, a clean-up merely swaps one error for another.
Yes. Changes go in as small batches outside office hours, so invoicing and dispatch never stop. Thanks to the mapping table, merged codes stay traceable on older documents too.
At SME scale, usually not. The built-in mandatory field and permission settings of Logo, Mikro, Netsis, Nebim V3, Business Central or Odoo, together with a regular quality report, are enough. With several ERPs or legal entities, a separate tool may be worth considering.
Yes. The cleaned card in the ERP becomes the source, and listings on Trendyol, Hepsiburada or your own site are updated from it. If your integration tool supports it, updates flow automatically from then on.
We access customer cards because the work requires it, and that access is defined in a data processor agreement. Wherever possible we work on exports with names and contact fields masked.
After the sample audit you get a quote with an estimated range of hours. Our rate is €55 an hour plus VAT, and a fixed price is available once the scope is settled.
Briefly describe the report that never reconciles or the card type that causes the most confusion. A sample audit shows us both how big the problem really is.
We have your enquiry
A reply will reach you by the next working day at the latest. If your message says work has come to a halt, it goes to the top of the pile.
No such city in our list. Try another spelling, or just pick the closest big city: we work entirely over remote connections, so nothing about the service changes from one province to the next.
The only cookies here are the essential ones: they keep the site running and remember the city you picked. Nothing is used for advertising or tracking. See our privacy notice for more.