Stay ahead.
The commerce operating system for Saudi and Gulf merchants.
Sabooq holds your storefront, catalogue, inventory, orders, customers and delivery as one operating truth — so your team stops reconciling systems and gets back to running the business.
Sabooq has not launched publicly yet; we are preparing a first group of merchants for onboarding. Everything on this page is labelled: what is built now, what is coming, and where we are heading.
Your business runs on systems that do not know about each other.
The store is in one place, stock in a spreadsheet, delivery in a provider's dashboard, accounting in a fourth system. The gaps between them are not an administrative annoyance — they are daily manual work, and profit leaking where nobody is looking.
Systems that disagree
One number is right in one system and stale in three. The difference reaches your customer as a cancelled order or a late delivery.
Repeated manual work
Re-keying, reconciling, chasing. Hours of your team's time move data between screens instead of selling or serving a customer.
Profit that leaks quietly
Shipping cost, returns, discounts, payment fees — each in a different system, so nobody sees the real profit on a single order.
Commerce here has its own shape
Arabic first, cash on delivery, national addressing, VAT, Gulf delivery zones. Tools built for another market treat all of this as an edge case.
What Sabooq does now.
Every item on this list is built and working. What is not is not here — it appears further down, carrying its stage.
An Arabic-first storefront
A store carrying your identity — your pages, menus and content — built right-to-left and Arabic-first from the ground up rather than translated afterwards, with a public presence search engines can read.
Catalogue and products
Products, variants, media and categories, with images stored and served by the platform itself.
Pricing, cost and inventory
Price lists, VAT, cost, and stock across more than one warehouse, with transfers and reservations.
Orders, with their commercial terms
Cart to order, with every order carrying a snapshot of the commercial terms it was priced under — so the past is not silently repriced when an agreement changes.
Customers and consent
The customer record, and consent held as facts that cannot be edited after the event — which is what you actually need when someone later asks who agreed, when, and to what.
Delivery you control
Your own delivery areas and your own rates, quoted to the shopper at checkout and fixed onto the order. Built for the merchant who delivers themselves or on their own arrangement.
A daily operating view
A page that opens on what needs attention today, and an exception centre that collects what broke until it is closed — instead of it surfacing as a customer complaint.
Usage and measurement
What the platform actually did, measured — the basis for any billing or analysis that follows, rather than an estimate.
Roles, authority and audit
Who may do what, enforced on the server rather than in the browser, with an audit trail. Each merchant's data is isolated in the database itself.
What Sabooq does not do today.
-
It does not move money
Sabooq prepares the order and holds its terms and amounts, but executing a payment or a settlement remains a human action outside the platform at this stage. No payment provider is contracted or activated.
-
It is not yet connected to carriers
Delivery today is your delivery on your arrangement. No carrier integration is activated, and we will not display a provider's logo we have not contracted with.
-
It does not decide for you
There is no running AI model, no automated recommendation and no self-executing action in Sabooq today. What is built is deterministic and auditable — which is precisely what has to come before any autonomy.
Nine parts of a commerce business, one operating truth.
Sabooq does not add a tenth system on top of the nine. It owns the truth itself — product, price, stock, order, customer, delivery — in one place, so every part reads the same number.
- Storefront
- Orders
- Customers
- Inventory
- Pricing & cost
- Delivery
- Payments
- Operations
- Administration
A store builder gives you a shopfront. An operating system gives you control.
Truth owned, not synced
No plugin syncing stock between two systems, because stock does not live in two systems.
Economics at the order line
Shipping, discount, tax and fees modelled distinctly on the order itself — not one total that hides where the margin went.
Arabic by construction
Arabic and right-to-left sit in the foundation rather than in a translation layer — a difference that shows up in every screen, message and invoice.
Not a marketplace competing with you
Your customer is yours. We do not sell alongside you, and we do not take a commission on your success.
Built for this market, not adapted to it.
Arabic is the original
Every screen and message is written in Arabic first and mirrored into English — not the reverse. Right-to-left is designed first and verified first.
Cash on delivery is modelled
Cash on delivery is not an edge case here: who collects it and how it reconciles are modelled explicitly, because it is the mainstream of commerce in this region rather than its margin.
VAT inside the pricing engine
VAT is calculated inside the pricing engine itself rather than added at the end, under settings the merchant controls. Tax invoicing and ZATCA e-invoicing are not part of what is built today.
The phone is the baseline
The Saudi shopper buys from a phone. Storefront speed on a phone is treated here as commercial performance, not a technical detail.
From a system that knows, to one that advises, to one that operates.
Autonomy does not come from a model's confidence. It comes from a trustworthy deterministic foundation, then evidence, then authority granted within declared limits that you can withdraw. This is the order we build in, and this is where we are in it.
-
Available now Level 1–2
A deterministic foundation
One trustworthy operating truth: product, stock, order, customer and delivery, shown as they are with an audit trail. No guessing, and no model.
-
Coming Level 2–3
Answers with evidence
Asking the system an operating question and getting an answer drawn from recorded facts, showing its source, its freshness and its uncertainty — before it is allowed to propose anything.
-
Coming Level 3–4
Recommendations, then approved actions
The system spotting a problem or an opportunity, proposing an action with its expected effect and its owner, and executing it only after your explicit approval.
-
Long-term vision Level 5
Bounded delegation
Granting Sabooq standing authority over a named scope, a declared budget and an explicit policy — stoppable and revocable at any moment.
-
Long-term vision Level 6–7
“Sabooq, run my ecommerce business profitably.”
The system coordinating growth, pricing, inventory, customer, delivery and cost toward one objective: sustainable contribution profit. This is our stated long-term goal, and it is not a feature you can buy today.
-
Available now
Built and tested in the platform today. Sabooq has not launched publicly, and no merchant is running on it yet.
-
Coming
A named, authorized stage in our plan that has not been built yet. Not available, and not sold as if it were.
-
Long-term vision
The direction we are building toward. Not a date, and not a feature you can buy today.
A platform usage fee. No commission, no take-rate.
A platform usage fee. No commission. No take-rate.
Sabooq is not a marketplace and does not stand between you and your customer. The store is yours, the customer is yours, the brand is yours.
Shipping is excluded from the platform fee and is always priced and shown as its own line.
Sabooq does not publish a public rate card at this stage. The numbers are set in your commercial agreement.
What we can show, rather than what we could claim.
No badges and no compliance logos on this page. These are properties built into the platform, and they can be reviewed.
Tenant isolation enforced in the database
Keeping one merchant's data from another does not depend on application code being right: it is enforced in the data layer itself and tested as a property in its own right.
Authority on the server, never in the browser
Hiding a button is not security. Every authority decision is taken on the server, and an unauthorized request is refused regardless of what the interface showed.
Money moves by human decision, by design
The platform prepares; a person executes. That is a declared posture written into the platform itself, not a gap we will quietly close.
Consent is a record, not a checkbox
A customer's consent is stored with its purpose, its moment and its origin, and cannot be edited after the fact — because the question about it always arrives afterwards.
The questions we actually get asked.
Can I sign up right now?
No. Sabooq has not launched publicly and no merchant is running on it today. We are preparing a first group for onboarding, and applying here puts you among the people we talk to — it does not open an account.
Do you take a commission on my sales?
No. Sabooq's model is a platform usage fee — no commission, no take-rate. Shipping is excluded and priced as its own line. We do not publish a public rate card at this stage; the numbers are set in your commercial agreement.
Is Sabooq an AI platform?
Not today, and we will not pretend otherwise. What is built now is a deterministic, auditable operating system. Intelligence, recommendations and delegated action are authorized later stages, and they are labelled as such everywhere on this site.
Do you process payments?
No. Sabooq completes the journey at the order and holds its amounts and terms. Executing payment and settlement stays outside the platform and with a person at this stage, and no payment provider is contracted.
Are you integrated with carriers?
No integration is activated today. What works now is your own delivery: your zones and your rates, quoted to the shopper and fixed onto the order. We will not display a carrier's logo we have not contracted with.
Where is my data stored?
Sabooq's infrastructure is defined to run inside the Kingdom (the Dammam region), and that choice is fixed in the infrastructure definition. Sabooq is not yet deployed to a production environment, so we describe this as a settled design rather than as something already in operation.
Would I migrate my current store?
That is part of the onboarding conversation. The application asks about your current platform, catalogue size and channels, because the honest answer depends on them — and it may be: not yet.
Who owns my customers and my data?
You do. Sabooq is not a marketplace, does not sell alongside you, and does not use one merchant's data for another's benefit. Each merchant's isolation is enforced in the database itself.
If any of that describes your week, let us start a conversation.
Applying starts a conversation; it does not open an account. We read every application and answer honestly — including when the honest answer is that Sabooq is not right for you yet.
Stay ahead.