Many Zid merchants don't sell through the online store alone; they have one or more branches, and maybe a separate warehouse for online orders. When each runs on its own numbers, the store sells an item the branch sold an hour ago, and the apologies to customers begin.
Why Odoo in the middle?
Odoo brings inventory, point of sale and accounting into one database. Connected to Zid, the quantity shown in the store is calculated from actual stock in Odoo, and branch sales and online sales draw down the same balance.
Three decisions before you integrate
- Which warehouses or branches feed the online store: all of them, or one dedicated warehouse?
- Do you keep a safety buffer, showing less than the real balance online for fast-moving items?
- Where does an online order ship from: the nearest branch, or always the main warehouse?
What moves between the two systems
- Zid orders enter Odoo as sales orders, with the customer and shipping address.
- Available quantities flow back from Odoo to Zid after every stock move.
- Order status updates in Zid as the order is picked and shipped.
- Payments are recorded for reconciliation against the gateway's statements.
- Point-of-sale sales in branches draw down the same stock directly.
How the connection works
Zid provides an API and notifications when orders are created or updated. The connector uses them to bring orders into Odoo and to push updated quantities back to the store. The quality of the integration still depends on two things: consistent product codes, and an error log that a named person reviews.
Before go-live
- A physical count in every branch and warehouse, because the integration moves numbers as they are, right or wrong.
- Aligned product codes and variants between Zid and Odoo.
- Sell the same item in a branch and online at the same time to confirm there's no double sale.
- Test returning an online order at a branch, if you allow it.
An integration alone doesn't fix stock; a clear decision about where quantities come from and how orders ship does, and the integration turns that decision into automation. That's where we start at MUNSAQ, before writing a line of code.
