Retail & E-commerce

One stock figure, every channel

Store, website, app and marketplace selling from the same inventory, invoicing that satisfies ZATCA, and payment methods Saudi shoppers actually use.

  • ZATCA Phase 2 compliant
  • mada, Apple Pay, Tamara & Tabby
  • Arabic storefronts that rank
  • ZATCAPhase 2 e-invoicing integrated
  • 1Stock figure across all channels
  • 4-8Weeks to a live storefront

Where retail margin leaks

Selling in more places should raise revenue, but without one stock figure and one invoice flow it mostly raises the number of things that can go wrong.

  1. 01

    The website sells what the branch already sold

    Stock counted separately per channel produces cancelled orders, refunds and a customer who does not come back.

  2. 02

    E-invoicing bolted on late

    ZATCA compliance handled by a separate tool means double entry, mismatched numbers and a stressful audit.

  3. 03

    Nobody knows who the customers are

    Thousands of transactions and no profile, no purchase history and no way to bring a buyer back for a second order.

  4. 04

    Peaks break the system

    Ramadan, Eid and promotions produce the traffic that matters most — and that is exactly when a fragile site slows or falls over.

What we build

Systems for retailers

Built new, or connected around the platform you already sell on.

  • Online stores & marketplaces

    Fast Arabic-first storefronts built for search and conversion, or a clean integration with Salla, Zid, Shopify and marketplace listings.

  • POS & inventory across branches

    One catalogue, one stock figure and transfers between branches, with offline-tolerant point of sale that keeps selling when the link drops.

  • ZATCA e-invoicing

    Phase 2 invoicing generated, cleared and archived inside the same flow that makes the sale — for store, online and B2B orders alike.

  • Payments & checkout

    mada, Apple Pay, card, Tamara and Tabby, with a checkout tuned for Saudi addresses and mobile-first buyers.

  • Loyalty & customer app

    Points, tiers, offers and push notifications tied to real purchase history, so a campaign reaches the people likely to buy.

  • Delivery & fulfilment

    Integrations with courier partners, branch pickup, delivery slots and a tracking page that stops the "where is my order" calls.

Rules we build around

Retail obligations are unforgiving because every transaction creates a record. We build them in rather than around.

  • ZATCA Phase 2 (Fatoora)

    Cryptographic stamping, QR codes, clearance and reporting handled in the same system that issues the invoice.

  • Consumer & payment rules

    Pricing, VAT display, returns and refund flows built to Ministry of Commerce expectations, with PCI-compliant payment handling.

  • PDPL for customer data

    Clear consent for marketing, an unsubscribe that works, and customer records stored and retained according to policy.

FAQ

Questions from retailers

  • No. Those platforms handle storefront and payments well. We are usually brought in to connect them to POS, inventory and accounting, to build the mobile app, or to add what the platform cannot do for your business.

  • If it exposes an API or a database we can read, yes — that is a common first project. Where a POS is genuinely closed, we will say so early rather than promising an integration that will not hold.

  • That is a load-testing question, and we treat it as one. We test at several times your expected peak before launch and use hosting that scales, because the busiest hour of the year is not the time to find out.

Selling in more places than you can track?

Tell us your channels and where the numbers stop matching. That gap is usually the whole project.