A web shop, ERP and accounting that talk to each other
Orders re-typed into three systems, replaced by a robust, event-driven integration.
- Client
- Typical client: online retailer, 10–30 employees
- Duration
- Typically 6–10 weeks
This is an illustrative example of a typical engagement, not a description of a specific client.
The challenge
Every web-shop order is copied by hand into the ERP, and the invoice is created manually in the accounting system. It takes time, causes typing errors and builds backlogs in busy periods.
- Several minutes of manual work per order
- Errors in addresses, product codes and prices
- No overview of where an order is
- Campaigns create a backlog lasting days
How we solve it
- 01
Discovery
We map the data flow, the fields that must match and who owns which data.
- 02
Events and a queue
The web shop emits one event per order. A queue receives it, so nothing is lost if the ERP is down.
- 03
Reliable delivery
Retries with increasing back-off, idempotency (no duplicate orders) and a clear "waiting" state.
- 04
Monitoring
Dashboards and alerts on queue depth, error rate and latency – so you see problems before customers do.
Before
- Orders copied by hand
- Errors found by the customer
- Backlog during campaigns
- No visibility of status
After
- The order reaches ERP and accounting in seconds
- Validation before data moves on
- The queue absorbs peaks, no order lost
- Real-time overview and alerts
Typical impact
- Manual entry typically disappears for standard orders
- Fewer errors, because data is entered only once
- Staff spend their time on customers instead of copying
- Operational problems are spotted before customers notice
Technology
Recognise the challenge?
Tell us what it looks like on your side and you’ll get a concrete proposal for the next step.