An ERP integration that keeps working.

An integration between your ERP and your webshop, portal or WMS usually works on day one. It goes wrong when one of the systems gets an update or when unexpected data comes through. This is how we build integrations that can handle that.

Serge HuijsenFounder and developer3 minute read
Someone points to a process diagram on a wall

Every exchange is in a log

Every order, stock change or invoice that passes through the integration is written to a log. If something goes wrong, you can see which message it was, when it was sent and what the other system returned.

What happens when a message does not arrive

If a message does not arrive, we put it in a queue and try again later. If it still fails after a few attempts, a developer gets an alert. So no order disappears without someone noticing.

Two people discuss something on a laptop with pen and paper beside it

Testing against a copy of your ERP

Before an integration goes live, we test it against a test environment of your ERP. Most packages allow this. We also test with the exceptions in your own data, such as a customer without a VAT number or an item with negative stock.

ERP updates

ERP vendors change their API regularly. We follow the announcements and test the integration before the change goes live for you. If an integration does fail, we usually see it in the monitoring before you do.

Portrait of Serge Huijsen
Written by

Serge Huijsen

Founder and developer

Serge started CodeIQ and still builds along. He leads most first conversations and sketches out the set-up of new platforms.

More about Serge

Share this article

LinkedInEmail

The coffee is already on.

Bring your question, your process or an idea that is not finished yet. In a first conversation we map out your situation and you get honest advice on the next step.

Freshly made

How do you take it?