Configuring Guest Checkout

If you'd like unauthenticated Community Portal users to process transactions without having to create a new user account, you must enable and configure the Guest Checkout on the related Store. Enabling Guest Checkout allows an unauthenticated Community Portal user to process transactions without creating a new user account. By default it is disabled.

1. Navigate to the Stores tab and Click the name of the Store requiring Guest Checkout configuration.

2. From the Store page, Click the Edit button. The Edit Store modal will open.

3. Scroll Down to the Guest Checkout section and Check the Enable Guest Checkout checkbox.
   
   

   

4. In the New Contact Fieldset(s) CSV field, provide the API Name of the field set created on the Contact. Field sets must be separated by a comma without any additional spacing. The First Name, Last Name, and Email fields are displayed by default. The field set will display in the portal on the Checkout page.

5. From the New Contact Parent Account Rule picklist, Select the name of the Parent Account to use for any Contact records created by guests or new customers. New Contact records are created as the children of the Guest Checkout Account by default.

6. In the Guest Checkout Account field, Select the Parent Account record.

7. From the Contact Match Rule picklist, Select a value to use when matching unauthenticated users to existing Contact records. The Contact Match Rule is set to EMAIL by default (matching on the Salesforce standard Email field). See Using the Contact Match Rule and Contact Match Custom Field section below for more information.

8. Optional: In the Contact Match Custom Field text box, provide the name of any field, including custom, to match unauthenticated customers to existing contact records.

   1. Check the Require Contact Match Custom checkbox to publish the Contact Match Custom Field on the page and allowing the customer to provide the required information. See Using the Contact Match Rule and Contact March Custom Field sections below for more information.

9. Click Save.

Additional Information on New, Guest, and Duplicate Profiles:

1. The system creates a guest user profile in the Community Portal when:

   1. The guest information provided does not match any existing users in the Community Portal.

   2. The guest information provided matches multiple contacts, but none of the users were configured for the eStore. In this instance, the system records the duplicate IDs in a custom field on the Guest Checkout Account Contact record.

2. If the Enable Guest Checkout field is checked, the system links the record to the Sales Order and will not create a Guest Checkout Account Contact record at the eStore when:

   1. The guest information matches a user profile in the Community Portal. The sales order links to the pre-existing user profile in the Community Portal.

   2. The guest information matches multiple user profiles, one of which is associated with the Guest Checkout Account.

Using the Contact Match Rule and Contact Match Custom Field:

To determine whether to create a new user profile at Checkout, the system will use the Contact Match Rule and the Contact Match Custom Field to match both authenticated and unauthenticated users to existing users in the Community Portal.

The search and comparison process varies according to the Contact Match Rule. When used in conjunction with the Contact Match Custom Field, staff users can use a search tailored to the system settings. By default, the Contact Match Custom Field has no value. Acceptable values for the Contact Match Custom Field are the name of any field, including custom, found on the user page in the Community Portal. If there is a field in Contact Match Custom Field that is also in the New Contact Field Set(s) it is displayed twice on the Checkout page.

Additionally, in order to be considered matching, the value entered into the Contact Match Custom Field must match the value in the existing profile, e.g., abbreviations in street addresses and formatting of phone numbers. The system determines the following addresses as unique: South 8th Street, S. 8th St., and South 8 St. If Phone Number is used as a Contact Match Custom Field, the system determines the following phone numbers as distinct and unique (703)111-1111, 703-111-1111, 7031111111.

The system uses the given email address to match the email address of an existing user in the Community Portal by default. A new Contact record is created if any of the given fields do not match to fields in an existing Contact record in the Community Portal. The picklist values for the Contact Match Rule are as follows:

• EMAIL- Default value; will only look to the given email without matching to any existing data.

• AND - The system uses the Contact Match Custom Field and the Contact Match Rule, which references the given email, to match to an existing user in the Community Portal.

• OR - The system uses either the Contact Match Custom Field or the Contact Match Rule, which references the given email, to match to an existing user in the Community Portal.

• CUSTOM - The system uses the Contact Match Custom Field to match to an existing user in the Community Portal.

• NONE - The system does not use any contact matching rules. Duplicate contacts will be made in the Guest Checkout Account in the Community Portal.

Validation Rules for Contact Match Fields:

• A validation error is received if the Require Contact Match Custom Field is checked and the Contact Match Custom Field is left blank.

• A validation error is received if the Contact Match Rule is AND, CUSTOM, OR and the Contact Match Custom Field is left blank.