ERP and PIM
Products, stock, prices, customers or orders. Systems we often see include Exact, AFAS, Microsoft Dynamics 365 Business Central, Odoo and SAP Business One. We are not an official partner of any of them; we build on the API you have.
Service
Integrations for your Medusa webshop
A shop that does not talk to the rest of the business becomes a second set of books. We connect Medusa to the systems that hold the truth in your company. Not a pile of separate apps, but a clear agreement on which system owns which data.
At a glance
- ERP and PIM
- Payments and shipping
- Accounting and email
- Making errors visible
Custom quote after a free intro call
What we do
What is included
Payments and shipping
Providers such as Mollie, Adyen or Stripe, and carriers or a shipping platform. The choice is yours. We connect it to the checkout and order status.
Accounting and email
Invoices, customer details or order confirmations. Only the flows someone actually uses, not five 'handy' syncs nobody checks.
Making errors visible
An integration that fails silently is worse than none. We log what goes wrong and make it clear who fixes it: the shop, the other system or a person.
Who it is for
Who this fits
- Companies where stock or prices are not managed in the shop.
- Teams that email CSV files back and forth between the shop and the back office.
- Shops with a payment or shipping provider not yet connected to Medusa.
- Organisations with an existing Medusa install that want one more system, without rebuilding the shop.
Honest advice
When we advise against it
- A list of ten integrations 'because we can', without an owner per data flow.
- Rebuilding an iPaaS scenario that already runs fine. Then we leave it alone.
Price
What determines the price
A custom quote after a free intro call. These factors determine the price, not a menu.
- Quality of the other API
- A documented API with a test environment is predictable. An export folder on a network drive is a different project.
- Direction and frequency
- One way, once a night, is smaller than both ways, per order, with conflicts when both systems may change data.
- Which system is in charge
- Until that is settled, we build the integration twice. That decision belongs in the proposal.
- Exceptions
- The basic flow is rarely the work. The exception — a partial delivery, a credit limit, a bundle item — is.
Process
The process
- 01
Map the data flows
Per data type: source, destination, frequency, and what happens when it fails.
- 02
Pilot on a narrow flow
One entity first, such as stock or orders. Not everything at once.
- 03
Build and test environment
We test against a sandbox if one exists. Production is not the first time an order goes across.
- 04
Handover
Logging, a short manual, and an agreement on who gets called when a sync turns red.
Insights
Further reading
From this service to the articles, and from each article back again.
- ArticleMigrating to Medusa: why, and how to do it rightWhy companies move to Medusa, from which platforms it makes sense, the six steps of a good migration and when you are better off staying.Read more
- ArticleFrom WooCommerce to Medusa: when a migration pays offSigns that WooCommerce is pinching, what does and does not come along in a migration, and why redirects are no ranking guarantee.Read more
- ArticlePrestaShop vs Medusa: modules, multistore and when to switchPrestaShop 9 and Medusa compared on licence, module subscriptions, hosting, multistore and three-year cost. With prices from prestashop.com (5 Nov 2026).Read more
- All articlesPlatform comparisons and the migration guide, with sources.To the articles
Other services
Which systems do you integrate with?
Any system with a usable API or a reliable export. ERP, PIM, payments, shipping, accounting and search are the most common. We do not publish partner badges we do not have.
Does it have to be real-time?
Only if the process demands it. Stock for a fast-moving product sometimes, product copy almost never. Real-time costs more to build and fails more often, so we choose it deliberately.
What if the other system has a poor API?
Then we say so before the build. Sometimes a nightly export is more honest than an API that keeps falling over. Sometimes the project only becomes possible once the vendor opens something up. That is a precondition, not a detail.
Do you also handle payments and shipping?
Yes, as part of the shop or as a separate connection to an existing Medusa install. You sign the contracts with the provider yourself. We build the technical integration.
Do you build directly on Medusa or through middleware?
Preferably directly, with Medusa workflows, so orders and products keep one lifecycle. Middleware only when there is already a stable integration layer in your landscape that we should not ignore.
Free intro call
What is your challenge?
Twelve shops that need to become one, an ERP that sets the price, or a checkout that does not do what you want. Tell us in one call. You will hear honestly whether Medusa fits.
Based in Nijmegen, the Netherlands, working with companies across Europe. How we work with European teams.