8th April 2026

  • Published on Apr 9, 2026
  • 3 minute(s) read
  • PP
 Prev Next

Two glowing star shapes on a gradient background, creating a vibrant visual effect.List of Features

No.

Feature

Description

1.

Auto-Creation of Missing SKUs in B2A Sync Using Attribute Matching Logic

During B2A Sync using Attribute Matching Logic, the system updated attributes for existing SKUs in the target catalog but did not create new SKUs if they were missing. This resulted in incomplete synchronization, as new SKUs and their associated attributes from the source catalog were not reflected in the PCC target catalog.

This has been enhanced by enabling automatic SKU creation when Attribute Matching Logic is used. If a SKU does not exist in the target catalog, the system now creates the SKU first and then applies the incoming attribute values from the source catalog.

This improvement ensures complete and accurate synchronization between source and target catalogs, eliminating data gaps and allowing Attribute Matching Logic to support both SKU creation and updates seamlessly.

2.

Introducing Search Support for Template Field Selection in Node Mapping

Previously, in Step 4 — Node Mapping of Template Configuration, the “Template Field” dropdown under the “Limit by Template Field” rule displayed a large list of fields without any search capability, making it difficult for users to quickly find the required field. This has been enhanced by introducing search functionality within the dropdown, allowing users to efficiently locate and select fields. This improvement significantly enhances usability and reduces time spent navigating large field lists.

3.

Enhanced UOM Configuration and Display Control in Templates and SKU UI

The restriction requiring users to configure LoV values for all enforced UoMs has been removed, allowing greater flexibility to define LoVs for any subset or independently. A new canHaveUoM flag has been introduced to control whether a field supports UoM; the UoM field is displayed only when this flag is enabled. This flag is now incorporated into Supplier Onboarding Portal template configuration and governs whether UoM setup can be configured.

This improvement enhances usability, reduces configuration complexity, and ensures more accurate and flexible management of UoM-related data across templates and SKUs.

List of Bug Fixes

No.

Module

Bug Fixes

1.

SP

Error no longer occurs while creating a new category template and selecting export options in the Onboarding Method when no custom export template is configured for the customer, ensuring smooth template setup for new suppliers.

2.

SP

Resolved an issue in the Syndication Import (Option 3) flow where repeated uploads of the same file caused AI mapping reuse to fail, resulting in 0 SKUs being uploaded for certain users. Mapping is now applied consistently, ensuring successful and reliable imports.

3.

SP

UOM values are now correctly displayed along with LOV values when using the wand icon in the Product 360 / Validation Dashboard, ensuring complete and accurate information visibility.

4.

SP

Alignment of automation toggles on the Distributor side has been corrected. The toggles no longer appear shifted due to the addition of extra options, ensuring a consistent and properly aligned UI.

5.

SP

Resolved multiple issues in the Field Formatting screen during template creation where:

  • Incorrect enforcement of LOV and UOM associations prevented users from proceeding.

  • The UI previously blocked progress when schema-based LOVs and UOMs were not properly associated, did not allow user-created LOVs to be linked with schema UOMs, and produced inconsistent errors during toggle and navigation actions.

The validation logic has been updated to remove unnecessary restrictions and ensure smooth configuration and navigation without blocking errors.

6.

SP

Removing an enforced UOM no longer results in an error when the same UOM is associated with a linked LOV. The system now allows removal with appropriate user confirmation and updates both the field and associated LOV accordingly.

7.

PCC

Fields with the magic wand (LOV) in the Product 360 screen allowed free-text entry instead of restricting input to predefined values, resulting in inconsistent data during SKU creation and editing.

8.

SP

Deleting a cloned template with conditional constraints incorrectly triggered an error pop-up and prevented deletion, even when the template was in draft state.

9.

PCC

Resolved an error that occurred when adding fields to a custom export template using attribute names containing “~”character.

10.

PCC

The SFTP option was not visible while configuring the onboarding method in the Onboarding Template under external options.