Shopify rollout discounts and WhatsApp order messages

By the Beacon Wave Studio team · Published October 5, 2026 · 6 min read

Shopify rollouts can switch a discount on for some shoppers only. What WhatsApp order confirmations and abandoned cart reminders show when that happens.

In October 2026 Shopify let merchants put discounts into Rollouts, the scheduling tool under Markets > Rollouts. A rollout can now switch a discount on at a set time together with a theme or catalog change, run it for a weekend and switch it off again, or serve it to half of your visitors to measure whether it pays. Shopify's overview of rollouts describes the three kinds: Launch, Event and Experiment.

If you send WhatsApp messages about orders, the natural question is what those messages say when a discount only some customers received is involved. The short answer for Beacon Messenger is: the same thing they always say, because every message is built from the order Shopify recorded, not from the discount settings. This post walks through each message type, the one case that needs care, and why the app itself did not need to change for this release.

How a rollout discount reaches a customer

A discount in a rollout keeps its own start and end dates. Shopify's page on rollout types explains that the discount is active for a customer when its own dates apply, or when an active rollout that activates it covers that customer. A rollout that deactivates the discount makes it inactive for the customers in the rollout even inside its own dates. In an Experiment the control group sees the discount in its normal state and the treatment group sees it as the rollout changes it.

Two consequences matter for messaging. First, the row on the Discounts page can say Scheduled while customers are checking out with the discount applied. Second, two customers who order a minute apart can legitimately pay different amounts for the same cart. Both are by design. Neither changes anything in the order itself: the order Shopify creates records the price that customer actually paid, with the discount line included or not.

Order confirmations: the total is the customer's total

When an order is created, Beacon Messenger reads the order Shopify sends in the webhook and fills the template variables from it: the customer's first name, the order name, your shop name and the order total. That total is Shopify's total_price for the order, after discounts. A customer in the treatment group who paid 85.00 gets a message that says 85.00. A customer in the control group who paid 100.00 gets 100.00. The app does not need to know a rollout existed, because the order already reflects it.

The same holds for cash on delivery confirmations, which use the order total so the customer confirms the amount the courier will collect. If the discount came from a rollout, the collected amount already includes it. Our post on how order notifications work covers which fields each template uses.

Shipping updates: no price at all

Shipping messages are triggered by fulfilments and carry the order name, the carrier and the tracking link. They do not mention money, so a rollout cannot make them wrong. The only thing to watch is timing: if an Event rollout coincides with a sale, expect the usual spike in fulfilments and messages in the days after it, and check your monthly message allowance before the sale rather than after.

Abandoned checkout reminders: the one case to think about

An abandoned checkout reminder includes the checkout total at the moment the shopper left. If that shopper was in a rollout that activated a discount, the total already includes it. When they come back through the link in the message, Shopify prices the cart again at that moment. Three things can have changed in between.

The rollout ended. An Event rolls its changes back on its end date, so a discount that only existed because of the rollout is gone, and the shopper sees a higher total than the message quoted.
The shopper is no longer in the audience. A rollout that reaches a share of visitors, or an Experiment, applies to visitors on your online store. A shopper who returns on another device or browser may not be recognised as the same visitor, and Shopify may price the cart as the control group.
The discount's own dates ended. This is the ordinary case that existed before rollouts and it is worth remembering that the two schedules are independent: a discount can be inside its own dates and still be switched off for a rollout audience, or outside them and still on.

None of this is specific to WhatsApp, and email reminders have the same exposure. The practical rule is to keep the reminder template about the cart, not about the price. Say that their items are waiting rather than that they will save 15%, and let the checkout show the current total. If you want a reminder to promise a discount, use a discount code with its own dates that you control, not one that a rollout switches on for part of your traffic.

Replying to customers who ask about a discount

When a customer replies to a WhatsApp message asking why they did not get the offer their friend mentioned, the answer is now in Markets > Rollouts before it is on the Discounts page. Before you tell a customer the discount has expired, check whether a rollout is running, what share of traffic it reaches, and whether it is an Experiment. Shopify's requirements page notes that Experiments and rollouts below 100% apply only to the online store, so a customer who ordered through point of sale or another channel was never in the audience at all.

For an Experiment, the honest reply is that the store is testing an offer with some visitors. Whether you then extend it to the customer by hand is a business decision; the point is that nobody should be told the discount does not exist when it is live for half the store.

What changed for apps, and why not here

Alongside the merchant feature, Shopify asked app developers to update any app that reads discount data. From API version 2026-10 every discount exposes the rollouts that include it, and apps that read a discount's status were told to request a read_rollouts permission and account for rollout schedules and traffic allocation, because the discount's own fields can be incomplete while a rollout is serving.

Beacon Messenger does not read discounts. It reads orders, fulfilments and abandoned checkouts, each of which already carries the amounts the customer saw. So there is no new permission to accept, no new prompt when you open the app, and no change in what your messages say. The only new work is on the merchant side: knowing that a rollout can make two customers' totals differ, and writing reminders that do not quote a discount they may not get.

Frequently asked questions

Does the WhatsApp order confirmation show the rollout discount?

It shows the order total Shopify recorded for that customer, after any discounts. If the customer was in the rollout audience and the discount applied, the total in the message includes it. If not, it does not. The app does not need to know about the rollout.

Will an abandoned checkout reminder quote a discount the shopper can no longer get?

It can, if the discount came from a rollout that ended or whose audience the shopper is no longer in when they return. Keep reminder templates about the items rather than a saving, and let checkout show the current total.

Does Beacon Messenger need the new read_rollouts permission?

No. Shopify's October 2026 notice is for apps that read discount data. Beacon Messenger reads orders, fulfilments and checkouts, which already include the prices the customer saw, so it needs no new permission and shows no new prompt.

Why did a customer who ordered in my shop not get the rollout discount?

Experiments and rollouts that reach less than 100% of visitors apply only to the online store. Orders placed through point of sale or other channels are outside the rollout audience, so the discount was never offered there.