- Zid runs the storefront, the selling and its own delivery network. That part is solved.
- Odoo runs what sits behind it: stock, purchasing, accounting, manufacturing and branches, on one ledger.
- The integration is partner-configured rather than a one-click marketplace install. A Zid partner app, API credentials, then mapping and go-live.
- Barlina went from three working days of manual processing at every month end to an order reaching the system in under 90 seconds, at 2,500 orders a day in peak season.
- Your store stays on Zid. Not one customer moves.
What your Zid dashboard already does well
Zid is strong at the part your customer sees and the part that gets the parcel to the door. The catalogue, the cart, the Saudi payment methods your buyers already trust, its own delivery network, and a dashboard your team learned quickly. Most stores run their first years entirely on it and have no reason to change.
This guide is not about replacing any of that. It is about the point where Zid is doing its job and something behind it is not. If you are still deciding whether the question applies to you at all, does your store need an ERP covers it from the start.
Where a growing Zid store stops being enough
The symptoms arrive in a fairly predictable order, and they are operational before they are financial.
First, stock stops agreeing with itself. The store shows availability the warehouse cannot honour, and somebody is refunding an order that should never have been accepted.
Then the retyping starts. Orders get pulled out of the dashboard and entered somewhere else, and the month is rebuilt by hand because that is faster than reconciling it properly.
Then the questions stop having answers. What did we actually make on this product, after packaging, delivery and the payment fee? That needs a spreadsheet, and the spreadsheet is a week old.
Then purchasing turns into memory. Reordering happens because someone noticed an empty shelf, not because the system knew the lead time and the run rate.
None of these is Zid failing. They are the same problem wearing different clothes: one fact living in more than one place.
What this looked like at Barlina
Barlina is a Saudi luxury womenswear brand running an administrative office, a factory, distribution warehouses and a store on Zid. Before the systems were connected, orders were processed by hand and reconciled once a month, and that reconciliation took three working days at every month end. With more than 5,000 core products, over 600 orders on an ordinary day and 2,500 at peak, the numbers management needed were locked inside a closing cycle that had already aged by the time it finished.
After the operating cycle moved onto one system, with accounting, sales, purchasing, manufacturing and barcode connected to each other and the Zid store integrated directly, an order or a product reaches the system in under 90 seconds. The full story is in the Barlina case study.
What syncs between Zid and Odoo
An integration is not one switch. It is a set of movements, each with a direction and a timing, and knowing which is which is most of understanding whether the setup will hold.
One distinction first, because it is where most confusion starts. Setting the connection up is a one-time import: your existing catalogue, customers and orders are pulled out of Zid and into the system so both sides start from the same records. Everything below describes what happens afterwards, once the system is running. The two are different jobs and they run in different directions.
| What syncs | Direction | When | Why it matters |
|---|---|---|---|
| Products and variants | Odoo to Zid | On change | One product master and one code, so the store and the warehouse describe the same thing |
| Stock quantities | Odoo to Zid | Near real time | Stops the store selling what the warehouse has already shipped |
| Orders | Zid to Odoo | On creation and status change | The order becomes a sales order, a delivery and a draft invoice without anyone typing it |
| Customers | Zid to Odoo | On first order | One customer record across the store, the branch and wholesale |
| Payments and method | Zid to Odoo | With the order | Reconciliation by gateway, so settlements match without a spreadsheet |
| Shipments via Zid's network | Both directions | On status change | Zid's own network carries the parcel, and the status moves both ways so fulfilment reads the same wherever your team is working |
| Returns | Zid to Odoo | On creation | Credit note and stock return in one step instead of two systems |
| E-invoice | Odoo to ZATCA | On confirmation | One compliant invoice per order, matched to the order and the payment |
Read the direction column twice. Once the system is running, it is the source for what you sell, products and stock, and the store is the source for what happens when someone buys: orders, customers, payments and returns. The shipments row is the one that is particular to Zid, because the delivery network stays Zid's and the status has to be readable from both ends. Odoo's inventory application holds the single ledger every channel reads from, and manufacturing is what makes the Barlina shape possible, where what you sell is also what you make.
How the integration is actually set up
This is where a Zid store differs from a storefront with a marketplace connector, and it is worth being plain about it rather than implying a one-click install. Zid does not publish a ready-made Odoo app in its app market. What it publishes is the API and the developer path, so the connector is built by a partner against Zid's own interfaces, authorised with OAuth using credentials from an app registered in the Zid App Market.
- Create a Zid partner app and obtain the API credentials.
- Connect in Odoo, import the catalogue, customers and orders, and map the records.
- Enable the sales workflow, run test orders end to end, then go live.
Step two is the one that takes the time. That import is the one-time move described above, and the mapping is only as good as the catalogue on both sides, which is why the products row sits at the top of the table. The Zid integration page sets out what the connection covers in one place.
What changes in the first month
The visible change is small and the operational change is not. Your team keeps taking orders in Zid. What stops happening is the second entry: nobody retypes an order, nobody rebuilds the month by hand, and nobody argues about which stock number is the real one.
The test is the first monthly close. Run it with the partner on call, then compare what the reports say against what the team expected them to say. Where those two disagree is where the configuration needs a second look, and finding that in month one is the whole point of doing it properly. Barlina is the version of this that worked: the three-day close stopped being a close at all.
If you want to see whether your own order flow is at that point, the Zid and Odoo integration is the place to start.
