05th August 2026

No.

Feature

Description

1.

Ability to map Passthrough custom attributes on AI Mapping Finalization screen in SOP

Introducing Passthrough attribute mapping, enabling distributor to map the fields in the custom import template to a Passthrough attribute instead of a predefined template field. During AI Mapping Finalization, distributors can review fields that are not mappable to any predefined template field, mark a column as passthrough and choose a Target Attribute by selecting an existing passthrough custom attribute, creating a new passthrough custom attribute, or using the input file field header as the Target Attribute name. Based on the selected option, the system either maps the value to the selected attribute or automatically creates a new attribute using the column header name.

The AI Mapping Finalization screen in the SKU Journey currently supports mapping only to predefined template fields. Custom attributes must be pre-configured before they can be imported or managed.

With this enhancement, distributors can efficiently manage custom attribute mapping during AI Mapping Finalization, streamlining custom attribute onboarding while improving the visibility and management of imported passthrough attribute data in SOP.

2.

Support for Packaging data constructs in AI Mapping Finalization screen in SOP

AI Mapping Finalization screen in SOP now supports mapping a field in the incoming file to a packaging data construct. This feature allows users to search and map Package Units and map package attributes, such as UPC, GTIN, and other package-related information, to the selected Package Unit.

User could only map incoming data to Template Fields, and there was no option to map data to Packaging Constructs.

With this enhancement, users can choose the packaging data construct to use as the target mapping. AI Mapping Finalization processes the selected mapping during the SKU onboarding, improving packaging-specific imports and streamlining the package creation process.

3.

Ability to import Relationship attributes using custom import template for Inter Entity Relationships (IERLN) feature

PCC now supports the Inter Entity Relationship (IERLN) Import feature, enabling users to import and maintain relationship attribute information for SKU-Domian relationships using configurable Relationship Import Templates. Users can create and manage Relationship Import Templates from the Relationship Import Template screen, execute Relationship Imports, and monitor import history from the Relationship Import screen.

Users could not import relationship attribute values for entity relationships or configure reusable Relationship Import Templates to support different incoming files and import configurations.

With this enhancement, users can create reusable Relationship Import Templates, execute Relationship Imports, and efficiently maintain relationship attribute information across existing entity relationships. During import, PCC validates that the referenced entity relationships already exist before processing the input, updates relationship attribute values where applicable, and creates new relationship attribute entries when they do not already exist, improving import accuracy while reducing manual effort

No.

Module

Problem Summary

Resolution

1.

PCC

When user selected Locate this SKU in Catalog from the Review Dashboard, the Catalog page opened but did not display the selected SKU, making it difficult to navigate directly to the required product.

Updated the Locate this SKU in Catalog workflow to correctly navigate to and display the selected SKU in the Catalog. The enhancement also ensures the Back to Review option is available for supported entity types and improves the navigation experience by correctly maintaining the selected record during the transition.

2.

PCC

Catalog imports could fail with a data truncation error when processing large Item ID sets in condition flows, preventing the successful completion of the import.

Updated the catalog import process to support large Item ID sets used in condition flows, eliminating data truncation errors during import and ensuring catalog imports complete successfully for large datasets.

3.

PCC

Package Unit information in the Product 360 Packaging screen could be displayed or managed inconsistently, including:

• Relevant and Other Attributes not persisting after save or refresh.

• Relevant and Other Attributes displaying incorrect or inconsistent information when switching between Package Units, including attributes appearing under the wrong Package Unit.

• Package attribute additions, updates, and deletions not being retained consistently.

• Relevant and Other Attributes not being deleted successfully during package updates.

• Other Attributes and their associated Unit of Measure (UOM) values not being retained or displayed correctly after save or refresh.

• Package attribute datatype validation not being enforced consistently across Product 360 and Package creation, allowing invalid values for supported datatypes.

• Package attributes and their values displaying inconsistently between read and edit modes.

Updated the Package Unit management in the Product 360 screen to ensure information is saved, displayed, and managed consistently. The enhancement improves the reliability of attribute creation, editing, deletion, validation, and navigation across Package Units, ensuring information remains accurate and consistent throughout the packaging.

4.

SOP

The current Node Mapping functionality did not allow users to create multiple mappings for the same target node, even when each mapping had a different set of conditions.

Updated the Node Mapping functionality to support multiple mappings for the same target node, provided each mapping uses a unique set of conditions.