ERP Integration: Custom Solutions for Swiss SMEs

ERP Integration: Up to 25 Percent More Work If It's Missing

In most ERP projects we support at Swiss SMEs, the real problem rarely lies with the ERP system itself. It stems from the integration of the online store, production, CRM, or accounting.

Typical Challenges with ERP Systems

  • Order data from the online store does not automatically flow into the ERP system but must be entered manually
  • Machine data from production is collected in Excel instead of flowing directly into the ERP
  • Customer service does not have real-time access to order status and has to call production to check
  • Customer and product master data exist in duplicate—in both the ERP and CRM systems—and become out of sync over time
  • Inspection procedures or technical expertise—which are actually core competencies—were manually entered into the ERP system years ago and have been difficult to maintain ever since

Up to 25% more effort after ERP implementation—that’s the result if these gaps remain. Each issue ties up staff who are needed elsewhere. And each can be resolved with the right interface. With manual double entry, the error rate in practice ranges from 1 to 5%.

What does ERP integration actually mean? 

ERP integration means that your ERP system automatically exchanges data with the systems around it—for example, withmachine control systems, CRM, online stores, time tracking, and industry-specific applications.  

Technically, this is achieved via REST APIs, EDI connections, or middleware. Which option is best depends on the volume and format of the data, as well as how critical real-time updates are to the process. The goal always remains the same: enter data once, make it available everywhere. 

Why is there still so much manual work despite ERP?

Gaps almost always arise in three areas:

  • between ERP and machines
  • between ERP and third-party systems such as CRM or online stores
  • between ERP and processes that are too specific for a standard module

Here’s an example: TESTEX AG tests textiles according to the OEKO-TEX Standard. For years, the testing logic was mapped manually in the ERP system. With each new branch office, it became more difficult to apply it consistently across all locations.

The article “More Work Despite ERP?” shows where such gaps might specifically arise in your organization.

Standard Connection vs. Custom Interface

Not every system comes with a suitable standard interface. And even when it does, it often coversonly part of the process.

At TESTEX, the solution was not to expand the ERP with additional modules. The testing logic was moved to a separate application, connected via a custom interface. Since then, TESTEX has been maintaining the test parameters itself, without having to wait for a new ERP release.

Custom interfaces fill in exactly what’s missing from the standard system. You can read about how such an interface is actually developed in the article “Having an ERP Interface Developed.”

Your ERP doesn't have to do everything

A second example: At Bucher Hydraulics, order status information was stored in the ERP system. However, the employees who worked on the orders every day were checking a different application. The information was there—just in the wrong place.

The solution: The status is transferred via an interface directly to the application where the actual work takes place. Customers and employees can now see the status in real time. In both cases, the ERP remained the database. The actual problem was solved separately, in a dedicated application.

Your process determines how much responsibility the ERP system bears. We explain this approach in detail in the article “Your ERP Is Not Your USP.”

ERP Interfaces for Common Swiss Systems

Abacus is one of the most widely used ERP systems among Swiss SMEs. Precisely because it runs reliably at its core, it becomes particularly evident where standard integrations are lacking: in custom reports, industry-specific logic, or integration with older line-of-business applications. The article “Abacus Interface for Swiss SMEs” highlights the typical gaps in Abacus and explains how we bridge them .

Here's How We Approach ERP Integration

1. Analysis of your existing systems and data flows: Where are media breaks currently occurring, and which data truly needs to flow in real time?

2. Concept for the appropriate interface solution—whether API, EDI, or middleware—tailored to data volume, frequency, and criticality

3. Development of a customized integration, including testing with live production data

4. Operation and maintenance to ensure the connection remains reliable even during ERP updates or system changes on the other side

Frequently asked questions

  • What is ERP integration?

  • What is an ERP interface?

  • Which ERP is right for a Swiss SME?

  • Does Abacus have its own API?

  • How do I connect my ERP to my online store?

  • Do I need a CRM in addition to the ERP?

Ready for an ERP integration?

Let us know where you’re having trouble. We’ll tell you during our first conversation whether and how we can help you resolve it.

This might interest you

Contact

Do you have any questions? Would you like to find out more about our services?
We look forward to your enquiry.

Sofia Steninger

Sofia Steninger
Solution Sales Manager