Case study collection
ERP & Exact Online Integration
Where Shopify and Exact Online disagree about what is in stock, and what it takes to make them agree.
04
Case studies
Connectors handle standard sync well: orders out, products in, stock levels updated. Each of these four engagements began where that stops — at the point where the correct number has to be decided rather than copied.
Exact deducts stock when an order ships, so between picking and dispatch the ERP still counts it as present. The reservation engine subtracts what the warehouse has already committed before any figure reaches the storefront. It has to happen on that side, because Shopify computes its own committed state from orders and transfers and will not let the Admin API write to it.
The pre-order system drives availability from Exact's incoming-stock data across 1,500+ SKUs, at SKU level rather than product level, reconciling on a 30-minute schedule. The order availability dashboard splits every line into available, incoming and unavailable quantities, because a line for ten units with three in stock is neither in stock nor out of it. The BI dashboard turns the same order history into revenue, region and reorder reporting over 1,400+ customer records.
Exact's constraints shape all of it. Parallel calls are not permitted, most reads return 60 records per request, and ten errors in an hour on one endpoint blocks the API key. Throughput becomes a queue design problem rather than a concurrency one, and proving that last night's sync was complete has to be a feature rather than an afterthought.
The engineering behind this work is Shopify ERP and CRM integration.
Your store next
Most engagements start with the same question.
What is actually slowing this store down, and is it worth fixing? Send us the URL and we will answer it honestly.