Install and authorize the Salla app
The integration is built for Salla Easy Mode, where Salla sends access tokens through app.store.authorize after merchant approval.
Built for Salla App Store Easy Mode
Salla accounting integration for Saudi e-commerce
Turn paid Salla orders into ZATCA-ready books
Connect Salla to Qeemah so checkout data flows into invoices, inventory, customers, payments, refunds, and the general ledger without spreadsheet cleanup.
Designed around the operational reality of Saudi online stores
Live sync workbench
Order 41027662 - paid checkout
Authorize
Map
Sync
Review
order.created
payment.updated
order.refunded
ZATCA
Signed invoice
SALE
Stock movement
mada
Payment routing
+966
Customer updated
Salla total
SAR 196.00
Ready for ZATCA QR and GL posting
ACK < 30s, process async
60,000+
Salla active-store ecosystem
Easy Mode
App Store-ready onboarding
Phase 2
ZATCA Phase 2 invoice path
Idempotent
Safe retry and audit trail
The gap
Your store sells in minutes. Your accounting should not wait for the weekend.
Most Salla merchants can see the order, the payment method, the customer, and the stock movement. The hard part is turning that activity into compliant accounting records before finance has to reconcile it manually.
Manual reconciliation
Unmapped SKUs
Refunds without trail
How it works
From Salla checkout to clean Qeemah records
Qeemah accepts Salla webhooks quickly, queues the accounting work, and keeps every order idempotent so duplicate webhook retries do not duplicate invoices or stock movements.
Map warehouse, tax, and accounts
Choose the warehouse, branch, ZATCA credential, payment accounts, revenue accounts, and SKU matching rules.
Turn paid orders into documents
Create a customer order or a signed ZATCA invoice with customer data, line items, discounts, VAT, and totals intact.
Review exceptions and lifecycle events
Failed orders show clear errors, while refunds and cancellations stay linked to the original accounting document.
Capabilities
Everything a finance team expects after the order syncs
ZATCA invoices at checkout
Turn paid orders into simplified tax invoices by default, or standard tax invoices when a buyer VAT number is present.
Multi-warehouse inventory sync
Match Salla SKUs to Qeemah products and deduct stock from the mapped warehouse with an auditable SALE movement.
Payment and GL routing
Map mada, Visa, Apple Pay, Tamara, Tabby, COD, and bank transfer channels to the right clearing or bank accounts.
Automatic customer updates
Create or update customer records from checkout details, matched by email or phone inside the same organization.
Refund and cancellation handling
Generate linked credit notes or order reversals for refunds and cancellations without silently deleting signed invoices.
Sync dashboard and retry
See every order as successful, pending, or failed, then retry safely after fixing the underlying mapping issue.
Connection mapping
Map each store to the right accounting behavior
One Salla merchant id resolves to one Qeemah connection. From there, each store can point to the correct warehouse, branch, ZATCA credential, payment clearing account, VAT treatment, revenue account, and SKU rules.
01
Store
Tie each Salla merchant id to the right Qeemah organization connection
02
Warehouse and branch
Choose where stock is deducted and where documents are issued
03
ZATCA and VAT
Select the signing credential and default 15% or exempt/zero tax treatment
04
Payments and revenue
Route payment channels, shipping, discounts, and revenue correctly
05
SKUs and products
Auto-match by SKU with manual overrides when the catalog needs cleanup
Before and after
What changes when Salla and Qeemah work together
Before the integration
Export orders, recreate invoices, reconcile payments later, and risk deleted or duplicated documents.
With Qeemah connected
Each paid order becomes a customer order or ZATCA invoice with inventory, customer, payment, and audit context.
When something fails
The dashboard shows a clear reason, such as missing SKU or payment account mapping, then supports safe retry.
Audit trail
Webhook signature verified
Document created once
Processing attempt recorded
Safe retry available
Reliability
Built for retries, refunds, and compliance edge cases
E-commerce accounting breaks when systems pretend every order is perfect. Qeemah records webhook attempts, shows human-readable errors, lets your team retry safely, and treats signed ZATCA invoices as immutable accounting documents.
FAQ
Salla integration questions
Can Qeemah create ZATCA invoices from Salla orders? +
Yes. Paid Salla orders can become Qeemah customer orders or signed ZATCA Phase 2 invoices, with simplified tax invoices by default and standard tax invoices when a buyer VAT number is present.
Can I connect more than one Salla store? +
Yes. A single Qeemah organization can connect multiple Salla stores, with each connection mapped to its own warehouse, branch, payment accounts, and ZATCA credential as needed.
What happens when an order is refunded or cancelled? +
In invoice mode, Qeemah creates a linked credit note for the original invoice. In order mode, it can cancel the customer order and reverse inventory movements without deleting signed accounting documents.
What if a Salla SKU is not mapped in Qeemah? +
The sync dashboard shows a clear error, such as a missing SKU. After the product is mapped or a non-inventory behavior is configured, the order can be retried safely.
Does the integration sync customers, stock, and payments? +
Yes. It syncs customer details, order lines, discounts, VAT, stock deductions, payment methods, shipping treatment, and revenue or clearing-account routing.
Ready to connect Salla sales to Saudi-ready accounting?
Book a guided walkthrough and see how Qeemah maps your Salla store, warehouse, taxes, payments, inventory, and ZATCA invoice flow.