Skip to main content
Go to como.com
Sign in

Customer Portal

Search

Merge Flow For Duplicates Users

Como Sense Knowledge Team

The Merge Flow empowers merchants to seamlessly manage multiple registration and update sources, providing enhanced control over user merging.

1. Common Use Cases

  • Different Source Identifiers: A user is registered from two sources with different unique identifiers, such as a phone number and an email address, resulting in an error when attempting to update their details.

  • Email Subscriber vs. Member: A user is registered as an email subscriber and also as a member with a phone number, resulting in an error when attempting to update their details.

  • Social Login Email Conflicts: A new or returning member attempts to register/sign in using a social account (Google, Apple, or Facebook) whose associated email matches an existing account created under a different phone number. For detailed information, refer to Single Sign-On (SSO) with Google, Apple, and Facebook article ↗.

Example: If a member registers through a Wi-Fi integration using only their email and later registers at the POS with a phone number, the system flags the duplicate identifier when the user updates their details in the customer portal. The system then verifies the user via 2FA on the existing identifier. Once verified, the Merge Flow combines the profiles into a single user, migrates all associated assets, and ensures that any updated member details are transferred to the merged profile, keeping the most recent information intact for a seamless and cohesive experience.

Note: The new Merge Flow is available exclusively in the customer portal with full registration mode enabled.

2. Prerequisites & Requirements

To enable and display the Merge Flow across customer-facing tools, merchants must ensure the following setup criteria are met:

  • Registration Form V2 Required: Merchants must enable the V2 Registration Form setting in HUB 1. The Merge Flow is available exclusively when Registration Form V2 is active across the Customer Portal and Mobile App.

    1. Go to HUB 1.

    2. Navigate to Branding (NEW) > Design (NEW).

    3. Set Registration Version to v2 = Customer Portal.

    4. Click Save and then publish the updated app version.
      Enabling V2 Registration Form.gif
       

  • Verified Identifiers: At least one verified identifier field (Phone Number or Email Address) must be enabled and set up for verification in the Hub.

3. Merge Flow Configuration

Step 1: Enable Merge Duplicates

  1. Go to Business Profile in the Hub.

  2. Click Registration from the side navigation menu.

  3. Click on Advanced Settings.

  4. Enable the Merge Duplicates.

  5. (Optional) Customize the prompt messages (Header, Body, and Note) that will be displayed to users when the Merge Flow is triggered.

  6. Note: Make sure that at least one verified field, either Phone Number or Email, is enabled.

  7. Click Save.

Enable Merge Duplicates.gif
  1. Go to the Customer Portal.

    • When prompted with the Matching Identifier Found modal in the Customer Portal, click YES to merge the profiles.

Matching Identifier Found.png

Step 2: Configure Member Already Exists Event

When the system detects that a member already exists with the same identifier during an updateMember request outside the Customer Portal, it captures this as an event. A trigger is available: Member Already Exists, with the condition: Conflicting Identifier (Conflicting Identifier = when two profiles use the same email or phone number).

  1. Create a new HUB rule:

    • Select the trigger: Member Already Exists.

  2. Define Rule Cases:

    • Handle different identifiers separately (for example, phone number vs. email).

    • Add the Conflicting Identifier condition.

      • For email conflicts, set up an SMS action.

      • For phone number conflicts, set up an email action.

  3. Exclude Customer Portal Source:

    • Add an additional condition: Source Name is not Customer Portal.

      • This ensures conflicts triggered directly from the Customer Portal are ignored, since those cases are already handled natively within the Merge Flow.

  4. Prompt Members to Merge Profiles:

    • Automatically notify members when a conflict is detected.

    • Include the mention MemberUpdateLinkUrl in each communication (SMS and Email). This will send members a secure update form where they can review and update their details.

Configure Member Already Exists Event.gif

4. Social Account Merging Behavior

  • If Merge Duplicates is enabled (in the Hub Advanced Settings): The system prompts the member to verify ownership and merges their social login with their existing profile, migrating all assets and keeping the most recent details intact.

  • If Merge Duplicates is disabled (in the Hub Advanced Settings): The system prevents duplicate creation and informs the member that an account already exists with that email address.

Related articles