ERP or accounting app at 100, 500 and 2,000 orders a month
What your books must track decides the system: stock across warehouses, purchasing and branches usually point to an ERP. Monthly orders decide the plan.
Connect ERPNext to your Zid store
Zid and ERPNext: every paid order and return posted to ERPNext, and each Zid location linked to its ERPNext warehouse for stock.
ERP ERPNext
ERPNext keeps stock per warehouse. Zid shows stock per location. Connecting the two means each Zid location shows the quantity in the ERPNext warehouse behind it. In the other direction, every paid Zid order is posted to ERPNext with the customer, items, tax and shipping.
How an order travels from Zid to ERPNext
Paid in Zid
The order is paid in your store and its notice reaches the app.
Customer matched
The customer is matched to their ERPNext record, or a new one is created.
Posted to ERPNext
The order is posted with the customer, items, tax and shipping, exactly once.
Read back
The order is read back from ERPNext to confirm it is there.
Back to Zid
The ERPNext document number appears as a comment on the Zid order.
Stock: each Zid location on its own warehouse
A store that sells from several branches or warehouses needs each Zid location to show what is really on the shelf behind it. So each Zid location is linked to an ERPNext warehouse, or to several regular warehouses whose stock is added together, stock flows to the location as often as every minute, and the app reads it back from Zid to confirm. A location cannot link to a group warehouse.
| Before | After | |
|---|---|---|
| Where the number comes from | A number typed into Zid by hand | The ERPNext warehouse linked to the location |
| When it changes | When someone updates it | It flows from ERPNext to Zid |
| Check | A manual look | The quantity is read back from Zid after each update |
Before setup
- Pick the data to connect: orders and returns from the Starter plan, stock from the Growth plan; price sync is set up on request.
- Your ERPNext API keys. Help getting them is available.
What syncs
Paid orders
Every paid order is posted to ERPNext with the customer, items, tax and shipping, then read back from ERPNext to confirm it is there. The same order is never posted twice.
From the Starter plan
Customers
Each customer is matched to their ERPNext record by email, then phone, or a new record is created.
Returns
Each return posts to ERPNext as one return sales invoice against the original invoice.
From the Starter plan
Stock per location
Each Zid location is linked to an ERPNext warehouse, or to several regular warehouses whose stock is added together, but not to a group warehouse. Stock flows to the location as often as every minute, then is read back to confirm.
From the Growth plan
Prices
Price sync with ERPNext is set up on request.
From the Growth plan
Document number
The ERPNext document number appears as a comment on the Zid order, as it does with every system.
Install
Install the app from the Zid App Market and choose a plan.
Data and API keys
Pick the data to connect, then enter your ERPNext API keys. Help getting them is available.
Scope of work
Approve the scope of work, which sets what is connected, including which ERPNext warehouse feeds each Zid location.
Test and go live
The link is tested on your store's orders and goes live once you approve the test report, about two weeks after install.
Questions merchants ask
My store sells from several branches. How does each branch's stock show in Zid?
Each Zid location is linked to an ERPNext warehouse. Each warehouse's stock flows to its location and is read back to confirm. Stock sync starts on the Growth plan.
How is a new branch added after go-live?
In settings, with no code. Our team links the branch's Zid location to its ERPNext warehouse, and can create the Zid location too.
Does every order create a new customer in ERPNext?
No. The customer is matched to their ERPNext record first, and a new record is created only when there is none.
Do I need ERPNext API keys?
Yes. Connecting your ERP needs its API keys, and help getting them is available.
What happens if an order fails to sync?
The assistant in the app can retry the sync once you approve, and a retry never creates a duplicate order in ERPNext.
Related comparisons
- ERP integration or manual entry for Zid orders?Manual entry needs no setup but grows with every order. Integration posts each paid order and return to your ERP and checks it. Point by point.
- ERP or accounting app for a Zid store?An accounting app covers invoices, VAT and the ledger. An ERP adds stock across warehouses, purchasing and branches. The app works with both.
- Spreadsheet or ERP for a Zid store?A spreadsheet starts fast but runs on manual entry. An ERP connected to Zid receives orders and returns and keeps stock in step. Point by point.
- Zid's built-in reports or a connected ERP?Zid's reports explain how the store performs: sales, products and stock. A connected ERP keeps the books: revenue, returns and stock per warehouse.
Related articles
Selling across the Gulf: four VAT markets, three rates
Four Gulf states apply VAT: 15% in Saudi Arabia, 10% in Bahrain, 5% in the UAE and Oman. Qatar and Kuwait publish no VAT rate as of October 2026.
From install to live in about two weeks: five steps
You go live about two weeks after install, in five steps: plan, data and system, scope of work, a test on your own orders, then a test report you approve.
Other systems
- ERPOdooOdoo 18 and 19: orders, returns and stock between Zid and Odoo.
- ERPMicrosoft Dynamics 365 Finance and OperationsDynamics 365 Finance and Operations: orders and stock between Zid and the ERP.
- AccountingWafeqWafeq (accounting): orders, returns and stock between Zid and your books.
- Public APIAny system with a public APIAnother system with a public API: the link is built for you on request.