{% include "elements/picture.twig" with { mock: mock } %}
Employee planning on screen with an ERP view in the office

ERP Connector

Apps · ERP Connector

Your ERP and your manufacturing operations, connected in both directions without the need for interface programming. No message gets lost.

Demo for your use caseDiscuss technical questions

The Problem

Is every interface its own project?

Traditional interfaces are programmed, tested, and reworked every time a change is made to the ERP system. If the connection goes down briefly, orders are missing from the production line, and no one notices until the start of the shift. And when an order doesn’t come through, the ERP team searches log files to find the cause.

  • Purchasing app on the iDIP platform

Four steps, each one visible

And back to the ERP: Data such as setup time, labor hours, good parts, and scrap are automatically sent back via the same process. Your ERP is always up to date with production status.

  1. The ERP system sends

    production orders, operations, components, and material master data to a secure webhook address, which is unique for each connector.

  2. The queue buffers

    Each message is immediately cached. Peak loads and brief outages do not result in data loss.

  3. The data is converted

    field by field into the iDIP format, properly typed according to your mapping.

  4. The app receives it

    The finished data records are sent to the target app as a production order, operation, or component, almost in real time.

What the app can do

  • Field mapping via the user interface

    Each ERP field is mapped to a field in the app and converted. Changes can be made without a new software release.

  • Fail-safe queue

    Messages are buffered and automatically retried in the event of an error.

  • Full transparency

    Status of each message: new, in progress, imported, or failed. The log shows the input and output for each step.

  • Correct instead of resending

    Check, correct, and reprocess an erroneous message without resending it from the ERP.

  • Multiple connectors running in parallel

    For different ERP systems, clients, or plants.

  • Update-safe extensibility

    Add custom processing steps, conversion rules, and additional document types without modifying the standard system.

  • Secure access

    The target app is written to only after authentication.

Who is it for

Anyone who works with the app

  • IT management: a maintainable integration instead of yet another custom interface.
  • ERP team: Enter the webhook address, map fields, and track every import.
  • Production management: Orders are on the production line as soon as they’re released in the ERP.
  • Workflow at a digital workstation at V-ZUG

How to Customize the App

Set up in just a few steps

A new connector can be configured quickly: Provide the webhook address to the ERP team, select the target app and access method, specify the document type, and map the fields. You can add new fields or document types yourself later via the interface.

If the default settings aren’t sufficient, you can incorporate your own steps at defined points—for example, to enrich data before conversion or to trigger a follow-up action after saving. The default settings remain unchanged, and you’ll continue to receive every update.

Is there a feature you're missing? No problem.

  • Something’s missing from the app

    We or your partner will integrate it—and make sure it’s update-compatible. Or you can expand the app yourself using low-code or the AI assistant.

  • You need something completely different

    That’s no problem either. It’ll be built as a standalone app on the same platform, connected to your machines, your ERP, and the apps you’re already using.

Illustration: iDIP als Datendrehscheibe zwischen ERP, Maschinen, Lager und Rechenzentrum

References

  • Konvekta
  • Glatz
  • Ospelt

To help you make your decision

  • Small startFixed-price PoC with your real ERP, credited on go-ahead
  • Predictable costsApp subscription per plant at a fixed monthly price from CHF 300 (together with another app), not per user or machine. Customize and extend with the Starter Package from CHF 1,000 per month
  • Reliable partnerPart of the Rey Group, an ISO 9001-certified company
  • Award-winningGerman Innovation Award 2026, Smart Production Innovation Award 2025

Technical data sheet with architecture diagram (PDF, German)

Start small. See quickly what it can do.

In the PoC, we connect your ERP system to a workstation: Orders arrive automatically, and your ERP team can view every step in the log. Only then do you decide whether to expand the system.

Demo for your use caseDiscuss technical questions

Frequently asked questions

Which ERP systems are supported?

These include SAP, Microsoft Dynamics, Business Central, Infor LN, and Abacus, as well as any ERP system that can provide messages via REST or other interfaces.

What does our ERP team need to do?

Common ERP systems already have standard interfaces for production orders, material master data, and confirmation data, or these can be set up through configuration. If such an interface is missing, the ERP system must provide it. We’ll clarify this with your ERP team during the use case review.

What happens if iDIP is temporarily unavailable?

The queue buffers all messages. Failed imports are automatically retried.

Can we change the field mapping ourselves?

Yes, via the user interface and without a new software release.

Does the connector run in the cloud or on our premises?

Both: in the Swiss data center or on your own infrastructure.

What if we’re missing a feature?

Then we or your partner will build it, or your team can add it themselves using low-code. If you need something completely different, it will be developed as a standalone app on the same platform.

How much does the ERP connector cost?

Starting at CHF 300 per month per plant, bundled with another iDIP app, including updates. Bundling multiple apps is more cost-effective; we’d be happy to provide you with a quote for the right combination.

Your contact person

Questions about your use case? Tomy Mändli is happy to help.