Built for a shop in Riyadh, not for a slide deck
Wameed means a flash of light. The name is deliberate: the thing that keeps working for the moment everything around it goes dark.
Where this started
The observation everything started from
In most Saudi shops, the moment a point-of-sale system fails is not a moment the system itself broke. The queue is there, the cashier is ready, the products are on the shelf — but something outside the shop stopped: the line, the vendor’s server, a third party’s API.
Then Phase 2 e-invoicing added a layer: it is no longer enough to complete the sale, it has to produce a signed legal invoice. Most systems sign on the server — so an outage stopped being merely inconvenient and started making what comes out of the printer non-compliant.
We decided to build from the other end. The device first: the catalogue, the prices, the promotions and the signing key all live on it. The cloud is where the data goes, not what you need in order to sell. Then everything else was built on that foundation.
Six decisions, and what each cost
Each of these makes something else harder. They are the trade-offs we took on purpose.
The device first, then the cloud
Everything a sale needs lives on the device. The cloud receives, distributes and analyses — but is never a condition of completing a sale. That decision costs us real engineering complexity, and we would make it again.
Arabic is not a translation
The product was built in Arabic and right-to-left from the first day, not as a layer over an English interface. It also speaks Urdu, Bengali and Pashto, because in many shops those are the people actually standing at the till.
We do not touch your money
Your customers’ payments settle straight into your own merchant account. Wameed is not a payment institution and never holds funds; its income there is a published revenue share. A system that holds your money owns your decision.
We publish what we do not do
This site carries a comparison table that concedes eleven rows, and feature pages that state their own limits. A merchant who finds a gap during implementation loses far more than one who read about it before signing.
Compliance in the core
ZATCA is not a module to buy or an upsell on a higher tier. It is on every plan and in every sale, because a non-compliant invoice is not a missing feature — it is a legal problem.
We build on the floor
Every feature on this site came from a real shop that asked for it or suffered without it: the gold karat, the IMEI, the bakery recipe, the kitchen ticket that prints when the network is down.
- 8+
- Shops and branches running on Wameed
- 478+
- Sales put through the system
- 268+
- ZATCA-signed e-invoices issued
- 10
- Delivery platforms in one order queue
Counted live from the Wameed platform
The numbers above are read from the platform itself each time this page is opened — not from a spreadsheet we update when we remember.
49documented features492capabilities listed2complete languages
Come and try it
All of this is easy to write. It is easier to watch it run on your own products for half an hour.