1st October 2026

Published on Oct 1, 2026

3 minute(s) read

M

List of Features

No.	Feature	Description
1.	Enable static value assignment using Transform to New Value on the Field Transformation screen in SOP	Added the ability to assign a static value to a target attribute under "Transform to New Value" on the Field Transformation screen in SOP. Users can apply the specified value regardless of whether the source field contains data or is empty. With this enhancement, users can populate target attributes with static values, regardless of the data in source field in SOP.
2.	Support for existence-based conditions on the Field Transformation screen in SOP	Added the “Existence” condition category in the SOP condition builder for Template Column Name with the Exists and Does Not Exist operators. These conditions allow users to filter SKUs based on whether the selected template column has a value for the SKU. With this enhancement, users can control transformations based on the presence or absence of attribute value in SOP.
3.	Support for submitting CSV files through Option 3 in SOP	Added support for submitting product data in CSV format through Option 3 in SOP. The system identifies the file format and displays the applicable parsing settings before submission. Field Delimiter, Field Enclosure, and Header row number are prepopulated and can be updated before submission. File Upload History displays the parsing settings used for each upload. With this enhancement, suppliers can submit CSV files directly without converting them to .xlsx and review the parsing settings used for their submissions in SOP.
4.	Support for additional Excel file formats (.xls/.xlsm) through Option 3 in SOP	Added support for submitting product data in Excel (.xls/.xlsm) formats through Option 3 in SOP. The system identifies the file format and displays the applicable parsing settings before submission. Header row number defaults to 1 and can be updated before submission. File Upload History displays the header row number used for each upload. With this enhancement, suppliers can submit .xls and .xlsm files directly without converting them to .xlsx and review the parsing settings used for their submissions in SOP.

List of Improvements

No.	Improvement	Description
1.	Support for updating and deleting existing SKU pricing records through Option 3 in SOP	Improved SKU pricing import through Option 3 in SOP to support updating and removing existing price records. When a price record in a re-imported file matches an existing record on the SKU price sheet, the existing price record is updated instead of being duplicated. If a previously mapped required pricing field is missing from a later import file, the import now errors out instead of skipping the price record. The price record can now be deleted when the price sheet combination is no longer supplied. A different pricing combination continues to create a separate record. Option 3 price imports only supported adding new records. Importing updated pricing data created duplicate price records instead of updating the existing records. There was also no defined way to delete price records. With this enhancement, users can update and delete existing price records through subsequent imports in SOP.
2.	Support for Suppress Mapping on the Field Transformation screen in SOP	Added support for suppress mapping on the Field Transformation screen in SOP. A suppress mapping withholds the mapping between the source attribute and the target attribute and excludes a selected target attribute from the mapped output. Users can configure suppress mapping as the default or apply it through a Conditional Override. With this enhancement, users can control which attribute mappings are included in the transformation process in SOP.

List of Bug Fixes

No.	Module	Problem Summary	Resolution
1.	PCC	The GET SKU Public API intermittently returns an empty result even when SKU records are available within the specified date range.	Corrected the underlying query to only return SKUs that currently exist in the SKU master data.
2.	PCC	A product catalog showed a SKU count mismatch between Bridge and PCC.	Corrected the underlying sync issue causing the SKU count mismatch and verified that catalog sync now completes across different scenarios.
3.	PCC	When Auto Cascade is enabled, updates to conditional schema requirements at a parent node are not inherited by child nodes. The child nodes do not retain the configured conditional requirement.	Updated schema cascading to propagate changes to conditional requirements from the parent node to inherited child schemas. Cascading now applies the configured conditions when schemas are created or updated.
4.	SOP	During incremental AI mapping, the distributor AI Mapping Finalization screen does not display existing mapped targets for fields with a mapping history. For fields mapped to Passthrough Custom Attributes, Pricing, Packaging, or ETIM, “Mapped to Entity” displays the correct entity, but “Will map to this Target data element” displays “+ Select target data element” instead of the mapped target.	Updated the distributor AI Mapping Finalization screen to display an existing mapped target with a mapping history, including mappings to template fields, Passthrough Custom Attributes, ETIM, packaging, and pricing. The target is displayed with edit and delete actions so users can review and manage the existing mapping.

Was this article helpful?