Salla abandoned cart recovery on WhatsApp: setup, timing, and costs (2026)
TL;DR: Quick Summary
- Salla stores can recover carts on WhatsApp when Salla's cart event starts a short template sequence on a WhatsApp Business API platform.
- SAMA reports 85% of Saudi retail payments were electronic in 2025, so a checkout link on WhatsApp matches how shoppers already pay.
- The abandoned cart event carries the shopper's mobile number and checkout link, and Make.com or a webhook passes it to WhatsApp.
- Collect WhatsApp opt-in at checkout, then send three reminders over about a day and keep any discount for the last one.
- Each reminder is a Meta marketing charge, so ending the sequence the moment Salla records the order is the biggest cost control.
Every abandoned cart in your Salla store holds what you need to win it back: the shopper's mobile number and a link straight to checkout. That's enough to reach them on WhatsApp within the hour, while they still remember what they were buying.
Salla's own reminders can send that first nudge. But when a shopper replies with a question about sizes or delivery, someone has to answer before they'll check out.
Saudi shoppers already pay online for most purchases: 85% of retail payments were electronic in 2025, according to the Saudi Central Bank. A WhatsApp reminder with a checkout link brings them back to a payment step they know.
Below, you'll find how the Salla cart event reaches WhatsApp, a three-message sequence you can copy, the consent you need first, and what each reminder costs after Meta's 1 Oct 2026 pricing change.
What is Salla abandoned cart recovery on WhatsApp?
Salla abandoned cart recovery on WhatsApp is an automated sequence that messages a shopper on WhatsApp after they leave items in your Salla checkout. The store records the abandoned cart, a messaging platform receives that event, and approved templates go out at set intervals with a link back to checkout until the shopper buys or the sequence ends.
Salla already has reminders built in. Under Marketing > Abandoned Carts, you can create a maximum of 5 reminder settings and send them by SMS, email, push notification for App Maker subscribers, or WhatsApp for WhatsApp by Salla subscribers.
That covers a store that only needs to send the reminder.
Salla's built-in reminders vs a WhatsApp Business API platform
The built-in reminders suit a store that wants a quick nudge with no extra tools. A WhatsApp Business API platform suits a store whose shoppers reply, ask about sizes or delivery, and need an answer before they finish checking out. The difference shows up once a shopper writes back.
There's a middle option too: a WhatsApp app from the Salla App Store. Many of them send cart reminders and suit stores that mainly need notifications.
Before you install one, check that it sends through the official WhatsApp Business Platform and see how it handles replies.
If you're still choosing how WhatsApp connects to your store at all, start with our guide to connecting WhatsApp to Salla, which compares Salla Chat, Salla App Store apps, and the official API.
How does a Salla cart event trigger a WhatsApp sequence?
When a shopper leaves a cart, Salla fires an event that carries their mobile number, cart total, and checkout link. A messaging platform receives that event, either through Make.com or a direct webhook, and starts a flow that waits, checks whether the order has come in, and sends an approved WhatsApp template if it hasn't.
What Salla sends when a cart is abandoned
Salla's developer docs list three abandoned cart events. Two of them matter here:
- abandoned.cart and abandoned.cart.update: fire when an abandoned cart is created or updated. The example payload includes the customer's name and mobile number, the cart total, the cart's age in minutes, and a checkout_url that takes the shopper straight back to their cart.
- abandoned.cart.purchased: fires when that cart is bought. This is your stop signal.
A shopper who adds one more item can send a second event for the same cart. Build your flow so that second event doesn't restart the sequence.
Route A: connect Salla to SleekFlow with Make.com (no code)
Salla's app on Make is maintained by Salla and includes Watch Abandoned Cart and Watch Order Created triggers. SleekFlow's Make app can create or update a contact, and SleekFlow's Pro plan and above include the Make.com integration.
- Trigger: Watch Abandoned Cart in Salla.
- Action: Update a contact in SleekFlow, saving the checkout link and the time into contact fields such as "Cart link" and "Cart abandoned at."
- Flow: a SleekFlow flow starts on the "Contact property field is updated" trigger, waits with a Time delay node, then sends your first cart template.
- Stop rule: a second Make scenario, on Watch Order Created, updates a "Cart status" field. Before each send, the flow checks that field and ends if the order is in.
Every cart event that reaches SleekFlow this way counts toward your plan's monthly API call limit, which Make.com shares with Zapier and the Platform API. A busy store should check its cart volume first.
Route B: send Salla webhooks straight to SleekFlow (developer needed)
A developer sets up a Salla app through the Salla Partners portal, installs it on your store, then registers webhooks for abandoned.cart and abandoned.cart.purchased through Salla's API, which accepts custom headers. In SleekFlow, the "A webhook is received" trigger supplies a webhook URL and token plus a trigger ID, with the ID and token sent in the request header.
You then point SleekFlow at the payload field holding the shopper's mobile number and paste a sample payload, so fields like the cart total and checkout link become message variables. The webhook trigger is on SleekFlow's Premium and Enterprise plans.
Why Zapier isn't the starting point for cart recovery
Salla's Zapier app has triggers for orders, products, and customers, but none for abandoned carts. It can still feed a stop rule, but the cart event itself has to come through Make.com or a webhook.
What should a three-message cart recovery sequence say?
Three messages over about a day give a shopper a reminder, a chance to ask a question, and a final reason to finish. Each message needs a Meta-approved template with the checkout link on a button, and each one should check for a completed order first, so nobody gets a reminder for something they've already bought.
These timings are a starting point to test against your own results. Salla's own scheduled reminders send the second one 12 hours after the first, which is a sensible baseline to compare against.
Message 2 is built to get a reply, because a reply opens WhatsApp's 24-hour customer service window. From that point, your team or an AI agent can answer freely, with the cart details already in the contact record.
Rules that keep the sequence clean
These keep shoppers from getting the wrong message, or too many:
- Switch off Salla's own reminders for the same carts. Otherwise one shopper can get two reminders for one cart, and you pay for both.
- Keep the discount for message 3. In our view, a code in the first message trains shoppers to wait for one next time.
- Mind the timing rules on discounts. Salla restricts when discount messages can be sent, citing the CST's anti-spam rules, so check send windows before you schedule message 3.
- Submit Arabic and English versions. Each template is approved for one language, so a bilingual store submits both under the same template name.
- Don't open or close a template with a variable. Meta doesn't allow it, so start with a word, as in "Hi {{1}}," and end on plain text or a button.
What consent do you need before sending cart reminders on WhatsApp?
You need opt-in before the first reminder goes out. Meta requires businesses to get opt-in that names the business and makes clear the person agrees to receive its WhatsApp messages. For a Salla store, the natural place to collect it is checkout or account sign-up, before the cart is abandoned.
Before you switch the sequence on:
- Ask at checkout or sign-up. A clear line or checkbox that names your store and WhatsApp meets Meta's opt-in requirements, and your website is one of the methods Meta lists.
- Ask for marketing by name. WhatsApp's Business Messaging Policy recommends separate opt-in by category, and cart reminders are marketing messages.
- Honor every stop request. The same policy requires you to respect requests to opt out, whether they come through WhatsApp or another channel, so tag those contacts and exclude them from the flow.
- Check local rules. Saudi messaging and data protection rules sit on top of Meta's. Confirm your consent wording with local counsel before launch.
Our guide to collecting WhatsApp opt-ins covers wording and placement in more detail.
What does a WhatsApp cart recovery sequence cost after 1 Oct 2026?
Each cart reminder is a marketing template, and Meta charges for marketing templates per delivered message at the rate for the shopper's country. A three-message sequence costs up to three marketing charges per cart, and fewer when the stop rule ends it early. Replies inside the customer service window are billed separately as service messages.
Meta's own template guidelines list "You left {{items}} in your cart!" as a marketing retargeting example, so don't expect a cart reminder to be approved as a cheaper utility template.
Costs for one cart:
- Each reminder: charged at the marketing rate for the shopper's market, and only when it's delivered, not when it's sent.
- Your replies after the shopper writes back: service messages. Since 1 Oct 2026, Meta charges for these after the first 1,000 each month per business phone number.
- Carts that convert early: cost nothing more, because the stop rule ends the sequence before the next send.
The stop rule is your biggest cost control, since every reminder it cancels is a charge you don't pay. For rates by market and category, see our breakdown of WhatsApp Business API pricing.
Why some cart reminders never arrive
WhatsApp applies per-user marketing limits, which adapt to how often each person reads marketing messages. A shopper who has had many marketing messages recently may not receive yours.
When that happens, Meta returns error code 131049 and asks you to wait at least 24 hours before trying that shopper again. Marketing messages sent inside an open 24-hour customer service window don't count toward the limit, which is one more reason message 2 asks for a reply.
How SleekFlow helps Salla stores recover carts on WhatsApp
SleekFlow is an official WhatsApp Business Solution Provider. For a Salla store, it turns the abandoned cart event into a sequence that stops at checkout and hands replies to the right person or AI agent.
SleekFlow doesn't have a native Salla integration, so Salla's cart events reach it through Make.com or webhooks, as described above. Your first WhatsApp Business API number on SleekFlow is free.
- Automation flows run the sequence: time delays, a check on the cart status before each send, and templates in Arabic and English.
- A shared team inbox holds the reply when a shopper writes back, with the cart link and total already on the contact.
- AI agents answer routine questions about sizes, delivery times, and cash on delivery at any hour, and hand over to your team when a sale needs a person.
Kashida, a UAE design brand selling home decor and corporate gifts, had relied on third-party plugins that got messages flagged as spam or didn't work as expected. It runs on Shopify rather than Salla, and it moved its WhatsApp messaging to SleekFlow with its store connected and follow-ups automated.
Results:
- More than 70% of its WhatsApp messages delivered
- English and Arabic chat flows that customers choose between
- Automatic reminders so no potential customer is forgotten
Ready to turn your Salla abandoned carts into WhatsApp conversations? Book a SleekFlow demo, and we'll map your cart events to a sequence that stops the moment a shopper buys.
Want to outcompete your peers with SleekFlow's help?
Book your personalised demo with SleekFlow today and unlock the potential of seamless communication
Frequently asked questions
Should I use Salla's built-in WhatsApp reminders or a separate platform?
Use Salla's built-in reminders if you only need to send the nudge and a small team can handle replies in WhatsApp by Salla. Move to a WhatsApp Business API platform when replies pile up, when you want AI agents to answer at night, or when the same inbox has to handle Instagram and other channels too.
Does SleekFlow have a native abandoned cart trigger for Salla?
No. SleekFlow's native abandoned cart triggers cover Shopify, with "Shopify Abandoned cart is created" and "Shopify Abandoned cart is updated" in its automation flows. Salla stores get the same result by sending Salla's cart event through Make.com or a webhook into a SleekFlow flow.
Why can't I send cart reminders to US phone numbers?
WhatsApp doesn't currently deliver marketing templates to users with US phone numbers, meaning a +1 dialing code with a US area code. Cart reminders are marketing templates, so sending one to a US number returns an error. Reach those shoppers by email or SMS instead, or reply to them inside an open customer service window.
How do I know whether the WhatsApp sequence is recovering carts?
Start with Salla's Abandoned Carts page, which separates carts by status, including Customer Returned to Store and Order Completed. Compare the share of carts that reach Order Completed before and after the sequence goes live. For a cleaner read, leave a share of carts without WhatsApp reminders and compare the two groups over the same weeks.
Can an AI agent answer the replies to cart reminders?
Yes. When a shopper replies, the 24-hour customer service window opens, and an AI agent can answer from your product, delivery, and returns information. Set it to hand the chat to your team when the shopper asks for something it can't confirm, such as a custom order or a delivery date outside your published times.
