...
Your guests can utilize a standard login & create account flow using an email and password. The guest will be required to remember these credentials every season unless they decide to switch to other methods such as passwordless, which will be available in an upcoming release.
For any existing customer in RTP that signs in and has any missing information that is required upon sign up, the guest will be prompted with ‘complete your profile’ and be asked to input any missing data. For example, if a customer/user exists in RTP with all fields except phone number, the guest will be shown only phone number field and be required to complete prior to signing in.
Note. If a new guest signs up and doesn’t complete their profile here, RTP will be populated with a first and last name of the guests email address. Due to RTP requirements and how auth0 works in conjunction, we must populate those fields so we can associated the auth0 account with an RTP customer ID. Once the user completes the process of signing up, those fields will be replaced by their values they enter for first and last name.
Customer Matching
Guests that sign in create a user account. The user account is mapped to a customer in the point of sale (POS). It's vital to limit duplicate customer creation in the POS when possible. For that reason, Aspenware created a customer matching feature. When a guest creates a new user account, they will be prompted to complete their profile, which creates a customer record in the POS. When the provided information matches an existing customer in the POS, we send them through a matching process in order to prevent creation of a duplicate customer. Aspenware will endeavor to prevent a duplicate and will attempt to match with the following information (must match to all):
...