What "zero lost orders" means
Every paid order that reached us is in your ERP. Behind that record: a read-back after posting, no duplicates, and a retry of a failed sync once you approve.
What does “zero lost orders” mean for a store that connects Zid to an ERP?
It means every paid order that reached us is in your ERP. Behind that record are three checks in the app: a read-back after posting, protection against duplicates, and a retry of a failed sync once you approve it.
A lost order, from your side
A lost order is one your customer paid for in your Zid store that left no trace in your ERP. It shows up in your store’s sales and never makes it into your books. The order carries its tax and shipping, so those go missing from the books too.
You usually find it at reconciliation. Zid sales say one thing, your ERP says another, and someone has to explain the gap. Each such order means a search in the store and a manual entry in the ERP before you close the books.
So “zero lost orders” starts with one question. Did every paid order reach the ERP? The app answers it with the checks below.
The checks behind the record
The order arrives
The paid-order notice reaches the app from Zid.
Posted to the ERP
The order is posted with the customer, items, tax and shipping.
Read back
The order is read back from the ERP to confirm it is there.
No duplicates
If the order notice arrives again, the ERP still holds one order.
Retry
If a sync fails, the assistant in the app can retry it once you approve.
Steps 1 and 2 are the posting itself. Steps 3 to 5 keep the record. They confirm the order is there, keep it to one order, and retry when a sync fails.
1. The order arrives and is posted
It starts when the order is paid in Zid. The order notice reaches the app. Depending on your ERP, the customer is linked to their ERP record or a new record is created, or orders post under one customer account chosen during setup.
Then the order is posted to your ERP with the customer, items, tax and shipping. That is where sending ends and checking begins.
2. The read-back
Sending an order to the ERP is one step. Confirming it landed is another. So after posting, the app reads the order back from the ERP, and the confirmation comes from the ERP itself. It runs on every paid order.
| Send only | Send, then read back | |
|---|---|---|
| After sending | No further step | Reading the order from the ERP |
| Confirmation comes from | The send going through | The ERP itself |
| What it proves | The order was sent | The order is in the ERP |
The app reads every paid order back from the ERP after posting it.
The two columns are the difference between “the order was sent” and “the order is in the books”. Reconciliation needs the second.
3. No duplicates
Even if the order notice arrives more than once, the order is not posted again, and each Zid order keeps exactly one matching order in your ERP. The same holds for an order whose sync is retried.
A duplicate throws off reconciliation from the other side, with more sales in your books than in your store. So the record has two conditions. Every order is in the ERP, and it is there once.
4. A retry, once you approve
If an order fails to sync, the assistant in the app can retry it once you approve. The retry does not create a duplicate in the ERP, because the same order never posts twice.
What you see in Zid and in the ERP
Once you are live, here is what you see in both places:
- In the ERP: one order for each paid Zid order, with the customer, items, tax and shipping. Depending on your ERP, the customer is linked to their record or a new one is created, or orders post under one customer account chosen during setup.
- For a return: with Odoo, ERPNext and Wafeq, one credit note per return in the ERP.
- In Zid: the ERP document number appears as a comment on the Zid order with every system. Updating the order status in Zid is available with Dynamics 365 Finance and Operations, and is switched on during setup.
Questions merchants ask
What if the order notice arrives more than once?
The ERP still holds one order.
What if a sync fails and is retried?
Once you approve, the assistant in the app can retry it. The ERP ends up with one order and no copy.
What about a return after the order is posted?
With Odoo, ERPNext and Wafeq, the return posts to the ERP as a credit note. The rule is fixed: one credit note per return.
Will I see the order status in Zid?
The ERP document number appears as a comment on the Zid order with every system. Updating the order status in Zid is available with Dynamics 365 Finance and Operations, and is switched on during setup. The status updates once the order is invoiced in Finance and Operations.
The record in numbers
These figures come from Zid Integrations data.
- lost orders
- Zero
- orders delivered to ERPs
- Over 14,000
- uptime
- 99.9%
“Zero lost orders” is a record in Zid Integrations data. The checks behind it are the read-back, the duplicate check and the retry once you approve.
Systems and going live
The app works with Odoo 18 and 19, Microsoft Dynamics 365 Finance and Operations, ERPNext, Wafeq, and any system with a public API.
The connection is tested on your store’s orders before you go live. You go live once you approve the test report, about two weeks from install.
Posting orders and returns to your ERP starts on the Starter plan, which covers 100 orders a month. The details and prices of each plan are on the app’s page in the Zid App Market.
To have these checks run on your own store’s orders, install the app from the Zid App Market.
