Bug Fixes:

• Bug fix for issue: No myAEON2go logo in Android Push Notification

Enhancements:

• Revert app icon to original icon

Enhancements:

• Display standard label for View Choice item when any of the variant options have the badge which is setup on Foxtrot

Transitioned app from App Center to Firebase. Shoppers can access the invite link to download the latest version to use. See details to setup here

Enhancements:

Changes to Promo Codes - Variant Rules:

1. ‘Minimum Optional Variant Quantity Required’ has been replaced with Minimum Optional Variant Rule Required
   1. Previous state: Field controlled the quantity of optional variants required despite what amount was set up in the variant rule.
   2. New state: Field controls the amount of optional variant rules (regardless of type) that must be met for the promo code to apply.
      1. This is only applicable if Is Optional is selected. If all rules are required, this should be left blank.
      2. User can apply meeting the same optional rule multiple times towards the required amount.
      3. Example: If there are 5 optional variant rules, and ‘Minimum Optional Variant Rule Required’ is set to 3, user needs to meet at least 3 of those 5 rules to activate the promo code.
2. Introducing a new ‘Variant Rule’ type for Value
   1. This is in addition to the existing variant rule type for Quantity
   2. Value rule will enforce that the value (dollar) amount of the variant or brand selected must be added to cart in order for the promo code to apply.
   3. Value variant rule can apply to select variants or brands
      1. i.e. Spend $100 on GID X and get Y discount with code
      2. i.e Spend $100 on Brand X products and get Y discount with code
   4. There can be multiple Value variant rules in one promo code
   5. Quantity and Value variant rules can be stacked within the same promo code
      1. i.e. Buy 2 units of GID X and spend $100 on Brand Y products to get Z discount with code
   6. All variant rules (including Value and Quantity) will apply to promo variants as long the promo variant is tied to a promo code group set up with the proper rule.
   7. Once the variant rules are met, all other conditions of the promo code apply.

See updated user guide here.

Bug Fixes:

• [Promo Codes] If scope is selected, scope definition field must be a required.

Enhancements:

• Improve app performance
• [Waon] Update Redeem Voucher dropdown to max limit of 20.
  Waon changes are only applicable for the Waon loyalty integration.
• UI/UX Checkout Enhancements on Android to be synchronized with iOS. See details here

Feature Releases:

• Add reasons to the order cancellation flow

Bug Fixes:

• Bug fix for issue: Android has shown all category for Nationwide postal code
• Bug fix for issue: Banner not properly displayed in new Android version 2024.23.1

Enhancements:

• [Waon] Update Redeem Voucher dropdown to max limit of 20.

Waon changes are only applicable for the Waon loyalty integration.

Enhancements

• Update "Received" order status to "Order Placed" for clarity. Applies to order history, order details and homepage tracking module

Enhancements

• Add a toggle at checkout for customers to apply their credit balance

  

• Update "Received" order status to "Order Placed" for clarity. Applies to order history, order details and homepage tracking module

Bug Fixes

• [Waon] Allow users to redeem vouchers if their point balance would go to exactly 0.

Waon changes are only applicable for the Waon loyalty integration.

Feature Release

• Display promo codes at checkout to allow user view and select multiple available promo codes. View user guide here for details ("Enabled Checkout Display" field)

  

Enhancements

• [Waon] Update copy on registration failure modal

  

• Add B2B Customer Policy in Help/Contact

  
  

Bug Fixes

• [Waon] Fix to ensure point balance updates if user redeems voucher from checkout page modal
• [Waon] Fix cancel CTA text alignment on the voucher redemption modal
• [Waon] Fix for error on checkout screen for non-waon users

Waon changes are only applicable for the Waon loyalty integration.

Feature Release

We added support for status at the shipment-level in the Order Fulfillment API. This enables the abilty to send delivery confirmation emails at the shipment-level.

What's New?

• You can now pass status when creating/updating shipments. View documentation here.
• Shipment-level shipping confirmation email will be sent upon setting a shipment as shipped.
• Shipment-level delivery confirmation email will be sent upon setting a shipment as delivered.
• If status is not sent, legacy logic applies:
  • Shipping confirmation email sent upon shipment creation.
  • Delivery confirmation email sent upon setting a fulfillment as delivered.

Deprecation Notice

The legacy email logic will be deprecated at a later time, after the full adoption of shipment status. For now, it remains in place to allow for a smooth transition.

Cutover Recommendations

• Start using status on new orders. Updating existing shipments may result in duplicate emails.
• When sending status, please ensure that it's sent for all shipments within the order to avoid duplicate emails being sent.