WhatsApp Cloud API Drops Marketing Messages Oct. 13, 2027

WhatsApp Cloud API Drops Marketing Messages Oct. 13, 2027
WhatsApp Cloud API Drops Marketing Messages Oct. 13, 2027
Affiliate disclosure: This post contains affiliate links. If you buy through them, I may earn a commission at no extra cost to you. Full disclosure

Meta will stop WhatsApp’s Cloud API from sending marketing messages on October 13, 2027, pushing every promotional send onto a separate Marketing Messages API.

For an ecommerce owner, that lands in two places. Any WhatsApp promotion your Shopify app or messaging vendor sends to customers outside the US needs a new endpoint and new terms, and any WhatsApp account created on or after April 13, 2027 cannot send marketing on the old API at all. US-only stores feel less of it, because WhatsApp has not delivered marketing templates to US phone numbers since April 1, 2025.

I track platform changes like this daily at Ecommerce Paradise because they decide which owned channels a high-ticket store can count on. If you are still sorting out the basics, start with my guide to what high-ticket dropshipping is, then come back here. The rest of this post covers the exact dates, the parts Meta has not explained, and five checks to run before your vendor’s migration window closes.

Customer phone numbers and messaging consent belong to a real business entity, so form your LLC with Northwest Registered Agent, the best LLC formation service for ecommerce owners. Northwest has operated for roughly 25 years under stable ownership, which is more than the cheap formation sites that change hands and upsell can say. Form your LLC with Northwest →

WhatsApp Cloud API Stops Sending Marketing Templates Oct. 13, 2027

According to Meta’s developer documentation, the “Cloud API will stop supporting marketing messages on October 13, 2027.” Per PPC Land’s report, Meta’s overview page adds that “After this date, sending marketing messages on Cloud API will produce an error.”

PPC Land reported on October 21, 2026 that Meta published a Meta for Developers blog post that day by Sascha Noll. Meta’s overview page dates the same announcement to October 13, 2026. The outlet noted the eight-day gap and did not find an explanation for it.

There are two cutoffs. Existing accounts keep sending marketing on the Cloud API until October 13, 2027, which is 356 days from today. For new accounts, Meta’s overview page says “Any new Messaging account created on or after this date will not be able to send marketing messages via Cloud API,” and the date it names is April 13, 2027, 173 days away.

Not everything moves. Service, authentication and utility messages stay on the Cloud API, according to PPC Land. Marketing templates go to a new endpoint, /<PHONE_NUMBER_ID>/marketing_messages, under separate terms that a business has to accept. Meta says existing phone numbers and approved templates carry over, and that “Most integrations may take about two weeks.”

The hard part is reclassification. PPC Land reports that a utility template Meta reclassifies as marketing must be routed to the new API, and that a reclassified template sent through the old endpoint will fail. During migration, setting disable_marketing_messages_on_cloud_api to true makes the standard messages endpoint reject marketing templates with error 131063, per the same report.

Meta’s case for the switch is better results. The company lists automatic delivery optimizations, performance benchmarks and recommendations, GIFs and other richer media, and expiry dates for time-sensitive campaigns. Meta says it ran an A/B test on about 12 million delivered marketing messages sent by advertisers in India from January 1 to 31, 2025, at a 95% confidence level, and that optimized delivery “drove more reads and clicks in testing.” It published no lift figure.

Several regions get less. In the EEA, UK, Japan, South Korea, Nigeria, South Africa and Thailand there are no delivery optimizations and no click or conversion reporting, according to PPC Land. Infobip’s documentation lists the same gap for the EEA, UK, Japan and South Korea, and says messages still deliver there.

Meta gave no new prices. The overview page says only that the product has “the same billing model as Cloud API,” and PPC Land found no rates. Vendors are already telling customers what to do: HighLevel’s notice walks users through enabling the new product in each sub-account and says it takes a few minutes per account.

How WhatsApp Marketing Got Split From the Cloud API

This did not come out of nowhere. The product was first called Marketing Messages Lite, or MM Lite, and Meta’s WhatsApp changelog shows it being built out through 2025. On May 29, 2025, Embedded Signup version 3 let partners onboard businesses to it. On August 12, 2025, Meta added an event that fires when a business account onboards. On October 1, 2025, a rate change listed it among affected products, and on October 8, 2025, Embedded Signup version 4 extended the onboarding.

The 2025 version was optional. The October 2026 announcement makes it the only door for marketing sends, which gives owners roughly a year of runway.

The US pause is the other half of the history. Per Infobip’s documentation, as of April 1, 2025 messages to end users in the United States are not delivered. Kanal, a WhatsApp vendor, says in a vendor blog post that the pause is still in effect and that Meta has announced no end date. Klaviyo’s guidance, as quoted in a Digismoothie roundup of Shopify WhatsApp apps, says “WhatsApp marketing templates cannot be delivered to US phone numbers.”

I covered the order-taking side of this channel in how to collect payments for phone and WhatsApp orders. That post is about conversations. This change is about broadcasts, and Meta is treating them as two different products.

I found no independent critic of the move yet, so there is no counterpoint to attribute. The open questions sit in Meta’s own fine print and in PPC Land’s reading: no published lift numbers, no prices, and nothing about how business solution providers will handle the migration for their merchants.

What the MM API Switch Means for a High-Ticket Store Owner

My read: most US high-ticket stores lose nothing on October 13, 2027. Marketing templates already do not reach US numbers, so there is no US promotional flow to break. The risk for a US-only store is smaller and sneakier. A shipping or order update that Meta decides is promotional will stop going through the old endpoint, and nobody will notice until a customer asks where their $3,000 order is.

Stores with customers outside the US are the ones who need to move. If a Shopify app sends WhatsApp promotions to buyers in the EU, the UK, or anywhere else Meta delivers marketing, that app has to ship the switch. Your vendor owns that work, not you, but you own the consequence if it misses the date.

Here is hypothetical math, with a real baseline. Digismoothie’s roundup describes one app, Dondy, charging Meta’s marketing rate plus 60%, and gives a Czech and Slovak example of $0.086 at Meta’s list rate against $0.1376 with the markup. At an invented 5,000 marketing sends a month in that market, Meta’s list rate is $430 and the marked-up rate is $688. That gap is $258 a month, or $3,096 a year. Meta has not said whether the new API changes cost, so the markup is the one number you can negotiate today.

For a high-ticket store, the value of WhatsApp is the conversation, not the blast. Kanal says that for US numbers, utility templates, authentication templates, free-form replies inside the 24-hour customer service window, and conversations started from click-to-WhatsApp ads all still work. That matches how a $2,000 buyer behaves: they want a human to answer a question about freight and installation. Protect that path first, and build your follow-up around my high-ticket sales follow-up process.

Pair it with a CRM so every WhatsApp thread lands on a contact record. HubSpot has a free tier to start on. My HubSpot setup guide covers the high-ticket version.

If you want a chat layer on the site itself, I ranked the best live chat software for high-ticket stores.

Email is the hedge. A Meta policy change cannot remove an email list, and Digismoothie’s roundup describes Klaviyo as offering native WhatsApp campaigns alongside email.

If you are weighing it against a Shopify-native SMS specialist, my Klaviyo vs Postscript breakdown shows the trade-offs. Omnisend is the other platform I would price before committing.

My Omnisend pricing guide explains how contact billing and SMS costs stack up.

Owned channels matter more every month. I wrote about Safari 27 blocking email-to-ID ad trackers, and the same logic applies here: the more a channel depends on someone else’s gate, the more it deserves a second path. Meta also raised the price of getting people into your funnel, as I reported in Meta ad prices up 23% in US and Canada.

Vendor risk is the part I would watch. PPC Land says Meta’s post does not address business solution providers, who carry most of the integration work. My rule: if an app that sends your WhatsApp marketing has not published a migration plan by the end of Q1 2027, treat it as a switching candidate. If you run chat automation, ask ManyChat or your equivalent directly.

If the answer is vague, my ManyChat alternatives roundup is where I would start looking for a replacement.

One compliance note. Meta’s terms for the new API are separate, so someone has to read them, and your privacy policy and consent language should name WhatsApp as a channel if you use it. Termly generates both documents. I am not a lawyer, so treat that as a starting point and have counsel review anything you collect consent under.

Running a high-ticket store means tracking ad policies, supplier feeds, support queues and now messaging APIs. If you would rather not babysit deadlines like this one, that is the work my team takes on in the done-for-you turnkey build.

Not sure which of your messaging tools sits on the Cloud API, or what to move first? Bring your stack to a 1-on-1 coaching call and we will map it before Black Friday. Get the coaching details →

Audit Your WhatsApp Setup Before the October 2027 Cutoff

Five checks, in this order:

  1. List every tool that sends WhatsApp messages: your messaging automation such as Tidio, your email and SMS platform, your help desk, your CRM and any Shopify app. Ask each vendor in writing whether it sends marketing templates through the Cloud API and on what date it moves to the Marketing Messages API.
  2. Split your templates into marketing and utility. Pull the last 90 days of sends by template and read each one as a customer would. Any shipping or order update with a discount code or cross-sell line is a reclassification candidate, so strip the promotion out of it.
  3. Count the marketing sends that went to non-US numbers last quarter. If the count is zero, the migration is a calendar entry. If it is not, ask the vendor for its per-message rate and compare it to Meta’s list rate for that country.
  4. If you run a custom build, have your developer set disable_marketing_messages_on_cloud_api to true in staging and confirm that marketing templates return error 131063 while order updates keep working. Do this before the vendor’s switch date, not after.
  5. Put April 13, 2027 and October 13, 2027 on the calendar, and build an email version of your best WhatsApp flow now. If you are on a help desk like Gorgias, ask whether its WhatsApp channel is affected, and confirm the answer in writing.

If you want a second set of eyes on your stack, book a discovery call. Pair the audit with the checklist in my high-ticket Black Friday stress test, since Q4 is when a broken order-update flow costs the most.

Frequently Asked Questions

Does this affect me if I only sell to US customers?
Marketing templates already do not reach US phone numbers, per Infobip’s documentation and Kanal’s reporting. Your risk is utility messages that Meta reclassifies as marketing, so run the template audit above.

What is the difference between the Cloud API and the Marketing Messages API?
The Cloud API keeps service, authentication and utility messages. The Marketing Messages API takes promotional templates on its own endpoint, with delivery optimizations in supported regions, according to PPC Land and Meta’s documentation.

Do my approved templates need re-approval?
Meta says existing phone numbers and templates carry over, and HighLevel’s notice says the same for its users. Confirm with your own vendor, because the migration steps differ by platform.

Will WhatsApp marketing cost more after the switch?
Nobody outside Meta knows yet. Meta says the billing model matches the Cloud API and has published no new rates, so ask your vendor about markup. My Shopify pricing guide shows how app costs add up on top of your plan.

Should I move follow-up to SMS or email instead?
For US customers, yes, at least as a second channel. Compare SimpleTexting against an all-in-one platform, and check text-message consent rules with a lawyer first.

What if I am just starting a store and have no WhatsApp setup yet?
Build on the Marketing Messages API from day one, because accounts created on or after April 13, 2027 cannot use the old route for marketing. Grab my free high-ticket niches list to pick a niche. Then follow the full launch checklist.

Already have a store doing sales, with a messaging stack held together by apps? My team rebuilds it so it keeps working when platforms change the rules. See the scaling service →

That is the full picture as of today. I will cover the migration details as vendors publish them. Subscribe to the YouTube channel for daily breakdowns. More breaking news coming through the day.

Related Articles

If this was useful, these go deeper: