Two features shipped in this release. Both are set per bundle, in the bundle editor.
New features
Countdown timer for bundle widgets
You can now display a live countdown timer inside your bundle widget on the storefront.
Turn it on in the bundle form: Advanced tab → Countdown timer → the Show countdown timer checkbox. Unticking the checkbox deletes the timer's settings, so re-ticking it later starts again from the default condition rather than from what you had configured before.
Once it is ticked, a Conditions select appears — labelled "Conditions" for the bundle-end option and "Timer conditions" for the other three. There are four to choose from:
Follow end date and time set for bundle (the default) — shows the bundle's real expiry, so the timer reaching zero and the bundle expiring happen at the same moment. It needs "Set end date and time" ticked in the Bundle active period card; with no end date, or one already past, no timer is drawn at all.
Fixed duration — a Duration (min) field appears beside the select, seeded to 15. Enter a whole number of minutes greater than zero and every shopper gets their own countdown of that length, remembered in their browser across page views until it runs out. Nothing is drawn when the number is zero or empty.
Ends at midnight (user's local time) — counts down to the next midnight in each shopper's own timezone. There is no further field to fill in.
Custom end date — End date and End time fields appear, seeded to one hour from now. The countdown section hides once it ends. Saving is blocked on a past or missing value, with the message "End date and time must be in the future".
The Title field above the countdown — labelled "Title" for the bundle-end condition and "Timer title" for the other three — is the caption shown to shoppers, with a placeholder suggesting "Hurry! Offer expires in". Leave it empty and it falls back to an older store-wide caption. The Translate button beside it gives you different wording per widget language.
The timer never deactivates a bundle
This is worth being precise about, because it is easy to assume otherwise: the countdown timer is a display element, in every one of the four conditions. None of them ever starts, stops or expires a bundle.
Only the End date and time in the Bundle active period card decides whether a bundle is served to shoppers. "Follow end date and time set for bundle" simply shows that same moment to the shopper — it mirrors an end date you set elsewhere, and does not create one.
A/B testing for bundle widgets
You can now run A/B tests on a bundle widget to see which configuration converts best.
Add variant creates up to four widget variants (A, B, C and D) of one bundle, each with its own configuration, its own preview, and its own tab. Run A/B test splits shoppers across whichever variants are active. End A/B test shows revenue and purchases per variant, so you can pick a winner: once chosen, all traffic moves to that variant and the rest are archived.
The bundle list marks tested bundles with an A/B test badge, and lets you expand or collapse their variants.
Fields that stay shared during a test
While a test is running, several fields are shared across all variants and can only be edited on the primary (A) variant:
the bundle's internal name
the bundle active period
the countdown timer
Markets
widget placement
subscription integration
Exclude B2B customers
bundle priority
If one of these is greyed out on variant B, C or D, that is why — edit variant A instead, or end the test and choose a winner.


