POS - Edge Cases
This page documents edge cases that can happen when RBI guests place orders using the POS, part of Customer Journey Scenarios - POS. See also POS - Redeem Offers and POS - Redeem Rewards.
Contents
1. Switch users
This is a potential fraud use, where a guest authenticates themselves using one loyalty code, and then attempts to redeem rewards using a different loyalty code.
This scenario is the same whether guests are redeeming offers or rewards.
Steps | Expected results (POS) | Expected results (RBI app) | Loyalty API usage (POS) |
---|---|---|---|
Guest opens the Loyalty code page on the RBI app |
|
|
|
Cashier is prompted to add a loyalty code |
|
|
|
Guest either scans the loyalty code, or tells the 6 digit code to the cashier |
|
|
|
Guest opens an reward on the RBI app in a different device, using a different user, and chooses to redeem in restaurant |
|
|
|
Guest (on their second device) either scans the reward’s QR code, or tells the 6 digit code to the cashier |
|
|
|
2. Payment Failure
This can be caused if users do not have enough funds to be able to complete the transaction.
This scenario is the same whether guests are redeeming offers or rewards.
Steps | Expected results (POS) | Expected results (RBI app) | Loyalty API usage (POS) |
---|---|---|---|
Guest opens a reward on the RBI app |
|
|
|
Guest taps “Redeem in Restaurant” |
|
|
|
Cashier is prompted whether the Guest has loyalty, and confirms |
|
|
|
Guest either scans the reward code, or tells the 6 digit code to the cashier |
|
|
|
Cashier adds reward to basket |
Note: If a reward can’t be redeemed because the reward rules are not met, the POS displays a modal to the cashier explaining why the reward can’t be added to cart |
|
|
Cashier attempts to finalize the order but there is a payment failure and order is not completed |
|
|
|
3. Stores without Loyalty
It is possible for some stores in a given Franchisee to now support Loyalty (either temporarily, e.g. during Loyalty rollout, or permanently e.g. due to commercial reasons). In this scenario, affected stores will have loyalty disabled in RBI’s RAM system and the behaviour needs to be different for POS as well.
3.1. Redeem offers
In this scenario, guests pre-select offers on the RBI app and continue their journey in the Kiosk by scanning the generated code. In this scenario, it is recommended that Kiosks show a warning advising guests that they will not earn loyalty points with this transaction.
Steps | Expected results (POS) | Expected results (RBI app) | Loyalty API usage (POS) |
---|---|---|---|
Guest opens an offer on the RBI app |
|
|
|
Guest taps “Use at restaurant” |
|
|
|
Cashier is prompted whether the Guest has loyalty, and confirms |
|
|
|
Guest either scans the offer code, or tells the 6 digit code to the cashier |
|
|
|
Guest opens a second offer on the RBI app, chooses to redeem in restaurant |
|
|
|
Guest either scans the offer’s QR code, or tells the 6 digit code to the cashier |
|
|
|
Cashier adds offer to basket |
|
|
|
Cashier checks out and pays |
|
|
|
3.2. Attempt to redeem rewards
In this scenario, guests pre-select rewards on the RBI app and continue their journey in the Kiosk by scanning the generated code. Because the store does not support Loyalty, rewards cannot be added to the guest’s basket.
Steps | Expected results (POS) | Expected results (RBI app) | Loyalty API usage (POS) |
---|---|---|---|
Guest opens an offer on the RBI app |
|
|
|
Guest taps “Redeem In restaurant” |
|
|
|
Cashier taps on the POS screen and scans the reward’s QR code or inputs the guest’s 6 digit code into POS |
|
|
|
3.3. Attempt to scan Loyalty code
In this scenario, guests attempt to scan their Loyalty code in the kiosk and are presented with a message informing them that loyalty is not available in this store.
Steps | Expected results (POS) | Expected results (RBI app) | Loyalty API usage (POS) |
---|---|---|---|
Guest opens Loyalty Code on the RBI app |
|
| |
Cashier taps on the POS screen and scans the reward’s QR code or inputs the guest’s 6 digit code into POS |
|
|
|