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

The Free Shipping data field in offer catalogues for OBI has been renamed to Shipping type. In addition, the following additional data sources are now available for this data field under Export as:Parcel1 to Parcel9Freight1 to Freight9The existing Free Shipping data source for free shipping remains available.Existing mappings for this data field remain unchanged. You do not need to update your existing mappings due to the renaming and the new data sources.Version       Available frombeta20 August 2026stable20 August 2026

When a customer uses the withdrawal form to withdraw an order, the contents of the message are now saved as a note on the order. This lets you handle enquiries more efficiently.

Two variations of an item with cross-selling links were opened one after the other without making or saving any changes. After opening the second variation and then switching back to the item, the Save button was active and the same cross-selling items were added again, resulting in a duplicate count being displayed. This error has been fixed. VersionAvailable frombeta19 August 2026stable26 August 2026

In the new item UI, changes in the Images tab (Delete, Reorder, Availability, Upload) as well as in free text fields, characteristics, and shipping profiles were visually reset after saving and only displayed after a full page reload.Cause: Since the TanStack migration of the item/variation services, the re-read operation after saving was answered from the outdated cache instead of from the server.The save processes now invalidate the item/variation cache before re-reading, and all involved write services (images, free text fields, shipping profiles, characteristics) directly invalidate the article cache so that saved changes are displayed immediately. VersionAvailable frombeta19 August 2026stable26 August 2026

Dedicated logs for data exports to refurbed are now available in PlentyONE. These new logs allow you to keep track of the product and offer listings as well as the prices and stock data you’ve exported to refurbed and check whether errors occurred during the data export. The logs also provide additional information on the individual data transfers, including the actual price and stock values transmitted.You can find the logs under:Systems with the new menu structure (Sales Channels » Channel Control Center)Sales Channels » Channel Control Centre » [Open your refurbed sales channel] » Data export logsSystems with the old menu structure (Sales Channels » Accounts)Sales Channels » Accounts » [Open your refurbed account] » Data export logs Further information is available on the refurbed (Setup via Channel Control Centre) page and on the refurbed (Setup via Sales Channels » Accounts) page in the PlentyONE manual. Version Available from beta 9 September 2026 stable 9 September 2026

A validation error was displayed when configuring a Messenger channel with Basic Auth credentials, even though all mandatory fields were completed. This behaviour has been fixed. VersionAvailable frombeta18 August 2026stable19 August 2026

Dedicated logs for data exports to OBI are now available in PlentyONE. These new logs allow you to keep track of the offer listings as well as the prices and stock data you’ve exported to OBI and check whether errors occurred during the data export. The logs also provide additional information on the individual data transfers, including the actual price and stock values transmitted.You can find the logs under:Systems with the new menu structure (Sales Channels » Channel Control Center)Sales Channels » Channel Control Centre » [Open your OBI sales channel] » Data export logsSystems with the old menu structure (Sales Channels » Accounts)Sales Channels » Accounts » [Open your OBI account] » Data export logs Further information is available on the OBI (Setup via Channel Control Centre) page and on the OBI (Setup via Sales Channels » Accounts) page in the PlentyONE manual. Version Available from beta 9 September 2026 stable 9 September 2026  

When generating PDFs and in the preview, the fonts Times New Roman and Courier from the output settings were not applied correctly and were instead replaced by a default font. These fonts are now correctly embedded in generated PDF documents and in the preview. VersionAvailable frombeta17 August 2026stable19 August 2026 

Version 2.42.0 of PlentyONE Shop is now available.The editor now includes a revision history for page templates. With the history, you can browse and restore the most recently saved revisions.Agencies can find information about further changes and fixed issues on GitHub.

Fix: In the new import UI (Data » Imports menu), a maximum of two possible mappings were incorrectly displayed, resulting in missing import values when there were multiple mappings. This behaviour has been corrected. Multiple mappings are now displayed correctly and are fully functional.Layout adjustments: In the mapping fields, the first field is now displayed at a minimum of 50% size and all subsequent fields at 25%. Furthermore, a line break is automatically inserted when there are 4 mappings or more. VersionAvailable frombeta14 August 2026stable26 August 2026

SummaryTo prevent errors when exporting stock and prices, the handling of SKU fields in the OBI module has been standardised and streamlined. In future, it will be clearly defined where the OBI SKU ID must be saved to ensure a correct mapping to OBI offers.Background: The OBI API stipulates that a valid SKU ID generated by OBI must be used to identify which offer on OBI receives the offer data sent by PlentyONE.What has changed?Primary data source for stock & price: For the export of stock and prices, the SKU field of the offer listing is primarily used as the OBI SKU ID.New data field OBI SKU ID in catalogue (as a fallback): The optional OBI SKU ID data field is now available in the OBI offer catalogue. If the SKU field in the offer listing is empty, the export will automatically fall back to this new data field in the catalogue.No more automatic VariationID mapping: Newly created OBI offer listings are now created with an empty SKU field so that sellers can enter the OBI SKU ID manually or via mapping in the offer catalogue.Disco...

To respond to positive reviews on eBay in PlentyONE Flow, the new event-based trigger eBay feedback received is now available. This allows you to directly transfer the corresponding actions from the Procedures into Flow.This trigger does not react to incoming reviews in real time. Instead, an hourly cron job (as soon as a flow with the trigger is active) checks whether there are new orders whose items have received a positive review. If this is the case, the event is triggered for each of these orders. VersionAvailable frombeta13 August 2026stable19 August 2026

Buttons in the detail item and variation views now display an integrated loading indicator during the execution of the respective action, clearly showing that the action is currently being performed.The affected actions include: saving, reloading, copying and deleting an item or variation, setting a variation as the main variation, as well as toggling inheritance.The buttons in the detail tabs also now show loading indicators: cross-selling (add item, reverse-link), text translations (copy, delete), images (link, unlink, upload, delete, assign availability, clear cache), shipping profiles (add), bundles/multipacks (add), sales price (update), barcodes (generate), suppliers (add), multilingual properties (delete), stock, serial numbers, category selection, and the "Print labels" dialogue.Buttons that initiate a batch operation are disabled during execution to prevent duplicate submissions from repeated clicks.The loading spinners are controlled via the feature flag “progress-indicators” and are subject to a short delay, so they only...

After the inheritance of sales prices for a sub-variation was disabled, it was not possible to add a price afterwards because the button was inactive. The system had to be reloaded first in order to add a new price.This issue has been resolved. VersionAvailable frombeta13 August 2026stable19 August 2026

The value for a property in the form of a string was cut off after only a few characters. In the UI, "…" was shown instead of the full value, even when there was enough space for the complete value. This behaviour has been fixed. VersionAvailable frombeta13 August 2026stable19 August 2026 

The option Parallel executions allowed has been added to the trigger settings for time-based and manual flows.Enable the toggle if you want to allow the same flow to be started multiple times simultaneously (before the previous execution has finished).If the option is disabled, only one run at a time can be active for the respective flow. VersionAvailable frombeta13 August 2026stable19 August 2026

If no email address was provided for the shipping address when using the FlexDeliveryService, the email address from the billing address was not used; instead, the information was missing entirely.This has been fixed: If the shipping data lacks an email address, the email address from the invoice will now be used. VersionAvailable frombeta13 August 2026stable13 August 2026

The optional XML field External supplier ID in DocumentBuilder was not included in the XML code for the formats X-Rechnung, Factur-X-Comfort and Factur-X-Extended.This issue has been resolved. VersionAvailable frombeta13 August 2026stable19 August 2026