Oribi home dashboards

• The home dashboard is available only to Spaaza customers using Oribi. Each team member also needs Oribi and Analytics permissions.
• You can now set up a daily dashboard around your business goals. Oribi creates goal cards with key figures, charts or tables, and suggested areas to investigate.
• The first dashboard starts when you save the setup. You can also select an existing briefing or use Generate now to refresh the dashboard without changing its daily schedule.
• Select View details on a card to review the full result, the period it covers, and any data limitations. Investigate opens a suggested question that you can review before sending.
• Super users can enable Oribi for a program and grant team members access. See Create your Oribi home dashboard for setup and use.

Campaigns and vouchers

• Switching between voucher reward types now shows the settings for the selected type and keeps entered values available if you switch back.
• Percentage vouchers now check that the discount is greater than 0 and no more than 100 before saving. An error appears beside the field, so it is easier to correct.
• Campaign overviews have clearer spacing and alignment. Barcode conflicts are easier to spot, and discount form guidance now appears beneath the related fields.

Customers and content management

• Customer lists show the member Number again, with Name, Number, Phone, and Email together at the start of the table. You can also filter by number.
• For supported businesses, voucher previews now match the customer-facing Embed Element's voucher labels, button state, and date format.

Other improvements

• Oribi answers now present findings more clearly and call out important limits in the available data, including when transaction data covers members only.
• Several smaller reliability and usability improvements have been made across Console.

Enjoy!

• Changed (breaking) Two-Factor Authentication (2FA) for admin user login. 2FA on login is now enforced for every request API version, including the default 1.0.0 used when no X-Spaaza-API-Version header is sent. Previously the passcode step only ran for requests with version 1.5.8 or higher, so older or version-less admin logins received a full session immediately and bypassed 2FA. Those clients now receive a session_passcode_key and session_passcode_expiry_date instead of session_info, and must complete the login by posting the emailed passcode to the session endpoint. Admin users with login_2fa_exempt set are unaffected and continue to receive an immediate session. See the versioning page for details.

• Changed POST /resources/access_token so that the scope of a new token is restricted to the chain given in the X-Spaaza-Chain-ID header of the request: only chain:{chain_id} and read_businesses:{chain_id} for that chain are accepted. A request whose scope names a different chain, or uses any other scope key, is rejected with access_denied (code 424) and no token is created. Previously the submitted scope was stored unchanged. Existing tokens are not affected. See scope.

• Fixed the resolution of the shopper from spaaza_user_id so that the shopper must belong to the chain identified in the request. A spaaza_user_id of a shopper in another chain is now treated as not found: the basket is processed as an anonymous basket and, from API version 1.5.2, the response carries a user_not_found warning, exactly as for an unknown ID. Previously such a request could attach the shopper from the other chain to the basket. The member_number and authentication_point_identifier fields were already limited to the chain of the request and are unchanged. This change is not tied to an API version. See shopper identification fields.

• Fixed the checks made when a privileged client acts on behalf of an end-user with the X-Spaaza-On-Behalf-Of header. The access token must now be scoped to the chain to which that end-user belongs; a request for an end-user in a different chain, or for an end-user that cannot be matched to a chain, is rejected with access_denied (code 424). Previously the end-user was not checked against the chain scope of the access token. See acting on behalf of an end-user.
• Changed the handling of the X-Spaaza-On-Behalf-Of header so that it is only accepted by the endpoints that support it, currently lock-voucher and delete-voucher. A privileged request that sends the header to any other endpoint is now rejected with access_denied (code 424) instead of being processed as an ordinary privileged request with the header ignored. API clients that send the header to other endpoints should remove it from those requests. This change is not tied to an API version.

Customer purchase history

• Customer profiles now have a Products tab for accounts with analytics permission.
• Recently purchased shows the customer's latest product and variant purchases, including the store, quantity, amount, and transaction date.
• Top products can be ranked by purchase frequency, units purchased, or purchase spend across the customer's available indexed history.
• Search can find a product, variant, product name, code, or barcode. Selecting a result shows purchase totals, first and last purchase dates, returns, a purchases-over-time chart, and matching transactions.
• Product and transaction links make it easy to move from the summary to a detailed purchase history or the original transaction.
• See Review a customer's purchased products for the complete workflow.

Embed Elements and content management

• Settings → Default campaign content settings now has an Advanced section for configuring Embed Elements styling variables.
• The editor suggests known variables, checks CSS values, and provides an Elements Styling JSON view when a complete configuration needs to be pasted or reviewed.
• Live previews now apply the saved default content styling consistently across Settings and Content Management, including immediately after saving or switching businesses.
• Percentage voucher previews no longer add an incorrect percentage prefix to the voucher title.
• The updated Content Item configuration guide now explains live campaign previews, inherited colours, voucher content, and tap actions.

Other improvements

• Signup report pie charts now contain long labels and wrap their legends more cleanly.
• Various smaller preview, layout, and usability fixes have been made across Console.

Enjoy!

• Fixed the checks made on each request that uses privileged (Bearer access token) authentication. A request is now rejected if the access token is inactive or deleted, or if the service client that owns the access token is disabled or deleted. Previously such a request could still authenticate for a period of time after the token or service client was revoked. See access token revocation.
• Changed the error returned for a request made with a revoked access token, or with an access token of a disabled or deleted service client. Such requests now return access_token_invalid (code 266, HTTP status 401) at authentication time instead of access_denied (code 424). This change is not tied to an API version. API clients that check for access_denied in this situation should check for access_token_invalid instead.

• Added the email provider webhook types ses and smtp to add-webhook and alter-webhook, configured on the email_verification_otp and email_verification_deeplink events, so a chain's email verification messages can be sent either by Spaaza's own email service or through the chain's own SMTP email provider. See sending verification emails from your own email provider.
• Added a backup provider for the messages that verify an email address or a phone number, configured as a pair of webhooks on the same event using the new delivery_role field on add-webhook and alter-webhook. The primary sends; the standby is held back and used only when the primary fails to accept the message, so the customer still receives exactly one message. Available on the email_verification_otp, email_verification_deeplink and phone_number_verification events. The new swap-webhook-delivery-roles endpoint exchanges the two roles in one step, and conflicts return the new error webhook_delivery_role_conflict (code 562). See backup email provider.
• Added last_purchase_date to the shopper object sent in webhook event payloads, such as the shopper.altered event. It holds the date and time of the customer's most recent purchase in UTC (for example 2026-06-27T13:33:43Z), or null for a customer with no purchases. The get-user response is unchanged.
• Changed the type of an email verification webhook so that it names the delivery provider, ses or smtp, instead of repeating the event name. The previous values email_verification_otp and email_verification_deeplink are no longer accepted by add-webhook; the event is given in event_name as for every other webhook.
• type can now be changed on alter-webhook, limited to switching an email verification webhook between ses and smtp.
• Changed alter-webhook and delete-webhook so that a primary verification webhook can no longer be deactivated, deleted, moved to another event or have its delivery_role removed or changed while its standby is still active. Such requests return webhook_delivery_role_conflict (code 562). To retire a primary, first swap the roles and retire the demoted webhook, or deactivate the standby first. Deactivating or deleting a standby, or a primary without a standby, is unaffected.

Content management

• We have made many improvements to how campaign content (used in Spaaza apps and Embed Elements) is managed in Console.
• A live Content preview updates as content is edited, showing different layouts and voucher cards together.
• Promotional fields now follow the order in which customers see them. Images are grouped together, colours use one shared picker, and clear captions explain when a default or an overridden value is active.
• Campaign overview pages and the loyalty styling and voucher-default settings now use the same previews, field names, ordering, and inherited-value display as the campaign form.
• Content management gives more room to the editor and preview, and makes selection controls clearer.
• A new tap action editor with a simple dropdown makes it easy to choose what happens when a customer taps the content item.

Oribi AI

• We've made big improvements to Oribi — it's much smarter, it can answer many more questions, and the user interface has been significantly improved.
• Answers now stream into the conversation as they are generated, with clearer progress and activity messages.
• Oribi can ask a clarifying question when a request is ambiguous, then present supported results as tables and charts directly in the conversation.
• Suggested follow-up questions make it easier to continue an analysis, while clearer handling of partial periods, missing data, and failed searches helps prevent incomplete results from being presented as definitive.
• A new Dashboard/Oribi switcher keeps standard Console navigation separate from New, Briefings, and saved conversations. Saved conversations are grouped by recent activity, and briefing shortcuts make recently generated briefings easier to revisit.
• Oribi is not enabled by default. Talk to a member of our team if you want Oribi activated for your business.

Reporting and navigation

• Improvements to analytics and chart query reliability
• Comparison series timelines are now shown on some charts
• A new expanded chart dialog has been added
• Reporting now has dedicated Realtime reports and Downloadable reports tabs, bringing both report types into one clearer workspace. See the updated Reporting guide.
• Catalog navigation now keeps Products and Variants together and preserves the correct active state as you move between pages.

Other improvements

• Successfully created export and download tasks now show a confirmation notification with a link. We have also added an indicator on the Exports navigation link in the menu to show there is a new export task created.
• Outlier ratio by store now correctly accounts for transactions without an outlier score.
• Several labels in the Outliers report have been clarified, including replacing Reimbursed with Flagged where the value describes transactions marked for review.
• Dialogs, tables, forms, and other layouts have received numerous smaller consistency and usability improvements, along with various bug fixes.

Enjoy!

• Added the chain option first_transaction_sets_home_and_signup_store, configured through alter-chain and also available on the Chain resource. When it is enabled, a customer's first completed transaction sets their signup store and their home store to the branch business of that transaction's basket. Each store is only filled if it is still empty, and later transactions never change either store. See stores set by the first transaction.
• Added the email verification webhook types email_verification_otp and email_verification_deeplink to add-webhook, so the delivery of a chain's email verification messages can be configured through the API.
• Changed the error returned by otp-verify for an incorrect or expired code to verification_code_invalid_or_expired (code 561), replacing the more general password_error_or_non_existent (code 5). Clients which show their own message for an invalid passcode should key on the new error code.
• Improved the performance of returns which do not supply an original_retailer_basket_code: matching a returned item to its original purchase is now fast even for customers with a very large transaction history, where such requests could previously take tens of seconds. The lookup covers the customer's 2,000 most recent transactions.
• Improved validation of points_tracker campaign rules, which are now rejected when no action is supplied. This prevents a rule which cannot be applied from being saved, and prevents the error which such a rule caused when a customer's purchase progress was updated.
• Fixed the survey campaign endpoints so that a request for an inactive or deleted survey is rejected with campaign_not_active (code 449), and a required consent question is only treated as answered when a value is actually supplied. An explicit false still counts as an answer.
• Fixed Shopify customer synchronisation so that a customer who already exists in Spaaza keeps their existing signup_channel. Only customers genuinely created by the Shopify webhook are recorded as a Shopify signup. See data synchronisation.

Surveys

• New Survey campaigns can collect first-party feedback, preferences, profile data, or consent signals, then issue a configured reward when the customer completes the survey.
• Surveys support single choice, multiple choice, rating, NPS, short text, long text, and consent questions, including required questions and multi-page question sets.
• Larger surveys have a searchable Questions workspace with one question editor and a live preview. Questions can also be imported from CSV and reviewed before they are added to the campaign.
• The campaign Preview, Report, and Responses pages make it possible to review the customer experience, analyse answer shares, ratings, NPS and demographic insights, and export individual responses.
• A new Surveys guide explains when to use surveys and how to create them.

Basket missions and transaction outliers

• Realtime reports now include Basket missions, with views of mission mix, average basket value, shopping times, category mix, private-label share, and comparisons across stores and store formats.
• A new Outliers report helps teams find stores with unusual transaction activity and investigate the timing, discount at stake, campaigns, products, customers, and tills involved.
• Basket-mission and outlier information is also available in relevant customer, transaction, store, and campaign views.
• Analytics cards now provide more plain-language explanations of what each visual shows and how to use it.
• These Insights are switched on for your business by Spaaza. Contact Spaaza to enable Customer enrichment or Transaction outlier score.

Wallets and campaigns

• Spend Target campaigns now appear as Spend Target Wallets in wallet creation, All wallets, and customer Wallet Entries. Their monetary progress can be reviewed and adjusted from the customer profile.
• Composable campaigns with multiple reward methods now use a searchable Reward methods workspace, with clearer overview summaries and value-calculation choices.
• Survey campaigns are clearly identified as Survey in campaign lists.
• Cancelling campaign edits now asks for confirmation before unsaved changes are discarded.

Competition draws

• Competition wallets now include a Winners page for reviewing draw results.
• Completed draw cards show each named set and provide a direct View winners action for that set.
• Winner results can be filtered and exported as CSV.

Other improvements

• Report filters now reload the latest data more reliably, including when a date or another filter changes while an earlier request is still loading.
• Resource filter libraries can now be searched by name or description and show a clear result count.
• Entity tabs remain on one scrollable row, making pages with many sections easier to navigate on narrower screens.
• Content and survey previews now provide desktop, laptop, and mobile sizes, with manual resizing when a custom width is needed.
• Virtual POS inputs and scrolling have been polished for clearer use on shorter screens.
• Numerous smaller layout and styling fixes have been made across Console.

Enjoy!

• Added survey campaigns, a composable campaign with context: "survey". The survey questions are configured on the campaign through survey_definition in add-campaign and alter-campaign, client applications fetch the definition and the shopper's completion state with GET /survey, and answers are submitted with POST /submit-survey. Completion is idempotent per shopper and campaign, issues the campaign's direct reward methods, and enforces the campaign's segment restriction on both retrieval and submission. Completed responses can be retrieved with GET /internal/get-survey-responses.
• Added email address verification, configured per chain with the email_verification_method option (off, otp or deeplink) through alter-chain and returned by get-chain. See verifying user contact details for the full flows.
• Added an email one-time passcode flow: otp-request and otp-verify accept an email parameter to send a six-digit passcode to a user's email address and verify it, mirroring the existing phone number flow with the same rate and attempt limits.
• Added an email verification link flow with the new email-verify-request and email-verify endpoints, which email a signed, single-use verification link that is valid for three days.
• Added an email_status field to the user, returned by get-user, showing whether the email address has been verified (1) or not (0). Changing a user's email address through add-user or alter-user resets email_status to unverified.
• Added privileged authentication for the Resources API, so a service client can use a bearer access token in the X-Spaaza-Access-Token header instead of an administrator session. See authentication for the resources and operations available.
• Added end-user (shopper) authentication for the Resources API, allowing a customer to retrieve their own data with the session credentials returned by login plus the X-Spaaza-MyPrice-App-Hostname header. GET requests are supported on the Business, Voucher and ContentPage resources, results are limited to the customer's own data and their app's chain, and properties that are only relevant to administration are omitted from the response.
• Changed the default voucher filtering for end-user Resources API requests: GET /resources/vouchers returns only vouchers with status generated or claimed unless redeemed vouchers are requested explicitly, for example GET /resources/vouchers?status=redeemed.
• Improved authentication handling so that a customer session is validated against the chain of the app making the request, and can no longer be used with an app belonging to a different chain.
• Fixed purchase progress distribution so that a campaign contributing progress into a wallet or stamp card honours its own earn_on_promotional_items setting, and no longer awards progress for promotional items when that setting is false.
• Fixed the counting of issued honour_voucher rewards against a reward method's usage_limit, so a composable campaign can no longer issue more rewards than the configured stock allows.
• Fixed the status filter on Resources API voucher requests, so GET /resources/vouchers?status=claimed now returns the matching vouchers.
• Fixed Shopify registration and customer synchronisation: registering with an email address that already exists in Shopify now returns the intended duplicate email error rather than a generic server error, customer lookups require an exact email address match so a similar address is never adopted, and synchronising existing Shopify customers into Spaaza no longer fails for customers without an existing programme opt-in.

Stamp cards and wallets

• Item Count campaigns now appear as Item Count Wallets throughout Console.
• Item Count Wallets can be used as digital stamp cards. Qualifying purchases add stamps, customers progress towards a target, and reaching the target can issue a reward.
• Standard campaigns can issue bonus stamps into an Item Count Wallet for actions such as completing a profile or joining a promotion.
• The wallet chooser makes it easier to find compatible active, scheduled, or completed wallets.
• A new Stamp cards guide explains how to plan and create a stamp-card program.

Customer profiles

• The customer Overview page has been redesigned to bring transaction activity, customer score, RFM information, channels, Favorite store, membership date, notes, and profile details into one page.
• Purchases, Wallets, and Available vouchers now provide quick summaries with links to the complete history.
• Wallet Entries now brings points, credit, competition, and Item Count wallets into one place, including balances, entry history, and manual adjustments.
• The customer Discounts page now has stronger campaign filters, including campaign groups.

Campaigns and Content Management

• Campaign lists can now be filtered by campaign group. Active groups are shown first, while More groups can be used to find scheduled or completed groups.
• Campaign action menus now follow campaign permissions more consistently.
• Content zones without a title are now clearly identified by their zone ID.
• Content Management action menus and layouts have received several small consistency improvements.

Reporting and other improvements

• Wallet and time-series charts now handle empty and zero-value data more clearly.
• Segment links now show a clearer customer preview when you hover over them.
• Numerous small styling and usability improvements have been made across Console.

Enjoy!

• Added support for campaigns contributing progress into a stamp card. Any campaign that supports purchase progress (for example a matching_item campaign) can add stamps to an item_purchase_count campaign by setting its recipient_campaign_id to the stamp card's campaign_id and its recipient_reward_method to points. The card's reward is issued when its target_count is reached, whether the completing stamps come from the card's own qualifying items, from contributions, or from a combination of both within the same basket. Existing stamp card behaviour is unchanged.
• Added an owner_code field to composable campaign reward methods, settable through alter-reward-method and returned by get-reward-method and get-reward-methods. It is a short label of your own choosing (maximum 64 characters) used to identify a reward method when several are listed together, and has no effect on how rewards are calculated or issued.
• Changed the max_basket_items_considered field on the reward-method basket_item restriction so that it counts individual items rather than basket lines. A single basket line with a quantity of 3 now counts as three items, exactly as three separate quantity-1 lines would, and the same limit is applied when the reward value is distributed across the matched items.
• Fixed the promotional state of stored basket items so that it is no longer re-derived from current product data when a basket is processed again, for example by claim-basket or a return. An item that was not on promotion when it was bought continues to earn from campaigns configured with earn_on_promotional_items set to false, even if the product has since been flagged as promotional.
• Fixed the handling of non-boolean item_is_promotional values in add-basket. Values such as "false", "0" and 0 are now interpreted as not promotional, values such as "true" and 1 as promotional, and any unrecognised value defaults to not promotional.

A refreshed Console

• Console now has a more consistent look across navigation, forms, buttons, tables, filters, and pop-up windows.
• Reporting charts and cards have been refreshed with clearer colours, labels, and spacing.
• Success messages, warnings, and errors are now easier to see and can be dismissed.

Competition draws

• Competition draws can now use the whole competition period or a selected date range.
• Draws can be split into named sets, with separate numbers of winners and backups for each set.
• Sets can be limited to a region, business format, or specific store.
• Backups can be drawn independently or from the same store as each winner.
• Previous winners and backups are automatically excluded from later draws for the same competition.

Campaigns and Content Management

• Campaign dates now follow the reporting time zone selected for the business.
• Creating or saving a campaign now shows a clear success message.
• Rewards can now be removed from a composable campaign without preventing the campaign from being saved.
• Mass voucher issuing now starts the correct process.
• The Content Management page picker now shows the selected page more clearly and makes parent and child pages easier to browse.

Team members

• The Team members page now includes Export CSV for downloading names, email addresses, and permissions.
• Super users also see whether each team member is exempt from two-factor authentication in the export.

Other

• Numerous small styling improvements and bug fixes.

Enjoy!

• Added a require_unique_phone_number chain option (set via alter-chain, returned by get-chain). When enabled, add-user and alter-user reject any request that would give two active accounts in the same app the same phone number, returning the new phone_number_already_exists error (code 555). When disabled (the default), duplicate phone numbers are still allowed and are only flagged via the phone_number_duplicate field. Enforcement applies to new writes only; accounts that already share a phone number are left unchanged when the option is enabled.
• Added two value_calculation_rule options for wallet_contribution reward methods on composable campaigns, configured through alter-reward-method: fixed_value_per_basket awards the configured value once per qualifying basket, and fixed_value_per_spend awards the value for each spend_step of basket spend (using the new spend_step reward-method field). Unlike the existing per-item fixed_value rule, both are independent of item quantity.
• Added the get-campaign-barcode-conflicts endpoint. Given a chain, a list of barcodes and a reference date window, it returns each barcode that is shared with another campaign whose active date window overlaps the reference window, along with those campaigns' details. This makes it possible to detect barcode and scheduling clashes between campaigns in a single request.
• Changed the chain basket_campaign_require_format_assignment option so that a Business (store) assignment now also satisfies the requirement. When the option is enabled, an active BasketCampaign is accepted if it has either a Business Format assignment or a Business (store) assignment, aligning the API with the Console campaign activation checklist.
• Changed date-time fields in Resources API responses to RFC 3339 format (a profile of ISO 8601), normalised to UTC (for example 2026-07-07T15:30:23+00:00), for API version 1.6.8 and above. Earlier API versions continue to receive the previous Y-m-d H:i:s format for backwards compatibility.
• Removed the shopper object from the transaction/receipt response. Member identity is now carried solely by the user field, which already contains the same name, contact, membership and address details, so the duplicate shopper block is no longer returned.

Reporting and campaign analytics

• Campaign reports now use clearer report sections, including Summary, Customer response, Basket context, Channel performance, Product entries, and Price and mechanics where the campaign data supports them.
• Campaign and campaign group reports now include deeper product, store, format, region, basket, customer-response, time-of-week, and price-mechanics cards for promotions with assigned products or redemption activity.
• A dedicated Levels report is now available in Realtime reports for current level membership and level joins over time.
• Wallet campaign reports now include clearer wallet activity, entry contribution, channel, mutation, and top-customer breakdowns.
• Reports now have a new "i" option where an explanation of the data shown and how it can be used is provided

Content Management and app pages

• Content Management now supports Voucher zones. A voucher zone shows each user their own vouchers instead of manually assigned campaigns.
• Voucher zones can show available vouchers, redeemed vouchers, or vouchers issued by a specific campaign.
• Console now shows example voucher previews for voucher zones, makes clear that the real result is personalized per customer, and limits voucher zones to the Card layout.

Campaigns, tasks, and rewards

• Entries wallets now include a Draws tab for competition draws.
• Competition draws can be started from Console by entering the number of winners and backup winners to draw. The draw uses the campaign's active date range when one is set, tracks status while it is running, and exposes the finished result download from the draw card.
• Campaign lists now include status filters for Active, Scheduled, Completed, and Disabled campaigns.
• Campaign group pages now separate wallet campaigns from other campaigns when no filters are active, making campaign groups easier to scan.

Virtual POS basket simulator

• The developer basket tool has been redesigned as Virtual POS: simulate basket requests.
• Teams can now select a store and customer, add products or manual line items, preview rewards and discounts, complete a basket, and review generated receipt artefacts from one screen.
• A new side panel shows the current request, latest price response, completed basket response, and request history.
• Usage in production is restricted to accounts flagged as "Virtual POS tester". Please talk to the Spaaza team to add an account/s

Other

• Numerous bug fixes and small improvements

Enjoy!

• Added manufacturer, private_label and listing_source product fields. These are returned in product responses (for example get-product) and can be set when creating or updating products, including through the product feed import.
• Added a visible_to_all_user_segments option to the composable campaign segment restriction. When true (the default) a segment-restricted campaign is still shown to everyone in get-campaigns and get-card, and the segment only affects whether the reward applies; set it to false to also hide the campaign from users who are not in the segment.
• Changed the composable campaign segment restriction to accept a single segment id for user_segment_id and excluded_user_segment_id. Comma-separated lists of segment ids are no longer accepted.
• Fixed composable interaction campaigns (such as scratch cards) so their reward methods can once again carry redeem-shaping restrictions (basket_item, business, currency), matching the behaviour already documented for these campaigns.
• Fixed composable voucher redemption so that when a reward-method redeem restriction (basket_item, business or currency) matches nothing in the basket, the voucher now redeems on nothing instead of applying its full value across all basket items.
• Removed the unused business_format and business_region composable restriction types. Filtering by business format or region remains available through the business restriction using its business_formats and business_regions fields.

Reporting and analytics

• Reporting is now organised around Realtime reports and Downloadable reports, making it clearer whether you are opening live on-screen analysis or generating a file for later collection.
• The main loyalty dashboards now have dedicated report pages for Loyalty, Signups, Baskets, Top Customers, Wallet Entries, Vouchers, and Personal Pricing.
• A new Transaction value buckets report helps teams review basket value distribution by configurable transaction buckets.
• Several analytics reliability improvements have been added, including more accurate comparison date ranges and more resilient campaign sales reporting for large barcode sets.

Insights

• New Insight guides explain Spaaza-derived customer and transaction attributes that can be used in Console, segmentation, exports, and API workflows.
• New documentation is available for Basket missions, Customer enrichment, Customer value insights, and Transaction outlier score.
• Insights are enabled per business by Spaaza, so contact Spaaza if you want to start using them.

Campaign controls

• Percentage-based basket discounts and percentage vouchers can now be limited with Maximum basket discount.

Team members and permissions

• The Team members settings page now supports filtering by name or email.
• Team member permission columns are clearer, with new permission visibility for Analytics, Export, and Segment query access.
• Creating or editing a team member now uses a clearer settings form, including a secure password generator for new users.
• Console now shows a permission notice when a user tries to open a page they are not allowed to view.
• Analytics, exports, campaign creation, and the global Create action now respect the relevant team member permissions more consistently.

Other improvements

• Product, voucher, wallet, and campaign reports include smaller data matching and display fixes.
• Monetary resource values are now displayed with cents where needed.
• User form labels and input IDs have been improved.
• Settings pages have received smaller layout and form consistency improvements.

Enjoy!

• Added max_basket_discount_amount campaign field, allowing a per-voucher cap on the discount value of percentage basket vouchers at redemption time. The cap is enforced per voucher during get-basket-price and add-basket.
• Added new admin permission fields permission_analytics, permission_export, and permission_segment_query on add-user, alter-user, and permission-related endpoints, enabling more granular access control for admin accounts.
• Added created_date and last_modified_date as sort parameters for the Business and AllowedIpRange resources in the Resources API.
• Changed percentage basket voucher application on chains that allow double discounting: get-basket-price and add-basket now apply all eligible campaign-level standalone percentage basket vouchers by threshold allocation — sorted by campaign reward_priority, then cap-aware delivered discount for same-priority vouchers, then created_date — instead of keeping only the single best percentage voucher. The max_basket_discount_amount cap applies per voucher.
• Changed voiding/cancelling a transaction via an empty get-basket-price (no items and basket_total_value 0) to also unlock the shopper's standalone vouchers: any claimed, non-expired voucher locked to the same retailer_basket_code / voucher_locking_code now has its lock cleared, not only on-the-fly basket campaign vouchers.
• Improved event handling so that deferred events (such as OTP SMS notifications) are no longer triggered when the API request that staged them fails.
• Improved get-basket-price to no longer return misleading warnings for auto-loaded vouchers that do not match campaign spend-assignment parameters.
• Fixed an issue where voucher key generation under high concurrency could produce duplicate keys.
• Fixed a get-basket-price error that occurred when the basket had no items and the user held vouchers from inactive campaigns.