Salla or Zid? A Store Owner’s Comparison of Accounting, Inventory, E-Invoicing and ERP Integration

E-commerce and e-invoicing illustration comparing Salla and Zid

The Salla vs Zid question is usually discussed in terms of design, themes, marketing tools and plan fees. But a store selling real volumes soon faces other questions: where is each branch’s stock recorded, how do invoices reach ZATCA, what happens to stock and the books when an order is returned, and how do orders reach the accounting system without manual entry?

The short answer: both are mature Saudi ecommerce platforms. Both offer product options, multi-location stock, a free link to ZATCA’s Fatoora platform, returns management and an API for connecting outside systems. The differences are in the detail: branch and warehouse limits per plan, how orders are allocated to warehouses, and what is ready-made for connecting an ERP.

This article compares Salla and Zid from the point of view of the accountant and the operations manager, based on both platforms’ official help centres as of October 2026. Features and plans change, so check each platform’s pages before you decide.

Why Compare Salla and Zid from the Accounting Side?

Because the cost of choosing the wrong platform does not show up in the subscription fee. It shows up in hours of manual reconciliation, stock differences and a slow month-end close. The platform is the source of your sales data, and any weakness in that data flows straight into the books.

Typical comparisons focus on the storefront, themes and customer experience, and those matter. But if you have more than one warehouse, sell both online and at a point of sale, or need an accurate cost of goods sold, the deciding questions are:

  • Does each product option carry its own SKU, price and quantity?
  • Is stock managed per warehouse, and which warehouse does an order draw from?
  • Are invoices sent to Fatoora directly?
  • Does a return put the quantity back into the right location, and how is the refund made?
  • Which events and data can an ERP read from the platform?

Products, Options and Prices

Both platforms support products with options such as size and colour, with a quantity and price per option. The differences are in presentation and documented limits.

On Salla, product options can be added as text, colour or image, and the quantities section lets you set the quantity and price for each option or keep the product’s base price. Salla’s help centre states a maximum of 100 variants per product.

On Zid, options are managed in an options library and shown to customers as a dropdown. Zid’s developer documentation shows that each product variant carries its own fields for SKU, price, sale price, cost, barcode and quantity per stock location.

From an accounting view, what matters is a fixed SKU for each variant that matches the item in your ERP, because the integration matches on that code. We cover this in detail in Salla product options: linking every size and colour to its price, stock and SKU in your ERP.

Stock and Multiple Warehouses

Both platforms support more than one stock location with separate quantities per location. The differences are the limits in each plan and how the platform decides which warehouse an order draws from.

On Salla, the branches and warehouses guide sets the number by plan: 5 on Salla Basic, 10 on Salla Plus, 20 on Salla Pro and unlimited on Salla Special, with the option to buy extra branches. The multi-warehouse feature lets you set a different quantity per branch, fulfil orders from the branch best suited to the customer’s location, choose a stock deduction strategy and ship one order’s items from several branches, alongside stock transfers and pickup from branch.

On Zid, inventory locations let you create warehouses linked to cities and assign each to online orders, Zid POS orders or both. Orders draw stock by a withdrawal priority the merchant sets, and the system logs every stock movement with the reason, channel and quantity before and after. The Professional plan allows 5 warehouses, plus one per POS device, and the Large Business plan is unlimited. The Professional plan also offers automatic replenishment between warehouses when stock falls below a minimum.

E-Invoicing and Returns

Both platforms offer a free link to ZATCA’s Fatoora platform, and both support full and partial returns with quantities put back into stock. The accountant still needs to make sure the books reflect it.

On Salla, the ZATCA integration app is installed free from the app store. It requires ZATCA registration, a commercial registration, a verified store and a complete address for the default branch. Salla supports returning a whole order or part of it, with edits to quantities or prices, an option to return products to stock, and a refund to the customer or to their store wallet.

On Zid, the Fatoora integration page states that the link is free and aimed at Phase 2 compliance. It needs the legal name, VAT number and address, and can cover the POS as well. Zid supports partial returns with a choice of the warehouse the goods return to and a record of received and damaged quantities, while the refund follows the original payment method.

Also read: E-invoicing for Zid stores: a ZATCA-compliant invoice for every order without manual work.

ERP and Accounting Integration

Both platforms provide an API and webhooks that an ERP can rely on. The practical difference is which ready-made connectors exist for your system.

Salla’s developer documentation lists events for orders, products (including low quantity and back-in-stock), customers, shipments and invoices, including an invoice-created event when an order is completed. Zid’s documentation lists events for order creation, order status and payment status changes, and for products, customers, categories and abandoned carts.

What an accountant needs from any integration is the same: each order posted as a sales invoice with items and VAT, collections recorded by payment gateway, returns reversed with a credit note and the quantity restored, and stock kept in sync across warehouses. The more of this is automated, the less manual reconciliation at month end.

Comparison Table: Salla vs Zid

CriterionSallaZid
Product optionsText, colour or image, with quantity and price per option; limit of 100 variants per productOptions library shown as a dropdown; each variant has SKU, price, cost and quantity per location via the API
Number of warehousesBasic 5, Plus 10, Pro 20, Special unlimited; extra branches can be boughtProfessional 5 (plus one per POS device), Large Business unlimited
Order allocationBy customer location and deduction strategy, with multiple shipments per orderBy the withdrawal priority the merchant sets
Stock transfersStock transfer between branchesTransfer requests, with automatic replenishment on the Professional plan
Fatoora linkFree app, subject to verification and address conditionsFree link from settings, including POS
ReturnsFull or partial, back to stock, refund or wallet creditFull or partial, choice of return warehouse, damaged quantities recorded
ERP integrationAPI and events covering invoices and quantitiesAPI and events for orders and products

How Daysum Works with Both Platforms

Daysum has a ready Salla integration app that moves orders from the store into the accounting system and on to ZATCA through Phase 2 approved e-invoicing. You can see how the data flows in our guide to Salla ERP integration.

For Zid, Daysum is built on Odoo, and an Odoo-based system can be set up to receive Zid orders and products through Zid’s API, as we explain in Zid Odoo integration. The scope of that setup depends on the size of the store and the number of warehouses.

If you are choosing between the two platforms and want to know how your data would reach the books in each case, talk to the Daysum team to review how your store works.

Conclusion: The Platform That Fits How You Run Your Store

Neither platform is better in every case. Salla offers higher branch limits on its upper plans, order allocation by customer location and multiple shipments per order, plus a ready integration with Daysum. Zid offers a clear withdrawal priority, a detailed stock movement log, automatic replenishment and direct integration with Zid POS.

Choose the platform that fits your number of warehouses and the way you sell, then make sure every order, return and collection reaches your accounting system automatically. Check current plans and limits in each platform’s help centre before you subscribe.

To discuss connecting your store to an integrated accounting system, on Salla or Zid, contact the Daysum team.

FAQs About Salla and Zid

It depends more on how you run your store than on the platform itself. If you need many branches and orders allocated by customer location, compare Salla's plan limits. If you sell through a POS in a physical shop and need automatic replenishment between warehouses, Zid offers that on its Professional plan.

Yes. Both platforms provide an API and webhooks that an ERP can use, and an Odoo-based system can be set up to receive orders from both and post them to the same books. The key is keeping SKUs consistent across both platforms and the system.

Both support multiple warehouses with separate quantities per location. On Salla the number ranges from 5 on Basic to unlimited on Special, and on Zid from 5 on the Professional plan to unlimited on Large Business. The way orders are allocated to warehouses differs between the two.

Yes. Both help centres state that the link to ZATCA is free. On Salla it is done through an app from the app store, and on Zid from the dashboard settings. Both need an activation code from your Fatoora account.

Both platforms let you put returned quantities back into stock and refund the customer. In the books, each return should be matched by a credit note reversing the revenue and VAT, and an entry returning the cost of goods to inventory. An automated ERP integration makes sure none of these entries is missed.

Share This Article

top
Business Challenges

Digital Transformation

Security

Automation

Gaining Efficiency