This page documents the expected user experience when RBI guests redeem rewards when they place orders using the POS, part of Customer Journey Scenarios - POS. See also POS - Redeem Offers and POS - Edge Cases.
Note:
Adding a modifier(s) to a reward could have an extra cost
Cost is set by the market and POS vendor
Example: extra patty on a Whopper reward costs $1 more than the base reward price of $0
Contents
1. While signed out
This is not possible. Rewards are only available to guests who have an account and have enrolled in the Loyalty program.
2. Authenticating with the Loyalty Code
In this scenario, guests do not pre-select any rewards and instead start their journey by scanning their Loyalty code at the POS. The guest in this scenario does a second scan to add a reward after the initial identification.
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, chooses to redeem in restaurant |
|
|
|
Guest either scans the reward’s QR 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 finalizes the order and guest pays at POS |
|
|
|
3. Using reward pre-selection
In this scenario, guests pre-select rewards on the RBI app and continue their journey in the POS by scanning the generated code. Then they add more rewards to their basket by choosing those rewards in the app and scanning them, and finally they ask the cashier to remove one of the 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 |
|
|
|
Guest opens a second reward on the RBI app, chooses to redeem in restaurant Note: the flow is exactly the same if the guest pre-selects multiple rewards. |
|
|
|
Guest either scans the reward’s QR 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 |
|
|
Guest requests to remove first reward from order |
|
|
|
Cashier goes 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 finalizes the order and guest pays at POS |
|
|
|
4. Limit one reward per purchase
This scenario only happens if the market has decided to limit redemption of one reward per purchase. This is currently the case in PLK ES and BK ES for example.
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 |
|
|
|
Guest opens a second Reward on the RBI app, chooses to redeem in restaurant |
|
|
|
Guest taps Replace |
|
|
|
Guest either scans the reward’s QR 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 finalizes the order and guest pays at POS |
|
|
|
Next: POS - Edge Cases