List price and List price currency are no longer mandatory fields in Temu product catalogues. You can save a product catalogue and export a product listing without mapping these data fields. Base price and Base price currency are still mandatory.If you use a list price, the existing conditions still apply:Both List price and List price currency must be mapped. It is not sufficient to map only the value for the list price.List price must contain a value.List price currency must be specified as a three-letter currency code, e.g. EUR.VersionAvailable frombeta8 September 2026stable8 September 2026 

Previously, when adding the Formula data source, an empty input field was displayed first. To create a formula, you then had to click the input field to open the formula creation window.This behaviour has been changed. When adding the Formula data source, the formula creation window now opens automatically. This eliminates an extra step. In addition, empty formulas can no longer be saved.This change simplifies entering formulas and prevents empty formulas from being saved in catalogues or Channel maps.Version         Available frombeta2 September 2026stable3 September 2026

Amazon provides the buyer’s company name in a dedicated data field in the order report (BuyerCompanyName). PlentyONE now supports this field and uses it as the source for the buyer’s company name in the billing and delivery address of the respective order.To have Amazon include the data field in the order report, you must enable the corresponding setting in Seller Central.Required stepsIn Amazon Seller Central, enable the setting for including the buyer’s company name in order reports (isBuyerCompanyNameEnabledInOrderReports) for each Amazon account.→ The buyer’s company name is then automatically taken from the BuyerCompanyName field when new Amazon orders are imported. No further settings are required in PlentyONE.Note: If you do not enable the setting, PlentyONE will continue to determine the buyer’s company name from the address data.Version         Available fromstable1 September 2026

Version 2.44.0 of PlentyONE Shop is now available. In the editor, the PriceCard block on the product page now contains an option to display the variation number. The editor now has a function to undo and redo inputs. This function only applies to changes to the template, not changes in the site settings. You cannot undo or redo changes if you switch the page. In the editor, the image input in the Image block now contains an option to set one image for all screen sizes simultaneously. This option is enabled by default. If you disable the option, you can still assign a separate image for each screen size. Agencies can find information about further changes and fixed issues on GitHub.

In the Data » Catalogues menu, the Restore a deleted catalogue and Restore a deleted channel map menus have been updated. The new versions of these menus have been designed to be more user-friendly overall and allow you to delete several catalogues/sales channels at once.VersionAvailable frombetaSeptember 1 2026stableSeptember 2 2026

In the Data » Catalogues menu as well as the Channel Control Centre, due to an internal error changes to certain complex mappings in catalogues would not be transferred to the connected listings, and the data would therefore not be exported to the respective marketplaces.This issue is now fixed. Listings that were affected by the issue can be updated by simply saving new changes to the connected catalogues.VersionAvailable frombetaAugust 27 2026stableAugust 27 2026

In the menu Sales Channels » Accounts as well as the Channel Control Centre, new listings could not be created for certain sales channels for a brief period of time due to an internal error. This issue is now fixed.VersionAvailable frombetaAugust 27 2026stableAugust 27 2026

When registering a DHL return using an address where the house number was included in the Street field and no explicit house number was specified, an error message occurred.This behaviour has been changed. From now on, this value will be processed and used in the address when requesting the return. VersionAvailable frombeta27 August 2026stable27 August 2026

When attempting to open an order from the reorder UI by clicking on the order ID, there was no redirection to the order UI; instead, the order was opened directly within the reorder UI. This behaviour has been fixed. VersionAvailable frombeta27 August 2026stable2 September 2026

Until now it occurred that adding a new language to a property in the Setup » Settings » Properties menu wasn't working. Only if you opened another property and added a new language there, you could also add one in the original property. This has been fixed.VersionAvailable frombeta27th August 2026stable2nd September 2026 

If a company GLN (Global Location Number) was added in the XML settings of a document template in DocumentBuilder, it was previously only added as the ram:ID field for the seller. This has now been fixed and also applies to the ram:GlobalID field. VersionAvailable frombeta27 August 2026stable2 September 2026

From now on, the AI assistant in your system is able to generate graphs. This way questions about sales, stock and more cannot only be answered via text but also be visually summarised.VersionAvailable frombeta27th August 2026stable27th August 2026

In Temu product catalogues, units for data fields that depend on a parent data field were not transmitted to Temu together with the value.Example: For the Material (Polyvinyl chloride) ► Thickness (mm) data field, the unit mm was not transmitted to Temu.This issue has been resolved. The unit is now available as a separate data field alongside the value and must be mapped separately. The unit is then transmitted to Temu together with the value.Required stepsIf you have already mapped values for dependent data fields that require a unit in a Temu product catalogue:Open the Temu product catalogue.Map the corresponding unit to the data field for the unit.Save the product catalogue.Create new product listings using the updated product catalogue.Important: Existing product listings are not updated automatically when you add the new mapping. You must create new product listings so that the unit is transmitted to Temu together with the value.Version       Available frombeta26 August 2026stable26 August 2026

When reopening the editor for a previously saved template in DocumentBuilder, some widgets occasionally stopped responding correctly. This issue has been resolved. VersionAvailable frombeta26 August 2026stable2 September 2026

The item property filter did not function correctly for order properties saved on the item.The item property filter did not function correctly for properties of the type None.These issues have been resolved.VersionAvailable frombeta26 August 2026stable2 September 2026

The filter Last status change (days) is now also available in the branch. VersionAvailable frombeta26 August 2026stable2 September 2026

The interface used to retrieve financial data from Amazon has been updated to the latest version of the Amazon Selling Partner API (SP-API).No action is required on your part. The update is applied automatically in the background.Version       Available frombeta13 August 2026stable13 August 2026

When a text property was added in the item UI under the Properties tab using the Add properties button, it was added twice in the widget and an error occurred when saving. This behaviour has been fixed. VersionAvailable frombeta25 August 2026stable26 August 2026

An error occurred in the Create document action in Flow for the document type Voucher.This error has been resolved. VersionAvailable frombeta25 August 2026stable26 August 2026

As part of an update to the OTTO Austria Group interface, the catalogue templates for product catalogues have been updated. As a result, some category-specific data fields have been adjusted.For category-specific data fields, the associated product category is now shown in the data field name. The product category is separated from the data field name by a vertical bar, e.g. Grundfarbe|Sonnenbrillen or Geschlecht|Sonnenbrillen.Required stepsCheck your product catalogues for OTTO Austria Group and review the mappings of the category-specific data fields.If an existing mapping is no longer available after the update, create a new mapping for the affected data field.Tip: Enter the name of the product category, e.g. Sonnenbrillen, in the search bar of the product catalogue to find the corresponding category-specific data fields faster.Version       Available fromstable24 August 2026

If a new order template was created, it was not selectable in the menu Setup » Orders » Templates.This issue has been fixed: Newly created order templates are now available for selection. VersionAvailable frombeta24 August 2026stable24 August 2026

When a value was entered into the search field of a selection bar, the selection bar did not jump to the first entry containing the search value, but instead displayed the last found entries. This behaviour has been fixed. VersionAvailable frombeta24 August 2026stable26 August 2026

Version 2.43.0 of PlentyONE Shop is now available.This update fixes issues with variation selection and the application of the trailing slash configuration in search suggestions.Agencies can find information about further changes and resolved issues on GitHub.

Previously, functions could only be used in the primary data source of a catalogue. You can now also map functions in fallback data sources. The following rules apply:Functions can be used in all catalogues with standard and marketplace formats that already support functions.Functions can only be mapped as data sources to data fields with simple mappings.You can add multiple fallback data sources with functions to a data field.A fallback data source is only used if the PlentyONE data source mapped before the fallback data source does not provide a value for a variation.Using functions in fallback data sources allows you to reuse a function with multiple parameters instead of creating a separate function for each data source.Example: You can use a function that removes HTML code from item names in the primary data source for Name 1 and in a fallback data source for Name 2. If Name 1 is not available for a variation, Name 2 is used and processed by the same function.Version       Available frombeta24 August 2026stable26 August 2026

In the detail view of item variations, the Clients and Images tabs could show an outdated status after switching to another tab and back: linked clients were shown as inactive, and linked images appeared as unlinked, even though the correct data was saved. To see the correct status, the page had to be fully reloaded.This issue has been resolved: Both tabs now always display the actually saved status of the client and image links, regardless of switching between the tabs. VersionAvailable frombeta21 August 2026stable26 August 2026

If a channel map was deleted from the Data » Catalogues » Channel maps menu, it is now possible to restore it.To restore a deleted Channel map, click Restore at the top of the toolbar in the Channel maps overview, select the Channel map and confirm the prompt. VersionAvailable frombeta21 August 2026stable26 August 2026

This update includes a number of under-the-hood changes aimed at improving the overall stability and usability of the import tool:In the import overview, accessible via Data » Import (New), the Schedule filter option has been removed. The option to schedule import runs itself is unaffected by this change.When creating a new import, step 2 can no longer be completed if the import tool could not generate a preview using the data source provided in step 1. This change was made in order to ensure that only functional imports can be created.Various additional fixes and stability improvements.VersionAvailable frombetaAugust 28 2026stableSeptember 2 2026

The new tag type "Board" was missing its name in the dropdown list in the Setup » Settings » Tags menu. This has been fixed. VersionAvailable frombeta20 August 2026stable26 August 2026

During the migration of the legacy automation to Flow, it could happen that the settings of the "tag" action and the values for the filter Last status change were not set as expected.This has been fixed. VersionAvailable frombeta20 August 2026stable26 August 2026

You can now assign a valid-from and valid-to date to each taric code / country VAT assignment. This allows multiple VAT rates to be set up for the same customs tariff number and country for different time periods. Future rate changes can thus be planned in advance instead of having to be manually changed on the effective date. VersionAvailable frombeta20 August 2026stable26 August 2026