Understand shopper profiles and shopper types

Shopper profiles include a predefined set of properties that store information about shoppers at your store.

Profile properties include common shopper data, such as firstName and phoneNumber, plus data used internally by Oracle Commerce.

A shopper type defines the set of properties that exist for each shopper profile of that type. Shopper types are similar to product types, in that a shopper type is a template for a shopper profile rather than a profile itself. However, there is a currently only one shopper type available. The ID of this shopper type is user.

You cannot create additional shopper types, but you can add custom properties to the user shopper type. For example, if your store carries books, you might want to add a favorite_author property to shopper profiles. You can do this by using the Oracle Commerce Admin API to modify the user shopper type.

The Shopper Types resource in the Admin API includes endpoints for creating and working with custom properties of the user shopper type. The Profiles resource in the Admin API includes endpoints that you can use to set the values of properties of individual shopper profiles, including custom properties that have been added to the user shopper type.

When you add a custom property to the user shopper type, the property is added to all shopper profiles and preview profiles, including any new profiles you create and any profiles that already exist.

Shopper profiles and preview profiles

Oracle Commerce maintains two separate sets of shopper profiles. The main set represents actual shoppers who register on your storefront. You can access and modify existing shopper profiles, and create new shopper profiles, using the Store endpoints on your storefront server.

The other set of profiles is for preview users. These are fictional shoppers that you can use to log into your store on the Admin server to preview changes before they are published. You can access and modify existing preview profiles, and create new preview profiles, using the Store endpoints on your administration server. See Access preview through the APIs for information.