This page documents the expected user experience when RBI guests are placing orders using the POS. Part of In-Store Loyalty & Offers Customer Journey
Contents
1. Redeem offers
1.1. While signed out
In this scenario, guests do not sign in to the RBI app and they want to use open offers. They scan two different offers in the same order.
Note: this scenario is only available if the market has made open offers available to their guests.
Note: this scenario does not require an integration with the Loyalty API.
Steps | Expected results (POS) | Expected results (RBI app) |
---|---|---|
Guest opens the RBI app without signing in, and selects an offer that is not available when users are signed out (known as a “closed offer”) |
|
|
Guest taps “Use at restaurant” |
|
|
Guest is worried about his privacy and decides not to use this offer. Guest opens an offer that is available when users are signed out (known as an “open offer”) Note: markets that don’t use scanners do not show a QR code in the RBI app, only the alphanumerical code |
|
|
Cashier is prompted to add a loyalty code |
|
|
Guest either scans the (static) offer code, or tells the alphanumerical code to the cashier |
|
|
Guest opens a second offer that is available when users are signed out (known as an “open offer”) |
|
|
Guest either scans the (static) offer code, or tells the alphanumerical code to the cashier |
|
|
Cashier finalizes the order and guest pays at POS |
|
|
1.2. Authenticating with Loyalty Code
In this scenario, guests do not pre-select any offers and instead start their journey by scanning their Loyalty code at the POS. The guest in this scenario does a second scan to add an offer after the initial identification.
Steps | Expected results (POS) | Expected results (RBI app) | Loyalty API usage |
---|---|---|---|
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 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 finalizes the order and guest pays at POS |
|
|
|
| |||
|
1.3. Using offer pre-selection
In this scenario, guests pre-select offers on the RBI app and continue their journey in the POS by scanning the generated code. Then they add more offers to their basket by choosing those offers in the app and scanning them.
Steps | Expected results (POS) | Expected results (RBI app) |
---|---|---|
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 Note: the flow is exactly the same if the guest pre-selects multiple offers. |
|
|
Guest either scans the offer’s QR code, or tells the 6 digit code to the cashier |
|
|
Cashier finalizes the order and guest pays at POS |
|
|
1.4. Limit one offer per purchase
This scenario only happens if the market has decided to limit redemption of one offer per purchase. This is currently the case in BK UK for example.
Steps | Expected results (POS) | Expected results (RBI app) |
---|---|---|
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 taps Replace |
|
|
Guest either scans the offer’s QR code, or tells the 6 digit code to the cashier |
|
|
Cashier finalizes the order and guest pays at POS |
|
|
2. Redeem rewards
2.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.2. Authenticating with 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) |
---|---|---|
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 finalizes the order and guest pays at POS |
|
|
2.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) |
---|---|---|
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 |
|
|
Guest requests to remove first reward from order |
|
|
Cashier finalizes the order and guest pays at POS |
|
|
2.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) |
---|---|---|
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 finalizes the order and guest pays at POS |
|
|
3. Edge cases
3.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) |
---|---|---|
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 |
|
|
3.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) |
---|---|---|
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 attempts to finalize the order but there is a payment failure and order is not completed |
|
|