Case study · Commerce · ERP ↔ shop

Three systems, one set of data. With no manual work.

Shop, marketplaces and ERP share one data model; every discrepancy lands in the log instead of being quietly overwritten.

Before
Stock and orders were reconciled by hand between the systems. One item stood in three systems in three different states.
State 1State 2State 3
My part
Concept and delivery of the integration layer and the synchronisation logic, including the field mapping between the systems involved.
built
01 Read
Stock changes in the ERP. The layer reads the change in.
02 Check
It checks the record against fixed rules before it passes anything on.
03 Log
on a discrepancy
If two systems disagree, the discrepancy goes into the log and is not overwritten. That two systems know different things is information you do not quietly clear away.
04 Map
Then it maps the fields to the target structure. Reconciling the fields is the part that costs the time.
05 Write
The result appears in the shop and on the marketplaces.
06 Reverse
The same route runs in the other direction too, by the same rules.
After
Reconciling by hand is gone. Data errors show up early.
one stateone stateone state

The evidence

How far the zero reaches. Rung 03 of 4: Handed over.

Counted: 0 manual stock discrepancies
Checked by: The case write-up, step by step. The reconciliation is documented as a process.
Not evidenced: Business figures. What the integration earned the client only the client can state, and no approval for that has been given.

The page Work shows all four rungs and the other systems.