Dutch SMEs live in Exact Online or AFAS. Their website still lives in WordPress or WooCommerce. The gap shows up as manual order entry, stale stock, and finance chasing CSVs. A durable WordPress ↔ ERP integration is boring infrastructure—and high ROI.
Typical sync objects
- Customers / debtors
- Orders and invoices
- Articles and stock levels
- Prices and VAT codes
Integration patterns
- Woo → ERP: paid orders create sales entries; failures retry with alerts.
- ERP → Woo: nightly or webhook stock/price updates.
- Forms → ERP: B2B quote requests become accounts/opportunities where supported.
Why Zapier-only setups struggle
- Partial failures without a dead-letter view.
- VAT/price list edge cases.
- Rate limits during campaigns.
- No clear ownership when Exact validation rejects a line.
What “done” looks like
- Idempotent order push (ERP external id stored on the Woo order).
- Structured error emails to ops, not only to developers.
- Staging Exact/AFAS environment for UAT.
- Runbook for token expiry and administration changes.
GDPR / AVG
Customer records move between processors. Update your processor list, minimise fields, and define deletion—erasing a WP user may require anonymising the ERP link, not a blind cascade delete.
HostHob builds these integrations in PHP (WordPress/Laravel) for NL/EU teams that want ownership without a twelve-vendor iPaaS bill.
Need this built? HostHob ships production integrations and Marketplace-ready apps from Rotterdam. See our services or Plan a WordPress–ERP integration.