Skip to content
digitapulia.com
Companies in two countries

Head office–subsidiary data sync

We copy every new price list by hand into the subsidiary's ERP.
What we do
Items, price lists, customers and stock move from one ERP to the other, with written rules on which side owns each piece of data.
How we do it
First we list with you the data that travels: items, price lists, customers and stock. For each one we write a rule: which system owns it, when it passes to the other, and what happens if both change it at once. Then we connect the two ERPs according to those rules, test on part of the data and, once it matches, extend the sync to all of it.
What you receive
The sync up and running, a log of the changes, and the rules in writing.
What changes for you
No one copies a price list or a new customer by hand from one system to the other. When a piece of data does not match, the change log says from which system and when it was changed, and the written rules say which one stands.
What we need from you
Access to both ERPs, one person from IT and one from sales management to decide with us which side owns each piece of data, and a recent extract of the price list, the customers and the stock.
Who it is for
IT and sales management
How you buy it
A project, plus a recurring fee.

Example use cases

These are examples: they do not describe a real client.

  • A fashion company with a subsidiary in Spain

    The situation

    Every season head office prepares the new price list. The Spanish subsidiary receives it in a spreadsheet and someone copies it by hand into its system, item by item. Sometimes a price is copied wrong and no one notices until the invoice has gone out; meanwhile, new items are slow to appear at the subsidiary.

    What we do

    We write the rules with sales management: head office owns the items and the list prices; the subsidiary, its customers. We connect the two systems: the price list is written once in Italy and reaches Spain by itself, together with the new items. The change log says what changed, when and from which side.

  • A component maker with a subsidiary in Argentina

    The situation

    The Argentine subsidiary sells parts held in the Italian warehouse, but cannot see head office's stock. Before promising a delivery, the sales rep emails Italy and waits for the answer; sometimes they promise anyway, and the part is gone. The customers the subsidiary creates do not reach Italy either.

    What we do

    Italy's stock reaches the subsidiary's system by itself, as often as the written rule says, and the sales rep sees it before promising. The subsidiary's new customers reach head office. The rules say which side owns each piece of data: head office its items and stock, the subsidiary its customers.

Frequently asked questions

What if both companies change the same piece of data?

The rules written before anything is connected say so: for each piece of data, which system owns it. The change log keeps both changes, so you can see what happened.

Does it work if the two ERPs are different?

Yes, as long as each system lets its data be read and written: we check that at the start, before scope and price are put in writing. Each system stays as it is.

Can we start with the price lists alone?

Yes. We start with what costs you most today, as in all our work, and the other data can be added in later stages, if you so decide.