Shopify Messaging Adds WhatsApp Marketing Campaigns

Until now, a Shopify merchant who wanted to run WhatsApp campaigns had to bolt on a third-party messaging app, maintain a subscriber list outside the customer record, and reconcile the results manually. Bringing the channel into Shopify Messaging removes that seam. Campaign creation, product media, audience selection and reporting all sit in the same admin as the store's email marketing.

A week later, on 6 August, Shopify closed the obvious gap in that release by adding the ability to collect WhatsApp marketing consent on Shopify Forms. The two releases only make sense read together: the first gives merchants somewhere to send from, the second gives them a lawful way to build the list they send to. Neither is much use on its own.

How it works

Campaigns are built inside Shopify Messaging, using either Shopify's pre-built templates or the merchant's own branded content. Media can be pulled straight from the product catalogue, so a launch or restock message carries the same imagery as the product page it points at, without a separate asset upload step.

Two features push this beyond a broadcast tool. Interactive buttons let a customer act on the message directly, and keyword replies fire an automated response when a customer replies with a set word. Together they turn a campaign send into the opening move of a conversation, which is closer to how people actually use WhatsApp than a one-way promotional blast is.

Pricing is per message. Shopify frames this as paying only for what you send, with the freedom to scale volume up through a peak trading period and back down afterwards. The underlying WhatsApp Business Platform pricing is worth understanding in its own right: it charges per message on delivery rather than on send, and rates vary by market and by message category. Marketing is one of four categories, alongside utility, authentication and service, and it is the most expensive of the four in most markets. Meta also does not charge for service messages, and there is a 72-hour free window when a customer starts the conversation from an ad that clicks to WhatsApp.

The consent side runs through Shopify Forms. A merchant can now capture a WhatsApp opt-in at the same moment they capture an email address, which means the subscriber list is built from first-party data attached to the customer record rather than assembled somewhere else and imported.

Where this earns its place

The obvious use case is time-sensitive stock. A restock alert on a size or colourway that sold out is the sort of message a customer genuinely wants, arrives in a channel they check within minutes, and converts on a short window. Email does this badly because the message competes with everything else in the inbox and often lands after the stock has gone again.

Launch and drop mechanics are the second fit. If a store trades on limited runs, the value of the announcement decays fast, and a channel with high open rates and near-immediate attention is worth paying a premium for. The interactive buttons matter here: a customer can move from notification to product page in one tap without hunting through a menu.

The third is post-purchase and reorder prompts on consumable products. A customer who bought a 60-day supply in March is a sensible target for a short, useful message in May, and keyword replies let them reorder or ask a question without leaving the thread. This is where the channel's economics work best, because the message is going to an existing customer with a demonstrated repeat pattern rather than to a cold list.

The pattern across all three is that WhatsApp rewards usefulness and punishes volume. A weekly promotional newsletter that would be tolerated in an inbox reads as an intrusion in a messaging app, and the unsubscribe (or worse, the block) comes quickly.

What this means for UK merchants

The compliance position is the first thing to get right, and it is stricter than most merchants assume. WhatsApp marketing is not a new grey area. Under the Privacy and Electronic Communications Regulations, it falls squarely inside the existing rules on electronic mail marketing, which the ICO confirms covers "direct messages via social media or any similar message that is stored electronically". The definition was written broadly on purpose, precisely so that new messaging channels would be caught by it. The ICO's guidance on electronic mail marketing is the reference to work from.

In practice that means a merchant needs specific consent to send WhatsApp marketing, or needs to rely on the soft opt-in for existing customers who bought or negotiated to buy a similar product, having been given a clear chance to opt out both when their details were collected and in every message since. Critically, an existing email marketing list does not transfer. Consent obtained for email does not cover WhatsApp, and importing a list from another channel is the fastest route to a complaint. This is exactly why the Shopify Forms consent release matters more than its two-sentence changelog entry suggests: it is the compliant collection mechanism for the channel Shopify has just opened up.

The second consideration is commercial. A per-message cost model behaves very differently from email, where the marginal cost of one more send is close to zero. On WhatsApp, every send has a price attached, which forces a discipline most email programmes never develop: segment tightly, send less, and measure per-message revenue rather than per-campaign revenue. Merchants who port their email sending frequency straight across will find the channel expensive and the list will erode. For stores running structured retention programmes, this is a channel worth building into the digital marketing mix deliberately rather than switching on because it appeared in the admin. The same cost discipline applies to the SMS automations that already sit in Shopify Messaging, and both channels benefit from Shopify no longer writing bot card-testing sessions into the abandoned checkout list they trigger from.

The third is that this narrows the gap between a native Shopify build and a heavily app-stacked one. Every third-party app carries a subscription, a data-sync risk and a support surface. Moving WhatsApp into Shopify Messaging removes one of those, which is a small but real argument for keeping a store's stack lean. That is the same logic we apply on Shopify builds, where native functionality nearly always beats an app doing the same job.

Practical considerations

Watch the gap between how Shopify describes the cost and how the underlying platform bills it. Shopify's changelog says merchants pay for the messages they send. Meta's own pricing documentation states that charges apply on delivery, not on send. In normal operation the two are close enough not to matter, but on a large campaign to an ageing list, the difference between messages attempted and messages delivered is where the budget forecast drifts. Model the cost on delivered volume.

Be careful with rate variation by market. WhatsApp pricing is set per market and category pair, so a store selling into the UK, Ireland and continental Europe will not see one flat marketing rate across its audience. A campaign that looks affordable against a UK cost per message can come in materially higher once the international segment is included. Check the rates for every market in the send before committing to a frequency.

Finally, the sensible sequencing is consent first, campaigns second. There is a temptation to launch a campaign in the week the feature appears, which almost always means sending to whatever contactable audience exists rather than to an audience that opted into this channel. Turn on WhatsApp consent capture in Shopify Forms, let the list build for a few weeks against a genuine incentive, and start sending when there is a properly consented segment to send to. A small compliant list outperforms a large borrowed one on this channel, and it does not carry a regulatory tail.

Shopify has since added a third collection point for the same permission: see our write-up of WhatsApp marketing consent being collected at checkout, and what the PECR consent rules mean for the wording beside it.

FAQ