25th September 2026

No.

Feature

Description

1.

Ability to reuse AI finalized mapping history for subsequent file uploads in SOP

Added support for reusing finalized mappings from a supplier’s earlier file uploads. When the supplier uploads a new file, the system checks that supplier’s own mapping history. If a past mapping clearly applies and its target is still valid, the column is automatically mapped without being sent to AI.
When past Template Field mappings conflict and no mapping clearly dominate, the most recent mapping is suggested. Fields without mapping history, and mappings whose targets are no longer valid follow the existing AI mapping process.
With this enhancement, suppliers can reduce repetitive mapping work on subsequent uploads, while first-time suppliers continue through the standard AI mapping process in SOP.

2.

FTP location support for Hybrid Import Template in PCC

Added support for importing product data files from a configured FTP location using the External Location option with a Hybrid Import Template for import in PCC.
The External Location option was available only for User Defined Import Templates and was not displayed when Hybrid Import was selected. With this enhancement, users can include hybrid imports in their FTP location, reducing the need to upload product data files manually in PCC.

No.

Improvement

Description

1.

Ability to edit rules and conditions in published category templates in SOP

Added the ability to edit rules and conditions directly in the Field Formatting screen of a published template in SOP. Users can update validation logic without cloning the template.
Changes to validation rules in a published template required cloning the template, which invalidated existing AI mappings and triggered unnecessary syndication/standard regeneration.
With this enhancement, users can update validation logic directly in a published template while preserving existing AI mappings and the template’s field list and order. Saving the changes automatically triggers SKU revalidation in SOP.

2.

Enhanced validation error navigation in the excel grid/product submission screen in SOP

Enhanced validation error navigation under the Products tab on the Excel grid/product submission screen. Hovering over the Invalid status in the Status column displays a list of fields with validation failures. The pop-up lists the affected fields in grid column order under the heading “This SKU is invalid. Check the fields below to fix the validation failures.”
Clicking a field name in the pop-up scrolls the grid to the corresponding cell in the same row and briefly flashes the cell to highlight it. If the column is hidden in the Columns panel, it is displayed before navigating to the cell.
Users had to scroll through the grid to identify fields with validation failures, making it difficult to locate errors when the grid contained many columns. With this enhancement, users can navigate directly to the affected fields, making it easier to identify and correct validation failures in SOP.

No.

Module

Problem Summary

Resolution

1.

PCC/SOP

Issues with conditional attribute validation and visibility:

• When the condition for a required attribute was met, another attribute was incorrectly marked as required even though its own condition was not met. Users were prompted to enter a value for an attribute that should not have been required.

• The configured condition for an attribute was not displayed when users searched the schema using the full attribute name, although it appeared when the attribute was opened directly from the Schema view.

Corrected conditional attribute validation and visibility:

• Updated conditional required-field validation to evaluate each attribute against its own configured condition, ensuring that only attributes whose conditions are met are marked as required.

• Updated the schema search to display the configured attribute condition when searching by the full attribute name, ensuring consistent visibility through both search and the Schema view.

2.

PCC

An import scheduled for a specific date and time could be rescheduled for the same date in the following year if the scheduling service restarted after the intended execution time.

Updated scheduling to prevent missed one-time imports from being automatically moved to the following year. The system does not automatically process these imports after their scheduled time has passed.

3.

PCC

In Product 360, updating a SKU's attributes could fail with a database error as the update operation did not pass a value identifying who made the change.

Updated the SKU attribute save process in Product 360 to consistently record the user making the changes for all attribute values, preventing save failures caused by missing user information.