Contents

...

• 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 Admin Support Tool

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

Overall Plan

This is the overall plan agreed with RBIberia for the loyalty system migration:

...

Phase 0 (pre & cleanup)

During this phase, both user and loyalty data is kept synchronized between SessionM and RBI.

...

• Expected to run for weeks

• Guests will earn but not burn. Change of plans in March: guests will continue to burn, because RBIberia does not want to risk a drop in sales by preventing burn.

• All clients apps (Airtouch, Homeria, Winrest, Tillster) will continue to record loyalty transactions on Session M (no integration to RBI loyalty yet)

• Change of plans in March: all client apps will also send earn transactions to RBI (burn transactions will not be sent). The purpose is to test the RBI system’s performance and ensure that we record loyalty transactions accurately. During this phase, we will compare transactions between RBI and SessionM (although the loyalty points balance is not expected to match).

• Guest and loyalty data (including email addresses, loyalty points balance, loyalty tier and loyalty transactions) will be migrated from SessionM to RBI, as a one time data dump and load before Phase 1 starts

  • ACTION REQUIRED: review the point above. We need to delete loyalty transactions done up to this point as well

• The above will be accomplished by extracting data into CSV files which will be placed in an RBI S3 bucket, and ingested with a script. CSV files will need to be obtained from Homeria (user data) and SessionM (loyalty data including points balance, tier and loyalty transactions).

• At the end of the data migration above, RBI will provide a list of RBI Cognito ID’s and , RBI Loyalty ID’s and email addresses for all users, to be imported by Homeria

• The RBI app is not live (all guests will use the Airtouch app)

• There will be no users created via the RBI apps (only via the Airtouch app or Homeria website)

• No need for rollback

...

• 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)

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