This is a field guide to maroof registration for the Saudi market. No theory you can't act on, and no advice that assumes a US search landscape.
Running an online store in the Kingdom means solving problems that pure-play advice from other markets ignores: cash-on-delivery economics, ZATCA clearance inside the order flow, Maroof registration, and delivery promises across a very large geography.
The short version
Most teams arrive at maroof registration after something stopped working: enquiries fell, a competitor became visible, or a target was missed. That context matters, because the right first move differs depending on whether you are fixing a decline or building from a standing start. Diagnose which situation you are in before applying anything below — the sequence changes completely, and applying a growth playbook to a decline problem wastes a quarter.
ZATCA-compliant invoicing inside the checkout flow
Electronic invoices must be generated in the required XML format, carry a QR code, UUID and cryptographic stamp, and clear through the Fatoora platform. Wave 24 closed on 30 June 2026 at a SAR 375,000 revenue threshold; Wave 25, announced in July 2026, halves that to SAR 187,500 with an integration deadline of 1 February 2027. At that level effectively every serious online store is in scope. Build clearance into the order pipeline with retry handling and reconciliation rather than bolting it on after launch.
Operations decide whether growth survives
Inventory accuracy across branches and warehouse, order routing, packing throughput, courier performance by city, returns processing and reconciliation. Ecommerce businesses in this market rarely fail on traffic; they fail when volume arrives and operations cannot absorb it. Model your capacity before you spend on the campaign that will test it.
Delivery promises you can actually keep
Saudi shoppers compare delivery time and cost before price. Publish realistic windows by city, be explicit about remote areas, and communicate proactively when something slips. An accurate three-day promise beats an aspirational next-day promise that fails a fifth of the time — failed promises drive returns, refunds, negative reviews and, ultimately, a permanent shift back to cash on delivery.
Platform choice: Salla, Zid, Shopify or custom
Salla and Zid are built for the Saudi context — Arabic-first administration, local payment and shipping integrations, ZATCA-aware invoicing — and get a small merchant trading quickly. Shopify offers a deeper app ecosystem and stronger international expansion. Custom builds make sense when the business logic is genuinely unusual: complex B2B pricing, ERP-driven catalogues, or regulated workflows. Choose on where your complexity actually sits, not on what is fashionable.
The businesses that win in Saudi search are rarely the biggest. They are the ones that did the unglamorous work consistently for four quarters.
Returns policy as a growth instrument
A clear, fair returns policy raises conversion more than it costs in returned goods. State the window, the condition requirements, who pays for shipping and how refunds are issued, in plain Arabic and English. Publish it where the hesitation actually occurs — on the product page and in the cart, not only in a footer link nobody opens.
Common failure modes worth checking today
Homepage targeting everything and therefore ranking for nothing. Service pages duplicated across cities with only the city name swapped. Arabic pages that are machine translations of English ones. Blog posts with no internal link to a commercial page. A robots.txt or noindex left over from staging. Each of these is a half-day fix and each has cost real Saudi businesses years of visibility.
Typical build and ramp
| Stage | Typical window | What you should see |
|---|---|---|
| Platform setup and catalogue | 2–4 weeks | Arabic product content is usually the bottleneck |
| Payments, BNPL and ZATCA clearance | 2–3 weeks | Sandbox access early avoids launch delays |
| Logistics and returns operations | 2–4 weeks | Courier selection and delivery promise testing |
| First profitable acquisition channel | 2–4 months | Usually search or Meta, rarely both at once |
Windows assume consistent execution and a market of ordinary competitiveness. Treat them as planning ranges, not commitments.
Budget allocation that survives a bad quarter
A workable starting split for a Saudi mid-market company: roughly 40% to demand capture — search, remarketing, marketplace presence — where intent already exists; 35% to demand creation across social and content; 15% to owned assets, website, email and CRM; 10% to experiments. Review quarterly against pipeline, not impressions, and move money towards whatever is producing qualified conversations.
Search intent decides the format
Look at what currently ranks before deciding what to build. If the first page is dominated by listicles, a sales page will not break in. If it is dominated by tools, publish a tool. If Google shows a map pack, the winning asset is a location page plus a well-tended profile, not a blog post. Matching format is a larger lever than word count, and it costs nothing but the discipline to check first.
Cross-border transfers and residency
Transfers of personal data outside the Kingdom carry specific conditions, and certain categories attract heightened expectations around local storage. This directly shapes hosting and cloud decisions. With hyperscaler regions now operating locally, in-Kingdom hosting is generally available at reasonable cost — and it also reduces latency for Saudi users, so the compliance choice and the performance choice frequently coincide.
Statistical honesty
Decide the sample size and duration before starting. Run full weeks to cover behavioural cycles — Thursday and Friday behave very differently from Sunday in this market. Do not stop the moment a variant looks ahead. Most reported CRO wins evaporate because the test was called early on an underpowered sample, and the organisation then builds strategy on a coin flip.
A checklist you can run this week
- Publish delivery windows by city, including remote areas, and measure accuracy
- Test the full checkout on a mid-range Android over a mobile connection
- Confirm ZATCA clearance is inside the order pipeline with retry and reconciliation
- Measure the current cash-on-delivery share and set a reduction target
- Show the total price including VAT and shipping before the final step
- Complete Maroof registration and display the badge
Reviews: volume, velocity, and the words inside them
Three signals matter and they are not equal. Volume gets you considered. Velocity — a steady trickle rather than forty reviews in one week — keeps you credible. And the language inside reviews feeds relevance: when customers naturally mention the service and the district, those terms strengthen the profile. Build a request into the moment of delivery, ask by WhatsApp because that is where Saudi customers actually reply, and never incentivise. Reply to every review in the language it was written in.
Where to start this week
Check three numbers: cash-on-delivery share, cart abandonment rate, and delivery promise accuracy by city. Each has a direct, known fix. Then confirm your ZATCA clearance pipeline handles failures gracefully — with Wave 24 in force since 30 June 2026 and Wave 25 due by 1 February 2027, an invoicing outage is now a trading outage.
The Saudi market is moving quickly enough that a decision deferred by two quarters is usually a decision made by a competitor instead. Choose the smallest useful version and start.
