Shopify can now send WhatsApp marketing messages on its own. Since 28 October, the marketing automations section of the admin ships with pre-built WhatsApp templates wired into Shopify Messaging: a welcome message, abandoned checkout, abandoned product browse, post-purchase follow-up. No third-party app in the middle, no separate monthly subscription, no second customer list to keep in sync. For a lot of Indian D2C stores that have been paying ₹2,500 to ₹8,000 a month to Wati, Interakt or AiSensy mostly to run two flows, that changes the arithmetic. If you're searching for Shopify WhatsApp marketing automation because you want the cart recovery flow live before the next sale weekend, this is now a job you can finish in an afternoon, assuming your Meta Business account is already verified.
The timing was not subtle. It landed days before the Diwali peak, on the channel that out-converts email by a wide margin in India because people actually open it. But native does not mean complete, and there are three places the new flows will quietly disappoint you. More on those below.
Does Shopify support WhatsApp marketing, or is this just chat?
Both, and the distinction matters. Shopify Messaging has handled inbound WhatsApp conversations for a while: a customer messages your business number, your team replies from the same inbox as online store chat. That's support, not marketing.
What's new is outbound, triggered, template-based sending from Shopify's own automation engine, using your WhatsApp Business Platform number through Meta's Cloud API. The automations run on the same customer and checkout data as your email flows, which is the whole point. No webhook plumbing, no app syncing abandoned checkouts on a five-minute delay and missing half of them.
What Shopify does not do is replace a full conversational platform. There's no broadcast campaign builder for a one-off Republic Day sale blast, no chatbot tree, no shared agent inbox with assignment rules and canned replies at the level Wati built its business on. If you run a 12-person support team on WhatsApp, this isn't your tool.
How to set up WhatsApp automation in Shopify, start to finish
Order of operations, because doing this out of sequence costs you two days:
- Pick a phone number that is not already running the WhatsApp Business app. This is where most setups stall. A number registered to the consumer WhatsApp Business app has to be deleted from it before it can join the Business Platform, and when you delete it you lose the chat history on that device. If your founder's number is your current support line, buy a new number. Do it before anything else.
- Verify your business in Meta Business Manager. GST certificate, certificate of incorporation or shop establishment licence, and a utility bill at the registered address. Review usually runs a couple of working days, longer in the last two weeks before Diwali when everyone remembers at once.
- Connect WhatsApp inside Shopify Messaging. Shopify walks you through the Meta embedded signup. You'll pick the WhatsApp Business Account, the number, and a display name. Display names get rejected for looking like a generic category word, so use your actual brand name.
- Turn on the automations one at a time. Enable abandoned checkout first, watch it for 48 hours, then add the rest. Switching on four flows on day one means you can't tell which one is annoying people when the block rate climbs.
- Submit your templates and wait. Template approval is Meta's, not Shopify's. Most clear in under an hour. Ones with aggressive discount language or a shortened link domain Meta doesn't like can sit in review for a day or get rejected outright.
One thing we get wrong on roughly a third of first attempts: the phone number format in the customer record. WhatsApp needs E.164, so +919876543210. Stores that collected phone numbers through a custom form, a COD verification app, or an old import frequently have ten-digit numbers with no country code sitting in the customer profile. Those customers silently never receive anything. Export your customer list, check the first 200 rows, fix it with a bulk edit before you blame the automation.
What the Shopify Messaging WhatsApp templates actually trigger on
The abandoned checkout flow is the obvious one and it behaves the way you'd expect: customer reaches checkout, enters contact details, doesn't pay, gets a message after a delay you set. Shopify already has the checkout object, so the product name, image and recovery URL populate without you mapping anything.
Abandoned browse is the one people misread. It does not fire when someone looks at a product. It fires when a known customer, already identified through a previous order or a logged-in session or an email click, views a product page and leaves without adding to cart. Anonymous traffic is invisible to it. So a store doing 40,000 sessions a month from cold Meta ads will see this flow send a few hundred messages, not thousands, and that's correct behaviour, not a bug. Browse abandonment earns its keep on repeat-purchase categories where a large share of sessions come from recognised customers: supplements, coffee, skincare refills, pet food. On a one-off purchase category it's noise.
The welcome and post-purchase templates are the ones worth rewriting immediately. The defaults are fine English and completely characterless. Hinglish lifts reply rates in most consumer categories we've tested it in, and a message that reads like a person typed it gets replies, which opens a 24-hour service window and makes your follow-up free. Write them yourself.
Abandoned cart WhatsApp messages that work in India
Three things are specific to this market and the default template handles none of them.
Timing. We've landed on 25 to 40 minutes for the first message rather than the hour-plus that's standard for email. WhatsApp is read in minutes. An hour later the intent is gone. Second message at 20 to 24 hours, third only if your margin supports a discount, and never a fourth.
COD. A UPI recovery link converts a prepaid order. Offering COD in the recovery message converts a different, worse order: higher recovery rate, higher RTO. If your return-to-origin rate on COD sits in the usual 20 to 30% band for apparel, a recovered COD order is worth meaningfully less than the gross number suggests. We usually push prepaid in message one with a small incentive, ₹50 off or free shipping, and only mention COD in message two.
The link. Shopify's recovery URL is long. WhatsApp renders it fine, but on a 3G connection in a tier-2 city the checkout it opens is the real variable. If your checkout takes four seconds to paint on a mid-range Android, the message worked and the store lost the order anyway. Worth a look at your mobile checkout load time before you spend anything on messaging.
Rough model, with your own numbers swapped in. Say 900 abandoned checkouts a month, of which 540 have a valid phone number and marketing consent. Two messages each is 1,080 sends. At ₹0.80 per marketing template message that's ₹864. Recover 7% of the 540 and you get 38 orders; at ₹1,850 AOV that's ₹70,300 in revenue for under a thousand rupees of message cost. Then subtract reality: if 60% of those 38 are COD and a quarter of those come back, you lose about 6 orders and eat roughly ₹130 each in forward and return freight. Still a wide margin. The point of the exercise is that the message cost is never the thing that decides this. RTO is.
Shopify WhatsApp marketing automation vs Wati, Interakt and AiSensy
Switch if your WhatsApp usage is basically four automated flows and the occasional broadcast, and you're paying a platform fee for the privilege. That describes most stores doing under ₹50 lakh a month.
Stay where you are if any of these apply: you run WhatsApp as a sales channel with agents closing orders in chat; you need a catalogue inside WhatsApp with in-chat ordering; you depend on a COD confirmation flow that cancels unconfirmed orders automatically, which is a genuinely valuable thing the native automations don't do; you send segmented broadcast campaigns weekly; or your support team needs ticket assignment and SLA tracking. Those are real products solving real problems and Shopify hasn't built them.
A reasonable middle path we've set up a few times: native Shopify for the transactional and triggered flows, because the data is cleaner and there's no sync lag, and a lighter third-party plan kept only for broadcasts and agent inbox. Check whether your current vendor has a plan that drops the per-flow pricing when you stop using their automation builder. Most do, they just don't advertise it.
WhatsApp opt-in rules for Shopify stores in India
Meta requires explicit opt-in before you send a marketing template. Not implied, not bundled into terms of service. The person has to have agreed to receive messages from your business on WhatsApp, and you need to be able to show when and how.
In practice, for a Shopify store:
- Use Shopify's SMS/phone marketing consent checkbox at checkout. Unticked by default. A pre-ticked box is a consent record that won't survive scrutiny and it poisons your quality rating when people block you.
- A separate checkbox on your newsletter popup for WhatsApp specifically works better than reusing the email consent. Collect the number with a country code selector.
- Order status and shipping updates are utility templates, a different category with different rules. You don't need marketing opt-in for them. Don't smuggle a discount code into a utility template; Meta reclassifies and your template gets pulled.
- TRAI's DLT registration covers SMS. WhatsApp sits outside it, under Meta's own policy. The DPDP Act's consent and purpose-limitation requirements do apply, so keep the consent timestamp and honour opt-outs within a day.
Every marketing template should carry an opt-out line. People will use it. That's fine. A list of 4,000 people who want to hear from you beats 14,000 who don't and are one tap from reporting you.
Cost and limits you should know before the festive peak
You pay Meta, not Shopify, per message. Marketing templates are priced per message in India at a rate Meta publishes and adjusts; utility templates cost less, and utility messages sent while a customer-service window is already open generally aren't billed. Check the current rate card rather than trusting any figure in a blog post, including the ₹0.80 used in the example above.
The limit that bites during a sale is the messaging tier. A new number starts capped at a limited number of unique customers in a rolling 24 hours and moves up through tiers as volume and quality rating hold. A store that registers a fresh number in the second week of October and plans a big Diwali push will hit the ceiling on day one of the sale. Register and warm the number six weeks out. Send real utility messages, get real replies, let the tier climb.
Quality rating is the other one. It's visible in Meta Business Manager, it drops on blocks and reports, and a number flagged low gets its tier cut. Two rescued carts are not worth a flagged number.
Where the native flow still falls short
No COD order confirmation. This is the biggest gap for Indian merchants and it's not close. A WhatsApp message asking the customer to confirm a cash-on-delivery order, with the order auto-cancelled or flagged if they don't, is the single highest-ROI WhatsApp automation in this market. Shopify's template set doesn't include it. You either keep a third-party app for that alone or build it with Shopify Flow plus a custom webhook, which is a small development job rather than a configuration one.
Limited branching. The automations are linear. No "if customer has ordered before, send A, else send B" inside the WhatsApp flow itself. You can approximate it with separate automations on segmented triggers, which gets messy past three variants.
Replies land in Shopify Messaging, which is a perfectly decent inbox for one or two people and inadequate for five. If your cart recovery message says "reply if you have a question" and 60 people reply during a Diwali weekend, someone has to actually be in there.
And attribution is thin. You'll see conversions in Shopify's marketing reports, but reconciling WhatsApp-assisted revenue against Meta ad spend still means doing it yourself in a sheet.
A sensible first week
Day one: register and verify the number. Day two to four: let Meta review while you rewrite the four default templates in your own voice and get the phone number formats fixed in your customer data. Day five: abandoned checkout live, first message at 30 minutes, prepaid incentive only. Day eight: read the numbers, then add welcome and post-purchase. Add browse abandonment last, and only if your repeat-customer share justifies it.
If your phone data is a mess or you're mid-way through a platform move and the customer records haven't settled, fix that first. Automation on bad data just sends bad messages faster. We'll look at your checkout and customer data in a free audit and tell you whether the native flows will do the job or whether you genuinely need to keep paying someone.