2nd March 2026

List of Features

No.	Feature	Description
1.	Supplier Domain Management Integration	The platform now enables distributors to manage supplier data as a dedicated domain within the distributor catalog, with its own properties, header values, digital assets, and relationships. Domains can now be classified using a configurable Domain Class (e.g., Supplier), allowing the system to recognize and manage supplier-specific domains more effectively. When a domain is designated as a Supplier domain: Supplier records are automatically created or linked in the Supplier Management area. Supplier domain data can be added or updated via domain import functionality. SKUs marked as PIM Ready are automatically associated with the relevant supplier domain in the staging catalog.
2.	Introducing Conditional Schema Constraints	The platform now supports conditional attribute requirements in both PCC and the Supplier Portal. Users can configure attributes to become mandatory based on the value or population of another attribute. Different values of a controlling attribute can trigger different sets of required attributes during save or submission, enabling more dynamic and context-driven data validation. Where this is available in the UI: PCC: Configurable within the Add Schema screen. Supplier Portal: Available during Category Template creation in the Field Formatting section. This enhancement improves data accuracy and ensures required information is captured based on business-specific workflows.
3.	Dependent LOV Schema Constraint (Dynamic LOV Attribution)	The platform now supports dynamic, dependency-based List of Values (LOV) validation. Attribute LOV options can be configured to dynamically change based on the value selected in another attribute within the same SKU. This enhancement allows users to define hierarchical or dependency driven LOV relationships (e.g., Country → State → City), ensuring that only relevant and valid options are available for selection. For example: If Country = USA, the State attribute will display only USA-configured states. If no dependency is configured for a selected value, standard LOV behaviour applies. The LOV selection tool (magic wand) will dynamically display only the applicable values based on the defined dependency rules. This enhancement improves data accuracy by enforcing context-sensitive LOV validation and preventing invalid attribute combinations.
4.	Domain Class Support in Master Domain Export	There was no clear distinction in the Master Domain Export file to identify whether a domain was related to core PCC functionality or to Supplier-specific data. This lack of classification created ambiguity when managing and integrating domain data. The Master Domain Export file now includes a new column, Domain Class, to clearly identify the type of domain. This column identifies whether a domain is classified as: Unspecified – Standard PCC-related domains Supplier – Supplier-specific domains This enhancement improves domain classification and provides clearer visibility when exporting domain data. Note: Each catalog can have only one Supplier domain defined.
5.	Mandatory Numeric Data Type Validation in Supplier Portal	All numeric data type fields in Supplier Portal templates now automatically enforce data type validation. This constraint is system-enabled and cannot be disabled by users. Validation logic has been strengthened to ensure only properly formatted integer and decimal values are accepted. This enhancement ensures higher data accuracy, prevents invalid numeric inputs, and improves overall data integrity during supplier onboarding and product updates.
6.	Pattern-Based Validation and Improved Schema Constraint Controls	The platform now supports pattern-based validation within schema constraints in both core PCC and the Supplier Portal. Users can configure custom validation rules to enforce precise input formats (e.g., email formats, structured IDs, or specific code patterns). This enhancement also strengthens overall schema constraint consistency and alignment across LOV, UOM, and data type enforcement. As part of this update: • A new Pattern constraint type has been introduced in schema configuration. • Schema configuration logic has been enhanced to ensure enabled constraints are properly supported by their required configuration (e.g., LOV and UOM enforcement consistency).

List of Bug Fixes

No.	Module	Bug Fixes
1.	SP	Resolved an issue where the Field Name column displayed the mapped attribute name instead of the original field name used to build the template.
2.	PCC	Resolved timeout issues in the Public Domain API when processing large data submissions, improving performance and reliability for high-volume requests.
3.	SP	Resolved an issue where certain attributes did not load in the Supplier Portal Add SKU popup due to schema constraint configuration limitations. Attributes now display correctly during template creation and SKU onboarding.