If you sell both in a branch and through an online store, you know the problem: a product sells online after it ran out on the shelf, staff enter orders twice, and the reports never match at month end. Connecting your Salla or Zid store to your POS and inventory solves this, provided the integration is designed before it is built.
In short, connecting Salla or Zid to POS and inventory means quantities, prices and orders have one source that both the online store and the branch read from. There are three ways to do it: a ready app from the platform's app store, a POS that supports the platform natively, or a custom integration using the APIs and webhooks that Salla and Zid provide to developers. Success depends on three decisions: unifying SKUs, choosing the system of record for stock, and defining how returns and cancellations are handled.
Why connect your online store to your POS?
- Prevent overselling: items sold at the till are deducted from what the store shows as available, and vice versa.
- Stop double entry: online orders appear in the branch system without being retyped.
- Unified reporting: sales from both channels in one report by item and branch.
- Consistent pricing and offers: change a price once and it applies to both channels.
What data is synced?
- Products: name, SKU, barcode and options such as size and colour.
- Stock: available quantity per item, and per branch or warehouse if you have several.
- Prices and offers: base price, sale price and its end date.
- Orders: line items, status, payment and shipping method.
- Returns and cancellations: to return quantities to stock and settle amounts.
- Customers: optional, if you run a loyalty programme or a single customer record.
What are the three integration methods?
1. A ready app from the platform's app store
Salla and Zid both list apps for accounting, inventory and POS systems in their app stores. This is the fastest option if your system is supported and your scenario is standard. Check what the app actually syncs, because some only transfer orders and not stock.
2. A POS that supports the platform natively
Some POS systems offer a direct connection to Saudi e-commerce platforms. This suits merchants choosing a new POS who want fewer moving parts.
3. A custom integration
When you run an existing system that no ready app supports, or you have special rules such as multiple warehouses or different prices per channel, the integration is built on the platform's and your system's APIs and webhooks, either directly or through an automation tool such as n8n. We deliver this through our systems integration and API service, and the scope is set after reviewing your POS interfaces.
Which system owns the stock figure?
This is the most important decision in the project. Only one system should own the stock number; the others read from it. In most cases the POS or inventory system is the reference, because it records receiving, stock counts and branch movements, while the online store receives the available quantity and sends orders. If both sides edit quantities, you get differences nobody can trace. The same rule applies to price: decide who owns it and block edits from the other side.
How do you handle multiple branches and warehouses?
- Decide which warehouses feed the online store: all of them, or one dedicated fulfilment location.
- Keep a safety buffer so the store does not show the last unit sitting on a branch shelf.
- Reserve stock when the order is created, not when it ships, so it cannot sell twice.
- Decide which branch fulfils an order when the item is available in more than one location.
How are returns, cancellations and invoices handled?
A return is not always the reverse of a sale: a damaged item should not go back into available stock. The integration needs clear states for a sellable return and a damaged one, and for cancellation before and after shipping. For VAT invoices, decide which system issues the invoice for the online order so it is not recorded twice in your books. The accounting side is covered in POS and accounting integration, and ERP sync requirements in POS integration with ERP and inventory.
Implementation steps
- Data clean-up: tidy the product list and unify SKUs across both systems before any connection.
- Ownership: write down who owns stock, price and product data.
- Method: ready app or custom integration, depending on what your system supports.
- Test environment: connect a test store or a limited set of products first.
- Acceptance tests: branch sale, online order, return, cancellation, an item with options, and an out-of-stock case.
- Gradual rollout and monitoring: an error log, an alert when sync fails, and daily reconciliation in the first weeks.
Common mistakes
- Connecting before SKUs are unified, which creates duplicate products.
- Allowing quantity edits from both the store and the POS.
- Infrequent scheduled syncs for fast-moving items.
- Ignoring returns in the design and discovering the gap after go-live.
- No error log, so nobody knows why the numbers differ.
If you do not have a POS yet, review our POS system, which connects to inventory and accounting, and our inventory and purchasing system.
We design Zid and Salla stores and connect them
If your store is not ready yet, we can handle Zid store design and development or Salla store setup, then connect it to your inventory, POS and accounting system. Request a quotation on WhatsApp.