06 / Services
Sync between systems
A link between the CRM, the warehouse, the bank, the storefront, and outside services, so the same data is not entered twice.
For companies where the same record lives in several programs.
Sync
Systems
From
To
Warehouse
Trace
Log
What it consists of
What goes into the system
- 01
Who owns the field
Every fact has one owner: the price lives in the records, the order status in the storefront, the contact in the CRM. The rest only read.
- The list of fields that travel
- Where people write, and who only reads
- What to do if both sources have changed the same field
- 02
Channel
An API, a webhook, or a queue — according to how the system can hand data over, not “whichever is more fashionable.”
- What arrives on its own
- What has to be fetched on a schedule
- What volume arrives in the peak hour
- 03
Failure
A packet that did not get through does not vanish in silence. It waits and tries again.
- A retry, with a pause
- A packet that must not be repeated
- A signal if the queue has stalled
- 04
Log
By order number or record number you can see: sent, arrived, refused, and why.
- A record of every attempt
- Search by number
- Who can restart the sync
- 05
What we leave unconnected
An extra link breeds mismatches. Fields that nobody reads do not come along.
- Systems that stay manual
- Fields kept out of the sync
- How to test a sync on a copy, before production data
What we do
- 01A map of who owns each field
- 02API, webhooks, and queues
- 03Connecting the records, the banks, and the storefronts
- 04A retry when something fails, not a silent loss of the packet
- 05A log that shows what did not arrive
How we proceed
- 01An audit of the systems
- 02A diagram of the sync
- 03Build
- 04A run on live data
- 05A description for the team
Stack
- REST
- GraphQL
- Node.js
- Python
- PostgreSQL
A guide for the timing
One sync takes from a week. Several systems with conflicting data take from a month.
Outcome
A fact is entered once and arrives where it is expected.
What usually comes later
Two-way editing of one field across three systems, and a “five-year historical migration,” we do separately, after a live sync of current facts.