Connect Salla or Zid to Accounting and Inventory: 2026 Guide

At first a Salla or Zid store looks self-contained: a customer places an order, it appears in the store dashboard, you pick and ship it, and you collect the money. As sales grow, quieter problems surface:

• Revenue shows up in the store but never flows automatically into the journal entries.
• Inventory is updated in the store based on online sales, but sales made at a physical counter or through wholesale never touch it.
• The true landed cost of each product (including shipping and customs) is not tied to the sale, so per-product profitability is never accurate.
• Invoices are issued in a format that may not meet ZATCA requirements, which creates problems when the merchant files the tax return.
• Returns are processed in the store, but no credit notes are created in the accounting system.

The result is hours of manual entry every day, errors that compound, and potential tax exposure. Connecting the store to accounting ends all of that with real-time sync, so every transaction in the store is reflected automatically in the books and in inventory.

Effective synchronisation covers four layers:

• Products: one product database (name, description, images, dimensions, category) shared by both systems.
• Prices and promotions: the price shown to the customer in the store matches the price in the accounting system, along with any linked discount or offer.
• Inventory: available quantities updated in real time, so the store never sells an item that has run out in the warehouse and never hides an item that is in stock.
• Orders and invoices: every order generates an accounting invoice, deducts inventory, records the revenue, and either creates a receivable (if payment is deferred) or posts the cash receipt (if payment is immediate).

Sync can be one-way (from the accounting system to the store, or the reverse) or two-way. For a growing business, two-way sync is the most effective: editing a product or a price on either side is reflected automatically on the other.

Before choosing how to connect the two, decide which system is the "source of truth" for each type of data. The common pattern that works: the accounting system is the source of truth for products, prices, and inventory, while the store is the source of truth for orders, customer details, and the buying experience.

Creating a product in the accounting system and pushing it automatically to the store saves you from duplicate work and keeps the data consistent. The fields that matter in the sync:

• Product name in Arabic and English.
• Product code (SKU) or barcode.
• Category and brand.
• Cost price (not shown in the store, but essential in accounting for profitability).
• Selling price (VAT-inclusive or VAT-exclusive, depending on the store's setting).
• Product images.
• Variants such as colours and sizes for apparel.

One critical point: Value Added Tax (VAT). Decide from day one whether store prices include or exclude tax, and configure the accounting system the same way. Mixing the two settings creates discrepancies in the tax return.

Seasonal offers and discounts should follow the same logic: a discount applied in the accounting system flows through to the store. If they are entered by hand in each system, they will inevitably diverge, and you lose a single audit trail.

Overselling is one of the worst failures in e-commerce: a customer orders an item that is not actually available, and the order is then cancelled. It damages the store's reputation and can cost you customers permanently.

The fix is real-time inventory sync between the store and the inventory management system, built on the right logic:

• A sale in the store deducts inventory automatically.
• A sale at a physical point of sale deducts inventory automatically.
• A wholesale sale deducts inventory automatically.
• Returns put the quantity back into inventory after inspection.
• Transfers between warehouses are reflected in the quantities available to each channel.

Some businesses ring-fence part of the inventory for each channel to avoid conflicts, but a single pooled inventory with smart allocation rules is better:

• When stock drops below a set threshold, the product is closed off in the lower-priority channel.
• Certain products are exclusive to the online store and never appear at the point of sale.
• The geographic location of the stock determines the delivery speed shown in the store.

This level of control cannot be achieved with a surface-level sync. It requires one unified system spanning the store and accounting.

Every order in the store should generate:

• A journal entry for the revenue.
• An inventory deduction at cost price.
• A receivable (if payment is on delivery) or a cash receipt entry (if payment is made online).
• An electronic invoice compliant with ZATCA.

A good sync does all of this automatically within seconds of the order being placed. It also handles changes in order status:

• Order cancelled before shipping: reverse the entry, return the stock.
• Order returned after delivery: issue a credit note, update inventory once the return is inspected.
• Partial order: invoice only the quantities actually delivered.

A practical point: keep a single invoice sequence across the whole business, not two separate ones (one for the store and one for the point of sale). A unified system guarantees invoice numbers that are ordered and auditable, which is exactly what ZATCA requires for e-invoicing.

Your Salla or Zid store may issue an invoice in a particular format, but that invoice may not fully meet ZATCA requirements, especially under Phase Two (integration) as approved by the Zakat, Tax and Customs Authority, which requires:

• An approved digital signature.
• Submission to the Authority (Reporting for B2C, Clearance for B2B).
• A QR code that meets the technical specifications.
• A credit note for every return, linked to the original invoice.

The answer is to have the accounting system connected to the store be the ZATCA-approved system, so it issues the official electronic invoice instead of the store. The store remains responsible for what the customer sees, while the legal invoice comes from the approved system.

This means the customer may receive an invoice from Snad that is linked to the merchant's Salla store, rather than from Salla directly. That separation protects the business from compliance risk and ensures that all invoices issued across all channels are consolidated into a single tax report, ready for the quarterly return.

The challenges that come up most often when connecting online stores to accounting systems:

• Mismatched SKUs between the store and the accounting system: decide on the sync key from the start (a single shared SKU on both sides is best) and make sure every product is unique.
• Different tax treatment per product (some items are exempt): set the tax categories correctly in the accounting system and let the store follow them.
• Negative inventory: if the system keeps accepting orders after stock runs out, set hard limits in the accounting system that block the sale.
• Confusing a parent product with its variants: make sure the sync operates at variant level (variant SKU), not only at parent product level.
• Differences between payment methods: the store supports cash on delivery, bank transfer, and card payments. Each one needs a different accounting settlement. Connecting bank feeds and payment gateways to the accounting system cuts down manual reconciliation.

The list looks long, but an accounting system built specifically for the Saudi market handles most of it through default settings, so the setup never turns into a project of its own.

Snad connects directly to both the Salla and Zid platforms and works as one central system:

• Real-time sync of products, prices, and inventory from Snad to the store, so nothing has to be entered in the store by hand.
• Automatic order intake from the store, with a ZATCA-compliant electronic invoice created for each one (tax invoice or simplified invoice, depending on the customer type).
• Inventory deducted the moment an order is confirmed, with available quantities updated in the store in real time to prevent overselling.
• Physical points of sale running on the same inventory base, so a sale in the shop is reflected in the store and vice versa.
• Unified profitability reports that bring together sales from the store, the point of sale, and wholesale in one report, broken down by product, category, branch, or channel.
• A single quarterly tax report ready for filing, consolidating every invoice from every channel.
• Store returns handled automatically through a credit note linked to the original invoice, with inventory and journal entries updated.

With this integration, digital transformation for a Saudi merchant is no longer a set of disconnected systems but one platform that grows with the business. That is exactly what an owner needs in order to focus on selling and marketing instead of data entry.