What Is Max Price for WhatsApp Marketing Messages in 2026?
Max price is a feature on the Marketing Messages API for WhatsApp that lets a business set the highest price it is willing to pay per marketing message delivery. Meta then charges that max price or lower. It enters Open Beta on 1 October 2026, after a Limited Beta that started on 15 May 2026, and Meta says it becomes required in eligible geographies at general availability in Q2 2027.
That last date is the one to plan around. At general availability, Meta says fixed published rates for marketing messages will only apply on the Cloud API. In other words, for marketing messages sent through the Marketing Messages API in eligible geographies, bidding stops being an option and becomes the way pricing works. October 2026 is the window to learn it while it is still optional.
| Phase | Date | What it means |
|---|---|---|
| Limited Beta | From 15 May 2026 | Any partner or directly integrated business can use it; each partner can enable it for a limited number of clients. |
| Open Beta | From 1 October 2026 | Any partner can enable max price and the reach estimation tool for all their clients. |
| General availability | Q2 2027 | Max price becomes required in eligible geographies, and fixed published rates for marketing messages only apply on the Cloud API. |
Why Does Max Price Matter for Marketing Budgets in 2026?
Because it turns a fixed rate card into a lever. Until now a marketing message on WhatsApp cost whatever the published rate for that market was, and the only way to spend less was to send less. Max price lets a brand decide, per campaign, whether it wants the same delivery at the same cost, wider reach at lower cost, or higher delivery during a peak.
Meta describes three uses directly, and they map to three very ordinary marketing situations.
- Set it at the published rate to lower costs while keeping delivery rates similar to current WhatsApp campaigns.
- Set it below the published rate to reach more customer cohorts on WhatsApp at lower cost.
- Set it above the published rate to increase delivery rates during periods such as holidays and peak sales periods.
For Indian D2C brands that run heavily around festive and sale calendars, the third case is the interesting one. A max price above the rate card is a deliberate decision to pay more for delivery at the moment it matters most, rather than discovering after the fact that a campaign under-delivered.
How Does bid_amount Work in 2026?
In the API you express max price as a bid_amount inside the optimization_spec object on the template. The value is the maximum price per 1,000 deliveries, written in the smallest unit of your Messaging account's currency: paise for INR, cents for USD, and so on. This unit is where most first attempts go wrong, because the number looks a thousand times too large.
| Desired max price per delivery | Convert to smallest unit | Multiply by 1,000 | bid_amount |
|---|---|---|---|
| INR 0.87 | 87 paise | 87 x 1,000 | 87000 |
| USD 0.05 | 5 cents | 5 x 1,000 | 5000 |
The INR 0.87 and USD 0.05 figures are Meta's own worked examples of the unit conversion. They are not the published marketing message rate for India or for any other market. Take your actual rate from Meta's published rate card for your market and currency, then decide where to set your max price relative to it.
Two further rules sit around bid_amount. The only supported bid_strategy is LOWEST_COST_WITH_BID_CAP. And if optimization_spec is not included on a template, that template uses standard rate card pricing.
The field rename to know about
optimization_spec replaced bid_spec as of 18 June 2026. bid_spec was accepted until 31 July 2026 and is no longer supported after that. The bid_amount and bid_strategy fields are identical in both objects, so the change is a rename of the container rather than a change in behaviour. Any integration still sending bid_spec is sending something Meta no longer reads.
How Do Per-Message and Per-Country Multipliers Work in 2026?
Max price has two scaling controls on top of the template's bid_amount. One adjusts individual messages, the other adjusts by destination country. Both let you avoid creating a separate template for every price point, which matters because each new template has to build its own quality history.
per_message_bid_multiplier
Meta's recommended approach is specific: set the template's bid_amount to the highest amount you are willing to pay per 1,000 deliveries, then apply a per_message_bid_multiplier of less than 1 to lower the effective max price for individual messages. Meta says this gives the delivery system the widest range to optimise against. In Meta's example, a bid_amount of 100,000 with a multiplier of 0.5 gives an effective max price of 50,000 for that message.
bid_country_multiplier_overrides
This map, set inside optimization_spec, scales the bid_amount for specific destination countries. Meta determines the recipient's country from their phone number and computes the effective bid as bid_amount multiplied by the country multiplier. Countries you do not list use a multiplier of 1.0.
| Constraint | Rule |
|---|---|
| Entries | Up to 50 |
| Multiplier value | Greater than 0 and at most 10 |
| Keys | Valid ISO 3166-1 alpha-2 country codes, for example IN, MX, BR |
| Unlisted countries | Multiplier of 1.0, so the bid_amount is used unchanged |
Meta's worked example uses a bid_amount of 1000 with an override map of India at 1.2 and Mexico at 0.8. The effective bid per 1,000 deliveries is then 1,200 for India, 800 for Mexico, and 1,000 for Brazil, which is not listed. A brand messaging customers in several countries from one template can therefore bid harder in its priority market without duplicating the template.
How Should You Test Max Price Before Scaling in 2026?
Meta recommends starting with A/B tests, and it is unusually prescriptive about the design. Run a four-arm test with 10,000 send requests per arm, using a similar audience and time window for each arm, so the only thing that differs is the max price setting.
| Arm | Max price setting |
|---|---|
| A | No max price set |
| B | Max price set at the rate card |
| C | Max price at 1.5x the rate card, or 1.2x for India and Saudi Arabia |
| D | Max price at 0.9x the rate card |
Note the India-specific line in arm C. Meta recommends 1.2x rather than 1.5x for India and Saudi Arabia, which is a meaningful signal that the useful bidding range in those two markets is narrower. Indian brands should not copy a global test plan unchanged.
Two practices sit alongside the test. Set your max price at the template level when you create the template, since Meta says bid_amount is what its delivery system optimises against. And ramp up gradually: when sending with a new max price template for the first time, increase volume slowly before sending at scale, in line with template pacing. Meta also describes max price as an early-stage feature whose performance may vary as its systems learn.
The reach estimation tool
Alongside max price, Meta provides a reach estimation tool that helps businesses understand estimated delivery rates and costs at different max prices. Treat it as a planning aid. It is the right input for choosing your test arms, not a substitute for running them.
Who Can Use Max Price, and What Do They Need in 2026?
To use max price you need an active Messaging account that has been onboarded to the Marketing Messages API for WhatsApp, and you need to be in a country that is eligible for that API. Max price applies to marketing messages sent through the Marketing Messages API, not to the Cloud API, which is also where fixed published rates continue to apply after general availability.
- During the Limited Beta, direct integrators and Solution Partners sign a beta agreement. End-businesses enabled by a partner do not need to sign it. Solution Partners allowlist the end-businesses they enrol, and those businesses must own or share their accounts with the partner and be onboarded to the Marketing Messages API.
- From Open Beta on 1 October 2026, any partner can enable max price and the reach estimation tool for all their clients, which removes the per-partner client limit that applied during the Limited Beta.
If your messages go through a provider, the practical step is simply to ask whether they have enabled max price for your account and how they expose the controls. For the platform-level account changes that arrive in the same month, see our guide to the new business account model.
How Should Marketing Teams Use Max Price in 2026?
Use it to make price a campaign decision rather than a fixed cost. The table below maps common campaign types to a sensible starting position. Every row is a hypothesis to test with the four-arm design above, not a setting to copy.
| Campaign type | Starting position in 2026 | Reasoning |
|---|---|---|
| Always-on nurture and reminders | At or below the rate card | Delivery timing is flexible; cost per delivery matters more than speed. |
| Win-back to lapsed customers | Below the rate card | Meta's stated use: reach more cohorts at lower cost. |
| Festive and sale-period launches | Above the rate card | Meta's stated use: increase delivery during holidays and peaks. |
| Multi-country sends from one template | Country overrides | Bid harder in the priority market without new templates. |
| Any brand-new template | Ramp slowly | Meta recommends gradual volume increases before scaling. |
Max price changes what you pay per delivery. It does not change what a message costs you if it reaches the wrong person. Measurement of what happens after the tap is covered in our guide to landing page view events, and the cost changes landing on 1 October 2026 are covered in the service message pricing hub.
What Are the Common Mistakes in 2026?
- Writing
bid_amountas a per-message price. It is per 1,000 deliveries, in the currency's smallest unit. - Treating Meta's INR 0.87 example as the India rate. It is a unit conversion example, not a published rate.
- Still sending
bid_spec. It was accepted until 31 July 2026 and is no longer supported. - Copying a 1.5x test arm to India. Meta recommends 1.2x for India and Saudi Arabia.
- Creating a template per price point. Use per-message and per-country multipliers instead.
- Scaling a new max price template immediately. Meta recommends ramping volume gradually.
- Assuming max price is optional forever. Meta says it becomes required in eligible geographies at general availability in Q2 2027.
Key Takeaways for 2026
Max price is the first real cost lever on WhatsApp marketing messages, and it is optional for a limited time.
- Max price enters Open Beta on 1 October 2026, after a Limited Beta from 15 May 2026.
- At general availability in Q2 2027 it becomes required in eligible geographies, and fixed published rates for marketing messages only apply on the Cloud API.
- Meta charges your max price or lower per delivery.
bid_amountis per 1,000 deliveries in the smallest currency unit, insideoptimization_spec, withLOWEST_COST_WITH_BID_CAPas the only strategy.- Set
bid_amounthigh and scale individual messages down with aper_message_bid_multiplierbelow 1. - Country overrides allow up to 50 entries, each greater than 0 and at most 10.
- Meta's recommended test is four arms of 10,000 sends, with 1.2x rather than 1.5x for India and Saudi Arabia.
Distk helps growth teams across India and internationally design and read max price tests, set country overrides for multi-market sends, and plan campaigns around the moment bidding stops being optional. If WhatsApp marketing is a meaningful line in your budget, that test design is where we start.
Sources
- Set a max price for marketing messages (BETA), Meta for Developers.
- Enroll in the max price feature, Meta for Developers.
- WhatsApp changelog, Meta for Developers, entry dated 15 September 2026 announcing the 1 October 2026 Open Beta.