How to develop an ERP-interface: Custom API integration

Your existing system needs to exchange data with the ERP, but there isn’t a suitable integration solution for it. Standard integrators cover common scenarios, but not yours. That’s why you need an ERP interface that understands your specific systems, data, and processes. That’s exactly what we develop.

• A legacy system needs to be integrated with SAP, but there is no off-the-shelf connector available for this combination.
• An Access database needs to work with Abacus, but the two systems aren’t compatible.
• A Delphi application that has been running reliably for years needs to exchange data with the ERP system.

In cases like these, you need an interface tailored to your specific situation, rather than being forced to adapt your processes to a standard product. You can find out more about this in this article!

Many companies believe they need a new system first. In practice, though, what’s usually missing is just the right connection between what’s already in place. That’s exactly where we come in—instead of trying to sell you a complete overhaul.

Most problems don’t arise in the code, but before it. These are the mistakes we see most often, and we make a conscious effort to avoid them:

• Ignoring the legacy logic: Older business applications are full of rules and special cases that often exist only in the minds of a few individuals. We make sure to understand the existing logic before we integrate it.
• Focusing only on the technology, not the process: The data may flow, but the business logic breaks down. We start with the process and first ask what needs to happen from a business perspective.
• No clear data leadership: If it’s not defined which system is the primary source for which data, contradictions and version conflicts arise. We establish this in advance.
• Errors remain hidden: Failed transfers are often only noticed when customers inquire about them. We build error handling that makes problems visible before they have consequences.
• Dependence on individuals: Without documentation, only one person knows how the integration works. We document the solution in a way that ensures it remains maintainable and scalable.

We follow a four-step process:

1. Analysis of data points: We determine which data needs to flow, in which direction, and how up-to-date it should be.
2. API design: We design the connection and define formats, rules, security, and error handling.
3. Testing: We test using realistic data before anything goes live.
4. Acceptance: You review the interface based on agreed-upon criteria, after which it goes live.

Bucher Hydraulics operates a Delphi configurator for lift systems used, among other places, in high-bay warehouses. The system was closely integrated with a large Access database and other components. The database was maintained separately from the configurator, so changes had to be manually synchronized afterward. As a result, not everyone was always working with the same version.

soxes developed the integration so that the database can be edited directly and the configurator updates automatically. Manual synchronization is no longer necessary. The status report, which used to be available only in the ERP system, is now accessible directly within the application and connected to the ERP via an interface. Sales, engineering, and service teams all work with the same data, which significantly reduces follow-up inquiries and duplicate checks.