
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.
Your system is not on the list? If it has a public API, the link can be built for you on request, and the scope of work sets what it covers.
Public API Any system with a public API
The app works today with Odoo 18 and 19, ERPNext, Microsoft Dynamics 365 Finance and Operations and Wafeq. If your store runs on another system with a public API, the link can be built for you on request.
The link needs a documented public API, and API keys that let the app reach the system’s data. What the link covers depends on what the API allows, such as creating orders and reading stock per warehouse, and the scope of work sets what it covers.
Name the system
The system, its API documentation, and the data to connect.
Scope of work
What is connected and how long the build takes, approved by you.
Build and test
The link is built, then tested on your store's orders.
Go live
The link goes live once you approve the test report.
Paid orders
Each paid order posted with the customer, items, tax and shipping, then read back to confirm it is there, never twice.
Depending on what the API allows; set in your scope of work
Returns
Whether the link covers returns is set in your scope of work.
Depending on what the API allows
Stock
Stock in each warehouse sent to its Zid location, then read back to confirm.
Depending on what the API allows; from the Growth plan
Install
Install the app from the Zid App Market and choose a plan.
System and data
Name the system and the data to connect, and share its API documentation and keys. Help getting them is available.
Scope of work
Approve the scope of work, which sets what is connected between Zid and the system.
Build and test
The link is built, then tested on your store's orders.
Go live
The link goes live once you approve the test report.
A documented programming interface that a system's vendor offers its customers, so another app can read and write data in the system using API keys the system issues.
It depends on the system and what its API allows, and the timeline is in the scope of work before you approve it. With the systems listed today, you go live about two weeks after install.
The link is built on request for systems with a public API. What it covers depends on the data the API lets the app read and write.

What your books must track decides the system: stock across warehouses, purchasing and branches usually point to an ERP. Monthly orders decide the plan.

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.

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.