
K/06Data that flows
Reference-data synchronisation
Decide which tool owns each field, then define exchanges and how differences are handled.
The need
A documented exchange, visible discrepancies and a recovery procedure the team knows.
When two tools hold the same information, another copy introduces risk. We agree the direction of travel, conflict rules and how to replay a failed exchange.
Discrepancy → log → resolution before retry
In practice
- 01Source AReference IDs and data
- 02RulesConflicts and duplicates
- 03Target BControlled updates
Starting scope
What the work covers.
- 01
Ownership matrix
Choose the fields and stable IDs, and define their source of truth.
- 02
Scoped connector
Implement the agreed exchange and limits after reviewing available interfaces.
- 03
Discrepancy log
Record rejected changes and test recovery with sample data.
Practical brief
How we deliver.
Every field has an owner and a conflict rule. Before automating an exchange, we review authorised access, interface limits and whether stable identifiers are available. The design accounts for retrying without duplicate creates and surfacing differences that require a human decision.
What to prepare
- Fields to match, an anonymised sample and expected volume.
- Available interfaces and any frequency or access constraints.
What you receive
- A source-of-truth matrix and the agreed exchange flow.
- A replay procedure and example discrepancy records.
Simulate an update, a missing ID and an interrupted exchange. Check that retrying does not introduce duplicates and that unresolved conflicts remain visible.
Good questions
To agree in the quote
Refresh frequency, API limits and any subscriptions are assessed during scoping.
Is the sync real-time?
Not necessarily. Timing depends on the need, volume and what the selected tools support.
Can it sync in both directions?
Yes if both tools allow it and conflicts can be handled. A one-way flow is often easier to operate and explain.
K/06 / Data
Let’s talk about your context.
This service is preselected in the enquiry form. The first conversation defines the need; it doesn’t place an order.