Customer Attributes

Copy

• Copy for LLM

  Copy page as Markdown for LLMs
• View as Markdown

  Open this page as Markdown
• Open in ChatGPT

  Get insights from ChatGPT
• Open in Claude

  Get insights from Claude

Customer Attributes in Fynd Commerce allow you to define custom fields that help collect, display, and manage additional information about your customers. These attributes can be used during registration, for segmentation, personalization, or display on specific ordering channels like Storefront, Store OS, or Kiosk.

This feature gives you complete flexibility to capture relevant customer details specific to your business needs—beyond the standard name, email, and phone number.

When to Use Customer Attributes

• To collect extra information at the time of registration (e.g., gender, preferences, membership ID)
• To personalize content, offers, or communication
• To group or segment customers based on specific traits
• To make attributes visible on selected ordering channels (like Storefront or POS)

Creating a Customer Attribute

Click Create to open the attribute form and fill out the following fields:

Basic Details

• Attribute Name: Display name of the attribute (e.g., Race, Membership Level)

• Slug: A system-friendly identifier (auto-generated or manually entered)

• Attribute Type: Choose from:

  • Text
  • Number
  • Dropdown
  • Boolean (Yes/No)
  • Date
  • Date and Time
  • File
  • Rich Text
  • Location
  • Team Member

• Icon: (Optional) Upload an icon for the attribute

• Description: Explain what the attribute is used for

Channel Visibility

You can select where this attribute should appear for the customer. Supported channels include:

• Storefront
• Store OS
• Kiosk

This setting helps you control where customers see and interact with these fields.

Advanced Settings

The following options help you customize behavior further:

• Accept Multiple Values: Allows entry of more than one value (e.g., if a user has multiple interests)

• Enable Encryption: Encrypts data for enhanced security

• Customer Editable: Allows customers to edit this attribute in their profile

• Collect During Registration:

  • Mandatory: Attribute must be filled to register
  • Optional: Customer may choose to skip

• PII Masking: Controls how the data is masked in your dashboard for privacy

  • Masked with visible first/last character
  • Masked with only last 4 characters visible

Managing Customer Attributes

All newly created attributes will appear in the Attributes list, where you can easily manage them. You can:

• Edit or delete any attribute using the pencil or bin icons in the Actions column.
• View how each attribute is used across customers and channels.

Once added, customer attributes are displayed in a structured table within the Attributes section, giving you a central place to review, update, and maintain all your custom fields.

Table View Details

Each row in the table displays:

• Name: The attribute name and slug (system identifier).
• Type: Attribute type (e.g., Text, Number, Dropdown) and configuration (e.g., Multivalue).
• Customer Editable: Whether the attribute is editable by the customer.
• Encrypted: Indicates if the data is encrypted for security.
• Modified By: Displays who last edited the attribute (if applicable).
• Actions: Icons to edit or delete the attribute.

Actions You Can Perform

• Edit Attribute : Click the pencil icon under the Actions column to modify an existing attribute. You can update the name, type, description, visibility, and advanced settings.

• Delete Attribute : You can click the trash icon to remove an attribute in the Actions column.

However, deletion is subject to the following rules:

• An attribute cannot be deleted if it is:
  • Being used in one or more user groups, or
  • Has values recorded in any customer profile.

In such cases, a warning message appears:

“This attribute is currently in use and cannot be deleted. It is either part of one or more user groups or has values recorded for one or more customers in their profiles. Please remove all dependencies before deleting this attribute.”

• If the attribute is not in use, you’ll be asked to confirm deletion:

“Once you delete the attribute it cannot be retrieved and the action cannot be undone.”

Make sure to review any dependencies before proceeding with deletion.

• Pagination Use the “Rows per page” dropdown at the bottom to view more attributes if you have several configured.

Best Practices

• Use clear, customer-friendly attribute names
• Use dropdowns when possible to ensure consistent data
• Use PII masking for sensitive data
• Limit mandatory attributes to avoid drop-offs during registration