Page Comparison

Guest opens an offer on the RBI app

• N/A

• Offer page is displayed:

• No action

Guest taps “Use at restaurant”

• N/A

• Offer is added to the guest’s pre-selection

• A unique offer code is generated

• No action

Guest taps on the Kiosk screen to start a new order

• User clicks on Offers tab and prepares to scan offer

Cashier is prompted whether the Guest has loyalty, and confirms

• Cashier asked if guest is a loyalty member and clicks on “Ok”

Image Added

• No action

• No action

Guest either scans the offer’s QR offer code, or inputs tells the 6 digit code into Kiosk

• User sees pop up in Kiosk letting user know they will not gain/burn any loyalty points with this order

• Offer(s) are shown on the Kiosk and guest has an option to customize

  Image Removed

• Modal is shown to guest confirming that the offer has been added to cart

Image Removed

to the cashier

• Either by scanning or entering the code, POS confirms successful identification (since the offer code also identifies the Loyalty user):

Image Added

• Offer is added to POS cart

  Image Added

• Guest receives a successful confirmation modal

Image Added

•  Offer pre-selection is cleared

• Call the Identify endpoint, which will return the Loyalty User ID, a list of offer(s) pre-selected, loyalty points balance and a transaction ID

• The Loyalty API will know this store does not have Loyalty enabled

Guest customizes offers at will and adds to basket

• These offer(s) are incrementally added to the cart and do not replace any of the existing cart items

  Image Removed

• No action

• Call the Transaction Validate endpoint to verify that the current basket selection is valid

• Note that the call above may return errors. Please refer to Loyalty API - Error List for details.

• The Validate call will return an error if any Rewards are added to cart

Guest opens a second offer on the RBI app, chooses to redeem in restaurant

• No action

• Only the second offer is added to the guest’s pre-selection

  Image Removed

Image Added

• A unique offer code is generated

• No action

Guest either scans the offer’s QR code, or inputs tells the 6 digit code into Kiosk

• Offer(s) are shown on the Kiosk and guest has an option to customize

Image Removed

to the cashier

• Either by scanning or entering the code, POS confirms successful identification:

Image Added

• These offer(s) are incrementally added to the cart and do not replace any of the existing cart items

• Modal is shown to guest confirming that the offer has been added to cart

Image Removed

Image Added

• Loyalty points balance is not updated, since the guest is scanning an offer

• Offer pre-selection is cleared

• Keep track of the current basket contents including offers

• Void the previous transaction

• Call the Identify endpoint again, which will create a new transaction ID and selected offers

• Update the basket with the offers returned

Guest customizes offers at will and adds to basket

• These offer(s) are incrementally added to the cart and do not replace any of the existing cart items

Image Removed

• No action

• Call the Transaction Validate endpoint to verify that the current basket selection is valid

• Note that the call above may return errors. Please refer to Loyalty API - Error List for details.

Cashier checks out and pays

• Order number shows up on the POS screen

• Receipt is printedPOS prints receipt

• Guest does NOT sees updated points balance

• Points do not change from before and after the order was placed

• Call the Transaction Update endpoint with a status of CLAIMED to complete the order

• After this call it is not possible to modify the loyalty transaction anymore

• Once this transaction is CLAIMED no Loyalty points are updated in the user’s balance