In this article11
- Start here: which kind of provider is yours?
- The first criterion: is the connection direct with Meta, or through a reseller?
- The second criterion: Arabic as a first language, not a translation layer
- The third criterion: billing in riyals, and an invoice your accountant accepts
- The fourth criterion: which law governs your data?
- The fifth criterion: local integrations — ask for the name, not the number
- The sixth criterion: pricing transparency — Meta’s fees are not part of anybody’s subscription
- Where an international provider genuinely wins
- The criteria, row by row
- How to test a provider in a week
- What does not belong in the comparison
Every platform writes the same list: campaigns, a bot, an inbox, reports. And because they look alike on paper, what separates them is not what they do but what happens when you need something: an invoice your accountant accepts, an answer to a question during your working hours, or your number when you decide to leave.
Start here: which kind of provider is yours?
The first question is not “which is better” but “where does your business sit”. And that question has one right answer per company, not a general one that fits everybody.
Where does your business sit?
decisionA local provider
- The invoice is in riyals and tax-compliant, so no currency conversion and no manual reconciliation
- Processing under the Saudi Personal Data Protection Law
- Support answers in Arabic during the hours you actually work
- The ready integrations are the shop platforms you actually use
An international provider
- One contract covering many markets with different currencies and regimes
- A far wider integration catalogue with the global systems
- Bigger product teams and audit certifications procurement departments recognise
- Support coverage spread across several time zones
The first criterion: is the connection direct with Meta, or through a reseller?
WhatsApp Business is not sold by WhatsApp directly. You reach it through a Meta-accredited technical provider, and that accreditation is not a marketing badge but a technical position with tangible consequences. And the difference that matters to you is not “are they accredited” — many are — but where the WhatsApp Business Account ends up after you connect.
- When the connection is direct: you connect your number through Meta’s official Embedded Signup in the browser, and the WhatsApp Business Account (WABA) ends up inside your own business account, with the provider a partner you granted access to and can withdraw.
- When a reseller sits in the middle: your number runs under the provider’s account. The experience looks identical in the first month, and the difference appears the day you want to raise your messaging limit, submit business verification in your own name, or move to another platform.
- And the effect when something breaks: a direct provider raises a report with Meta on your account. A reseller raises one with whoever sits above them, and you become a third party to your own problem.
The second criterion: Arabic as a first language, not a translation layer
Almost every platform lists Arabic among its languages. The right question is not “does it support Arabic” but “was it built right to left, or flipped into it”. That difference shows up in four specific places:
- The interface. A product built for Arabic opens its menus from the right side, shows numbers and dates inside an Arabic sentence without them inverting, and writes its error messages in Arabic too. A translated product holds up until the first unexpected case, then falls back to English at the moment you need to understand what happened.
- The bot. Your customer does not write in formal Arabic. They write “how much” and “when will it get here” in dialect. A model that only understands formal Arabic will produce a grammatically correct reply that misses the context, or will not understand the question at all and escalate to an agent who need not have been involved. And the more important question after dialect is where the bot gets its answer from— your own documents, or general knowledge.
- Template review. Meta templates are rejected for precise reasons: a variable in the wrong place, marketing wording inside a utility template, a missing sample. Reviewing the template in Arabic before submitting it saves a whole rejection cycle, and repeated rejections are not free — they are days of delay on a campaign with a date.
- Support. Explaining a technical problem in a second language to somebody whose day starts as yours ends is not a small detail. Ask a specific question: in what language do you reply? In what hours? And what is the average time to first reply?
The third criterion: billing in riyals, and an invoice your accountant accepts
This is the clearest difference you can verify before buying, and it needs no opinion: ask for a sample invoice. A tax invoice in Saudi Arabia has a known shape — in riyals, carrying VAT, the tax number and a QR code — and is issued electronically under the requirements of the Zakat, Tax and Customs Authority.
An invoice issued in dollars by an entity outside the Kingdom does not do that job. And the problem does not end at the exchange rate; it ends at your tax return and your input-tax deduction. The result is monthly manual work for your accountant, and a different figure every month from the price you originally agreed.
The fourth criterion: which law governs your data?
Your customers’ conversations are personal data: phone numbers, names, orders, and sometimes health or financial information. And the Saudi Personal Data Protection Law (PDPL), issued by the Saudi Data and AI Authority, binds youas the controller of that data — not your provider.
So it is not enough for a provider to declare compliance. Ask for what you can keep on file:
- A written data-processing agreement stating that you are the controller and they are the processor, and limiting what they may do with the data.
- A published privacy policy explaining the data subject’s rights: access, correction, deletion, objection and portability, and the channel requests are made through.
- An undertaking to notify you of any breach, and within what time.
- A statement of where the data is stored and for how long, and whether hosting inside Saudi Arabia is available if that is a requirement in your sector.
An international provider may comply fully, but its regulator, its contract template and its forum for disputes are written for another regime, and you are the one who will stand before the local authority if asked. What we commit to is published on the policies page rather than promised on a call.
The fifth criterion: local integrations — ask for the name, not the number
“More than a hundred integrations” is a sentence that means nothing until you know whether one of them is your system. And in the Saudi market, the two ready integrations that matter to most shops are Salla andZid, and they are what let you connect orders, shipment states and abandoned baskets without writing a line of code.
And the practical question for any provider: what is the name of the integration with my shop platform? What exactly is synced — orders only, or customers and shipment states too? And who runs it when it breaks?
The sixth criterion: pricing transparency — Meta’s fees are not part of anybody’s subscription
This is the most misunderstood point in the market. Your cost on WhatsApp is made of two entirely separate numbers:
- Meta’s per-message fees. Set by Meta according to the recipient’s country and the template’s category, and they are the same for every provider — nobody buys them in bulk and nobody has a special price on them.
- The platform subscription. The price of the tools: campaigns, the bot, the inbox, reports, support. This is the only place offers differ.
Meta’s prices for the Saudi market, effective from 2026-04-01, worked out below over 1,000 messages so they show precisely — the price of a single message is a fraction of a halala that disappears in the rounding:
| Category | Cost of 1,000 messages | When it is used |
|---|---|---|
| Marketing campaigns | 187.70 SAR | Offers, launches and promotional messages |
| Utility messages | 40.10 SAR | Order confirmation, a shipment update, an appointment reminder, an invoice |
| Verification codes (OTP) | 40.10 SAR | Verification codes and sign-in |
| Replying to a customer | No fee from Meta | Replying to a conversation the customer started |
Work out your expected volume on the cost calculator, and the full detail of template categories and messaging windows is in the guide to Meta’s fees.
Where an international provider genuinely wins
A comparison that concedes nothing convinces nobody. There are places where an international provider is the sounder choice, and they are not few:
- Multi-country operations. If you send to ten countries with different currencies and tax regimes, one contract covering them all is genuine value, and splitting them across several local providers is more administrative burden than benefit.
- The integration catalogue. The global platforms pre-connect to many enterprise systems that have no ready local integration. If one of those is your backbone, a ready integration saves you a whole development project.
- Channel breadth. Anyone needing WhatsApp, email, SMS and other channels inside one product at global scale will find that more mature with the large platforms.
- Audit certifications. Procurement departments at large companies ask for international information-security certifications by name. A global provider usually has them ready, and it is a question worth putting to any provider explicitly — to us too — rather than inferring it from a security page.
- Engineering scale. Bigger teams mean a faster release cadence, more mature APIs, and wider documentation and developer community.
And the practical note: all of those advantages are billed to you, and you consume only the part that fits your case. A company selling in Riyadh and Jeddah and audited by a Saudi authority will not use the twenty-market contract, but it will pay the exchange difference every month and reconcile an invoice its accountant does not accept.
The criteria, row by row
The table below is not a verdict but a checklist. Apply it to any provider you are considering — to us as well — and ask for evidence on every row rather than settling for the answer.
A local provider against an international one
comparison| A local provider | An international provider | |
|---|---|---|
| Billing in riyals with no currency conversionPricing in dollars means a different figure every month from the one you agreed to | Yes | No |
| An approved electronic tax invoice with a QR codeA foreign invoice does not do its job in your tax return | Yes | No |
| Processing under the Saudi data protection lawAn international provider may comply, but its regulator and its contract template are foreign | Yes | Partly |
| An interface built right to leftTranslation moves the text but not the direction, nor the error messages | Yes | Partly |
| Support that answers in Arabic during your working hoursGlobal coverage exists, but usually in English and in another time zone | Yes | Partly |
| A ready integration with the local shop platformsLocally: Salla and Zid. Internationally: sometimes, and usually through custom development | Yes | Partly |
| Meta’s fees shown separately from the subscriptionCheck this with both — merging them is a pricing practice, not a nationality | Yes | Partly |
| A direct official connection through Embedded SignupAccreditation is nobody’s monopoly — check where the WhatsApp Business Account sits in either case | Yes | Yes |
| A wide global integration catalogueLocally the rest is covered by the API and webhooks rather than a ready integration | Partly | Yes |
| Operating in dozens of countries on one contractMeta’s prices are global for everybody, but the contract, the billing and the support are aimed at the local market | Partly | Yes |
| International security audit certifications, by nameAsk any provider for them explicitly rather than inferring them from a security page | Partly | Yes |
How to test a provider in a week
The pitch decks look alike. What separates them shows up at the first real contact, and six steps are enough to expose it before you commit to a year.
Six steps before you sign
sequence- 1Ask for the connection to happen in front of youIt must go through Meta’s official Embedded Signup in the browser, and end with a WhatsApp Business Account in your company’s name inside Meta’s business tools. And finish it on a desktop machine — connecting from a mobile browser stalls halfway more often than not.
- 2Ask for a sample invoice before you payIn riyals, carrying VAT, the tax number and a QR code. If the sample is in dollars you know your answer on the third criterion without further discussion.
- 3Write to support in Arabic during your working hoursWith a real technical question, not a sales enquiry. Measure the time to first reply, its language, and whether they understood the question or sent you back a help page.
- 4Submit one real templateYour own template, in its Arabic wording with its variables. Ask for it to be reviewed before it goes to Meta, and see whether the notes were useful or just “submitted, we are waiting”.
- 5Ask for the two numbers separatelyThe platform subscription on its own, and Meta’s expected fees at your expected volume on its own. Anyone refusing to separate them is selling you opacity, not a discount.
- 6Ask about leaving before you joinIf you decide to move after a year: who owns the WhatsApp Business Account? How long does releasing the number take? Are your contacts and conversations exported? A written answer here is worth everything before it.
What does not belong in the comparison
- The number of features. The long lists are nearly identical because the foundation is the same: WhatsApp itself. The difference is in how a feature is implemented, not in its presence on a list.
- “Sending speed”. The messaging limit is set by WhatsApp for your number according to your verification and your quality rating, not by the provider. The detail is in the messaging-limits guide.
- The advertised customer count. An unverifiable number, and it tells you nothing about your own case.
- A promise of “no Meta fees”. Not possible. Meta’s fees are paid to Meta; anyone saying they have removed them has folded them into the price.
How do I check for myself that a provider is Meta-accredited and not a reseller?
Open Meta’s business tools after connecting and look at the WhatsApp Business Account (WABA): it must sit inside your own business account, you must be the owner, and the provider must appear as a partner you granted access to. If you cannot find a WhatsApp Business Account in your company’s name at all, your number is running inside the provider’s account rather than yours — and that is the whole practical difference, visible in two minutes.
Is a local provider more expensive than the global platforms?
Meta’s per-message fees are the same for everybody — no provider has a special price from Meta. The whole difference is the platform subscription and what it includes. Compare three numbers, not one: the monthly subscription, what is charged on top of it, and Meta’s expected fees at your volume. An offer quoting “one price per message” that merges the two is not cheaper, only less transparent.
If I change my mind later, can I move my number to another provider?
Yes, whenever the WhatsApp Business Account is yours: the number is deregistered from the current platform and registered on the new one, and the number, the business name and the verification all stay as they are. But if the account is in the provider’s name you need their cooperation to release it, and that can take weeks. Ask about the exit before you sign, not after.
What is the practical difference between an Arabic interface and a translated one?
Translation moves the words and not the direction. In a translated interface menus open from the wrong side, numbers and dates break inside the sentence, and error messages come back in English at the first unexpected case — the exact moment you need to read them. The difference shows up most in the template editor, where punctuation and variables get tangled with the Arabic text.
Is it enough for a provider to say it complies with the data protection law?
No. Ask for four things in writing: a data-processing agreement stating that you are the controller and they are the processor, a published privacy policy explaining the data subject’s rights, an undertaking to notify you of any breach and within what time, and a statement of where the data is stored and for how long. The law binds you as the data controller, so your responsibility does not transfer to the provider on the strength of the word “compliant”.
I have a shop on Salla or Zid — what changes in the choice?
What changes is that you can ask for the integration by name rather than by count. The two ready integrations in the local market are Salla and Zid, and they are what let you connect orders and abandoned baskets with no development. Any other system — a point of sale, a CRM or an internal system — is connected through the API and webhooks, or managed by uploading a contact file by hand. Ask for the name, not the number.
