In the Document Hub, you could previously download a maximum of 6,000 documents in a bulk download. This limit no longer applies. The system automatically splits the documents into multiple ZIP archives, with a maximum of 5,000 files per ZIP.You can download the generated ZIP files together using a group function. You can use another group function to delete them together.What this means for you: you can download even very large quantities of documents in one go. You no longer need to manually split them into smaller downloads. VersionAvailable frombeta28 October 2026stable4 November 2026.

Reminder: With version 2.8.0 of the METRO plugin, a Shipping profile mapping assistant has been added. You can use this assistant to map your PlentyONE shipping profiles to the carriers specified by METRO. The mappings are used with the Send fulfilment notification to METRO flow or event procedure to submit the corresponding carrier to METRO.Required stepsFrom 30 October 2026, METRO will no longer accept custom carrier names. Use the Shipping profile mapping assistant to map your PlentyONE shipping profiles to the carriers specified by METRO before 30 October 2026.For more information, refer to the plugin changelog.

In the new navigation layout, the Order UI displayed a cached copy of the order details when opening an order from the order overview. As a result, the data might not have been up to date. The order details are now always loaded fresh from the backend. If you open an order from the Recently visited section, you will still see the cached version. The behaviour in the old navigation layout remains unchanged. VersionAvailable frombeta26 October 2026stable28 October 2026  

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

If you place the availability statuses in a different tab than the default one in a custom MyView (e.g. in the Product details tab), the Active toggle in the toolbar did not set the variation to active or inactive. The toggle also did not update when you set the variation to active or inactive directly in the tab. This issue has been fixed. VersionAvailable frombeta26 October 2026stable28 October 2026

For all sales channels that use listings, you can now delete listing groups for offer or product listings. You can also select and delete multiple listing groups at once.After deletion, you will see how many listing groups were deleted and how many could not be deleted.Note: Only empty listing groups will be deleted. If a group still contains listings, it will remain.This means you can remove listing groups you no longer need yourself, without accidentally losing any listings.Deleting listing groups:Go to Sales channels » Channel Control Centre.Open the sales channel for which you want to delete listing groups.Open the Offer listings or Product listings menu, depending on which listing groups you want to delete.Switch to the listing group view.Select the listing groups you want to delete.Click Delete listing groups.VersionAvailable frombeta22 October 2026stable22 October 2026

After you created a new variation and assigned images to it, the Images tab of an item did not display the attribute values of the new variant. When you reopened the item, the attributes were not reloaded. As a result, only the previous values were available in the selection of marketplace attribute values. You could only select the new values after a hard reload of the page. This issue has been fixed. The attributes are now also reloaded when you update the item using the Reload button. VersionAvailable frombeta22 October 2026stable28 October 2026

When a request to the conversation list or conversation search returned no results, the route returned page: 1 and isLastPage: false. The other REST routes return page: 0 and isLastPage: true in this case. In addition, the date filters fromDate, toDate, updateFromDate, updateToDate and deletedAtBefore failed with a 500 error when you provided a UTC timestamp ending in Z, for example 2026-09-22T02:55:00Z.These errors have been fixed. Requests with no results now return page: 0 and isLastPage: true. The date filters now also accept UTC timestamps with Z. Formats with an offset, such as +02:00, continue to work. VersionAvailable fromstable22 October 2026

On eBay Germany, when the base price was enabled, the number of units was exported to eBay using a comma as the decimal separator, for example 1,8. This value was incorrectly interpreted by eBay, which led to the base price on the eBay listing being displayed incorrectly. For example, for an item priced at 85.34 EUR and weighing 1.8 kg, eBay displayed 4.74 EUR per unit instead of 47.41 EUR per kg.This issue has been fixed. The quantity is now exported using a decimal point as the decimal separator. As a result, eBay calculates the base price correctly and the base price is displayed correctly at the listing.To-do:Active listings will not be corrected automatically. If the base price of an active listing is incorrect, you have to carry out the following settings:Go to Sales channels » Active listings.Select the affected listings.Click Group function at the top.Under Update eBay options, select the options Characteristics and Quantity, price and variations.Click Execute.After these changes, eBay will display the correct base price. V...

In PlentyONE Flow, the pick list is now available as a new object. New actions have been added for this: You can search for pick lists, load them interactively and change the pick list status.You can also start a Flow manually using a pick list ID. To do this, use the pick list ID, not the document ID.The action for searching for pick lists adds pick list objects to the Flow execution.The action for changing the pick list status requires a pick list object in the Flow execution.To load the orders of a pick list into the Flow execution, use the adapter. You can then use the order actions as usual.This means that you can now control pick lists directly in your flows and process pick lists and their orders automatically.  VersionAvailable frombeta21 October 2026stable21 October 2026

Previously, for complex mappings and multiple mappings in the catalogue under Data & Plugins » Catalogues, the mapping field only displayed the ID of the selected value, for example BRAND_63852239. From now on, the readable name of the value is displayed as the mapping. The mapping ID is displayed after the readable name in brackets.Nothing changes for catalogue exports. The mapping ID will continue to be transferred to the various sales channels. VersionAvailable frombeta21 October 2026stable28 October 2026

What changedThe XML data of e-invoices (XRechnung and Factur-X) always contained your own bank account as the payment account, even for orders paid with PayPal Pay Upon Invoice (invoice purchase). With this payment method the buyer has to pay to the account of the payment service provider, so the XML did not match the payment. The XML now uses the bank details that PayPal provides for the payment. The PDF invoice was already correct and is not affected.How it worksIf the payment of the order contains bank details from PayPal, as with PayPal Pay Upon Invoice, the XML shows this account: IBAN, account holder and, where the format allows it, the BIC. The account holder is also named as the payee of the invoice.The XML also contains the payment reference that the buyer has to quote when paying.Unless your template defines a payment means code, the payment is marked as SEPA credit transfer (code 58).For PayPal payments that come without bank details, for example PayPal wallet or card payments, no bank account is written. Your own bank a...

Previously, existing REST access tokens remained valid even after changes were made to the associated user account. A user's access tokens are now automatically invalidated for security reasons when:the password is changed,the user is locked or deactivated,the user type, such as administrator status, changes,the user's roles or permissions change.When logging out, the associated refresh tokens are also invalidated.What does this mean for you?Requests with an invalid access token receive the response 401 Unauthorized.Integrations and scripts that log in via POST /rest/login must log in again after one of the account changes mentioned above.You do not need to configure anything. VersionAvailable frombeta21 October 2026stable21 October 2026

With the Flow action Send refund, the Mollie core integration always refunded the entire payment, even when the credited amount was smaller. In addition, the Flow treated failed refunds as successful. As a result, the Refund failed trigger was not activated. These issues have been fixed.The Send refund action now only refunds the total credited amount. If a refund fails, the Flow activates the Refund failed trigger.  VersionAvailable frombeta20 October 2026stable21 October 2026

In the menu Data » Catalogues, you can now use the Live preview feature when editing catalogues with the following standard formats:ItemItem (New)ListingThe Live preview displays what values each mapping in a catalogue would export for a given variation saved in your system.VersionAvailable frombeta20 October 2026stable21 October 2026

The Flow filter Query phone number assessed the condition as not fulfilled, although no phone number was stored for the address. As a result, the Flow was not executed. This error has been fixed.You can run affected Flows again. You do not need to deactivate and reactivate them for this. VersionAvailable frombeta20 October 2026stable21 October 2026

If you manually entered the date in the supplier’s Last price query field, it was always saved as one day earlier. The error was caused by an incorrect time zone conversion. If you selected the date using the date picker, it was saved correctly.This error has been fixed. VersionAvailable frombeta19 October 2026stable21 October 2026

When you scrolled down to the text properties on the properties page of a variation in the item UI, the view would sometimes jump back and forth uncontrollably when scrolling slowly. This made the properties difficult to read and edit.This issue has been fixed. VersionAvailable frombeta19 October 2026stable21 October 2026

In the item description editor, nested HTML layouts lost their structure, for example Bootstrap grids with row and col-* containers. The editor removed the <div> structure and turned it into simple line breaks. This affected layouts you entered in the code view or loaded from existing descriptions. It happened when you saved and when you switched back to the WYSIWYG view.This issue has been fixed. Your layouts are now preserved in both cases. VersionAvailable frombeta19 October 2026stable21 October 2026

In EmailBuilder, the language tabs flickered when editing a template. They also jumped back and forth when the window size was changed. This issue has been fixed. VersionAvailable frombeta19 October 2026stable21 October 2026

In Flow, you can now select which order item types are included in the Order items value filter. Previously, all order items were added together, including shipping costs. An order with items worth 2.99 and shipping costs of 2.49 was therefore valued at 5.48.You can now select only the item types that should be counted. This allows you, for example, to exclude shipping costs from the value.Existing flows are not affected. They were adjusted automatically and will continue to count all item types as before. VersionAvailable frombeta19 October 2026stable21 October 2026

In English systems, “Center” was not spelt the same way everywhere in the Channel Control Centre. We now use the British spelling “Centre” throughout. VersionAvailable frombeta19 October 2026stable21 October 2026

You can now create more than one custom order document for the same order. Until now, only one template could be used per order, even if you had set up several. Now every template whose settings match the order can produce its own document, for example a separate document for each purpose or recipient.How it worksIn the Document Builder, custom order document templates have a new setting Order type. Use it to restrict a template to a certain order type, for example sales orders or returns. Existing templates are set to all order types, so they keep working as before.You can have up to 5 active custom order document templates with identical order settings. Activating a 6th one is rejected with an error message. The same applies to templates whose settings overlap with an existing template without being identical.Order overview: when you create a custom order document, you can now select the template to use. A selected template creates exactly one document.Order group functions: the function has a new template selection. The default ...

Version 2.49.0 of PlentyONE Shop is now available. To-do: In this version, a new styling for headings has been added to the rich-text editor: Footer H2. This is an H2 heading with a smaller font size. This styling is intended for column headings in the footer and improves accessibility. Existing footers will not be migrated automatically. You have to adjust the styling manually if required.Agencies can find information about further changes and resolved issues on GitHub.

The new version 5.0.86 of the plentyShop LTS plugin is now available.For more information, see the plentyShop LTS plugin changelog and the IO plugin changelog.

In the Create document Flow action, the All warehouse option is now always available for selection and is preselected for new steps. The field is no longer required. Existing configurations remain unchanged. VersionAvailable frombeta15 October 2026stable21 October 2026

When you created new variations with the new attribute picker, the stepper did not display the generated variations correctly. After you clicked Create variations, the variations were created, but the stepper jumped back to the attribute selection. If you then selected the attributes again and clicked Create variations a second time, the error message “Attribute values do not match the other variations” appeared. This issue has been fixed. VersionAvailable frombeta15 October 2026stable21 October 2026 

When you worked in the catalogue settings for an extended period, the user interface became increasingly slow to respond.This issue has been resolved. The user interface now continues to run smoothly even when you use the Settings tab for an extended period.VersionAvailable frombeta15 October 2026stable21 October 2026

After you have moved a sales channel to the Channel Control Centre, PlentyONE now hides the assistants for this sales channel in the Setup » Assistants menu. For sales channels with multiple accounts, such as Zalando, the assistants are only hidden once all accounts for this sales channel have been migrated. As long as at least one account hasn’t been migrated, the assistants remain available in the Setup » Assistants menu.For you, this means that you only see the assistants which are relevant to your current setup or for the migration to the Channel Control Centre.Important: All the assistants you need to configure a sales channel are still available in the Channel Control Centre. Only the assistants in the Setup » Assistants menu are hidden once a sales channel has been moved to the Channel Control Centre. VersionAvailable frombeta15 October 2026stable21 October 2026

Previously, event procedures with the Pick list generated trigger could not be migrated to PlentyONE Flow, as the Pick list document type was not available for the Document created trigger.When creating a flow in Flow Studio, you can now select Document > Document created from the Trigger selection drop-down list and then select Pick list from the Document types drop-down list. This allows you to migrate event procedures with the Pick list generated trigger to PlentyONE Flow.VersionAvailable frombeta13 October 2026stable14 October 2026