Systems that sync themselves.
Webshops, ERPs, suppliers, accounting, BI. We connect them through one integration layer that routes orders, stock, invoices and documents for you, fault-tolerant and repeatable.
We've been wiring systems together for 16+ years a while now.
Since 2008 we've been building integration layers from Arnhem. First the simple Excel-to-ERP link. Then webshop orders that book themselves. Hundreds of integrations later, we know where it tends to go wrong in your context.
Not abstract. Concretely that means: less copy-paste work, fewer phone calls, fewer month-end surprises. And an audit trail that lets you explain exactly what happened where.
Six ways systems talk to each other.
No religion about the right protocol. Just an honest choice based on what your partner or vendor supports. Often we use several alongside each other.
Webhooks & event-driven
React to events the moment they happen, order placed, stock changed, payment received, no polling, no lag.
- Webhooks
- Pub/Sub
- Realtime
- Queues
File-based exchange
CSV, XLSX, XML or TXT over FTP, SFTP, S3 or email. For legacy systems that speak nothing else, or as a temporary bridge.
- CSV
- SFTP
- S3
- Legacy
Database & ETL
Direct database links, scheduled jobs and pipelines. For analytics environments, data warehouses and BI flows.
- SQL
- ETL
- Pipelines
- Warehouse
Webshop ↔ ERP
The classic. Products, stock, pricing, orders and invoices in sync between your shop and ERP. Two-way, real-time.
- Shopify
- WooCommerce
- Exact
- SAP
Where integrations tip the scales.
Four sectors where copying between systems by hand pushes back hardest. Four patterns we've solved most often.
Webshop, ERP and POS in sync
Products, stock, orders and invoices that route themselves between Shopify or WooCommerce, your ERP and the POS.
EDI with carriers and WMS
Track & Trace, dock planning, transport orders and packing-slip processing between ERP, WMS and EDI partners.
SAP, supplier EDI and quality
Orders and shipping confirmations between SAP and partners. Certificates, allergens and EAN data synced in real time.
Accounting, payments and credit
Bookings straight into Exact or AFAS, payment links on invoices via Mollie or Stripe, automated credit checks.
One integration layer between your systems.
The mistake we see most: ten point-to-point integrations between ten systems. Result: a spaghetti where one change ripples through five places. We design differently.
One central integration layer in the middle. Every source sends to that one point. Every receiver listens to it. Replace a vendor: you update one integration, not five.
- Mapping and transformation centralised, not in every integration.
- One place for logging, retries and monitoring.
- Adding a partner or system = one integration, no rebuild.
What changes when the integration starts running?
Concretely, in your team's day to day.
- Excel files travelling between email and folders.
- Retyping orders between webshop, ERP and accounting.
- Stock that's "roughly right" until the first complaint arrives.
- Scanning packing slips and booking them by hand.
- Every supplier with their own email format for confirmations.
- Monthly reconciliation between ERP and accounting.
- A single source of truth, synchronised across all systems.
- Order placed = order in ERP = booking created, automatically.
- Stock correct in real time, with alerts on low values.
- Electronic packing slips that handle themselves.
- One supplier portal or EDI layer that partners connect to.
- Real-time reconciliation, no more month-end surprises.
Clients on their integration project.
Snippets from long-running relationships. What they actually noticed, not the price-list quotes.
Insight has completely transformed the way we work with data: from reactive and scattered to proactive, transparent, and future-oriented.
An integration is only finished when it stops falling over.
The four things that separate a script that "kind of works" from a production integration you can rely on three years later.
Monitoring & alerting
Heartbeat checks per integration, error alerts via Slack or email, dashboards that show how it's actually running.
Retries & queues
Exponential backoff on transient errors, dead-letter queues for what gets stuck. No message lost.
Idempotency
Safe to retry on network failures. Duplicate detection ensures one order never lands twice.
Audit & traceability
Full trail per message: input, output, timing. Replayable for compliance and debugging.
When to choose bespoke?
iPaaS tools like Zapier, Make or Workato are sometimes exactly what you need. For other flows, bespoke is the sensible call. The honest trade-off.
iPaaS / no-code
Quick wins- Hundreds of pre-built connectors for SaaS tools.
- No developer needed for simple flows.
- Low upfront cost, monthly fee.
- Per-task pricing scales with your volume.
- Complex transformation or validation hits walls fast.
- Fault tolerance and debugging are limited and vendor-dependent.
- Vendor lock-in: your flows don't move easily.
Fits when: low volumes, standard SaaS tools, no business-critical flow.
Bespoke integration
On your flow- Exact fit to your data model and process.
- Full control over transformation, validation and error handling.
- You own the code and data. No vendor lock-in.
- No per-task pricing, scaling doesn't cost extra.
- Idempotency, retries, queues, audit log, production-grade.
- Higher upfront investment, longer ramp-up.
- Maintenance and evolution need to be organised (or kept with us).
Fits when: critical flow, high volume, complex transformation, or strategic ownership matters.
A sample of the systems we connect.
Vendor not in the list? No problem. If it speaks APIs, files or webhooks, we connect it.
Microsoft Dynamics
Business Central, Finance & Operations or NAV connected to your channels.
Multivers
Unit4 Multivers koppelen zodat orders, facturen en debiteuren doorstromen.
Excel
Lists of orders, stock or products? We integrate Excel directly into your systems.
GS1
Allergens, EAN codes and product images from GS1 straight into your ERP.
Mollie
Payment links on your invoice. Paid faster, less hassle.
Stripe
Payment links via Stripe. Customers pay straight from the invoice.
Adyen
Payment links via Adyen. Higher conversion on outstanding invoices.
SendGrid
CRM and mail provider in sync. Marketing without stale lists.
From first call to a running integration.
A steady rhythm that keeps you in the loop on where we are, and why. No circus of templates and standups.
System inventory
One hour, free. We map your systems, data flows and manual steps. An honest read on where the gains would be largest.
Scope & fixed-fee quote
A clear scope per integration, with impact and time. Fixed-fee so you know up front what you're looking at. No open ends.
Build, test, validate
We build on staging with test data. You see it running before it goes to production. Edge-case validation is in scope.
Cutover & go-live
Phased rollout: one partner or flow first, then broad. We guide the cutover and stay close until it settles.
Support & evolution
Monitoring, SLA response, and new requests landed in iterations. Single point of contact, no ticket-system roulette.
After go-live we stick around.
Delivering an integration isn't the end of the project, it's the real start. That's when actual production volume starts running through it, and that's when you find out where it pinches. We stay available until it settles, and structurally after under SLA.
Concretely: a single point of contact, an SLA on response, monitoring that alerts us before your partner notices, and weekly standups as long as changes are in flight.
- A single point of contact, no ticket-system roulette.
- Heartbeat monitoring and error alerts.
- Replay capability for messages that got stuck.
- Roadmap sessions twice a year for expansion.
- Documentation of data mapping that keeps up.
Frequently asked questions.
What we hear most often during scoping. Honestly answered.
What if you don't have capacity?
We're a small team, sometimes the queue runs a few weeks. Better honest up front than stuck halfway in. If it's genuinely urgent and we can't take it, we'll think along about partners who can at that point.
Wat kost een koppeling of portaal?
Dat hangt af van de stromen, systemen en schermen die meedoen. Na de gratis proces-scan krijg je een fixed-fee offerte: één vast bedrag voor een afgesproken scope. Geen uurtje-factuurtje met open eind en geen meerwerk-discussies achteraf.
Hoe lang duurt het voordat het live staat?
Een gangbare koppeling tussen twee systemen staat in 4 tot 6 weken op productie. Zwaardere trajecten, bijvoorbeeld met SAP, meerdere administraties of een datamigratie, lopen tot 8 weken of langer. Wat voor jou geldt, zie je vooraf terug in de planning.
Will it work with our current ERP, CRM or WMS?
Almost always. We've worked with Exact, AFAS, SnelStart, SAP, Oracle, Business Central, NetSuite, Lightspeed, Salesforce, Dynamics, and bespoke apps. API, file or webhook: anything with an interface, we can connect.
How does it scale with high volumes?
We build integration layers around message queues (RabbitMQ, SQS, Redis streams) and async workers. A few hundred messages per minute is standard, thousands per second is achievable if we design the architecture for it. Load and growth projections go into scope.
What if our process changes later?
We design for it from day one. Mapping configuration lives in tables or YAML, not hard-coded. A new supplier, format or field can be added by someone on your team (or us) without a release.
Is it GDPR-proof?
Ja. Encryptie at rest en in transit, EU-hosting en een verwerkersovereenkomst horen er standaard bij. We verwerken alleen de gegevens die functioneel nodig zijn en hanteren heldere bewaartermijnen.
Ready to get your systems wired together?
In a single one-hour session we look at your data flows and integrations. Then a fixed-fee quote. No surprises after.