Published at: 2026-09-17
Enable product category objectification for existing enterprises
Move product categories in an existing enterprise from legacy backend settings to CRM frontend object data.
Before you start
[!IMPORTANT] - Permissions: You need management permissions for item and product configuration in the enterprise backend. - Prerequisites: Confirm whether products, items, price book details, and related custom settings use the legacy product category field. - Impact: You cannot turn off the switch after enabling it. The system synchronizes data, and related fields and integrations may require updates.
Checks before enabling
- Record the current number, codes, hierarchy, and product relationships of product categories.
- Confirm whether products, items, and price book details use the legacy category field.
- Confirm whether ERP, OpenAPI, or other external systems depend on the legacy field or category API.
- Notify business and technical teams so they can schedule post-switch data validation.
Configuration steps
- Go to Setup > Item/Product Configuration > Product Category Settings.
- Find the Product Category Objectification switch on the Product Category Settings page.
- Read the notes about data migration, related objects, permissions, and integration impact.
- Confirm the impact, and then turn on Product Category Objectification.
- Wait for the system to complete backend data synchronization.
- Open the Product Categories list in the CRM frontend. Check category data and hierarchy.

Validation
- Category counts, codes, and hierarchies match the values before the switch.
- Products, items, and price book details relate to the correct product categories.
- Relevant roles can view or maintain product categories according to their responsibilities.
- Product selection pages in business records display categories and allow users to select products.
How to revert this configuration
You cannot turn off product category objectification after enabling it. Complete impact assessment and migration preparation before enabling the switch.
Key validation term
Confirm that the Validation Object relationship is available after synchronization.