# Decide master data ownership before you connect systems

> Most integration conflicts are ownership conflicts. A short method for assigning the system of record for customers, products, prices and stock.

Source: https://itnetsolution.com/resources/insights/master-data-ownership-before-integration

Enterprise Integration

9 July 2026

5 min read

## Decide master data ownership before you connect systems

Most integration conflicts are ownership conflicts. A short method for assigning the system of record for customers, products, prices and stock before the first connector is built.

By IT NET Solution

Two systems both claim to hold the customer's address. Both are updated by people doing their job correctly. Synchronising them in both directions produces a loop of overwrites that nobody can explain a week later.

The fix is not a tool. It is a decision: for each domain of data, one system is authoritative and others hold a copy. Copies may be enriched locally, but never overrule the source.

### A workable method

- 01 – List the domains, not the fields – Customer, product, price, stock, order and invoice. Field-level debates are easier once the domain owner is settled.
- 02 – Choose the owner by process – The owner is the system where the data is created and corrected as part of daily work — not the system with the nicest interface.
- 03 – Define what copies are allowed to change – Local additions are fine; local edits to authoritative fields need a request path, or the copy will drift.
- 04 – Publish the contract – Write the owner, direction of flow, refresh timing and escalation into the integration documentation everyone already reads.

### The uncomfortable cases

Prices are usually split: list prices live in the ERP, commercial agreements live in the CRM. Stock may be owned by the warehouse system while the website needs a near-real-time view. These are not failures of the model; they are places where the model needs a rule and a staleness tolerance, stated explicitly.

Test of a good decision

If two people disagree about a value, everyone should be able to say which system decides and where to correct it. If that sentence is hard to finish, the integration is not ready.

Topics

- Master data
- Architecture
- ERP

Related service: Enterprise Integration

In this article

- A workable method
- The uncomfortable cases

Working on something similar?

Describe the systems, the constraints and what needs to change. We will outline a realistic path and the trade-offs behind it.

Talk to us

Related reading

Enterprise Integration

5 November 2026

#### Designing integrations for the failure case

The happy path is the easy part. Retries, idempotency, dead-letter queues and ownership are what decide whether an integration survives its first bad night.

7 min read

Case study

6 August 2026

#### Order-to-invoice flow across commerce, ERP and logistics

An illustrative integration programme: nightly exports and manual reconciliation replaced by a monitored, queue-based flow between a commerce platform, SAP Business One and a logistics provider.

8 min read

Zoho & Customer Experience

28 October 2026

#### Designing a CRM your sales team will actually use

Most CRM problems are design problems, not software problems. A practical view of module structure, pipeline logic and the fields that decide whether adoption holds.

6 min read

### Working on something similar?

Describe the systems, the constraints and what needs to change. We will outline a realistic path and the trade-offs behind it.

Talk to us

Explore services
