ecommerce ERP integration

Your shop and your ERP hold different numbers, and your team reconciles them by hand.

We map how the data actually moves, then connect the systems so it moves on its own.

We work with B2B manufacturers, distributors, and value-add businesses, most often on Business Central and Odoo.

What is ecommerce ERP integration?

Ecommerce ERP integration connects the systems a business runs on so that orders, stock, pricing, invoices and customer records move between them without being typed in again at every step. The work rarely stops at the shop and the ERP: it reaches into the CRM, the fulfillment provider, the payment provider, the marketing platform, and whatever industry system the business depends on. We map the flows first, then connect them, with an integration platform or direct API work depending on what the operation needs.

How integration problems reach us

One product stops selling

Orders arrive across the catalog and one line stays at zero. The cause tends to be a mismatched record between two systems, and the first sign of it is a gap in the sales report.

A group of customers cannot buy

Their orders fail at checkout, and your support team has neither an explanation to give them nor a date to promise.

Records leave one system and arrive short in the other

A hundred are sent and eighty arrive. The missing twenty are found weeks later, by the team that needed them.

Each of these has a small technical cause and an expensive week around it, and they tend to arrive together. They surface at the start of a season, at a year-end, during a promotion, in the week a new channel opens. At ordinary volume, the weakness stays out of sight, and it shows at peak, in the weeks when your team has least time for it.


When the systems already exchange the data, and a person still carries the work between them, the fix is automation.

Operational Automation →

What we find when we take over a connection someone else built

Untested paths

An integration is built against the situations its author could foresee, and the rest stay untested until a real customer runs into one. The failure looks sudden from the outside, although the condition behind it has typically been there for months.

Silent data loss

The sending system returns success, the receiving system holds fewer records than it should, and there is no alert between the two. We start by counting what was sent against what arrived, because a loud failure is easier to live with than a quiet one.

Testing on the live system

Connections are often built directly on production, leaving nowhere to try a change before customers see it. Our first request on those projects is a copy of the setup we can test against, because without one, every change is made with the business running.

‍

All three are ordinary, and they reflect nothing bad about whoever built the connection first. This is the normal condition of software extended for years by people solving one problem at a time, under deadlines, with what they had. It is also why we map what a connection actually does before changing it.

When to buy the connection and when to build it

BUY

Buying is usually the better call for a requirement that is standard, comes from outside the business, and has a deadline attached. A change in law that gives customers a new right is the clearest example: a product that already implements it arrives in days, where building the same thing takes several times longer for the same result. We say so when that is the answer, including when it means less work for us.

BUILD

Building is usually the better call, and the cheaper one in the end, for a requirement that is specific to how your business runs. Pricing that differs by customer and channel, rules about who may order what, a fulfillment sequence with your own exceptions in it: bought as an approximation, these get paid for twice, once for the product and again for the work of living with what it does not do.


The same test applies to the layer underneath. An integration platform earns its place with several systems to connect and a mapping between them that keeps changing. For two systems that are likely to remain the only two, it adds a license and a dependency for little gain.

How we connect systems

Mapping the flows

What moves, in which direction, how often, and what has to be true before it moves at all. This is also where we find the flows that exist only because of a limitation that has since been lifted.

Deciding which system owns which record

Most integration arguments are ownership arguments in disguise. Once it is settled that the ERP owns stock, the shop owns the customer account, and the finance system owns the invoice, most of the design questions answer themselves and the ones that remain are the real ones.

Building with somewhere to test

A copy of the setup to test against, checks that catch a bad record before it travels, and a recovery path that has been tried rather than assumed. When something does fail, the person who needs to know has to be able to see it and put it through again without calling us.

Handing it over

The connection, the field mapping and the failure handling are documented in one place, and the whole of it runs in your own accounts and environments. Another team could take it on without calling us first.

‍

A choice about the whole stack, beyond a single connection, is best mapped in a discovery engagement first.

Systems Architecture & Discovery →

What we have connected

Giunti Psychometrics

Giunti Psychometrics

Four systems in one chain, running since 2022.

Giunti sells exam reservations to students who need a certificate their university asks for. The shop takes the booking and the payment, the learning platform runs the exam and issues the certificate, the ERP receives the invoice data, and a fourth system carries the certificate on to the universities. The record is validated at each hop, because an incomplete student record means a support call in the week the academic year starts.

Tisch Scientific

Tisch Scientific

A stock feed connecting the commerce platform to the client's own portal.

Tisch Scientific runs a customer portal alongside its shop, and the two held separate pictures of the same catalog. We connected them, so availability in the portal is read from the system that holds it, and we prepared the product and category data the portal reads on a schedule it can rely on.

Vrijbuiter

Vrijbuiter

Custom connections replaced with a middleware layer.

Vrijbuiter takes product data from around fifty suppliers, each sending it in a convention of their own. We replaced the point-to-point connections that had accumulated with a middleware layer, and normalized the supplier data on the way through, so the catalog stopped inheriting whatever each supplier happened to send.

‍

Tell us which systems you want working together.

Book a meeting

What we connect

B2B ecommerce integration is rarely a single connection, which is why we treat the ERP as one node instead of the whole picture. The integration of ERP and CRM is the connection most businesses ask about first, and it is rarely more than half of what the operation needs. The list below is where we are fastest, and the systems around it matter as much as the two at the center.

‍

Commerce and portals

Magento, Shopware, Shopify, and the industry systems your sector runs on.

ERP and finance

Microsoft Business Central, Odoo, and the tools that close your books.

The connecting layer

An integration platform when several systems are involved, direct API work when two are.

Everything that joins later

CRM, fulfillment and carriers, payment providers, marketing platforms.

What connected systems change

A customer, a salesperson and the warehouse look at one number instead of three versions of it, and the reconciling stops being a daily task for your team. Over a longer horizon, a new channel, a new supplier or a new obligation becomes a change to one connection instead of a project.

What we measure is what stopped being carried by hand and what stopped failing. The map made during the first connection is the map every later one starts from, so the groundwork is done once rather than per project.

Where we are the wrong choice

Call us when the connections cross several systems, the rules are yours instead of the vendor's, and an unnoticed failure is counted in customers instead of tickets.

For two mainstream products with a supported connector and ordinary rules between them, installing that connector is usually the right call, and we can test the cases that matter to you before it goes live.

Existing connections count too: if one is slow, unreliable, or expensive to run, the same mapping is what makes optimizing it worthwhile.

FAQ

How long does an ERP integration take?

A single connection with clear rules is live within weeks, and most of that time protects your data rather than builds screens: mapping the flow, reconciling what exists, and testing against a copy of your setup before anything touches production. A multi-system operation with customer-specific rules runs to months, and what shortens it is settling the rules early, which is the part we do first.

How do you integrate an ERP with an ecommerce platform?

Through the interfaces both systems expose, either directly or through an integration layer between them. The work is in the rules around it: how often data moves, what has to be validated before it goes, what happens to a record that fails, and who sees that it failed. We work those rules out with the team that handles the exceptions today, before anything is built.

What is middleware, or an iPaaS, in commerce?

A layer between your systems that holds the connections in one place, so each system talks to it rather than to every other system. The practical argument for one is visibility: somebody outside the development team can see whether last night's run succeeded, and which records failed. The argument against it is that it becomes another system to license, learn and keep current.

Who owns the integration once it is built?

You do. The code, the mapping and the credentials are yours, the documentation goes with them, and another competent team could pick the work up. We would rather be kept because the work is good than because leaving is difficult.