We have optimised the workflow for ticket creation in our Service Desk: Our new AI-powered system replaces the previous nested dropdown menus with a single, intelligent text field.The system now analyses your error description and automatically recognises so-called "entities" (such as the product area, the desired action, and relevant IDs). This means your ticket is immediately and correctly categorised without detours, eliminating the need for manual input from you. This makes ticket creation significantly faster for you and reduces our response times.To ensure our system can perfectly assign your request, please always include these three details in your description:The affected area (e.g. Data Management, CRM, Warehouse App)Your exact action (e.g. article import, checking change history)Relevant IDs or names (e.g. order ID, variant ID, plugin version)Example of an optimal description: "During article import (Data Management), the upload for variant ID 12345 fails with an error message."

Previously, the Kategorie (category) field was available in Channel Maps for OTTO product catalogues.As the available values for this field vary depending on the product category on OTTO, it is not suitable as a common field for Channel maps. It has therefore been removed from Channel maps for OTTO.The Kategorie values from existing Channel maps created for OTTO were automatically copied to the respective linked product catalogues before the field was removed. This ensures that existing category mappings are preserved.VersionAvailable fromstable11 November 2026

In repair orders, the Item status column in the Order items section of the order details should display the item condition. Instead, the column remained empty. A saved item condition was also not displayed in the table in the Edit items window.This issue has been fixed. The column is now called Item condition and displays the saved condition both in the Order items section of the order details and in the Edit items window.VersionAvailable frombeta11 November 2026stable11 November 2026

Flow has a new order filter called Shipping service provider which lets you filter orders for their shipping service providers. With the new filter Shipping service provider, you can now select all orders of a shipping service provider, for example DHL or DPD, without picking every shipping profile of that shipping service provider by hand. You no longer need to update your selection when your shipping profiles change.This is how to use the new filter:The filter is available for the search, batch search and for branches.Use Is in (IN)  to keep orders with one of the selected shipping service providers. Use Is not in (NIN) to exclude these orders.Select one or more shipping service providers from the list.VersionAvailable frombeta12 November 2026stable18 November 2026

When several flows changed the tags of the same order at the same time, one of the flows could fail with a database error about a duplicate entry. The tags of the failed flow were then not set. This could disrupt follow-up processes that depend on these tags.This behaviour has been changed. Changes to the tags of an order are now processed one after another instead of at the same time. This applies wherever order tags are saved, for example in flows.Note: You do not have to change any flow. However, check the orders for which a flow ended with this error before the update. The tags step were not set for these orders. Start the flow again for these orders, or add the missing tags manually. VersionAvailable frombeta12 November 2026stable18 November 2026

The PlentyONE manual is now available in two versions: main: The current version describes the new PlentyONE menu structure. This version of the manual will continue to be updated as usual. archive: The archive describes the old PlentyONE menu structure. This version of the manual will no longer be updated. If you are still working with the old PlentyONE menu structure, you can still find the relevant instructions in the archive. By default, the current version (main) opens when you access the PlentyONE manual.Here’s how to switch between the manual versions: Open the PlentyONE manual (link). Click main in the bottom-left corner of the navigation bar, next to PlentyONE manual. Select the version you want: main for the current version or archive for the archive.

In the order overview, the notes badge was cut off when an order had 10 or more notes. This issue has been fixed, so the badge now shows the full number. From 100 notes onwards, the badge shows 99+. VersionAvailable frombeta10 November 2026stable11 November 2026

Orders with a partially refunded payment previously had the wrong paid amount. Refunds booked on credit notes weren’t deducted when the paid amount was recalculated. This also applied to refunds in a foreign currency. In addition, even a partial refund fired payment events and changed the order status. These issues have been fixed.Orders with a partially refunded payment now get the correct paid amount. A partial refund no longer fires payment events or changes the order status. The order only becomes unpaid again once a refund brings the paid amount down to 0. VersionAvailable frombeta9 November 2026stable9 November 2026

When creating a channel map for the marketplace Kaufland, individual product categories are only available for selection once at least one Kaufland catalogue with that category has been created in the system via the dedicated assistant. In order to streamline this process a new option is now available in the Data & Plugins » Catalogues » Channel Maps menu.When Kaufland is selected in the pop-up menu Create channel map a new option appears in the Categories drop-down menu. This option, which is called Add Kaufland categories, directly opens the assistant for creating new Kaufland catalogues, enabling users to quickly create catalogues for Kaufland product categories as needed.VersionAvailable frombetaNovember 9 2026stableNovember 11 2026

In Flow Studio, you can now use the new trigger All packages have a shipping number. This trigger only starts your flow once every package in an order has a shipping number.VersionAvailable frombeta9 November 2026stable11 November 2026

Version 2.51.0 of PlentyONE Shop is now available.This update contains bug fixes.Agencies can find information about further changes and resolved issues on GitHub.

What changedWhen you created a storage location label and selected a specific document template, the label was sometimes created with a different template. For example, the label was created with the template "Lagerort A4" although you had selected "Lagerort 10x3". The template you select is now used for the label.How it worksThe template you select when creating a storage location label is used for the label.If no template is selected, the template that fits the warehouse best is used, as before.If the selected template cannot be used, for example because it is deactivated, the best fitting template is used instead. The label then shows this template as the one that was used.What you need to doNothing for new labels. Select the template you want and create the label.Labels that were already created with the wrong template are not changed automatically. Create these labels again and select the template you want.You no longer need to restrict a template to a warehouse or deactivate other templates to get the correct template.Good to...

You can now use item properties as variables in pick list templates. Until now, they were only available for order documents.The new variables are in the pick list item variables, in the group Variation properties:One sub group per property group with one variable for each property.One variable per select or multiselect property group. It returns the selected properties of the group, separated by commas.The values come from the variation of the pick list item and are output in the language of the document.How it worksOnly properties that are set to be displayed in PDF documents are available. Your property settings stay unchanged.Like other variables, the item properties can also be used as restrictions in the template editor.What you need to doOpen your pick list template and add the item property variables where you need them.Save the template settings after you change the content or the restrictions, so that the restrictions are updated.Good to knowProperties that are flagged as order properties are not available for pick lists ...

In rare cases, foreign currencies were temporarily converted with the exchange rate 1 even though the option Update exchange rates automatically was active. This usually lasted for up to an hour or longer. During this time, orders were saved with incorrect amounts. Invoices, accounting exports and price exports to marketplaces used these values.This issue has been fixed. Automatic exchange rates are now applied reliably. If an exchange rate is missing, the system no longer converts with the factor 1. VersionAvailable frombeta5 November 2026stable11 November 2026

Restore flows before they are permanently deletedThe Mark for deletion function in Flow Studio no longer deletes a flow immediately. Instead, the flow is permanently deleted after 7 days. Until then, you can restore the flow using the new Restore flow function in the context menu at the end of the table row. Flows marked for deletion cannot be edited or activated. You can also delete a flow immediately using the Delete permanently function.Note: Flows marked for deletion continue to count towards the flow limit until they are permanently deleted, but they do not count towards the active flow limit.New "Deletion" column and "Marked for deletion" filterThe flow overview in Flow Studio now includes a new Deletion column and a new Marked for deletion filter. For flows marked for deletion, the tooltip in the Deletion column shows when the flow was marked for deletion and when it will be permanently deleted.Import backupsThe new Import backup function in the context menu at the end of the table row allows you to import a flow backup as a...

In Flow Studio, the Send email action now includes the new Supplier option in the Recipient selection field. The option only works for reorders. VersionAvailable frombeta6 November 2026stable11 November 2026

You can now transfer the duration of the manufacturer’s guarantee in years to Kaufland. PlentyONE sends this value to Kaufland via product catalogues, using the data field Manufacturer guarantee (years) whenever products are created or updated.Kaufland accepts whole numbers from 1 to 99 as values for the manufacturer’s guarantee.To transfer a product’s manufacturer’s guarantee in years to Kaufland, open the relevant Kaufland product catalogue in the Data & Plugins » Catalogues menu and map the Manufacturer guarantee (years) data field.VersionAvailable frombeta 5 November 2026stable5 November 2026

The import function in the Listings section of your OBI account's Channel settings has been improved. During import, PlentyONE now matches the EANs of active SKUs on OBI with the barcodes of your variations in PlentyONE. If a matching variation is found, a new offer listing is created and the corresponding OBI SKU is entered in the listing's SKU field. If you have already created an offer listing for this variation, PlentyONE takes the following into account during the import:If the SKU field is empty, PlentyONE enters the corresponding OBI SKU.If the SKU field already contains a value, it remains unchanged.If only one offer catalogue exists for OBI, the offer listings are automatically linked to this catalogue during import. You do not need to link them to a catalogue manually afterwards. If multiple offer catalogues exist, PlentyONE does not create any new offer listings.PlentyONE also does not create an offer listing if no variation with a matching EAN is found.VersionAvailable fromstable2 November 2026

What changedA Flow without steps or without a trigger could prevent the Flow overview from loading. As a result, you could not see or edit any of your other Flows either, and you could not deactivate or fix the faulty Flow. Such Flows are now handled correctly. The Flow overview loads as usual, and you can open and repair the faulty Flow.How it worksFlows without steps are displayed in the overview. They are marked as not activatable and show the message that an empty Flow cannot be activated.If you open an active Flow that is faulty, it is deactivated automatically so that you can edit it right away. A warning message informs you about this.If a Flow has no trigger, the manual trigger is set by default when you open it. It uses the object type of the Flow (for example contacts or items). If the Flow has no known object type, orders are used. You can change the trigger afterwards.If the automatic deactivation fails, an error message is shown and the Flow is displayed as it was loaded.Active Flows that are valid and Flows that are a...

Previously, the VAT ID for the billing address was determined solely based on the BuyerTaxRegistrationId field. This field could contain multiple VAT IDs separated by commas, relating to different countries and ID types. As a result, it was not always possible to unambiguously identify the VAT ID relevant to the order.PlentyONE now checks the BuyerVatNumber field first, as it contains the VAT ID relevant to the specific order. Only if this field is empty the BuyerTaxRegistrationId is used as an alternative. If this field contains multiple entries, only a VAT ID of type VAT is considered whose country matches the shipping country of the order.VersionAvailable frombeta4 November 2026stable4 November 2026

For partial refunds, in some cases, PlentyONE was previously unable to match manually created credit notes to a refund from the VCS report.Example: An order item has a quantity of 3, and the amount for 1 piece is refunded. You then created a credit note with a quantity of 1. However, the VCS report contained a quantity of 2 or 3 and distributed the refunded amount across these items. Due to this discrepancy in quantity, the credit note was ignored and a new credit note, including a document, was created. The manually created credit note remained unassigned.This behaviour has been adjusted. If PlentyONE finds no match, the system now checks the credit notes a second time. It searches for credit notes whose quantity matches the refunded amount and which are not yet assigned to any other Amazon transaction ID. If such a credit note is found, the VCS correction adjusts the quantity of the order item to the value in the VCS report. This also applies to associated bundle or set components. VersionAvailable fromstable3 November 2026

If an order item had multiple promotion positions, only one of the promotion positions was previously updated when correcting the order based on VCS reports. The other promotion positions remained unchanged. This could result in incorrect discount amounts being shown on invoices.This issue has been resolved. When correcting orders based on VCS reports, all promotion positions for an order item are now taken into account. The discount amount Amazon specifies for an order item in the VCS report is distributed across the associated promotion positions. The distribution is based on the previous discount amounts of these promotion positions. Any rounding remainder is allocated to the last promotion position. This ensures that the total of the corrected discount amounts exactly matches the discount amount specified by Amazon.Example:A customer orders a T-shirt. The order contains two promotion positions for this item:PositionOriginal discount amountOrder item: T-shirt–Promotion position 1€6.00Promotion position 2€4.00Total discounts€10.0...

When you added the Barcode column in the table settings of the item overview or variation overview, the barcode selection was sometimes empty and displayed “No results found”. As a result, no barcode could be selected for the column. This issue has been fixed. When opening the table settings, all barcodes are now always listed. VersionAvailable frombeta3 November 2026stable4 November 2026

The returns process had several issues. These have been fixed:The warehouse selected in the returns process was not used when Pro Auftrag kann ein Lager zugeordnet werden (one warehouse can be assigned per order) was active. The selected warehouse is now used for the return.Items with a best-before date (BBD) could not be returned via delivery orders. This is now possible. You can select the BBD, and it is kept when the items are booked back.The quantity already returned was displayed incorrectly when a delivery order was selected. It is now displayed correctly.Bundles from delivery orders were not booked back into stock, including components with a BBD. They are now booked back.Existing returns showed 0 / n instead of the quantity booked back, including for bundles. They now show the quantity booked back, for example 1 / 1. VersionAvailable frombeta3 November 2026stable4 November 2026 

Version 2.50.1 of PlentyONE Shop is now available.This update contains bug fixes.Agencies can find information about further changes and resolved issues on GitHub.

When opening the group function in the item overview, the saved default preset was sometimes not applied, and the dialogue displayed no values. This behaviour has been resolved. The default preset is now applied every time the group function is opened. VersionAvailable frombeta30 October 2026stable4 November 2026

For a variation without sales prices, a price that you added in the Pricing tab was not displayed in the table, either after adding it or after saving. The price was saved, but only appeared after a hard reload of the page. This behaviour has been fixed. Added prices are now displayed immediately and remain visible after saving. VersionAvailable frombeta30 October 2026stable4 November 2026

After clicking Manual run on a subscription, the screen was grayed out and the run never started. This is fixed. The manual run now opens and can be started as expected. VersionAvailable frombeta30th October 2026stable4th November 2026

Creating a large number of storage locations at once could cause problems. This is now fixed, and generating storage locations in bulk works reliably.

What changedDocuments could not be created for some orders if the template used a discount total variable and an order item of that order had no amount. These documents stayed in the status pending and were finally marked as faulty. This is fixed. Documents for such orders are now created, and items without an amount are left out of the discount total.Affected variablesOrder system amounts: Discount total amount gross and Discount total amount netOrder foreign amounts: Discount total amount gross and Discount total amount netTemplates that do not use these variables were not affected.What you need to doNew documents: nothing. They are created correctly.Documents that were marked as faulty because of this problem: create them again. This is only possible if no following document exists for them, for example a reversal document for an invoice or a credit note.Good to knowYour orders are not changed. The fix does not add missing amounts to order items. It only makes sure that the document can be created without them.Items without an a...