Is the integration official?

Yes. The Salla connection uses official OAuth, and messages are sent over Meta's official WhatsApp Cloud API.

Do I need a new WhatsApp number?

You need a number dedicated to WhatsApp Business. It can be a new number, or your current one if it is not tied to a personal WhatsApp account.

Do I need a developer?

No. The connection is one click in the dashboard, and messages are built by drag and drop.

What if I have more than one store?

Each Barqia account belongs to one store and one number. Multiple stores run as separate accounts so each store's data stays isolated from the others.

How long does setup take end to end?

The Salla connection itself takes a minute. Meta's flow to activate the number takes ten to fifteen. The part with no guaranteed time is template approval: Meta reviews them, which can take minutes or a day. Start the templates early so you are not waiting on them at the last step.

What if a customer blocks or reports my number?

Meta lowers your number's quality rating and may reduce your daily sending limit. Barqia shows the rating in the dashboard and alerts you when it drops, because the fix comes before you hit the limit, not after: cut back the broad campaigns and look at the template that preceded the drop.

Are messages sent in Arabic?

Yes, and it is the default. Templates are written in Arabic, and order statuses are translated into readable Arabic rather than passed through raw from the store or the courier. The dashboard itself is fully Arabic, with English available.

WhatsApp Business for Salla stores

Your Salla store already knows when a cart was left, when an order was placed, and when its status changed. Barqia turns those events into WhatsApp messages that reach the customer at the right moment — over Meta's official API, not an unofficial number. Connecting is one click through OAuth, and running it needs no developer and no middleman server.

Try 7 days free Pricing

What syncs from Salla

As soon as you approve the permissions, Barqia subscribes to Salla's webhooks and events start arriving the moment they happen — no hourly polling, no manual export.

An order is not read and forgotten: it is stored in Barqia as a real order record tied to the customer's number. That is what makes later targeting possible — "bought once and never came back in 60 days" is a question you cannot answer if the orders were never captured.

New orders, with total, currency and payment method.
Abandoned carts, with the resume link that returns the customer to the cart exactly as they left it.
Order and shipment status changes.
Products, so you can send a catalog item inside a conversation without copy-paste.

What you can automate

Every automated message is built on a Meta-approved template — that is the platform's requirement for any message you start, not a Barqia restriction. Variables (customer name, order number, total) are filled from Salla's data at send time.

What matters more is that automation does not run in isolation from the customer: before every marketing message or reminder, Barqia checks quiet hours, the per-number frequency cap, and consent — a message at two in the morning costs you a complaint, and three reminders in a day costs you a block. Utility messages (order confirmation, shipping update) are deliberately exempt from quiet hours: the customer is waiting for them, and deferring one delays their shipment. They still respect opt-outs and your quota, just not the clock.

A reminder for a customer who left a cart — up to three touches, on timing you choose.
A confirmation request for cash-on-delivery orders before you ship, so you don't ship an order nobody will accept.
A notice when the order ships and when it arrives, with the status written in Arabic rather than passed through from the courier.
A rating request after a conversation or an order closes.
Targeted campaigns to a segment of your customers — not to the whole list.

Abandoned carts: three touches, not one

Most tools send one reminder and stop. Barqia allows three: the first after two hours by default, the second after a day, the third after three days — and each delay is measured from when the cart was abandoned, not from the previous reminder, so one quiet-hours deferral cannot push the rest of the sequence into next week.

The second and third are optional, and each needs its own approved template — re-sending the same text is the fastest route to being blocked. Make the second a gentle nudge and the third a last call.

The sequence stops the moment the customer buys: the first order that arrives from Salla closes every open cart for that customer, so nobody who has already paid gets chased. After seven days the attempts stop for good — a week-old cart is not a warm lead.

Answering the customer afterwards

The automated message is half the job; the other half is what happens when the customer replies. Their conversation opens in a shared inbox your whole team can see, with their Salla orders alongside it. Nobody needs a second tab open to answer "where is my order?".

When the customer writes first, a 24-hour service window opens in which you can reply in free text with no template at all. Barqia shows the remaining time inside the conversation, because once that window closes your next reply only arrives as an approved template.

Conversations can be split across staff with different access: who sees which number, who sees only the chats assigned to them, and who never sees the customer's mobile at all.

Consent: marketing versus service

"Stop the messages" is not one request with one meaning. Someone who wants the offers stopped does not necessarily mean stop their shipping notice, and a tool that treats the two as one silences the confirmations they were actually waiting for.

So Barqia splits consent into two scopes: marketing (campaigns and offers) and utility (order confirmation, shipping update, a reply to a question). Opting out of marketing — through WhatsApp's own "Offers and announcements" control — leaves the utility messages alone. A typed «إلغاء» in the conversation, on the other hand, stops everything, deliberately: an explicit request is not one we split on the sender's behalf.

This is not cosmetic: Saudi Arabia's Personal Data Protection Law is built on consent, and Barqia keeps a consent and opt-out record per number, and can export or erase a customer's data on request.

Why the official API and not an unofficial number

Tools that drive WhatsApp through a hidden browser or a connected phone violate WhatsApp's terms, and the number they run on can be banned without warning and with no route back. The difference is not price — it is what happens the day the number all your customers know stops working.

Barqia is a Meta Tech Provider, and sending goes through the official WhatsApp Cloud API. That means concrete things: a verified display name on your number instead of an unknown one, messaging limits that grow with your number's quality instead of being guessed at, and a quality rating for your number shown in your dashboard, so you can watch it fall before you hit a sending limit — provided you look. (There is no automatic alert on a quality drop today; automatic notifications cover template rejections and account restrictions.)

The trade-off, plainly: messages you initiate need pre-approved templates, and Meta bills you for them. Templates are not administrative friction; they are what keeps the number alive.

What you actually need to start

Three things: a Salla store, a mobile number not tied to a personal WhatsApp account, and business verification.

Verification is two separate levels, and confusing them costs time. The first is Barqia's: we ask for a business document before you connect a WhatsApp number. Connecting your Salla store removes that step — the store already verified you, so your account is approved here with no documents. The second is Meta's own Business Verification, which is entirely separate and which connecting a store does NOT satisfy; without it your number runs at a lower sending tier. Clear the first by connecting your store, and start the second with Meta early.

How to start

1Create a Barqia account and complete your business profile — five fields open the 7-day free trial.
2In the Barqia dashboard, click "Connect Salla" and approve the store permissions. This removes the business-document step on our side.
3Activate your WhatsApp Business number through Meta's embedded signup, inside the dashboard.
4Create your message templates and get them approved by Meta — one template per message you intend to send.
5Pick the events to automate and set their timing: abandoned cart, COD confirmation, order status.
6Send a test message to your own number from inside the campaign dialog before your first broadcast, then switch it on.

Common questions

Is the integration official?: Yes. The Salla connection uses official OAuth, and messages are sent over Meta's official WhatsApp Cloud API.
Do I need a new WhatsApp number?: You need a number dedicated to WhatsApp Business. It can be a new number, or your current one if it is not tied to a personal WhatsApp account.
Do I need a developer?: No. The connection is one click in the dashboard, and messages are built by drag and drop.
What if I have more than one store?: Each Barqia account belongs to one store and one number. Multiple stores run as separate accounts so each store's data stays isolated from the others.
How long does setup take end to end?: The Salla connection itself takes a minute. Meta's flow to activate the number takes ten to fifteen. The part with no guaranteed time is template approval: Meta reviews them, which can take minutes or a day. Start the templates early so you are not waiting on them at the last step.
What if a customer blocks or reports my number?: Meta lowers your number's quality rating and may reduce your daily sending limit. Barqia shows the rating in the dashboard and alerts you when it drops, because the fix comes before you hit the limit, not after: cut back the broad campaigns and look at the template that preceded the drop.
Are messages sent in Arabic?: Yes, and it is the default. Templates are written in Arabic, and order statuses are translated into readable Arabic rather than passed through raw from the store or the courier. The dashboard itself is fully Arabic, with English available.