Customer Profile Enhancements

Updated
  • Updated on Jan 14, 2026
  • Published on Mar 27, 2025
  • 4 minute(s) read
Prev Next

Prerequisites

NewStore customer profile enhancements provide flexibility in managing and customizing customer information, allowing retailers to tailor customer profiles to their unique business needs. These enhancements enable associates to capture, view, and edit customer details more effectively, supporting a personalized customer experience.

Accessing customer profile customizations

To enable these customizations:

  1. Go to Settings > Associate App > Customizations as an Admin user.

  2. Click Get started or Add if there are existing customizations.

From this screen, you can choose between two customer profile customization options:

  • Customer Profile (Create/Edit): Where associates add or modify customer information.

  • Customer Profile (Overview): Where associates preview existing customer information.

Types of customization

The NewStore platform supports two types of customization for customer profiles:

  • Widgets: Used to add, edit, or display customer extended attributes on the mobile screen.

  • Webviews: Enables integration with external systems like wishlists, loyalty programs, or service tracking.

Associate App Customization Screen in NOM

Widgets

Widgets facilitate data input and display for associates. Each widget uses a Data Key to fetch and store values from the customer extended attributes. The Data Key should be unique.

There are 5 types of Widgets:

Widget

Customer Profile (Create/Edit)

Customer Profile (Overview) →all fields are not editable

Typical Use case

Text box

Displays a text box for the associate to ender free form text.

Displays a text box with the data populated form the customer extended attributes. If the data is not populated, the text box will be empty.

  • Favorite Color

  • Favorite Size

Single Select

Displays a list of configured values for the associate to edit. It will a show radio button if there are 4 or less than four options configured in the single select option. If there are more than 4 options, a drop-down menu is displayed in the UI.

Displays a drop-down menu with the value pre-populated and disabled. The associate will not be able to edit the selection from the screen.

  • Birth month

  • Customer Type

Toggle

In the toggle option, the platform can support configuring an URL typically used for privacy policy and T&C to be displayed to the customer.

Displays a toggle with on/off options disabled. The associate will not be able to edit the selection from the screen.

  • Marketing Opt in/out

Information

(non editable in both screens)

Displays an information section which cannot be edited from the Associate App screen. To populate the data, it needs to pull the information from the integration or API.

Displays an information section which cannot be edited from the Associate app screen.

  • Notes to the associate relating to the customer, for example if the customer is a Social Media Influencer

Date picker

Displays a date picker for the associate to chose. The app can support multiple formats like

  • full

  • year

  • month

  • day

  • month-day

  • year-month

Displays the selected date format as is in a non-editable format.

  • Birth Month

  • Birth date (with out year)

  • Membership Expiry date (only in the Customer preview screen)

While configuring the widget, the platform supports the attributes to be re-ordered. To order attributes, drag and re-arrange the attributes in the preview screen on the right side.

Webviews

Webviews provide a versatile method to integrate external systems into the customer profile. Common use cases include:

  • Loyalty sign-up

  • Wishlist integration

  • Service tracking

  • Gift registry

Optional authentication can be configured for secure data access. 

The user can configure a webview in both the Customer Profile (Create/Edit) and the Customer Profile (Overview) screen. The NewStore platform also supports an optional authentication step that can be enabled while configuring the webview. typical use case include, Loyalty Sign up, wishlist, product recommendation, service tracking, gift registry.

Configuring a Webview with External Authentication

This section outlines the steps required to configure a webview in the NewStore platform that uses external authentication to control access and data rendering.

Step 1: Define the Webview in NOM

In the Omnichannel Manager (NOM) configuration, define the webview and assign a value to the identity_provider field. This value will be used as the identifier for authentication mapping in later steps.

Step 2: Add External Integration in AA Configuration

In the Associate App (AA) configuration, add an entry under external_integration > post_login_callback_urls using the same identity_provider name defined in Step 1. Set the url to the endpoint of the external identity provider. This URL will be used for token exchange.

Step 3: API Key Authentication Flow

The specified endpoint receives a NewStore-issued token from the platform. After validating the token, the identity provider responds with an API key/token, which the Associate App caches. This key is passed securely to the corresponding webview using the identity_provider name.

Step 4: Webview Token Verification

The webview retrieves the cached API key and verifies it before loading and displaying any content. This mechanism ensures that only authenticated webviews can access external data.

Note: Each webview can use a unique authentication endpoint. If multiple webviews share the same endpoint, assign the same identity_provider name across all configurations.

Special Case: Loyalty Webview

Important

For loyalty-related webviews, the identity_provider configuration is managed directly in the AA config and is not set in NOM.

Tutorial