Why KSA restaurants urgently need WhatsApp direct in 2026
Saudi Arabia is one of the most aggregator-dependent F&B markets on the planet. HungerStation (Delivery Hero group), Jahez, Toyou and Marsool together intermediate more than 90% of paid online delivery volume in the Kingdom. HungerStation alone routinely runs above 45% market share in the largest cities. That concentration is comfortable for the guest and expensive for the operator. Base commissions typically run 22-28%. On top of that, aggregators charge a "sponsored listing" or "top-slot" fee that most operators quietly treat as mandatory — without it the listing disappears below the fold in the first search screen. Add payment processing and mandatory promotional co-funding and the all-in take rate sits between 25% and 33% of gross order value.
On a SAR 40 ticket that means SAR 10-13 leaves the outlet before any food cost, packaging cost, delivery fee reimbursement or salary hits the P&L. On thin-margin cloud kitchens in Riyadh Al Malaz or Jeddah Al Rawdah working at 60-65% food cost plus packaging, that all-in aggregator take can convert a nominal 15% gross margin into a small operating loss. This is the reason well-run Saudi operators — from single-outlet Riyadh shawarma joints to Kingdom-wide chains — are building a direct channel in parallel with, not instead of, aggregators.
WhatsApp is the natural direct channel in the Kingdom. It is the default messaging app across every region and every nationality. It is where the guest already talks to the restaurant to ask "is the kabsa spicy?" or "when will my order arrive?" — so pushing an order button into that same thread is a zero-friction upgrade. And unlike a mobile app the guest never has to install it or remember a login. There is also a strong cultural signal: WhatsApp is now the default booking channel for Saudi wedding catering and majlis events, both of which sit outside the aggregator flow entirely.
WhatsApp usage in Saudi Arabia — the numbers
Smartphone penetration in Saudi Arabia sits at approximately 90% of the adult population, and roughly 93% of those smartphone users are on WhatsApp — one of the highest rates in the world. That cuts across nationalities: Saudi national, GCC-national, Egyptian, Levantine, South Asian and Filipino guests all default to WhatsApp for personal and small-business communication. In the KSA F&B context this means the WhatsApp inbox is already the primary channel where a guest asks operating hours, sends a delivery address, confirms a majlis catering booking or complains about a late order. The delta between "restaurant on WhatsApp for chat" and "restaurant on WhatsApp for ordering" is a tooling upgrade — the audience is already there.
The cultural fit runs deeper than in most markets. Arabic-speaking Saudi audiences use WhatsApp voice notes heavily, which is not a workflow any aggregator supports well. Family orders in the Kingdom frequently get placed by one member on behalf of the household, and WhatsApp's group-chat pattern maps onto that far better than an aggregator app that assumes a single user. And Saudi hosting culture — from the daily majlis to Ramadan iftars, weekend gatherings and weddings — makes WhatsApp catering orders a growing segment that aggregators simply do not cover.
WhatsApp Business API in the Kingdom — CST + telecom setup
WhatsApp Business comes in two flavours. The free WhatsApp Business App is fine for a single outlet answering messages manually — up to a few hundred contacts. Beyond that, WhatsApp Business API is required, and it is what powers the catalog, automated confirmations, payment links, order routing to KDS, and CRM syncing that this guide is about.
The API is provisioned through a Meta-approved Business Solution Provider (BSP). Meta does not sell API access directly to end-restaurants. The BSP holds the messaging contract, runs template approvals, provides the sending infrastructure, and often bundles a dashboard for template management and analytics. Online eMenu's sister BSP, Go4WhatsApp, serves KSA operators from a Dubai base alongside other Meta-partner BSPs — the choice of BSP is separable from the choice of ordering software.
Setup requirements are light on the KSA regulatory side. The Communications, Space and Technology Commission (CST, formerly CITC) does not require a separate licence for WhatsApp Business messaging — WhatsApp runs over data, not SMS, so it sits outside the A2P SMS licensing regime that applies to bulk SMS senders in the Kingdom. The Green Tick (verified business badge) is optional and worth applying for if the outlet is a chain, franchise or well-known standalone — it takes 4-8 weeks of Meta review after the BSP submits. Arabic-first display is strongly recommended: roughly 95% of Saudi guests prefer Arabic for restaurant browsing, unlike the UAE which is more English-mixed.
Aggregator commission comparison — HungerStation, Jahez, Toyou, Marsool, Careem Food, WhatsApp direct
Every KSA operator argues about the "real" commission rate. The confusion is fair — aggregators quote the base rate, operators feel the all-in rate. Below is a side-by-side that treats the five KSA aggregators consistently: base commission published in the restaurant partner agreement, ad-boost or sponsored-slot spend that most competitive listings run, restaurant-funded discount contribution that runs almost continuously during Ramadan and summer campaigns, payment processing, and the resulting all-in take on a headline SAR 40 order.
| Line item | HungerStation | Jahez | Toyou | Marsool | Careem Food KSA | WhatsApp Direct |
|---|---|---|---|---|---|---|
| Base commission | 22-28% | 20-25% | 25-30% | 20-25% | 22-28% | 0% |
| Ad boost / sponsored slot (typical) | 3-5% | 3-5% | 2-4% | 2-4% | 3-5% | 0% |
| Restaurant-funded promo (typical) | 2-4% | 2-4% | 2-4% | 2-4% | 2-4% | Optional |
| Payment / gateway fee | 1-2% | 1-2% | 1-2% | 1-2% | 1-2% | 2.5% + SAR 1 |
| All-in take (headline) | 28-33% | 26-32% | 30-33% | 25-30% | 28-33% | ~4-5% |
| On SAR 40 order, taken by platform | SAR 11-13 | SAR 10-12 | SAR 12-13 | SAR 10-12 | SAR 11-13 | SAR 2.60 |
| Net to operator on SAR 40 | SAR 27-29 | SAR 28-30 | SAR 27-28 | SAR 28-30 | SAR 27-29 | SAR 37.40 |
WhatsApp direct is not free — it carries a fixed subscription (Online eMenu Ordering Suite at USD 9/month, roughly SAR 34, for the GCC bundle) plus per-conversation WhatsApp charges of roughly SAR 0.28 for utility and SAR 1.60 for marketing conversations. Even at the higher end that sits well under 5% of order value for a 200-500 order/month single outlet. The math tilts more in favour of direct as order volume grows.
Setup path — BSP-assisted, 48 hours
The full BSP-assisted setup runs in about 48 elapsed hours, most of which is Meta Business Verification waiting time. Active operator work is 5-7 hours across the two days, including ZATCA e-invoice integration testing. The 8 steps below are the exact sequence.
Complete Meta Business Verification with CR number
Create a Meta Business Manager account at business.facebook.com. Add your Commercial Registration (CR) certificate PDF, a recent SEC utility bill in the business name, and the authorised signatory's Saudi national ID or Iqama. Submit for Business Verification. Turnaround is typically 24-72 hours. Rejections almost always come from mismatched trading names on the CR versus the Business Manager entity — get these character-for-character identical in both Arabic and English where the CR shows both scripts.
Sign the BSP contract
Pick a Meta-approved BSP with KSA billing capability. Sign the messaging contract, which covers per-conversation charges, template approval SLA, and — optionally — Green Tick submission assistance. Prepay the first month's messaging budget: SAR 100-300 covers a comfortable buffer for a single outlet.
Provision the WhatsApp Business API number
Use a dedicated KSA mobile or landline number that is not already on consumer WhatsApp. If it is, delete the consumer account from settings first — the API migration will fail otherwise. The BSP triggers the migration via Meta, and within a few hours you get a phone-number-ID and access token that the ordering platform can use to send and receive.
Import the menu to Meta Catalog (Arabic + English)
Meta Commerce Catalog is where WhatsApp reads product listings from. Upload via CSV (best for 50+ SKUs) or the Catalog Manager UI (fine for smaller menus). Each SKU needs an Arabic-first name, English secondary name, SAR price (inclusive of 15% VAT), a 500-800px square image, and a short description. Category grouping — Starters, Mains, Rice, Grills, Desserts, Beverages — improves in-thread browsing.
Wire the KSA payment gateway
Connect Tap, HyperPay or PayTabs — whichever the outlet already uses for its point of sale. Enable Mada acceptance, Apple Pay, Google Pay, STC Pay and card processing. Configure a payment-link template that gets pushed into the WhatsApp thread the moment the order is confirmed on the KDS. Test with a live SAR 1 transaction end-to-end before opening to real orders.
Test the Arabic RTL catalog
Verify right-to-left rendering of every catalog item on both iOS and Android WhatsApp before going live. Fix any mixed-script SKU names where the Arabic dish name renders alongside an English brand or ingredient — these are the most common visual defects on the KSA launch checklist. Ask two or three Arabic-native staff to scroll the catalog on their own phones and flag anything that reads awkwardly.
Integrate the ZATCA Phase 2 e-invoice test
ZATCA Phase 2 requires every B2C order to generate a Fatoora-compliant e-invoice with a QR code, seller VAT number, itemised amounts, 15% VAT and a cryptographic signature. Wire your ZATCA-approved e-invoicing solution to the ordering platform, then run a live SAR 1 end-to-end test — the customer should receive a payment link, pay by Mada or Apple Pay, and receive a QR-tagged Fatoora e-invoice PDF inside the WhatsApp thread. See our ZATCA compliance page for the current wave rollout and technical spec.
Go live with the first opt-in flow
Print a small QR code that opens a wa.me deep link with a pre-filled greeting message ("مرحبا، أرغب في رؤية القائمة" or "Hi, I would like to see the menu"). Stick the QR on every table, every takeaway bag, and every till receipt. Send a launch template message to your existing customer database — but only to contacts who have documented opt-in under KSA PDPL (2023). Watch the first 24 hours closely, tune anything that misfires, then flip on paid Meta click-to-WhatsApp ads.
Menu + catalog for bilingual Arabic + English audience (Arabic-first)
Meta Catalog fully supports Arabic and English side-by-side. The default field layout gives you 150 characters for product name and 9,999 for description — comfortable for both scripts. Right-to-left rendering is native inside WhatsApp threads on both mobile OS versions.
The KSA best-practice pattern is Arabic-first. Unlike the UAE where Marina and DIFC menus often lead with English, roughly 95% of Saudi guests prefer Arabic browsing — from Riyadh Al Olaya to Jeddah Al Rawdah to the Eastern Province. Put the Arabic dish name in the primary name field ("كبسة لحم") and the English transliteration or translation in the description first line ("Kabsa Lahm — Saudi lamb and rice"). For a chain with strong Western-expat clusters — for example a Riyadh compound-catering brand — duplicate the SKU into two catalog entries with distinct locales, and let the customer pick their preferred browsing language on first message.
Traditional Saudi dish names deserve care. "كبسة" (kabsa), "مندي" (mandi), "مطبق" (mutabbaq), "جريش" (jareesh), "قرصان" (qursan) — write them in Arabic as the primary name and give a one-line English gloss for expats. Never let auto-translate produce the Arabic — hire a native Saudi copywriter for the menu once, and the catalog reads naturally to every guest. A few catalog hygiene rules that save time later: keep item names under 40 characters even though the field allows 150 (long names get truncated in the WhatsApp product card); use consistent capitalisation on English secondary names ("Chicken Shawarma" not "chicken shawarma" and not "CHICKEN SHAWARMA"); and price every item SAR-inclusive of 15% VAT with two decimals ("SAR 26.25", not "SAR 26" or "26.25 SAR").
Payment integration — Mada, Apple Pay, STC Pay, Tap, PayTabs, HyperPay
The Kingdom has one of the most Mada-dominated payment stacks in the region — Mada is the interbank card scheme run by SAMA and the default rail for domestic card payments. A properly wired WhatsApp ordering flow should accept, at minimum, Mada, Apple Pay, Google Pay, STC Pay, international card (Visa/Mastercard for tourists and expats), and cash on delivery. Below is how each gateway maps to what most KSA F&B operators actually use.
| Gateway | Mada | Apple Pay | Google Pay | STC Pay | Setup fit |
|---|---|---|---|---|---|
| Tap | Yes | Yes | Yes | Yes | Kuwait HQ, strong KSA presence — clean API, best for chains and multi-outlet |
| HyperPay | Yes | Yes | Yes | Yes | Amman-based with heavy KSA install base, robust Mada acceptance |
| PayTabs | Yes | Yes | Yes | Via partner | Strong SME plan, good Arabic checkout UX |
| Moyasar | Yes | Yes | Yes | Yes | KSA-native, well-liked by developer teams |
| Checkout.com | Yes | Yes | Yes | Via partner | Best for cross-border chains billing outside KSA |
The mechanics inside WhatsApp are identical across gateways: the ordering platform generates a hosted-checkout link on order confirmation, pushes the link into the WhatsApp thread, the customer taps and pays inside their browser (Apple Pay finishes in one Face ID confirmation, Mada finishes with SMS 3DS in seconds), and the webhook confirms payment back to the KDS which marks the order paid. In-thread native WhatsApp payments are not yet enabled in KSA at the time of publication — the hosted-link pattern is the working alternative and converts well.
15% VAT is auto-calculated on every line item and shown separately on the Fatoora e-invoice PDF that gets sent alongside the payment confirmation. This is a ZATCA Phase 2 requirement — the customer needs a QR-tagged e-invoice, not just a payment receipt. STC Pay is worth enabling specifically for younger Saudi guests, for whom it is the default digital wallet.
Compliance — ZATCA Phase 2 e-invoicing (Fatoora), SFDA + Municipal food licence, PDPL 2023
WhatsApp direct ordering does not create new compliance obligations — it inherits the compliance the outlet already has. But four boxes must be visibly ticked in the customer flow.
1. ZATCA Phase 2 e-invoicing (Fatoora). Every paid order in KSA must generate an e-invoice through a ZATCA-approved integration that produces a Fatoora-compliant record with a QR code, seller VAT number, buyer detail where applicable, itemised amounts, 15% VAT amount, and a cryptographic signature. The QR code encodes seller name, VAT number, invoice timestamp, VAT total and grand total in a Base64 payload that the buyer can scan and verify against ZATCA. Online eMenu generates this automatically via its ZATCA-approved integrations and delivers a QR-tagged Fatoora e-invoice PDF link inside the WhatsApp thread on payment confirmation. See our ZATCA compliance page for the current wave-by-wave rollout and integration options.
2. SFDA licence plus Municipal food permit. The Saudi Food and Drug Authority (SFDA) licenses food businesses federally; each city Municipality (Amanah) then issues the local food-establishment permit — Riyadh Municipality in Riyadh, Jeddah Municipality in Jeddah, Dammam Municipality in the Eastern Province. Both numbers should appear on the WhatsApp order confirmation message and on the Fatoora e-invoice. Showing licence numbers on every confirmation doubles as guest trust — it is a visible signal the outlet is properly licensed.
3. Saudi Personal Data Protection Law (PDPL, 2023). Every WhatsApp contact is personal data under Saudi PDPL. Store only what you use: phone number, name, delivery address, order history. Provide a clear opt-out ("للإلغاء أرسل STOP" — "Reply STOP to unsubscribe") in every marketing template. Larger operations (multi-city chains, franchises, aggregator-scale operators) should designate a Data Protection Officer as required under PDPL. Do not export or share the contact list with third parties without documented consent.
4. 15% VAT — auto-included on the Fatoora e-invoice. KSA VAT is 15% on prepared food (raised from 5% in July 2020). The Fatoora e-invoice must show the VAT amount separately from the base amount. Online eMenu wires this into the e-invoice template so no manual calculation is ever required at the till.
Real Riyadh cloud kitchen cost math (SAR breakdown)
Take a working example — a single cloud kitchen unit in Al Malaz, Riyadh, doing 500 delivery orders per month at an average ticket of SAR 42. Monthly gross delivery revenue is SAR 21,000. Compare two operating models: 100% aggregator versus 70% aggregator + 30% WhatsApp direct.
| Line item | 100% aggregator | 70% aggregator + 30% WhatsApp |
|---|---|---|
| Monthly orders | 500 | 500 (350 aggregator + 150 WhatsApp) |
| Avg ticket | SAR 42 | SAR 42 |
| Gross monthly revenue | SAR 21,000 | SAR 21,000 |
| Aggregator all-in take @ ~26% | -SAR 5,500 (500 × SAR 11) | -SAR 3,850 (350 × SAR 11) |
| WhatsApp gateway fees (2.5% + SAR 1 per direct order) | - | -SAR 90 (150 × ~SAR 0.60 net over base fee) |
| Online eMenu Ordering Suite subscription | - | -SAR 34 (USD 9) |
| WhatsApp per-conversation charges | - | -SAR 80 (est.) |
| Total channel cost | SAR 5,500 | SAR 4,054 |
| Monthly saving (channel cost) | - | SAR 1,446 |
| Annualised saving | - | SAR 17,350 (~USD 4,625) |
The SAR 1,446/month saving is on a modest 30% direct-channel share. Operators who cross the 50% direct-channel mark — which repeat-customer-heavy Al Malaz and Al Olaya cloud kitchens routinely do after 12-18 months of consistent WhatsApp acquisition — see the saving roughly double. The single biggest driver of that shift is the second-order effect: repeat guests who first discovered the outlet on HungerStation come back through the WhatsApp number printed on the packaging insert, and that guest lifetime value moves off-aggregator permanently. Punch your own volume into our aggregator profit calculator to see the shape for your outlet.
Getting customers to your WhatsApp — insert cards, GBP, Meta ads
The WhatsApp channel only compounds if new customers keep arriving. Four acquisition mechanics carry most of the load for KSA operators. Each is compatible with the others — most well-run outlets run three or four in parallel.
1. Insert card in every delivery bag. A5 card, printed both sides, Arabic on one side and English on the other. Message: "اطلب مباشرة في المرة القادمة ووفر SAR 5 — امسح للواتساب" / "Order direct next time and save SAR 5 — scan to WhatsApp." QR opens a wa.me deep link with a pre-filled greeting. Conversion rate on well-designed insert cards runs 4-7% of delivery guests over a 90-day window — slightly higher than the UAE because of stronger price sensitivity in the Saudi mid-market.
2. Google Business Profile with click-to-WhatsApp CTA. Every KSA outlet needs a claimed GBP with the "Message" button wired to WhatsApp. Guests searching "أفضل مطعم كبسة قريب مني" or "biryani Al Olaya" land on the GBP and can start a WhatsApp order without ever leaving the search result. Free, high-intent, permanent. Bilingual profile — English and Arabic name fields both filled — is essential.
3. Meta click-to-WhatsApp ads. Instagram is the dominant social platform in the Kingdom for F&B discovery, and Meta's click-to-WhatsApp ad objective converts strongly. Target region (Riyadh / Jeddah / Eastern Province) + neighbourhood + interests, run a SAR 100-400/day budget for a new outlet, use the ad creative to preview a specific dish and SAR price. Cost per opt-in in KSA for a well-targeted F&B campaign runs SAR 5-15 — typically lower than UAE because of larger addressable audiences per creative.
4. Guest opt-in on dine-in tables. QR sticker on every table that opens a wa.me link. Waitstaff mentions it once per table ("Scan here to save this table's number in WhatsApp for next time"). Converts dine-in guests into a delivery-capable contact base at zero incremental cost. Deploy Online eMenu's WhatsApp opt-in generator to build the exact link and QR in under a minute.
Ship WhatsApp ordering for your KSA restaurant — $9/month, live in 48 hours
Online eMenu Ordering Suite runs WhatsApp catalog, orders, KDS routing and ZATCA Phase 2 Fatoora e-invoicing for USD 9/month per outlet across the GCC. Arabic-first bilingual out of the box. Compatible with every KSA payment gateway including Mada, Apple Pay and STC Pay. WhatsApp Anuj on +971 54 508 5552 for the 48-hour BSP-assisted setup, or see the pricing card first.
WhatsApp us — +971 54 508 5552 See pricingFrequently Asked Questions
Is WhatsApp Business API available in Saudi Arabia?
Yes. WhatsApp Business API is fully available in Saudi Arabia and is provisioned through a Meta-approved Business Solution Provider (BSP). The API works over data — the same as consumer WhatsApp, which has ~93% penetration among KSA smartphone users, one of the highest rates globally. No special product licence is needed from Meta; the BSP handles number onboarding with the operator's Commercial Registration (CR) number, template approvals and Green Tick verification for chains and franchises.
Do I need CST or telecom licence to send WhatsApp Business messages in KSA?
No. The Communications, Space and Technology Commission (CST, formerly CITC) does not require a separate licence to send WhatsApp Business messages in Saudi Arabia. WhatsApp runs over data, not SMS, so it sits outside the A2P SMS licensing regime that applies to bulk SMS senders. You still need to respect WhatsApp Business Policy, WhatsApp Commerce Policy and the Saudi Personal Data Protection Law (PDPL, 2023) — meaning documented opt-in for every recipient and a clear opt-out path in every message.
How much does WhatsApp Business API cost for a Riyadh restaurant?
Meta charges per conversation, not per message, and the KSA market rate is roughly SAR 0.28 for a utility conversation (order confirmation, delivery update) and SAR 1.60 for a marketing conversation (promo blast). Service conversations initiated by the customer inside 24 hours are free. BSP platform fees add USD 5-40/month depending on tier. Online eMenu bundles WhatsApp catalog, orders and KDS at USD 9/month (~SAR 34) — the WhatsApp usage cost sits on top and typically stays under SAR 100/month for a single outlet doing 500 orders.
Can WhatsApp catalog show my menu in Arabic and English?
Yes. Meta Catalog supports bilingual product names and descriptions per SKU. The KSA best practice is Arabic-first — put the Arabic name in the primary name field and the English name on the description first line — because 95% of Saudi guests prefer Arabic browsing. Character limits are 150 for name and 9,999 for description — comfortable for both scripts. Right-to-left rendering is native inside WhatsApp threads on iOS and Android.
Which payment methods work with WhatsApp orders in Saudi Arabia?
Any KSA payment gateway that returns a shareable payment link works — the link is pushed into the WhatsApp thread the moment the order is confirmed. Tap, HyperPay and PayTabs all support Mada (the dominant KSA card network), Apple Pay, Google Pay, STC Pay, Visa, Mastercard and card processing. Mada plus Apple Pay is now the highest-conversion combination in the Kingdom for mobile-first checkout. Cash on delivery is also supported end-to-end — the driver marks the order paid on delivery and the ticket closes.
How does WhatsApp ordering compare to HungerStation commission?
HungerStation's all-in take rate in KSA — base commission plus mandatory ad boost plus payment fee — typically lands between 27% and 33% of order value. On a SAR 40 ticket the outlet nets around SAR 27-29. A WhatsApp direct order using Online eMenu costs a fixed USD 9/month subscription plus the payment-gateway fee (roughly 2.5% + SAR 1 on Mada). On the same SAR 40 ticket the outlet nets around SAR 37.60. Break-even against a single outlet's HungerStation volume is usually crossed inside the first 15-20 direct orders per month.
Are WhatsApp orders ZATCA Phase 2 compliant?
Yes, if you issue a Fatoora e-invoice through a ZATCA-approved integration. ZATCA Phase 2 requires every B2C order in KSA to generate an e-invoice with a QR code, the seller's VAT number, buyer detail where applicable, itemised amounts, 15% VAT and a cryptographic signature. Online eMenu integrates with ZATCA-approved e-invoicing solutions and delivers the Fatoora-compliant e-invoice as a PDF link inside the WhatsApp thread on payment confirmation. See our ZATCA compliance page for the full wave-by-wave rollout.
Do I need SFDA licence to accept WhatsApp orders?
Yes. You cannot legally accept a paid food order in any channel — WhatsApp, aggregator, dine-in, phone — without a valid Saudi Food and Drug Authority (SFDA) food business licence plus the equivalent Municipal food permit for the city (Riyadh Municipality in Riyadh, Jeddah Municipality in Jeddah, Dammam Municipality in the Eastern Province). The licence numbers should also appear on the confirmation message and on the Fatoora e-invoice — this doubles as guest trust.
Can I use the same WhatsApp Business number across Riyadh + Jeddah + Dammam?
Yes. One WhatsApp Business API number can service outlets across every KSA city under the same Commercial Registration. Most Saudi chains run a single WhatsApp number for the brand and route orders to the correct outlet by delivery address — Riyadh Al Malaz, Jeddah Al Rawdah, Dammam Al Faisaliyah — from inside the ordering platform. Keep one Meta Catalog per brand, and configure the KDS to auto-route each order to the nearest kitchen. Where a franchise operates each city under a different CR, keep separate numbers so ZATCA e-invoicing is issued under the right VAT entity.
How long does WhatsApp ordering setup take for a Riyadh restaurant?
About 48 hours end-to-end via a BSP-assisted flow. Meta Business Verification with the CR number takes 24-72 hours depending on document quality. WhatsApp Business API number provisioning is same-day once verification clears. Meta Catalog import for a 50-100 item menu runs 2-3 hours. Payment-gateway wiring is 1-2 hours if the Tap or HyperPay account already exists. ZATCA Phase 2 e-invoice integration testing is 2-3 hours. Arabic-first bilingual catalog polish is the longest step — plan a full working day if you want the Arabic copy to read naturally rather than machine-translated.