Industries
One stock count, every channel, every invoice valid.
Saudi shoppers move between the shop floor, the app and a marketplace in the same afternoon. We connect your store, POS, ERP and fulfilment so the price, the stock level and the tax invoice agree wherever the customer happens to buy.
What this removes.
Stock that sells twice
Today
The website, the branch POS and the marketplace each hold their own count, and a popular item gets sold after it has gone.
With the system
A single inventory source that every channel reads and writes, with reservations while a basket is open.
Invoices assembled by hand at month end
Today
E-invoices are exported from one system and corrected in another, and finance finds mismatches only when a customer complains.
With the system
Invoices generated at the moment of sale in the required format, with failures queued and visible instead of silent.
Checkout that drops buyers who prefer mada
Today
Payment options differ by channel, and a card that works in store is declined online for reasons nobody can see.
With the system
A tested checkout with mada, cards, Apple Pay and cash on delivery, and clear error messages in Arabic.
Loyalty programmes nobody can measure
Today
Points live in a spreadsheet or a third-party tool that does not know what was actually bought.
With the system
Loyalty tied to real transactions across channels, so you can see who returns and what brings them back.
What actually applies.
ZATCA e-invoicing
ZATCA's e-invoicing regulation requires structured invoices generated by compliant solutions, delivered in waves that move from generation and storage to integration with the Fatoora platform. We build the invoice engine and ERP or POS connection to the technical specification for the wave that applies to your business, and test it before go-live.
E-commerce and consumer protection rules
The Saudi E-Commerce Law and Ministry of Commerce consumer-protection rules set expectations for price display, store identity, returns information and handling of customer complaints. We build the required disclosures, returns flows and order records into the storefront so they are not left to a footer link.
mada and card payment acceptance
Payment acceptance runs through licensed gateways and acquirers, and mada support depends on your gateway agreement. We integrate the gateway you contract with and handle tokenisation so card numbers never touch your own servers.
Delivered through these services.
Asked before signing.
Should we use Salla, Zid, Shopify or build custom?
Start on a hosted platform if your catalogue and checkout are conventional, because it is faster and cheaper. Move to headless or custom when you need unusual pricing, deep ERP sync or several brands on one back end.
How long does a ZATCA integration take?
For a single ERP or POS with a standard invoice flow, 4 to 8 weeks including testing is typical. Multiple branches, several POS vendors or heavy customisation extend that, and we confirm the range after a short discovery.
Can the store and the branch POS share one stock figure?
Yes. We connect the POS and store to one inventory source through their APIs. Whether it updates in real time or in short batches depends on what your POS vendor allows.
Will the store work well in Arabic?
Yes. Layout, search, product copy, numerals and email templates are designed right to left, and Arabic product search handles spelling variants so customers still find what they typed.
Tell us where your numbers stop agreeing.
Send us the channels you sell on and the systems behind them. We will return a short plan for getting stock, price and invoices to match.