Best ERP Integration Developers in the Netherlands (2027)

There is no single best developer for AFAS, Exact, SAP Business One, Microsoft Dynamics or TOPdesk integrations in 2027. The right choice depends on one question: do you need a platform that runs many standard flows, or a developer who builds a few flows that carry your own business logic? This list names nine options, shows how we chose them, and says for each one which buyer it suits best. Disclosure: Crux Digits publishes this list and is listed first. We say why, and who the others are better for.

It is written for the IT manager, informatiemanager or integration architect at a Dutch or Flemish organisation of 250 to 5,000 FTE who has to add or replace koppelingen without losing the audit trail. Crux Digits builds integrations and the AI that reads and writes through them, next to your ICT partner, and hands the code over to you.

How did we choose these integration developers?

We checked every firm on its own website on 29 October 2026 against four criteria, and left out any firm we could not verify.

1. Real integration work in this market. The site names the ERP, service management or commerce systems Dutch organisations actually run, not general digital transformation.

2. Published specifics. Named systems, named platforms and prices where the firm publishes them. We quote a price only where the firm itself does.

3. A clear operating model. A platform licence, a project, or both, so you know what you are buying after go-live.

4. Honest fit. Every entry names the buyer for whom it is the better choice, including against us.

The list is not a ranking beyond our own pick. Crux Digits is first because we publish the list; every entry after ours is in alphabetical order. No firm paid for a place and there are no affiliate links. For software houses in general rather than integration specialists, see our guide to custom software development companies in the Netherlands.

Which ERP integration developers should you shortlist for 2027?

Nine names cover the realistic options: one fixed-price build partner, four platforms or frameworks, and four integration specialists or consultancies.

Crux Digits (our pick)

Disclosure: Crux Digits publishes this list and is listed first. We say why, and who the others are better for.

Crux Digits, based in the Utrecht region, builds integrations between ERP, service management and line-of-business systems, and the AI that reads from and writes to them. The reason we place ourselves first is the part you can check: published fixed prices of €2,500 for an AI audit, €20,000 for a Production-ready MVP and from €50,000 for a production launch, all excluding VAT. The source code and documentation go to your own repository. We work next to your ICT partner, who keeps hosting, identity and support, and we work in English and Dutch.

Best for: an IT team that needs one or a few bounded koppelingen with its own logic, such as matching purchase invoices in Exact Online or AFAS with a human approval step, at a price fixed before the build. Not the best choice if you want a platform licence that runs hundreds of standard flows, or a supplier that operates your integrations around the clock. We do neither.

Alumio

Alumio is an integration platform (iPaaS) with offices in Groningen, Hamburg, London and Stockholm, according to its website. It names connections to e-commerce, ERP, CRM and PIM systems, including Shopify, Shopware, SAP, NetSuite, Microsoft Dynamics 365 Finance & Operations, Salesforce and Pimcore, and offers a multi-entity edition for agencies and system integrators. It is one of the few on this list with a published price: Connect Lite starts at €499 per month, and Connect Core is priced to scope.

Best for: an organisation that wants one governed integration layer between webshop, ERP and PIM, configured rather than coded.

Brixxs

Brixxs, in Almere, describes itself on its website as a partner for low-code, API integrations, AI and custom software. Its AFAS page names integrations with AFAS Profit, InSite and OutSite, GetConnector flows with logging and rights management, and UpdateConnector flows with validation, retries and an error queue. It is listed in the Exact App Store with custom solutions on the Exact Online API, and its site describes TOPdesk work.

Best for: an organisation whose core is AFAS Profit or Exact Online and that wants a specialist in those platforms' APIs.

ChannelEngine

ChannelEngine is a marketplace integration and multichannel e-commerce platform. Its site claims more than 1,300 marketplaces and sales channels, names plugins for Shopify, Adobe Commerce, SAP, Microsoft Business Central and NetSuite, offers APIs for custom systems, and syncs listings, orders, stock and prices.

Best for: a wholesaler or brand whose integration problem is selling through bol.com, Amazon or Zalando from one ERP or WMS, rather than internal process flows.

Codit

Codit designs, builds and runs data-driven solutions on Microsoft Azure. It is a Microsoft Solutions Partner, reports more than 200 employees and ISO 27001 certification, and lists offices in Belgium, the Netherlands and other European countries. Its published cases name Azure API Management and a migration away from BizTalk.

Best for: an organisation standardised on Microsoft Azure that wants one firm to build and also operate its integration platform there, including in Flanders.

eMagiz

eMagiz, in Enschede, offers an iPaaS with messaging, an API gateway, event streaming and more than 100 connectors, and presents itself as a Dutch product with European servers and Dutch and English support. A testimonial on its site from BAM Infra describes 40 connected systems and more than 700 data streams a day.

Best for: an organisation with a large integration landscape that wants a Dutch platform to model, run and manage all of it in one place.

Linq5

Linq5, in Groningen, describes itself on its website as an Exact software specialist offering consultancy, custom software and online business solutions, with standard e-commerce apps under its xCore label. It names Exact Online, Exact Synergy and Exact Globe.

Best for: an organisation that still runs Exact Globe or Exact Synergy, or combines them with Exact Online, and needs a developer who knows all three.

WeAreFrank!

WeAreFrank! maintains the Frank!Framework, an integration framework its site describes as fully open source and low-code, with more than 100 building blocks, plus training, Frank!Gateway and managed integrations. It names government, including Common Ground for municipalities, financial services and enterprise, and positions the framework as an alternative to TIBCO BW5, Microsoft BizTalk and SAP Integration Suite.

Best for: a municipality or financial institution that wants no licence fees and full access to the integration source code.

Yenlo

Yenlo, headquartered in Schiphol-Rijk, calls itself on its website an API, integration, IAM and iPaaS expert with more than 100 experts. It names WSO2, Boomi, AWS and AFAS Software, its own Connext platform, and services from architecture to 24/7 operations.

Best for: an organisation that wants API management and identity and access management in the same programme as its integrations, operated around the clock.

Should you choose an iPaaS platform or custom integration code?

Choose a platform when most flows are standard and numerous; choose custom code when a few flows carry logic specific to your organisation.

Our decision rule, which is a rule of thumb and not a measured result: list every flow and score it on two questions. Is there a maintained connector for both ends? Is the mapping standard, where an order is an order, or is it yours, such as a price rule, an approval matrix, or a werkbon that becomes three invoice lines? If most flows score connector-yes and mapping-standard, a platform licence pays back in reuse, monitoring and governance. If a handful of flows carry your own logic, custom code in your own repository is easier to test, version and audit.

Most organisations of 250 to 5,000 FTE end up with both: a platform for the standard traffic and a small number of custom services for the logic that is theirs. Ask one more question before you sign: who runs it after go-live? A platform includes a runtime and a monitoring console. Custom code needs your ICT partner to host it and a named person to watch the error queue.

What does an AFAS Profit integration actually involve?

An AFAS Profit integration runs through an AppConnector and its token, with GetConnectors to read and UpdateConnectors to write.

According to the AFAS help centre, the AppConnector determines which Get and UpdateConnectors a token may use. You define a GetConnector's data structure yourself and receive JSON, XML or CSV. An UpdateConnector adds, changes or deletes data in Profit, and the message is validated before Profit accepts it. The REST API exchanges JSON with the token in a header; the SOAP API does the same with XML. The total size of an API call is at most 75 MB.

Three design consequences follow. Give each integration its own token, scoped to the connectors it needs, so one leak does not expose payroll data. Page large exports to stay under the 75 MB ceiling. And plan for rejected UpdateConnector messages: they need an error queue and a person who reads it. AFAS also accepts a systemintegrator request through its customer portal and lists certified solutions on partner.afas.nl, which is worth checking before anyone builds.

How do Business Central and SAP Business One integrations differ?

Business Central throttles its web services with HTTP 429 and offers webhooks; SAP Business One offers the Service Layer, a REST API.

Microsoft's guidance on Business Central API limits states that a throttled client receives 429 Too Many Requests and must retry with a cool-off period, such as exponential back-off. A request that runs longer than 10 minutes is aborted with 504 Gateway Timeout. Microsoft recommends webhooks instead of polling, filters on lastModifiedDateTime to fetch only changes, batching and deep inserts.

For SAP Business One, SAP's own Service Layer course describes the Service Layer as a REST API to customise business processes, aimed at newer web development platforms. The practical test for any developer is the same on both systems: ask how the integration fetches only what changed, and what it does when the ERP says no.

How should TOPdesk connect to your ERP and other systems?

TOPdesk's API uses Basic authentication with an account and an application password that carries an expiry date.

TOPdesk explains that each application gets its own password, shown once at creation, so one application's access can be revoked without touching the others. For outbound flows, TOPdesk action sequences exchange data with a target program in steps, with a stored connection; towards a TOPdesk environment you can use an application token or an integration client with OAuth 2.0, where TOPdesk refreshes the access token automatically.

The expiry date is a planned outage unless somebody owns the renewal. Put each application password, its account and its expiry in the runbook, and give the renewal to your ICT partner or service desk, not to the developer who has left.

What about webshop and WMS integrations?

Webshop and WMS integrations usually fail on stock and order status, so decide per field which system is leading before anyone builds.

A common split, which you should confirm for your own landscape: the WMS leads on stock and shipment status, the ERP on prices, customers and invoices, the PIM on product content, and the webshop or marketplace only on the order it took. Platforms such as Alumio and ChannelEngine sync these fields; they do not decide which system wins when two disagree. That decision belongs in your design document, signed by the process owner.

What should the integration proposal you sign contain?

Eight items: record types, direction, leading system per field, error path, replay, limits, credentials with expiry, and the owner after go-live.

1. Record types: customers, orders, invoices, stock, tickets, each named.

2. Direction: one way or both ways. Two-way costs more because both systems can disagree.

3. Leading system per field, as above.

4. Error path: where a rejected message goes and who is told.

5. Replay: how the last hours are resent safely after an outage, without duplicates.

6. Limits: each system's published API limits and the behaviour on HTTP 429.

7. Credentials: which tokens, application passwords or OAuth clients, where they are stored, and when they expire.

8. Owner after go-live: a name at your ICT partner, your IT team or the platform supplier.

A proposal that says only 'integration between system A and system B' has priced the happy path.

Where does Crux Digits fit?

Crux Digits builds bounded koppelingen and the AI that works through them, at fixed prices, with the code handed over. We do not host, run a helpdesk or operate integrations around the clock; your ICT partner, or a platform from this list, does that. If you already run eMagiz, Alumio or Frank!Framework, we can build the custom service that carries your own logic and leave the standard flows on the platform.

What an API integration costs and what breaks after go-live is set out on API integration. For AI that reads from and writes to Exact Online and AFAS, see connecting AI to Exact and AFAS.

Last updated: 29 October 2026.

Frequently asked questions