Versions Compared

Old Version 7

changes.mady.by.user Lopes da Costa, Valentina

Saved on

compared with

New Version 8

changes.mady.by.user Lopes da Costa, Valentina

Saved on

Key

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

...

Steps

Expected Results

Data Events

User inputs 6 digit Loyalty code or scans Loyalty QR code

  • User sees success modal in the app

The event Loyalty Transaction Created is triggered at this time

User pre-selects a reward and inputs 6 digit Loyalty code or scans Loyalty QR code

  • User sees success modal in the app

  • User sees rewards cost temporarily removed from user balance

The event Loyalty Transaction Created is triggered at this time

User pre-selects an offer and inputs 6 digit Loyalty code or scans Loyalty QR code

  • User sees success modal in the app

  • User loyalty point balance does not change

The event Loyalty Transaction Created is triggered at this time

...

Steps

Expected Results

Data Events

User inputs 6 digit Loyalty code or scans Loyalty QR code

User sees success modal in the app

The event Loyalty Transaction Created is triggered at this time

User that has no other items in the basket attempts to add an Offer that has a minimum spend of $5 required. Loyalty API will return error and error message will show in the Kiosk showing that at least $5 needs to be added to check for offer to be redeemed in Kiosk.

  • Loyalty API will return error and error message will show in the Kiosk showing that at least $5 needs to be added to check for offer to be redeemed in Kiosk.

  • Full list of rules to be tested here: Loyalty API v1 - Error Responses

N / A

1.3. Earning loyalty points

Steps

Expected Results

Data Events

Pre-select offer in the app, scan loyalty code at Kiosk/POS and complete transaction with Offerthe order with this offer.

  • Correct amount of loyalty points are added to user’s balance.

  • Confirm the offer used disappears from your app’s offer list

Info

Note: Unless the user can redeem the offer more than once, specified with offer Limit ruleset in Sanity

these events are fired:

  • Loyalty Transaction Claimed when channel = RESTAURANT

  • Loyalty Transaction Claimed In-store

  • Offer Redeemed In-store if offers are included in the order

Input 6 digit Loyalty code or scan QR code, then select offer and/or menu item in the Kiosk/POS

  • Correct amount of loyalty points are added to user’s balance.

  • Confirm the offer used disappears from your app’s offer list

Info

Note: Unless the user can redeem the offer more than once, specified with offer Limit ruleset in Sanity

these events are fired:

  • Loyalty Transaction Claimed when channel = RESTAURANT

  • Loyalty Transaction Claimed In-store

  • Offer Redeemed In-store if offers are included in the order

Pre-select offer in the app and input 6 digit Loyalty code at Kiosk/POS. Then select a second offer in the Kiosk/POS.

  • Correct amount of loyalty points are added to user’s balance with 2 offers added to order.

  • Confirm both offers used disappear from your app’s offer list

Info

Note: Unless the user can redeem the offer more than once, specified with offer Limit ruleset in Sanity

these events are fired:

  • Loyalty Transaction Claimed when channel = RESTAURANT

  • Loyalty Transaction Claimed In-store

  • Offer Redeemed In-store is triggered twice.

...

Steps

Expected Results

Data Events

Pre-select reward and an offer in the app, and scan loyalty code at Kiosk/POS. Complete order with offer and reward.

  • Correct amount of loyalty points are added and removed from user’s loyalty point balance.

  • Confirm the offer used disappears from your app’s offer list

Info

Note: Unless the user can redeem the offer more than once, specified with offer Limit ruleset in Sanity

these events are fired:

  • Loyalty Transaction Claimed when channel = RESTAURANT

  • Loyalty Transaction Claimed In-store

  • Reward Redeemed In-store

  • Offer Redeemed In-store

Pre-select reward in the app and input 6 digit Loyalty code or scan QR code. Then, add a menu item in the Kiosk/POS, and complete the transaction.

  • Correct amount of loyalty points are added and removed from user’s loyalty point balance.

  • Loyalty Receipt match content added in Sanity:/wiki/spaces/HELP/pages/5019500623

these events are fired:

  • Loyalty Transaction Claimed when channel = RESTAURANT

  • Loyalty Transaction Claimed In-store

  • Reward Redeemed In-store

  • Offer Redeemed In-store

Input 6 digit loyalty code or scan QR code. Then, add a menu item, an offer, and a reward in the Kiosk/POS, and complete the transaction.

  • Correct amount of loyalty points are added and removed from user’s loyalty point balance.

  • Confirm the offer used disappears from your app’s offer list

Info

Note: Unless the user can redeem the offer more than once, specified with offer Limit ruleset in Sanity

these events are fired:

  • Loyalty Transaction Claimed when channel = RESTAURANT

  • Loyalty Transaction Claimed In-store

  • Reward Redeemed In-store

  • Offer Redeemed In-store

Input 6 digit loyalty code or scan QR code. Then, add a menu item, 2 (or more) offers, and 2 (or more) rewards in the Kiosk/POS, and complete the transaction.

  • Correct amount of loyalty points are added and removed from user’s loyalty point balance.

  • Confirm both offers used disappear from your app’s offer list

Info

Note: Unless the user can redeem the offer more than once, specified with offer Limit ruleset in Sanity

these events are fired:

  • Loyalty Transaction Claimed when channel = RESTAURANT

  • Loyalty Transaction Claimed In-store

  • Reward Redeemed In-store is triggered twice assuming there are 2 rewards in the order.

  • Offer Redeemed In-store is triggered twice assuming there are 2 offers in the order.

...

Steps

Expected Results

Data Events

Pre-select offer and/or reward in the app, and scan loyalty code at Kiosk/POS. User decides not to finish order in the Kiosk.

  • Kiosk sessions times out and session closes.

  • Loyalty points balance of user returns to what it was before the user began the order.

this event is fired:

  • Loyalty Transaction Voided

Pre-select offer and/or reward in the app, and scan loyalty code at Kiosk/POS. Payment fails at checkout and/or order fails to inject in the POS.

  • Error is shown to guest or operator

  • Loyalty points balance of user returns to what it was before the user began the order.

this event is fired:

  • Loyalty Transaction Voided

Pre-select offer and/or reward in the app, and scan loyalty code at Kiosk/POS but the reward or offer fails to be added to the kiosk and guest decides to scan a new loyalty code.

  • User pre-selects Offer and/or Reward in the app, logins to the Kiosk, BUT the Reward and/or Offer fails to be added to Kiosk → IF user decides to re-scan Loyalty OTP code, THEN Kiosk vendor sends VOID transaction to Loyalty API and user loyalty points returns to previous balance before user begins a new transaction Loyalty points balance of user returns to what it was before the user began the order.

  • New scan triggers success confirmation modal in the app

these events are fired:

  • Loyalty Transaction Voided

  • Loyalty Transaction Created

2. Kiosk & POS

2.1.

...

User logins in the Kiosk with or without pre-selected items, selects Pay@Counter, and completes purchase in the counter/POS successfully

...

User loyalty points with new order are updated before user pays for order in the counter/POS

...

Once user pays for order in the counter/POS successfully, then user continues with updated loyalty point balance

...

Pay at counter test cases

Steps

Expected Results

Data Events

User scans loyalty code at the Kiosk, creates a basket, selects Pay at Counter option and completes order.

  • points balance of the guest are temporarily deducted with rewards points cost.

  • guest does not earn any loyalty points at this moment

this event is fired:

  • Loyalty Transaction Created

User then approaches cashier and pays with cash the order he placed at the kiosk.

  • user earns points from the order and points balance are updated permanently.

these events are fired:

  • Loyalty Transaction Claimed when channel = RESTAURANT

...

  • Loyalty Transaction Claimed In-store

...

  • 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

User logins in the Kiosk with or without pre-selected items, selects Pay@Counter, and NEVER completes purchase in the counter/POS successfully

...

User loyalty points with new order are updated before user pays for order in the counter/POS

...

Another user logs into the kiosk, scans loyalty code, creates a basket, selects Pay at Counter option BUT never goes to pay order at the counter.

  • points balance of the guest are temporarily deducted with rewards points cost.

  • After X minutes of time where this transaction was not closed

...

  • at the counter/POS,

...

Data events: the event Loyalty Transaction Voided and Loyalty Transaction Deleted are triggered at this time

Test Cases for In-Store Offers

  •  Open RBI app
  •  Go to your offer list (/rewards/offers)
  •  Click on the Offer you would like to test in-store
  •  Click on the button to Use at Restaurant
  •  Scan the in-store Offer QR Code or input the offer code in the respective POS/Kiosk vendor
  •  Check correct offer shows in POS/Kiosk screen
  •  Complete the transaction
  •  Confirm your Loyalty points balance increase by the correct amount
  •  Confirm your offer disappears from your offer list (*UNLESS specified otherwise with Sanity rulesets)
  •  Confirm the Offer Redeem In-Store event is fired in Amplitude for your user and redeemed offer

  • transaction is cancelled (VOIDED) and points balance return to what it was before order was initiated

these events are fired:

  • Loyalty Transaction Voided

  • Loyalty Transaction Deleted

Instructions for Integration Partners (Kiosk and POS)

...