...

• Phases 0 and 1 - doesn’t matter because RBI is not the master of loyalty

• Phase 2:

  • Import loyalty data including earn and burn transactions for the last two years (no points expiration data will be imported)

  • Run the loyalty points expiration on our side

  • Update the loyalty points balance to match SessionM

  • From this point onward, rely on the RBI loyalty points expiration process

...

• We will disable downgrades from Superking to King during the migration, to avoid guest frustration

  • We propose during During the migration (Phase 1-3) to we will change the requirements for users to move from Loyalty Tier 2 to Loyalty Tier 1 in Sanity to 6 months instead of 1 month as it is today. In this way, no users would be downgraded Tiers during the migration. In this way, no Development work would be needed.

Cancellations and refunds

• There are no gaps with cancellations and refunds initiated by the POS, since they will use both the RBI and

  • .

• User will continue being able to go from Tier 1 (King) to Tier 2 (Superking) by earning 15000 points in 6 months on a rolling basis.

  • Session M will send this information to RBI

Cancellations and refunds

• There are no gaps with cancellations and refunds initiated by the POS, since they will use both the RBI and SessionM API’s

• For cancellations and refunds currently handled in SessionM, during the transition period support staff will continue to use SessionM and, in addition, will repeat the operation on the RBI Support Tool

• This will guarantee that cancellations and refunds result in the same loyalty points balance in both RBI and SessionM

...

• During this phase, RBI will become the master for loyalty data, and SessionM will be used as a backup in case we need to roll back.

• When Phase 2 starts, we need to import the last two years of loyalty transactions from SessionM, to make history available to guests (on the Airtouch app now, and when they later switch to the RBI app). The import process will be as follows:

  • All loyalty (earn) transactions made to date will be voided. We need to void instead of deleting, because data in Snowflake cannot be deleted.

  • An extract will be taken from SessionM, covering the last two years of transactions and the current loyalty points balance. Each transaction record needs to include the date and time when the transaction took place, loyalty points, whether earn or burn, channel, if the burn is due to spending rewards of points having expired.

  • The extract will be loaded into RBI, after which the expiration points feature will be switched on. This will expire RBI will migrate users without loyalty point expiration balance. From this point onward, rely on the RBI loyalty points expiration process. RBI will expire all loyalty points that were accrued over 6 months ago, rounded to the nearest month end.

  • At this point the RBI loyalty points balance will not match SessionM’s because it doesn’t have the full transaction history. So we will calculate the loyalty points balance on RBI based on the total of transactions and compare with the current SessionM balance for each user.

  • Finally, we will record a single remediation transaction per user with the difference, to make the loyalty points balance in RBI match SessionM.

• Airtouch app and Homeria website will need to call the Get Loyalty User endpoint, using the RBI Loyalty User ID as input. Get Loyalty User will return RBI loyalty points balance, tiers and guest email.

• Rewards will be configured in Sanity.

• Configure the generic PLU for rewards

• RBI rewards become active on the Airtouch app and the Homeria website, and guests are able to redeem them when making collection, delivery or in-store orders (requires the app to retrieve rewards from RBI)

• Reward redemption should use the RBI Loyalty API version that was customized for RBIberia: RBI Iberia | Loyalty POS/Kiosk Integration

...

Open questions

Point expiration

...

Point expiration will be set to 180 days and will expire at the end of each month (confirmed by @Raúl Moreno)

We will only migrate user’s point expiration based on their active loyalty points. Past loyalty points expiration from previous point balance will not be migrated.

...

After migration, RBI point expiration dates will be different from SessionM since SessionM will expire points daily and RBI will expire points at the end of the month (confirmed by @Raúl Moreno)

Confirm how SessionM will send us the point expiration date

...

Loyalty Tiers

Users will be able to upgrade tiers. Can you confirm how many crowns users need to earn and in how much time for them to become Tier 2?

...

Users that are in Tier 2 will continue in Tier 2 for the next 6 months once the migration starts  (confirmed by @Raúl Moreno)

...

Loyalty Transactions

• Two years worth of loyalty transactions will be migrated to the RBI app at the end of Phase 1 (confirmed by @Raúl Moreno)

...

Cancellations

• Vendors will send us cancellations using the VOID endpoint (confirmed by @Raúl Moreno)

• Customer Support team will also have access to the support tool and will cancel orders in RBI support tool as well as Session M support tool only in Phase 2 and onwards (confirmed by @Raúl Moreno)

When to send Identify and Update Transactions

Raul raised potential fraud implications for order to be identified and claimed only when the order is picked up/ delivered for mobile ordering

...

Potential solutions: Homeria creates 2 orders - (1) to claim Rewards only and deduct points right after payment is complete and (2) to earn points after order is delivered or picked up

...

Implications: If the above solution is chosen, then to cancel orders Homeria will need to VOID both order 1 and order 2 to void complete order

...

Next actions

• Phase 0:

  • Confirm that we can retrieve loyalty data from SessionM to be ingested by RBI (Miguel-Romero, Almudena)

• Phase 1:

  • Confirm that the existing user sync endpoint can be modified to return the RBI Loyalty ID in addition to the Cognito ID (Miguel-Romero, Almudena)

  • Confirm that Get User Details returns the loyalty points balance and tier (Silva, Carlos)

  • Share testing environment details with all vendors (Lopes da Costa, Valentina)

  • Provide example payloads for endpoints not documented in the standard Loyalty API documentation (Francisco Paglia)

• Phase 2:

  Define how rewards will be handled (Silva, Carlos)

  Data Dump at the End of Phase 1

  • Pending on understanding the structure and size of the data dump to be sent from SessionM to RBI at the end of Phase 1 for script to be worked on

Change Log

• In March 2024 there were two changes of plans:

  • To continue to burn rewards throughout Phase 0, to minimise impact on sales. This means that burn transactions will be sent to RBI, and the loyalty points balance will not match between RBI and SessionM

  • To change the Loyalty API interface allowing authentication with an email address, to reduce the number of calls made by POS/Kiosks