Contents
| Table of Contents |
|---|
...
During this phase, both user and loyalty data is kept synchronized between SessionM and RBI.
Change of plans in Phase: loyalty data will not be kept synchronized as guests will continue to burn on Session M, but in RBI we will only record earning transactions.
Plan
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, 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
...