Bulk activate or deactivate with confidence: the parent offer now shows context-aware action buttons based on the live state of its children — "Activate All" when all sub-offers are stopped, "Deactivate All" when all are active, or both buttons when the mix is varied. A confirmation modal always appears before any bulk action is applied, showing exactly how many offers will be affected.

Parent expiry date always stays accurate: when sub-offers exist, the parent's expiry date is automatically set to the latest expiry across all child offers — no manual adjustment needed. The field is only editable while the parent has no sub-offers; once children are added, it becomes system-managed.

At-a-glance status breakdown on the parent row: instead of a single status label, the parent offer now displays a live breakdown of its children — for example, "Parent · 3 Live, 2 Stopped, 5 Expired" — so you can see the full picture without opening each sub-offer.

Dedicated edit experience for parent offers: editing a parent offer now opens a tailored interface with the fields relevant to parent-level configuration, keeping the experience clean and focused.

Steps you have already visited when creating or editing an offer are now interactive. Click any completed step bar to jump directly back to it without stepping through each screen in sequence.

Unvisited steps remain non-interactive, so it is always clear which steps are available to navigate to.

When you revisit a step, it is highlighted with a distinct pill-shaped indicator and a soft teal glow, making it easy to see where you are in the flow.

A new setting in Loyalty Management lets you restrict point earnings to whole numbers only, preventing fractional points from being awarded on transactions.

When enabled, you can choose how decimal values are handled — rounded down, up, or to the nearest whole number — giving you full control over your programme's points logic.

The setting is configured at programme level, so it applies consistently across all transactions without any per-campaign configuration.

When setting up a push notification campaign, you can now configure three additional fields: title, body, and a source identifier. They are included in the data payload sent to your app provider.

Your app can use these fields to display notification content however suits your experience best.

When configuring a Journey Decision with a "Clicked specific link" condition, the selected link is now retained correctly even when the URL contains multiple query-string parameters such as UTM tracking values.

Previously, re-opening the decision would silently revert the selection to "All Links", causing journeys to branch incorrectly; this is now resolved.

The image resizing tool in the Asset Library within Wallet Management now works consistently, the resize button is hidden for users who have not consented to functional cookies, preventing failed resize attempts.

Selecting and editing a company whose name contains special characters (such as an apostrophe) in Company Setup now works correctly; the Edit button responds as expected and no browser error is shown.

All companies are now editable regardless of the characters used in their name.

Custom list campaigns now always have an export format assigned at creation, resolving an issue where the format could be left unset and require manual correction before the campaign could be sent.

Exporting Social Media Monitoring data to Excel now produces a complete, valid file every time, resolving an issue where the exported file could be corrupted or incomplete with no error shown.

Previously, if a transaction was sent without an OrderTypeID or OrderStatusID, it would be hidden in the Contact Profile. Now, it's displayed regardless of whether those fields are sent through as empty or not.

This prevents a scenario where a transaction is stored but never appears in Acteol, removing a hard-to-diagnose discrepancy between stored data and what is visible in the platform.

API documentation has been updated to accurately reflect which fields are required for a transaction to be processed correctly.