Skip to main content
Work

Business Systems Integration

Three systems that each held part of the truth about an order, and no reliable way to assemble the whole.

Sector
Distribution and logistics
Scope
Integration architecture · API layer · Master data alignment
01Challenge

An order was created in one system, fulfilled in a second and invoiced in a third. Staff bridged the gaps by hand, which meant the same order existed under three different reference formats. Any question that spanned two systems — how much of last month's revenue was still unfulfilled, for instance — required someone to sit down with exports and reconcile them manually.

02Approach

Replacing all three systems was neither affordable nor necessary. We treated it as an integration problem: establish one canonical identifier for an order, define who owns each field, and build interfaces that carry changes between systems reliably — with monitoring, so a failed sync is visible immediately rather than discovered at month-end.

03Solution

What we built.

  • 01A canonical order identifier carried consistently across all three systems
  • 02An integration layer handling data exchange, with defined field ownership
  • 03Master data alignment and de-duplication of customer and product records
  • 04Error handling and retry logic, with alerting on failed synchronisation
  • 05A reconciliation view exposing any record that failed to propagate
04Outcome
  • Order data flows between systems without manual re-entry
  • Cross-system questions can be answered without a manual reconciliation exercise
  • Failed synchronisations surface immediately instead of at month-end
  • The three existing systems were retained — no replacement programme was needed

Have a technology challenge?Let's figure it out.

Tell us what isn't working. If we're the right people to help, we'll say so — and if we aren't, we'll say that too.