Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Identifying user

    • Identify user with 6 digit Loyalty OTP or scanning Loyalty QR code, select menu item, Offer and/or Reward in the POS and check if correct amount of points is added to user balance

    • Choose items with cashier in the POS, then Pre-select Offer in the app, and scan loyalty user into POS. The items chosen before scanning the loyalty user should be maintained in check

    • Data events: the event Loyalty Transaction Claimed when channel = RESTAURANT and the event Loyalty Transaction Claimed In-store are triggered at this time

      • If Rewards are included in the purchase, the event Reward Redeemed In Store is also fired

      • If Offers are included in the purchase, the event Offer Redeemed In-store is also fired

  • Transaction Validate endpoint

    • User logins with Loyalty into POS, and adds an Offer that has a minimum spend of $5 required with no other menu item selected in the POS. Loyalty API will return error and error message will show in the POS showing that at least $5 needs to be added to check for offer to be redeemed in POS.

      • *Please test all potential rule validation errors and responses described in this document

  • Earning loyalty points

    • Pre-select Offer in the app, login to POS and complete transaction and check if correct amount of points is added to user balance

    • Identify user with 6 digit Loyalty OTP or scanning Loyalty QR code, select offer and/or Menu Item in the POS and check if correct amount of points is added to user balance

    • Adding more than 1 offer per order, completing transaction and checking if correct amount of loyalty points is added to user balance

      • *This test case assumes the market you are testing for allows for more than 1 Offer per order

    • Loyalty Receipt match content added in Sanity and structure specification of vendor

    • Data events: the event Loyalty Transaction Claimed when channel = RESTAURANT and the event Loyalty Transaction Claimed In-store are triggered at this time

      • If Rewards are included in the purchase, the event Reward Redeemed In Store is also fired

      • If Offers are included in the purchase, the event Offer Redeemed In-store is also fired

  • Burning loyalty points

    • Pre-select Reward in the app, login to POS, complete transaction and check if correct amount of points is removed from user balance

    • Identify user with 6 digit Loyalty OTP or scanning Loyalty QR code, select Reward in the POS and check if correct amount of points is removed from user balance

    • Adding more than 1 reward per order, completing transaction and checking if correct amount of loyalty points is removed from user balance

      • *This test case assumes the market you are testing for allows for more than 1 Reward per order

    • Loyalty Receipt match content added in Sanity and structure specification of vendor

    • Data events: the event Loyalty Transaction Claimed when channel = RESTAURANT and the event Loyalty Transaction Claimed In-store are triggered at this time

      • If Rewards are included in the purchase, the event Reward Redeemed In Store is also fired

      • If Offers are included in the purchase, the event Offer Redeemed In-store is also fired

  • Earning and Burning

    • Pre-select Reward and Offer in the app, login to POS, complete transaction and check if correct amount of points is added and removed from final user balance

    • Pre-select Reward in the app, login to POS, add a menu item in the POS, complete transaction, and check if correct amount of points is added and removed from final user balance

    • Identify user with 6 digit Loyalty OTP or scanning Loyalty QR code, add offer and/or reward and/or menu item in the POS and check if correct amount of points is added and removed from final user balance

    • Adding more than 1 reward and more than 1 offer per order, completing transaction and checking if correct amount of loyalty points is added and removed from user balance

      • *This test case assumes the market you are testing for allows for more than 1 Reward and more than 1 Offer to be added per order

    • Loyalty Receipt match content added in Sanity and structure specification of vendor

    • Data events: the event Loyalty Transaction Claimed when channel = RESTAURANT and the event Loyalty Transaction Claimed In-store are triggered at this time

      • If Rewards are included in the purchase, the event Reward Redeemed In Store is also fired

      • If Offers are included in the purchase, the event Offer Redeemed In-store is also fired

  • Void Transaction / Cancelling Loyalty Transaction

    • User pre-selects Offer and/or Reward in the app, logins to the POS, BUT decides not to finish order in the POS → POS vendor sends VOID transaction to Loyalty API and user loyalty points returns to previous balance before transaction was started

    • User pre-selects Offer and/or Reward in the app, logins to the POS, BUT Payment fails at checkout and/or Order fails to inject into POS, THEN POS vendor sends VOID transaction to Loyalty API and user loyalty points returns to previous balance before transaction was started

    • Data events: the event Loyalty Transaction Voided is triggered at this time

...