We connect systems that have never talked to each other

As soon as the same data is maintained in several systems, or someone regularly closes the gap by hand: transferring product data from the PIM into the shop, retyping orders into the ERP, reconciling customer data between CRM and newsletter. That does not only cost time, it mainly creates discrepancies, because the same record looks different in three places. An interface ends the duplicate work and makes it clear which system takes the lead.

Typically shop, ERP or inventory management, PIM, CRM, booking and payment systems, shipping providers as well as email and analytics tools. Many of them already come with an API that was simply never used, which is why we check what is there first. For PUKY we converted Akeneo exports automatically into a format Shopify can use; for RHEWUM we made invoice data from Microsoft Navision usable via Lobster.

Through three things: a documented mapping of which fields belong where, proper error handling with logging, and tests with real records rather than only the ideal case. When two systems cannot talk to each other directly, we put a service in between that translates, checks and logs the data. If something gets stuck, it is reported instead of disappearing quietly into an export.

In most cases, yes. An inventory management system without a modern API, a booking system with file exports or an older CRM can be connected as well, as long as the path of the data is clearly defined. Often an interface takes so much load off the legacy system that a replacement is not needed for the time being – and when it does come, the clean separation makes it considerably easier.