An Arabic-first online store on Odoo, or your existing Salla or Zid store, wired into one stock pool, ZATCA invoicing and the back office your team already runs.
The question Saudi brands keep asking is whether to replace Salla or Zid with Odoo, and the honest answer is that it depends on what the storefront needs to do beyond selling: multi-warehouse routing, wholesale pricelists, bundles that consume components, or one invoice per order cleared with ZATCA. Odoo eCommerce sells from the same product, stock and price data as your point of sale and sales team, and orders become deliveries and tax invoices with no re-entry whether the storefront is Odoo, Salla or Zid, which is the decision Naqlah, Odoo Gold Partner in Saudi Arabia, helps you make before any build starts.
The e-commerce law requires VAT-inclusive prices before checkout, published return and delivery policies, your trade name and CR, and a contact channel on the store, and Naqlah builds those into the theme alongside the Maroof badge rather than leaving them for a later audit. Each order produces a ZATCA e-invoice through the Odoo Saudi localization, the privacy policy and consent flow follow PDPL, and the 7-day return right is handled through the return workflow. If you stay on Salla or Zid, the Naqlah Salla app and Zid connector push orders, customers and payment status into Odoo and send stock and prices back, so Odoo Inventory stays the single stock ledger.
Salla and Zid connected, not replaced
Orders, customers and payment status flow into Odoo, and available stock and prices flow back to the storefront. Your marketing team keeps the tools they know and your operations team stops re-typing orders.
Local checkout
mada, Apple Pay and cards run through PayTabs, Paymob, Moyasar or Tap, with cash on delivery as a payment method whose remittance is reconciled against the carrier statement in Odoo.
Carrier-ready fulfillment
Torod, OTO, Aramex and SMSA labels print from the delivery order, tracking numbers go to the customer by WhatsApp or email, and COD collections are matched to invoices rather than to a spreadsheet.
1. Order placed on Odoo, Salla or Zid
The order arrives with the customer, items, payment method and national address, either natively or through the connectors Naqlah maintains.
2. Stock reserved in the right warehouse
Routing rules reserve from the Riyadh warehouse, the Jeddah branch or your 3PL depending on the destination city and availability.
3. Picked, labeled and shipped
The warehouse picks by barcode, prints the carrier label and the tracking number is sent to the customer automatically.
4. ZATCA invoice issued and payment reconciled
The invoice is submitted to Fatoora, the gateway payout or COD remittance is matched, and a return within the 7-day window restocks the item with a credit note.
Timelines depend on scope and the storefront strategy chosen, and Naqlah gives you a clear roadmap in the first consultation.
| Area | Before | With Odoo via Naqlah |
|---|---|---|
| Orders | Re-typed from the store panel into accounting | Synced automatically, native or through the connector |
| Stock | Oversold between the store, branches and wholesale | One pool reserved per order, pushed back to the storefront |
| Invoices | Manual ZATCA invoices per order or none | E-invoice per order, simplified or standard, submitted automatically |
| Payments | Gateway and COD reports reconciled by hand | Payouts and COD remittances matched to invoices |
| Shipping | Copy-paste into the carrier portal | Labels and tracking from the delivery order |
| B2B | Price lists sent on WhatsApp | Portal with customer pricelists, credit terms and order history |
Everything else, we cover in a free 30-minute consultation.
Free consultation. Meet the team and get a clear roadmap in one call.
.svg)
.svg)
