Skip to content
← Guides

Mapping interfaces between systems: a practical example

How to describe a data exchange so that different vendors implement it the same way.

Board with cards linked by threads, like an interface map

When two systems hold the same data, they eventually diverge. Mapping interfaces means deciding, for each piece of data, who creates it, who receives it, when, and what happens if the exchange fails.

01

One source per data entity

For each entity (customer, item, price, order) name a single authoritative system. Others receive it and do not change it, or change it only under written rules.

02

Five facts for every interface

Each row of the interface list should state:

  • Direction (from A to B)
  • Trigger or frequency (on change, nightly)
  • Fields exchanged and format
  • Error behaviour
  • Interface owner
Interface table with highlighted rows
03

Responsibility boundaries

When an interface links systems from two vendors, write down who answers for what: sender, receiver, monitoring. This is the most frequent cause of unresolved issues.

Example

Interface list excerpt

Interface list excerpt
InterfaceDirectionFrequencyOn errorOwner
Customer masterERP → CRMOn every changeQueue and notify accountingERP vendor
Stock levelsWarehouse → Online shopEvery 15 minutesItem shown as unavailableShop vendor

More guides

Want to apply this to your case?

The "Architecture and integration design" service produces these documents tailored to your systems.

Request a quote