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

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

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

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 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

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

As from today, you can migrate event procedures to PlentyONE Flow that have the trigger Packing list generated.VersionAvailable frombeta13th October 2026stable14th October 2026

The flag filter in order search within Flows did not find the expected orders when filtering by the None option.This issue has been fixed. VersionAvailable frombeta8 October 2026stable14 October 2026

If an event-based flow contained a filter that was either no longer available (plugin) or faulty, this could result in other flows with the same trigger (e.g. Order created) no longer being checked. This behaviour has been fixed. VersionAvailable frombeta7 October 2026stable14 October 2026

The Guest order filter in Flows was not returning the correct results. This has now been fixed. VersionAvailable frombeta5 October 2026stable7 October 2026 

The new Manufacturer filter has been introduced, allowing you to filter by the manufacturers of the items in an order. VersionAvailable frombeta1 October 2026stable7 October 2026

An error occurred in the filter selection in the branch and in the search in PlentyONE Flow Studio. As a result, it was possible to select filters in the branch that were only intended for the search, and vice versa, filters in the search that were only intended for the branch. This led to errors in the flows. This error has been resolved. To Do:Affected flows must be corrected manually and the incorrect filters removed/replaced. These filters are marked accordingly so that they cannot be selected. VersionAvailable frombeta24 September 2026stable30 September 2026 

A new selection field has been added to all amount filters in Flow. The options are Order currency and System currency. The default setting is Order currency, and all existing templates also use Order currency. VersionAvailable frombeta23 September 2026stable30 September 2026  

Previously, all referrers were listed in the referrer filter. Now, only filterable referrers are listed. VersionAvailable frombeta17 September 2026stable23 September 2026

The new action Change order client has been added in Flow Studio. VersionAvailable frombeta10 September 2026stable16 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

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

The PayPal Refund flow action, when run against a credit note, was always refunding the full paid amount instead of the credit note's amount. From now on, the refunded amount will match the credit note's value. Multiple partial refunds against the same order are now supported.The payment status will now correctly show Partially refunded when only part of the amount has been refunded. VersionAvailable frombeta24th August 2026stable24th 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

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

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

In some cases, the input value was not correctly carried over from the previous action step, which caused subsequent action steps to be executed incorrectly. This behaviour has been resolved. VersionAvailable frombeta12 August 2026stable19 August 2026

There were instances where time-based flows were activated without taking the local time zone into account. As a result, these typically ran two hours later than the set time. This issue has been resolved. VersionAvailable frombeta11 August 2026stable12 August 2026

From now on, flow runs can be stopped if the Search returns no results. The flow run can be continued afterwards.VersionAvailable frombeta7th August 2026stable12th August 2026

The Error handling control is now available in Flow Studio. It detects faulty objects within a flow and allows you to decide how these should be handled.When you create a new flow in Flow Studio, you will find the new control among the controls. Simply drag it to the desired location. Various settings are then available to determine how to deal with an error in the flow.An overview of the settings can be found in the manual.  Version Available from beta 30 July 2026 stable 5 August 2026

As of today, the Flow action Refund in the the PayPal section has a new option for the refund usage for payments that are directly attached to an order.VersionAvailable frombeta16th July 2026stable22nd July 2026

The new flow action Octopia: Send invoice to Octopia is now available in the Flow Studio under Actions » Plugin (Legacy). You can use this flow action to automate sending invoices to Octopia.Note: Due to the process by which invoice uploads are handled by Octopia this flow can fail to send an invoice to the marketplace in some cases, e.g. when the submitted invoice is in an unsupported file format. Status notifications for this flow are automatically added in the Notes section of each affected order in the Orders » Orders menu. You can use these status notifications to check whether and why an invoice was not successfully sent to Octopia.VersionAvailable frombetaJuly 2 2026stableJuly 8 2026

Additional settings have been added for the time-based trigger.For the options Minutes and Hourly under Frequency, a time frame (start and end time) can now be selected to specify when a flow should or should not be executed. This is useful, for example, when a task needs to be performed overnight. VersionAvailable frombeta15 June 2026stable17 June 2026

When a flow containing a print/save step is executed and a print/save event occurs AND a print/save configuration is present AND automatic execution is enabled, the print/save operation will be carried out in the background.Furthermore, the execution of such steps should resume immediately after login, provided the above settings are met (automatic execution and configuration). VersionAvailable frombeta10 June 2026stable17 June 2026