Current Update - August 27, 2025

This release demonstrates our ongoing commitment to enhancing system reliability, performance optimization, and overall platform strength. In addition to introducing valuable user-focused enhancements, we've addressed numerous issues and implemented significant infrastructure upgrades.

This update includes new features, error corrections, and planned channel updates.

New Features for PDX

New functionality is described below:

Improved Translations in Channel UI

In some of the PDX Multi-language channels, certain parts of the Channel UI are available in translated versions, which includes the below elements:

Attribute name
Attribute group names
Category names
Help text
List of Value
Unit of measures

Previously, these elements would change when users switched between data languages, as in the screenshot below.

With the introduction of the new functionality, the following navigational elements will no longer be translated when users change the data language but will always be shown in the Default Language of the channel:

Attribute name
Attribute group names
Category names
Help text

This functionality provides users with consistent navigation experience in multi-language channels as in the example below:

The Default language can be identified in the Language dropdown:

This new behavior will affect Multilanguage Onboarding Channels and Amazon US and Amazon CA.

Also note that for some channels, the Default language can be set by user. This means that users of these channels can, in effect, select what language will be used when Attribute name, Attribute group names, Category names, and Help text are displayed. For more information on modifying language settings, refer to 'See and Control Default Language in Channels' in the 2025 Updates topic.

1WorldSync Channel: Update to Product History Message

Submissions to the 1WorldSync Channel include hierarchies of products, not just individual products. As part of generating submissions, PDX needs to resolve potentially many products references for inclusion in the submission.

The submission process will only be successful if all referenced products are valid for submission. If a product is invalid, it will be removed from the submission scope, meaning other parts of the hierarchy cannot be submitted because the referenced product is now missing. This can lead to other products being rejected with an error message of the form 'Cannot submit hierarchy - one or more products were missing. Missing products: [111]' where 111 is the PDX ID of the invalid product.

One challenge is that the error is reported on one product (the one that could not be submitted), but the error is actually caused by an issue on the missing / invalid product. Also, in case the hierarchy is very large, the same errors may appear on many products in the hierarchy and may appear on levels in the hierarchy that are not directly referencing the missing product.

Resolving the issue involves looking up the missing product by PDX ID and checking why it is invalid. Then, fixx the issue and resubmit the hierarchy.

Different problems can lead to a product being invalid for submission. Examples that can lead to a product being invalid are listed below:

Product has attribute validation errors
Product does not belong to IP-GLN of the submission
Product is not even in the 1WorldSync channel
Product can, at the time of submission, have been part of another open submission waiting for a response from 1WorldSync

In the 1WorldSync Channel, GTIN is used as a unique product identifier. To facilitate a better understanding of the concept of missing products and to expedite locating the missing products, with this release, the error message has now been updated to include the PDX ID of the missing product along with the PDX ID and GTIN of the product that reference the missing product. An example is below:

Changes to Unit of Measure (UOM) in Direct Channels

Direct channels work with the concept of unit of measure (UOM) in some attributes, and this can sometimes lead to issues in writing and entering different kinds of units of measure in the PDX channel UI, such as ft3 or 15°C / 59°F (degrees Celsius / Fahrenheit).

With this release, users can more easily write a correct UOM since those values will now be available in a dropdown. User can then select the desired UOM instead of writing it manually. Examples are below:

Improved Performance of Attribute Mapping Screen

Previously, the attribute mapping screen would not be shown before the calculation of AI suggested mappings had been completed. In cases where many attributes were used in master data or in the channel, waiting time could be increased for users of the attribute mapping screen. This has now been improved.

With the recent updates, the AI suggested mappings are generated asynchronously in the background, and the attribute mapping screen may initially be shown without AI suggested mappings but with a spinning icon instead.

After the calculation of AI suggested mappings has been completed, the results will be added to the attribute mapping screen:

Amazon Channel: Adjustment to Handling of Warnings

In the Amazon channel, a completed submission receives a response from Amazon, which may include warnings and/or errors.

Previously, any response containing warnings, regardless of whether errors were also present, resulted in the product being placed in the Returned state. The accompanying message was the following:

'Product had some issues and was not accepted by Amazon,' followed by a list of warnings and errors.

This behavior remains unchanged when Amazon responds with errors.

However, now if the response contains only warnings, the product will be placed in the Accepted state. The new message is the following:

'Product was accepted with warnings,' along with the list of warnings.

This change more accurately reflects that Amazon has accepted and updated the product, despite minor issues being present.

Error Corrections

The following error corrections are described below:

Description
1WorldSync Channel: Improved Handling for Delayed Responses from 1WorldSync Channel When a product is submitted from the 1WorldSync Channel, the PDX platform will wait for 24 hours. If a full response has not been received from 1WorldSync during that period, the submitted product will be automatically rejected. This makes it possible for users to retry the submission. We have recently seen cases where submissions have received partial responses before and after the 24-hour limit. The combination of the partial responses mixed with the automatic rejection after 24 hours ended up leaving products in the submitted state. This has now been fixed. The PDX platform will still wait for 24 hours. Now, if a full response has not been received from 1WorldSync during that period, the submitted product will be automatically rejected. However, if 1WorldSync ends up providing a full successful response (also after 24 hours), the products will no longer be stuck in submitted but will go into the accepted state.
Value Transformations at Receiver / Market Level Previously ‘Value Transformations’ were not saved if they were applied on an attribute at receiver / market level. This bug has now been fixed, so value transformations created at receiver / market level will be saved and applied.

Description

1WorldSync Channel: Improved Handling for Delayed Responses from 1WorldSync Channel

When a product is submitted from the 1WorldSync Channel, the PDX platform will wait for 24 hours. If a full response has not been received from 1WorldSync during that period, the submitted product will be automatically rejected. This makes it possible for users to retry the submission.

We have recently seen cases where submissions have received partial responses before and after the 24-hour limit. The combination of the partial responses mixed with the automatic rejection after 24 hours ended up leaving products in the submitted state.

This has now been fixed. The PDX platform will still wait for 24 hours. Now, if a full response has not been received from 1WorldSync during that period, the submitted product will be automatically rejected. However, if 1WorldSync ends up providing a full successful response (also after 24 hours), the products will no longer be stuck in submitted but will go into the accepted state.

Value Transformations at Receiver / Market Level

Previously ‘Value Transformations’ were not saved if they were applied on an attribute at receiver / market level. This bug has now been fixed, so value transformations created at receiver / market level will be saved and applied.

Planned Channel Updates

The planned channel updates are listed below:

1WorldSync Channel Updates

As part of this release, the 1WorldSync Channel and the 1WorldSync Preprod Channel have been updated to match the 3.1.32 GDSN (IM 8.64) release.

Brandbank Channels Update

The Brandbank channels in PDX have been updated to match the Brandbank Release 18 on August 25, 2025.

Next Update

The next update to PDX is scheduled for September 18, 2025.