From Zid order to ERP in six steps
A paid Zid order takes six steps: notice, customer, posting, read-back, the document number in Zid, then status with Dynamics 365 Finance and Operations.
What happens to a paid Zid order before it shows up in your ERP?
It goes through six steps. The paid-order notice arrives, the order gets its customer in the ERP, and the order is posted to the ERP and read back to confirm it. Then the ERP document number appears as a comment on the Zid order, with every system. With Dynamics 365 Finance and Operations, the order status in Zid can be updated too.
The six steps
Here is one paid order, followed from payment in Zid to the ERP document number on that same Zid order, and then to its status update with Dynamics 365 Finance and Operations.
Paid in Zid
The order is paid in your Zid store and its notice reaches the app.
Customer in the ERP
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.
Posted to the ERP
The order is posted with the customer, items, tax and shipping, exactly once.
Read back
The order is read back from the ERP to confirm it was posted.
Document number in Zid
The ERP document number appears as a comment on the Zid order with every system.
Status in Zid
Updating the order status in Zid is available with Dynamics 365 Finance and Operations, and is switched on during setup.
Steps 1 to 4 are the core of every connection between Zid and an ERP. Steps 5 and 6 bring information from the ERP back to Zid: step 5 with every system, step 6 with Dynamics 365 Finance and Operations only.
1. The paid order arrives
The path starts when the order is paid in Zid. Zid sends the order notice, and the app reads it. From that point the app starts working on the order.
2. The customer in the ERP
Before posting, and 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.
With Odoo, ERPNext and Wafeq, the app looks for the customer’s record in your ERP and creates a new one if it finds none. With Dynamics 365 Finance and Operations, orders post under one customer account chosen during setup.
This comes first because an ERP order belongs to a customer.
3. The order is posted to the ERP
The order goes into the ERP with four parts: the customer, the items, the tax and the shipping.
The same order never posts twice. Each Zid order has one matching order in the ERP, even if the order notice arrives more than once.
4. The order is read back
After posting, the app reads the order back from the ERP.
5. The document number in Zid
The ERP document number appears as a comment on the Zid order with every system. Once the document is created in the ERP, the app adds a comment to the Zid order that reads “ERP Sales Order:” followed by the document number. You see the matching document number on the order itself in Zid, and you can use it to find the order in the ERP.
The comment is on by default and can be turned off for your store. If the comment fails, the order in the ERP is not affected.
6. The status in Zid
Updating the order status in Zid is available with Dynamics 365 Finance and Operations, and is switched on during setup. Once it is on, the app checks the sales order in Dynamics 365 Finance and Operations every hour. When the sales order shows “Invoiced”, the Zid order moves to the status chosen during setup, which is “delivered” by default.
With other systems, the order status in Zid is not updated from the ERP.
What you see in Zid and in the ERP
The table puts the same order in both places, row by row.
| In Zid | In the ERP | |
|---|---|---|
| Customer | The customer who paid in your store | The existing customer record or a new one, or one customer account chosen during setup, depending on your ERP |
| Order | The paid order in your store | One order with the customer, items, tax and shipping |
| Document number | The ERP document number as a comment on the order, with every system | The order's document number in the ERP |
| Status | Updated after invoicing with Dynamics 365 Finance and Operations, once switched on during setup | The order invoiced in the ERP |
The numbers
These figures come from Zid Integrations data.
- posted within seconds of reaching us
- Each order
- orders delivered to ERPs
- Over 14,000
- lost orders
- Zero
Questions merchants ask
What if the order notice arrives more than once?
Even if the order notice arrives more than once, or a sync is retried, the ERP holds one order.
What about a return after the order is posted?
With Odoo, ERPNext and Wafeq, a return posts to the ERP as a credit note. The rule is fixed: one credit note per return.
What if a sync fails?
If an order fails to sync, the assistant in the app can retry it once you approve. A retry does not create a duplicate order in the ERP.
What about stock?
Stock has its own flow, separate from orders, from your ERP warehouses to each Zid location.
Systems the app works with
The app works with Odoo 18 and 19, Microsoft Dynamics 365 Finance and Operations, ERPNext, Wafeq, and any system with a public API. Our team does the setup with you, and you go live in about two weeks, after a test report you approve.
Plans
Posting orders and returns to your ERP starts on the Starter plan, which covers 100 orders a month. Growth covers 500 orders and adds stock and the grow-sales tools; price sync is set up on request. Business covers 2,000 orders and adds priority support and multi-warehouse routing, which sends each order to the warehouse that serves the shopper’s ship-to city. Trials run 7 days on monthly billing and 30 days on yearly billing. Prices are on the app’s page in the Zid App Market.
To see these six steps run on your own store’s orders, install the app from the Zid App Market.
