Short answer: integration errors usually come from the meaning of the data, not from the connection
Connecting an ERP to an e-commerce site can take a few days technically; problems show up later, as the same order arriving twice, an out-of-stock product being sold, or an invoice amount that differs from the payment. Below are eight common mistakes, each with its symptom and its remedy. This list is a checklist compiled with our own judgment; it is not based on error logs from Besh's completed projects. The technical behaviours come from Shopify's webhook documentation, its order webhook guide and its inventory states page; look for the equivalent in your own platform's documentation.
| # | Mistake | Symptom | Remedy |
|---|---|---|---|
| 1 | Processing the same event twice | Duplicate order and shipment in the ERP | Deduplicate by event ID |
| 2 | Assuming events arrive in order | A new state is overwritten by an old one | Check timestamps, treat each event's current state as the truth |
| 3 | Trusting events alone, without reconciliation | An order silently disappears | A regular comparison job |
| 4 | Doing the work while receiving the event | Timeouts, resends | Save and acknowledge first, do the work in the background |
| 5 | Treating physical stock as "sellable stock" | A sold product is not on the shelf | Calculate sellable stock separately |
| 6 | Mixing VAT-inclusive/exclusive and rounding | A few cents of difference between invoice and payment | One rule, one rounding point |
| 7 | Leaving returns and cancellations out of the integration | Stock does not return, the invoice is not corrected | Design the return flow from the start |
| 8 | Matching products by name | The same product has two records, wrong variant | An immutable matching key |
1. Processing the same event twice
Webhook systems (automatic calls the platform makes to your address when something happens) can deliver the same event more than once. Shopify's documentation accepts this and recommends the X-Shopify-Webhook-Id header for deduplication: store the IDs you receive and skip a delivery you have already seen.
Symptom: the same order is opened twice in the ERP and the warehouse sees two shipment orders. Remedy: put a unique constraint on the event ID in a table; a second insert attempt should end as "already processed", not as an error. Also deduplicate the order's counterpart in the ERP by order number, so you are protected from both sides.
2. Assuming events arrive in order
Shopify states that it does not guarantee ordering within a topic or across different topics for the same resource: for example, a product's "updated" event can arrive before its "created" event. The documentation recommends using the X-Shopify-Triggered-At header or the updated_at field in the payload to order events. The order webhook guide adds that every payload carries the full current state, so you should treat the latest delivery as the truth instead of merging earlier events.
Symptom: an order's status goes back from "shipped" to "awaiting payment". Remedy: compare the timestamp of the incoming record with the last update in the ERP; if it is older, do not apply it.
3. Trusting events alone, without reconciliation
Shopify's documentation says plainly that your app should not rely on receiving webhooks: delivery is not always guaranteed, and handlers can fail or downtime can occur. The recommended method is a reconciliation job that periodically pulls data from the platform and compares it with your own records; many queries support an updated_at filter.
Symptom: weeks later, the complaint "this order is not in the ERP". Remedy: a daily job pulls the orders updated since its last run, compares them with the ERP, writes any difference to a queue and alerts a person. The data this job needs should live in the order record itself; data that exists only in "what we were told" cannot be recovered after an outage.
4. Doing the work while receiving the event
The same order webhook guide says to acknowledge receipt quickly with a 2xx and process the payload asynchronously. If the reply is late, the sender counts the delivery as failed and retries, which opens the door to the double processing in item 1. There is a trap in the other direction too: if you reply without a durable record and the process crashes in between, the event is lost.
Remedy: write the event to a durable queue or table first, then return 2xx, and let a separate worker that reads from the queue do the ERP write. If the ERP does not respond, the job waits in the queue, is retried and, after a set number of attempts, lands in an "error queue" and notifies someone.
5. Treating physical stock as "sellable stock"
Shopify's inventory states page splits a location's stock into three parts: available (sellable), committed (set aside for orders and not yet fulfilled) and unavailable (held back: damaged, in quality control, safety stock). On hand is the sum of the three. The "current stock" field in your ERP may correspond to the on-hand total, depending on the ERP you use; sending the on-hand total to the website shows committed and unavailable units as "sellable" too.
Symptom: the site says in stock, the product is not in the warehouse; the order is cancelled and the customer complains. Remedy: define the value sent to the site explicitly. Our suggestion: sellable stock = physical stock in the ERP − quantity set aside for open orders − safety stock. This formula is our interpretation; the field names may differ in your ERP, so first settle in writing with your ERP company which field means what. In a multi-warehouse setup, calculate per warehouse.
6. Mixing VAT-inclusive/exclusive and rounding
In sales to consumers, the price is shown as the cash price including all taxes under the Price Label Regulation. If your ERP keeps list prices exclusive of VAT and the site shows them as they are, the customer meets an unexpected amount at the payment step. The reverse happens too: if you take a VAT-inclusive price from the site and write it to the ERP as "exclusive", VAT is calculated a second time on the invoice.
Symptom: a few cents of difference between the amount paid and the invoice amount. Remedy: write in a table which field is VAT-inclusive and which is exclusive. Decide whether you round per line or on the order total, and do it in the same place on both the site and the ERP. If the VAT rate varies by product, send the rate with the product. Involve the accounting team in the invoice amount from the start.
7. Leaving returns and cancellations out of the integration
For goods, under the Distance Contracts Regulation the consumer can withdraw without giving a reason within fourteen days starting on the day they receive the goods, and the seller refunds the payments within fourteen days after the return process. If the integration was built only as "the order goes to the ERP", a return pulls the two systems apart: the site refunds the payment, but stock does not come back in the ERP and the sales invoice is not corrected.
Symptom: months later, a gap at the inventory count, and the revenue of a returned order still visible in accounting. Remedy: define the return states ("requested", "goods reached the warehouse", "payment refunded") as separate events in the integration. Put a rule on whether the returned product enters sellable stock or inspection stock (item 5). Settle the invoice correction method with your accountant.
8. Matching products by name
What says "the same product" in two systems cannot be the name: names change, spellings differ, and a variant (size, colour) gets lost under one name. Remedy: choose an immutable matching key for each product and variant (stock code or barcode) and verify that it is unique on both sides. Keep an "unmatched" list: if a new product enters the site before it is added to the ERP, it should not vanish silently but become visible to someone. Changing the key later is far more expensive than choosing it correctly on day one; this is also our view.
Test list before the integration goes live
- ☐ Send the same webhook twice: is a single record created in the ERP?
- ☐ Send an old update afterwards: does the state go backwards?
- ☐ Shut the ERP down, place an order, start it again: is the order processed from the queue?
- ☐ Send two orders while one unit is left: is the second handled correctly?
- ☐ Build a cart with one VAT-inclusive and one VAT-exclusive product: are payment, order and invoice amounts the same?
- ☐ Return an order: do stock, payment and invoice update together?
- ☐ Add an unmatched product: does it raise an alert?
We covered extra checks for campaign periods in our pre-Black Friday e-commerce infrastructure checklist, and ERP connection methods on the dealer portal side in connecting a dealer portal to an existing ERP.
Frequently Asked Questions
Should the ERP and e-commerce integration be real time?
Not for every kind of data. Orders and stock decreases should be near real time; data such as price list updates or product descriptions can be moved at intervals. Write in a table which data moves how often, at the start.
Should I build the integration with a ready module or custom software?
If a ready connection exists for your ERP and platform and meets your need, it is usually faster. But ask how the module handles the eight items above: if it has no deduplication, reconciliation, error queue or return flow, custom development may be needed. See our e-commerce and automation software services.
Is connecting my accounting program to the e-commerce site enough, or do I need an ERP?
If the order, stock and invoice flow is simple, an accounting program can be enough. If you need multiple warehouses, production or dealer-based pricing, an ERP becomes more suitable. For this decision, look at our accounting software service and the 5-year ERP cost calculation.
Will I lose orders when the integration breaks?
Not if you have a queue, retries and a reconciliation job; the order stays on the platform and is processed once the integration is fixed. Without one of these, the risk of loss is real; ask whether the quote includes these three.
If you would like to define your integration need together, you can get in touch.
Sources: About webhooks (Shopify developer documentation), Order webhooks (Shopify developer documentation), Understanding inventory states (Shopify Help Center), Price Label Regulation, consolidated text (Lexpera), Law No. 6502 and secondary legislation, Distance Contracts Regulation (Ministry of Trade Consumer Portal)
Cover photo: Unsplash