- Salla runs the storefront: catalogue, checkout, payment, shipping labels. That part is solved.
- Odoo runs what sits behind it: stock, purchasing, accounting, branches, wholesale.
- The connector is a product rather than a project. It installs from the Salla app store and is maintained after go-live.
- Eight things move between the two, and the two that decide whether it works are stock and orders.
- Your store stays on Salla. Not one customer moves.
What your Salla dashboard already does well
Salla is strong at the part your customer sees. The catalogue, the cart, the Saudi payment methods your buyers already trust, the shipping labels, an app store with accounting and marketing tools, and a dashboard your team learned in a week. Most stores in the Kingdom run their first two or three 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 Salla is doing its job and something behind it is not.
Where a growing Salla 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 two bags available, the warehouse has none, and somebody is refunding an order that should never have been accepted.
Then the retyping starts. Orders get exported from Salla and entered into the accounting system, or the accountant rebuilds the month from a bank statement because that is faster than reconciling it properly.
Then the questions stop having answers. What did we actually make on this product, after packaging, courier 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 supplier needs twelve days and you sell four a day.
None of these is Salla failing. They are all the same problem wearing different clothes: one fact living in more than one place. If you are still deciding whether this applies to you at all, does your store need an ERP covers the question from the start.
What syncs between Salla and Odoo
An integration is not one switch. It is a set of syncs, each with a direction and a timing, and knowing which is which is most of understanding whether the setup will hold.
| What moves | Direction | When | Why it matters |
|---|---|---|---|
| Products and variants | Odoo to Salla | On change | One product master and one SKU code, so the store and the warehouse are describing the same thing |
| Stock quantities | Odoo to Salla | Near real time | Stops the store selling what the warehouse has already shipped |
| Orders | Salla to Odoo | On creation and on every status change | The order becomes a sales order, a delivery and a draft invoice without anyone typing it |
| Customers | Salla to Odoo | On first order | One customer record across the store, the branch and wholesale |
| Payments and method | Salla to Odoo | With the order | Reconciliation by gateway, so settlements match without a spreadsheet |
| Shipping status | Both directions | On status change | Tracking visible inside the system, the notification still sent by the store |
| Refunds and returns | Salla 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 |
The two rows that decide whether the setup works are stock quantities and orders. Everything else is convenience built on those two. Odoo's inventory application is what holds the stock figure the store reads from.
Installing the app
The connector installs from the Salla app store, which is the part that matters commercially: it is a maintained product with a version history, not a one-off script that stops working the first time an API changes and nobody is responsible for it. Naqlah's Salla to Odoo integration app is the one this article describes.
- Salla app store. Find and install the app.
- Authorise. Connect the store.
- Settings. Map products and accounts.
- First sync. Products first, then stock.
- Pre-launch check. Test orders end to end.
The order of the first sync matters. Products carry the codes that everything else matches on, so they go first, and stock follows once the catalogue on both sides is describing the same items.
What changes in the first month
The visible change is small and the operational change is not. Your team keeps taking orders in Salla. What stops happening is the second entry: nobody retypes an order, nobody rebuilds the month from a bank statement, 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.
If you want the full picture of what the connector covers before installing anything, the Salla integration page lists it in one place.
