Integrations, APIs & backend

Systems that talk to each other, without retyping.

Store to Exact Online, CRM to scheduling, ERP to customer portal: we build integrations and backends that move data reliably, with error handling, logging and monitoring. One integration live in two weeks.

What we do

Integrations and backend development that keep working

Retyping is the most expensive software you own. Every order entered into the books by hand, every address typed twice, every stock count that doesn’t match: it costs hours and creates errors. A good integration removes that work and keeps your data true in one place.

We build integrations through the official APIs of Exact Online, AFAS, Moneybird, Twinfield, Shopify, WooCommerce, Lightspeed, HubSpot, Salesforce, Microsoft 365 and dozens of industry systems. Where there’s no API, we work with EDI, Peppol, SFTP exchange or controlled browser automation.

The difference from a Zapier flow is in the details: queues that don’t lose orders when a system is briefly down, retries, duplicate checks, a log you can read yourself and alerts before you see the problem. That’s backend work, and that’s exactly our craft.

Integration layer Plate 07 · INTEGRATIONS, APIS & BACKEND
  • 2 wks first integration live
  • 99.9% availability through queues and retries
  • 40+ systems we have integrated with
  • 0 retyping

Components

8 components

What you get.

01

E-commerce integrations

Shopify, WooCommerce, Magento or Lightspeed connected to accounting, inventory, shipping and marketplaces such as bol.com and Amazon.

02

Accounting and ERP

Exact Online, AFAS, Moneybird, Twinfield, SAP Business One and Microsoft Dynamics: orders, invoices, debtors and stock in sync automatically.

03

CRM and marketing

HubSpot, Pipedrive, Salesforce and Klaviyo connected to your website, portal and administration so sales and marketing see the same customer.

04

Custom APIs

Your own API for your product or platform, documented with OpenAPI, secured with OAuth and ready for partners and apps.

05

Integration layer and middleware

One layer between all your systems, with queues, transformations, logging and a dashboard. Add a system, and you connect it once.

06

Backend development

Node.js and TypeScript backends with PostgreSQL, background jobs, webhooks and scalable architecture, for apps, portals and platforms.

07

Process automation

Workflows in n8n, Make or custom code that replace manual steps: from order confirmation to reminder to reporting.

08

EDI, Peppol and legacy

E-invoicing via Peppol, EDI messages with large customers and exposing older systems without replacing them.

Delivered

  • Working integration or backend
  • Data mapping document
  • Queues, retries and error handling
  • Log and monitoring with alerts
  • Test environment with real data
  • OpenAPI documentation
  • Handover and training
  • Management plan (optional)

How we work

→ Process

How an engagement runs.

  1. 01

    Data mapping

    We map which data comes from where, where it needs to go and which system is the source of truth in conflicts.

  2. 02

    Build

    Integration or backend in TypeScript with queues, retries and logging. Every step has tests with real data from your systems.

  3. 03

    Test with real data

    We run in a test environment with copies of your administration until the numbers match to the cent.

  4. 04

    Go-live

    Phased launch: read first, then write. Monitoring and alerts are on before the first real order flows.

  5. 05

    Management

    APIs change. With a management plan we keep integrations running, update versions and resolve incidents before you notice them.

Why RABZI

Why RABZI for this work.

01

Official APIs, no hacks

We work through certified integrations and the official partner programs of Exact, AFAS and Shopify. More stable and future-proof.

02

Built for outages

Systems go down. Our integrations buffer, retry and report, so no order disappears.

03

Readable log

Every sync can be traced: what, when, why. You don’t have to call us to know what happened.

04

Fast, with a fixed price

One integration from €3,950, live in two to four weeks. An integration layer for three systems from €9,500.

05

Yours

Code, documentation and access are in your name. No dependency on a tool that gets more expensive next year.

Pricing

→ Pricing

Pricing for integrations, APIs & backend.

Fixed prices, excl. VAT. Extra work only after approval.

Launch from€3,950

One clear goal, sharply executed. The entry level you keep building on.

  • One integration (e.g. store ↔ Exact Online)
  • Error handling & logging
  • Documentation
  • Monitoring
  • 30 days of aftercare
Request a quote
Flagship from€24,500

For platforms, multiple brands or markets, and projects where nothing is standard.

  • Middleware / iPaaS
  • EDI & Peppol
  • Exposing legacy APIs
  • High volumes & SLA
  • Ongoing management
Request a quote

Work

→ All work

Relevant work

Fleet control · −32% · 98.4% · 1,240 · 14 wks Plate 01 · FLEET CONTROL

Illustrative caseTransport company, Rotterdam · 2025

Real-time planning platform for 140 vehicles

−32% empty kilometers

Orders · 0% · +41% · 14,000 · 11 wks Plate 02 · ORDERS

Illustrative caseRestaurant group (6 locations), Utrecht · 2025

Commission-free ordering and reservation platform

0% commission on owned orders

Work orders · −6 h · 100% · 12 → 2 · 8 wks Plate 03 · WORK ORDERS

Illustrative caseInstallation company (35 technicians), Brabant · 2025

Work-order and planning app connected to Exact

−6 h paperwork per technician per week

Frequently asked questions

Questions about integrations, APIs & backend.

01What does it cost to build an integration?

A single integration, for example store to Exact Online, costs from €3,950 excl. VAT and is live in two to four weeks. An integration layer connecting three systems starts at €9,500. Middleware with EDI or Peppol for high volumes starts at €24,500. Management is available from €450 per month.

02Can you connect my store to Exact Online or AFAS?

Yes. This is one of the integrations we build most: orders and customers into accounting, payments and credit notes back, stock and prices in sync. We work through the official APIs and know the quirks of VAT codes, shipping costs and discounts.

03Why not just use Zapier or Make?

For simple, low-volume flows that’s fine and we recommend it. Once orders, money or stock are involved, you want queues, duplicate checks, a log and no subscription that grows with your volume. Then we build a dedicated integration, often cheaper within a year.

04What happens if one of the systems goes down?

The integration puts messages in a queue and retries with increasing intervals. Nothing is lost. If a system stays unreachable for long, you and we get an alert. As soon as it’s back, the backlog catches up automatically.

05Can you integrate a system without an API?

Usually yes. We use exports and imports via SFTP, email processing, database access or controlled browser automation. We’ll tell you honestly if an integration is too fragile to build on.

06How long does it take to build an integration?

A standard integration between two known systems: two to four weeks including tests with real data. An integration layer for multiple systems: six to eight weeks. Lead time mostly depends on how quickly we get access to the systems and a test administration.

Knowledge

→ All articles

Keep reading

Reply < 1 business day · Available for new projects

Which systems need to talk to each other?

Name the two systems and what happens manually today. Within one business day you’ll know whether it can be done, what it costs and when it goes live.

info@rabzi.nl · ...