WhatsApp marketing templates leave the Cloud API in October 2027
Meta will stop carrying marketing templates on the WhatsApp Cloud API on 13 October 2027. Which Shopify notifications are affected (abandoned checkout) and which are not.
On 21 October 2026 Meta published a notice on its developer blog: marketing messages sent through the WhatsApp Cloud API will stop working on 13 October 2027. From that date, a template in the marketing category can only be sent through a separate product, the Marketing Messages API for WhatsApp. Utility, authentication and service messages are not part of the change and stay on the Cloud API. Meta's documentation adds an earlier date that matters for new stores: WhatsApp accounts created on or after 13 April 2027 cannot send marketing templates through the Cloud API at all. PPC Land has a careful summary of the notice and the two dates.
For a Shopify store this is a smaller event than the headline suggests, because almost everything an order triggers is a utility message. It is not nothing, though, and it is worth knowing which of your automations sits on which side of the line, what Beacon Messenger will do about it, and the one habit that keeps you clear of trouble between now and then.
What is moving and what is staying
WhatsApp sorts every template into a category when you create it: marketing, utility or authentication. Service messages are the free-form replies inside a 24-hour customer service window. The sunset applies to one category only. A template Meta has approved as utility, such as an order confirmation or a shipping update, keeps going out through the same Cloud API endpoint it uses today. A template approved as marketing, such as an offer, a newsletter or a reminder to finish a purchase, has to go through the new endpoint from 13 October 2027.
Both APIs live on the same Graph API host, use the same phone number and the same WhatsApp Business Account, and the templates themselves do not need to be recreated. What changes is the endpoint a sender calls. Meta describes the migration as a few weeks of integration work for a typical sender, and that work belongs to whoever runs the integration, which in Beacon Messenger's case is us.
| Automation | Suggested template category | Affected by the sunset |
|---|---|---|
| Order confirmation | Utility | No |
| Cash on delivery confirmation | Utility | No |
| Shipping update | Utility | No |
| Abandoned checkout | Marketing | Yes |
Why abandoned checkout is the one
Beacon Messenger treats the abandoned checkout reminder as a marketing message, and so does Meta. The automation's settings page says so, the template guidance suggests the marketing category when you create it, and the app requires marketing consent before sending it unless you turn that requirement off; the consent post explains where that consent comes from in Shopify. A reminder to come back and pay is a nudge to buy, which is the definition of marketing in WhatsApp's rules, and merchants who have tried to pass one off as a utility template have had the template paused or reclassified, as the template status post describes.
So from 13 October 2027 the abandoned checkout automation needs to send through the Marketing Messages API, and the three order automations do not. Nothing about that requires a change on the Shopify side: the checkout webhook, the delay, the consent check and the template variables are the same. It is the last step, the call that hands the message to Meta, that changes for one of the four automations.
What Beacon Messenger will do
The sends go through our server, not your browser or your theme, so routing marketing templates to the new endpoint is an app update rather than a setting you have to find. The intention is simple: well before the date, marketing-category templates go out through the Marketing Messages API and everything else stays where it is, with the log showing which route a message took. We will publish a post when that ships, and the dashboard will carry any warning that needs your attention. Until then there is nothing to switch, and nothing you can switch.
One thing we will not do is quietly recategorise abandoned checkout as utility to dodge the change. Meta reviews template content, not the sender's label, and a reminder to buy is marketing whatever the category field says. Templates Meta reclassifies from utility to marketing are explicitly covered by the notice: they move to the new API too.
The habit that matters now: keep utility templates utility
The practical risk between now and October 2027 is not the abandoned checkout automation; it is a shipping or confirmation template that drifts into marketing. A shipping update that ends with a discount code for the next order, a confirmation that mentions a sale, a COD message that upsells, are all candidates for reclassification under Meta's template guidelines, and a reclassified template becomes a marketing message with a marketing price and, after the sunset, a marketing route.
- Keep order, shipping and COD templates to the transaction: what was ordered, what it cost, where it is, what to do if it is wrong. The template examples post has versions that have stayed utility.
- Put offers and codes in the abandoned checkout template, which is marketing anyway, or in a campaign tool built for it.
- When Meta changes a template's category, the app shows the new category next to it. If a utility template turns into marketing, edit the text rather than accepting the change.
- If you are connecting a brand new WhatsApp account after 13 April 2027, expect abandoned checkout to need the new route from day one, and the three order automations to work as usual.
Pricing and the United States
The notice is about routing, not pricing, but the two are entangled. Marketing templates already cost more than utility ones under the per-message pricing that took effect in 2025, and the October 2026 pricing change post covers the current rates. The Marketing Messages API has its own terms, and merchants outside the United States should read them as they appear; inside the United States the question is moot, because Meta has paused delivery of marketing templates to US numbers since 2025, a pause that is still in place as of this writing. A US store's abandoned checkout messages have not been arriving for some time, and this change does not alter that.
What to do this month
- Open each automation in Beacon Messenger and check the category shown next to its template. Order, COD and shipping should read utility; abandoned checkout should read marketing.
- Read your three utility templates as Meta would. If any of them sells, trim it.
- Leave abandoned checkout alone. It works today through the Cloud API, and the switch to the new endpoint is ours to make before October 2027.
- If your WhatsApp setup is changing anyway, the messaging account split is the other Meta change on the calendar, and the two are separate.
A year is a long time in Meta's platform calendar and dates have moved before, in both directions. The developer blog and the Marketing Messages API documentation are the authority; this post reflects them as of early November 2026, and Beacon Messenger will carry the change when it is time.
More guides
- WhatsApp Business app drops order tools: move orders to Shopify
- A customer replied STOP to a WhatsApp order message. Now what?
- WABA to Messaging Account: what changes for Shopify WhatsApp
- Order paid later, refunded or edited: which WhatsApp messages send
- Edited your WhatsApp automation? What queued messages send
- How to add a WhatsApp chat button to your Shopify store (2026)
- How to send Shopify order confirmations and shipping updates over WhatsApp with the official Cloud API
- Cash on delivery on Shopify: confirm orders over WhatsApp before you ship
- Recovering abandoned checkouts on Shopify with WhatsApp, the compliant way
- Why WhatsApp apps get your number banned: linked device vs API
- How a "free" WhatsApp app for Shopify ends up charging you
- Por qué una app de WhatsApp "gratis" para Shopify te cobra
- Pushdaddy or SuperLemon alternative: WhatsApp apps compared
- How to verify Shopify WhatsApp notifications were delivered
- Chat button still on your store after uninstalling the app?
- WhatsApp API pricing changes on Oct 1, 2026: Shopify impact
- Setting up the WhatsApp Cloud API with Meta's MCP and an AI agent
- WhatsApp chat outside business hours: what shoppers should see
- WhatsApp product sharing on Shopify: tracking dark social
- WhatsApp template rejected? Fixing Shopify order templates
- One WhatsApp number or two? Shopify notifications & support
- Shopify Canvas and Beacon Messenger: what works today
- Shopify now collects WhatsApp marketing consent at checkout. Here is what it changes
- Split shipments on Shopify: how many WhatsApp updates to send
- WhatsApp's 250-a-day messaging limit and your Shopify store
- WhatsApp, SMS or email for Shopify order notifications?
- WhatsApp is down: what happens to your Shopify order notifications
- Shopify orders with no phone number: why WhatsApp messages get skipped
- Shopify rollout discounts and WhatsApp order messages
- Add a Track order button to WhatsApp order messages
- Which Shopify orders trigger a WhatsApp message?
- The abandoned checkout timer restarts every time the shopper comes back
- Blank names, twelve-item orders: what WhatsApp merge fields fall back to
- Who looked at your customers' phone numbers? The access log behind a WhatsApp app
- Send a WhatsApp test message before your first order: what the Connect and Test buttons check
- Disconnect, update credentials, app secret: what each does
- COD reply not tagged: how Beacon Messenger matches replies
- WhatsApp template language: why name alone is not enough
- Finding one WhatsApp message in the Beacon Messenger log
- WhatsApp automation is On but nothing sends: a checklist
- Mapping WhatsApp template variables to Shopify order fields
- Every WhatsApp chat button setting in the Shopify theme editor
- WhatsApp template examples for Shopify: order, shipping, COD, cart
- The Share on WhatsApp block, setting by setting
- WhatsApp order messages when customers speak several languages
- Reading the Beacon Messenger dashboard: sent, delivered, failed, skipped
- Shopify batch fulfilment: what happens to 250 WhatsApp shipping messages
- WhatsApp template status: approved, pending, paused, disabled, and what sends
- WhatsApp quality rating: the field on the Connected number card
- COD returns (RTO) on Shopify: confirm orders on WhatsApp first
- WhatsApp error codes on failed messages: a reference
- WhatsApp display name: what customers see on your order messages
- Shopify Messaging WhatsApp automations vs Beacon Messenger
- OXXO, bank transfer and pay-later orders: when the WhatsApp confirmation goes out
- How many WhatsApp messages will Black Friday send? Sizing your plan
- WhatsApp usernames and BSUIDs: what changes for Shopify order messages
- Reconciling your WhatsApp bill with the Beacon Messenger log
- Track with Shop vs WhatsApp shipping updates on Shopify
- Meta changed my WhatsApp template from utility to marketing
- Shopify's new app security review: what Beacon Messenger can access
- A shopper cancels their own Shopify order: what WhatsApp sends
- Customer erasure in 5 days: what the WhatsApp log keeps
- WhatsApp INR billing deadline: Indian Shopify stores
- WhatsApp template headers: text, image or document?
- Gift orders on WhatsApp: buyer's phone or the recipient's?
- WhatsApp order messages at night: when each one sends
- Downgrading a WhatsApp app plan after peak season: what changes
- Shopify subscription renewals and WhatsApp order messages