Skip to content

Integrations

Your store’s orders reach your books on their own

If you sell on Salla or Zid, connecting means every order becomes an invoice in Mezan and every return becomes a credit note — with nobody retyping anything at the end of the day.

  • Salla
  • Zid
  • No code required

What connecting means

  • Orders become invoices

    Every order in your store creates its document in Mezan.

  • Returns accounted for

    A return becomes a credit note tied to its invoice.

  • E-invoicing

    Store invoices follow the Phase 2 flow like every other invoice.

  • Stock movement

    A sale draws the quantity down from your store in Mezan.

The two supported platforms

A deliberately short list. These two cover most Saudi e-commerce, and two connections that work well beat twenty that half do.

S

Salla

سلة

Connect your Salla store to Mezan and its orders and returns reach your books as they happen.

  • Orders arrive as sales invoices
  • Returns arrive as credit notes
  • Customers and products matched to your records
  • Event replay if something falls behind
Z

Zid

زد

The same connection for Zid stores: an order becomes an accounting document with no manual entry.

  • Orders arrive as sales invoices
  • Returns arrive as credit notes
  • Customers and products matched to your records
  • Event replay if something falls behind

How you connect a store

From inside Mezan, with no developer and no files to export and import.

  1. 1

    Open integrations

    In your organisation settings in Mezan, choose the platform your store runs on.

  2. 2

    Authorise the connection

    You are taken to your store to grant Mezan access, then brought back. No keys to copy, no files to upload.

  3. 3

    Set the mapping

    Choose which store stock is drawn from, which account sales land in, and how products are matched.

  4. 4

    Leave it running

    New orders arrive by themselves, and anything that falls behind is replayed rather than lost.

What moves

An order becomes a full accounting document

The integration does not copy figures into a table, it creates the document. The invoice posts its journal entry, draws down stock, and follows the e-invoicing flow exactly as one you raised by hand.

  • A paid order becomes a sales invoice with its journal entry
  • A return becomes a credit note tied to its invoice
  • Quantity is drawn from the store you nominated
  • Store sales appear in your reports alongside your other channels

The path from store to ledger

  • The order

    Placed in your Salla or Zid store.

  • The event

    Reaches Mezan as it happens.

  • The document

    A sales invoice or a credit note.

  • The entry

    Stock moves and the journal entry posts.

Need to connect a different platform, or your own system? The Mezan API and webhooks are there for that.

Mezan API

Common questions

Do I need a developer to connect my store?

No. The connection is made from inside Mezan by authorising it from your store, after which you set the stock location, the accounts and how products are matched.

What if the connection drops for a while?

Delayed events can be replayed, so orders that did not record arrive rather than being lost or keyed in by hand.

Are store invoices ZATCA compliant?

Yes. The invoice created from an order is an ordinary Mezan invoice and follows the Phase 2 flow like the rest of them.

Do you support other platforms?

Salla and Zid are the supported platforms today. For any other platform or in-house system, the route is the Mezan API and webhooks.

Book a demo

Leave your details and we’ll call you back within one business day to arrange your session.

We use your details only to contact you about your Mezan session.