This article was originally published on Botsense on 13 August 2026.
Meta has published a date for the end of fixed pricing on marketing messages. Not a hint, not a roadmap slide — a line in the developer documentation, in the same paragraph as a quarter.
The WhatsApp max price feature moves to General Availability in Q2 2027, and at that point, in Meta's own words, "fixed, published rates for marketing messages will only apply on the Cloud API." Everyone billing marketing messages through the Marketing Messages API has a pricing model with an expiry date on it.
That much is documented. Three things are not, and the gap between them is where most of the current commentary lives.
- Meta dates max price GA to Q2 2027. After that, fixed published rates for marketing messages apply only on Cloud API.
- Meta says max price becomes required in "eligible geographies" and never defines the phrase in any public document.
- India is not excluded by any published geographic restriction. That is not the same as India being in scope.
- Meta publishes a numbered error code when it declines to deliver a marketing message. There is no such code for max price, across eight documents.
- Solution Partner allowlists went 5 to 15 to 100 during the beta. Almost none of this has been covered.
The WhatsApp max price timeline, as Meta dates it
Meta's pricing page states the position plainly: "The max price feature is available in Limited Beta as of May 15 and will be optional throughout 2026. Meta plans to make max price generally available in Q2 2027."
The three phases are set out on the same page:
| Phase | Date | Who can use it |
|---|---|---|
| Limited Beta | 15 May 2026 | "Any partner and any directly integrated business". Each partner limited to a set number of clients |
| Open Beta | October 2026 | "Any partner can enable these features for all their clients" |
| General Availability | Q2 2027 | Required in "eligible geographies" |
The enrolment doc puts a closing bracket on the beta that the pricing page does not: it describes "the Limited Beta period (May 15 to October 2026)". So the Open Beta date and the Limited Beta end date are the same month, from two different pages.
Nothing about billing changes in the meantime. Meta is explicit that "there is no change to how Meta charges on the WhatsApp Business Platform. Meta continues to charge on a per-message basis". If you never set optimization_spec on a template, nothing happens to you at all — "If optimization_spec is not included, the template uses standard rate card pricing."
What GA actually means if you are not on Cloud API
This is the line worth reading twice.
"General Availability (GA) as of Q2 2027 — The max price feature will become required in eligible geographies and fixed, published rates for marketing messages will only apply on the Cloud API." — Set a max price for marketing messages, Meta for Developers, retrieved 11 August 2026
Two commitments in one sentence. The WhatsApp max price stops being optional somewhere, and the familiar per-category rate card survives somewhere else — on Cloud API. For anyone whose marketing volume runs through the Marketing Messages API, the fixed rate is a 2026 arrangement. Which API your traffic actually sits on is an account-architecture question, and if you are not certain, the account model change is the place to start.
The word doing the most work is "eligible". Meta does not define it.
I checked five documents: Set a max price for marketing messages; Enroll in the max price feature; Control max price visibility in WhatsApp Manager; Marketing Messages API changelog; Marketing Messages get-started, which carries the geographic availability table.
The phrase "eligible geographies" occurs exactly once across all five — in the GA sentence above. No list, no link, no table.
One source could contradict this and could not be read: the "Max price explainer PDF" linked from the pricing page. It sits on Meta's Highspot instance behind both a browser gate and a sign-in wall. If a list of eligible geographies exists anywhere, that is the likeliest place for it, and it is not public.
India is not named in any published restriction group. That means India is eligible to use the Marketing Messages API. It does not mean India is in scope for the GA requirement. Those are two different statements about two different lists, and only one of those lists has been published.
What Meta says the WhatsApp max price does
Meta describes the feature by objective, not by mechanism. A max price can be set "the same as, lower than, or higher than the published rate", and the page attaches an outcome to each: setting at published rates to lower costs "while maintaining delivery rates similar to current WhatsApp campaigns"; setting below to "Reach more customer cohorts on WhatsApp at lower cost"; setting above to "Increase delivery rates during periods such as holidays and peak sales periods".
The charging rule itself is one clause: "when a max price is set, Meta will charge that max price or lower for delivery."
The Reach Estimation API is the only place Meta puts numbers on the trade-off. Its own example response, at a targeted audience fixed at 1,000 users:
| bid_amount | Targeted users | Estimated deliveries |
|---|---|---|
| 400 | 1,000 | 500–570 |
| 520 | 1,000 | 600–650 |
Raising the bid from 400 to 520 — thirty per cent more — moves the estimated delivery range from just over half the targeted audience to just under two thirds. Meta caveats it directly: "Meta generates estimates from historical data, and they are for informational and planning purposes only."
Read those two rows carefully and you will notice what they concede. At a bid_amount of 400, between 430 and 500 of the 1,000 targeted users do not receive the message.
What Meta never says
Meta does not say what happens to those messages.
I searched nineteen terms across eight public documents: auction, clearing price, clearing, market rate, market price, demand, competing, competition, bid against, outbid, win the, lose the, second price, not sent, undelivered, not be delivered, fails to deliver, dropped, skipped. Zero occurrences, all nineteen, in all eight.
That absence carries more weight than a word count, because Meta plainly has a way of saying this when it wants to. Error 131049 reads "This message was not delivered to maintain healthy ecosystem engagement." Error 130472 reads "Message was not sent as part of an experiment." Both describe a marketing message Meta decided not to deliver; both get a number, a published description and a row in the error code reference, where 69 codes are documented and not one mentions price, bid or budget.
Meta issues a numbered, published error code when it declines to deliver a marketing message. It has not issued one for max price.
One distinction worth stating: this shows Meta has not documented the outcome, not that no mechanism exists. Something is clearly deciding — the estimated delivery range moves with the bid, so a decision is being made per message. What is missing is any published account of what that decision is, or what becomes of the messages it goes against.
The Solution Partner controls nobody is reading
Meta shipped a partner-facing control surface for the WhatsApp max price through the beta, and it has gone almost entirely uncovered.
The allowlist cap moved twice. The changelog records the 17 June increase from 5 to 15, and then on 31 July: "Solution Partners can now allowlist up to 100 end-businesses for the max price feature during the Limited Beta period, increased from 15."
On 5 August, Meta added a visibility switch. The whatsapp_manager_marketing_messages_max_price_enroll_status field on the WhatsApp Business Account takes OPT_IN or OPT_OUT.
"This setting controls only the visibility of the max price experience in WhatsApp Manager. It doesn't change a WABA's eligibility for max price, and it doesn't affect max price settings configured through the API." — Control max price visibility in WhatsApp Manager, Meta for Developers, retrieved 11 August 2026
So it hides a UI. It does not gate the capability, and an end-business with API access is unaffected by it.
One more route worth knowing: since 17 July, an approved template can be cloned at a different max price by passing source_template_id, and "The duplicate is created in APPROVED status without re-review."
What to do with an undefined scope
The honest summary is short. Meta has committed to a date and a consequence, and has not published the list of places the consequence applies to. If you sell or buy WhatsApp marketing in India, you are entitled to know whether Q2 2027 changes your rate card, and as of today Meta's public documentation does not tell you.
Four things you can act on:
- Decide whether your marketing volume runs through Marketing Messages API or Cloud API, because Q2 2027 treats them differently.
- If you are a Solution Partner, check your allowlist headroom against the 100 cap before Open Beta in October.
- Read whatsapp_manager_marketing_messages_max_price_enroll_status as a UI switch, not an access control.
- Do not commit to a max price strategy on savings percentages that carry no link to Meta.
Read the full analysis with sources at botsense.io
Top comments (0)