Corresponding to the event action with the same function, the action Transfer shipping permission to FBA has also been added in Flow, which authorises shipping via Amazon FBA.  VersionAvailable frombeta29 April 2026stable6 May 2026

An additional filter has been introduced in FlowStudio in the Search control to filter orders based on the package number. VersionAvailable frombeta29 April 2026stable6 May 2026 

The filter Order shipment registered is now also available as a search filter in the search control. VersionAvailable frombeta24 April 2026stable24 April 2026

An option has been added to the Assign serial number interactive action, enabling new serial numbers that do not yet exist in the system to be created and assigned directly. VersionAvailable frombeta24 April 2026stable24 April 2026

If you have previously started a flow for multiple orders (in Flow Studio or in the Orders menu), one flow per order was started.We are now introducing the option to start only one flow for all selected or entered orders, both already within the flow and when starting via the group function in the Orders menu. For this, there is a new setting called execution mode in the flow trigger.  The following options are availableOne flow per objectPrevious behaviour, each object (e.g. order) is executed in its own flow. One flow for all objectsAll selected (in the Orders menu) or specified (Flow Studio) jobs are executed in one flow. Current limit of the number of objects per flow is 200 objects. Select when starting a flow (default: one flow per object)Like One flow per object with the difference that users have the option to select a different option at execution (see images below). Select when starting a flow (default: one flow for all objects)Like One flow for all objects with the difference that users have the option to select a differ...

The names for flows have a maximum length of 63 characters. During the migration of actions from the action manager, this caused an error if the name was longer. From now on, the name will be truncated at the end and marked with three dots (...). VersionAvailable frombeta12 March 2026early12 March 2026stable12 March 2026

There were instances where the time zone affected the execution of defined time-based flows in an unexpected way.This has been fixed. Important note:If an unexpected execution time is detected, the time-based flow must be deactivated and the start time updated once in Flow Studio. VersionAvailable frombeta10 March 2026early10 March 2026stable11 March 2026

Until now, the delivery country filter for flows in the order search did not work and didn't return any results. This behaviour has been fixed.VersionAvailable frombeta27th February 2026early27th February 2026stable27th February 2026

Before, under specific circumstances, the action manager and time actions weren't working as intended. This behaviour has been fixed. VersionAvailable frombeta17th February 2026early17th February 2026stable17th February 2026

The following additional options have been added to the Flow action Create delivery orders:Split by warehouseSplit by shipping profileSplit by warehouse and shipping profileSplit by warehouse stock and net stock > 0Split by warehouse stock and net stock >= order item quantity VersionAvailable frombeta2 February 2026early11 February 2026stable18 February 2026

Under certain circumstances, it was possible for flows to be executed for orders even though the corresponding filters did not match (e.g. status did not match during a status change). This behaviour has been fixed.  VersionAvailable frombeta4 February 2026early4 February 2026stable4 February 2026

Two new optional columns have been added to the Flow Tracker overview, which show which user started a flow and from where.The same information is displayed in the detail view of a flow in Flow Tracker. VersionAvailable frombeta4 February 2026early11 February 2026stable18 February 2026

The flow action Register incoming payment has been added.With this action, the outstanding amount due is added to the order and the order is marked as paid. VersionAvailable frombeta29 January 2026early4 February 2026stable11 February 2026

As in the overview of the order UI via the group function, flows can now also be started from the detail view of a single order. All flows activated for the order UI are available in the selection. VersionAvailable frombeta30 January 2026early4 February 2026stable11 February 2026

The Item property filter did not take into account all item properties of all order items with variations when the operator EQUAL was used and the sub-filter was also set. As a result, it did not always work correctly. This has now been fixed. VersionAvailable frombeta26 January 2026early28 January 2026stable4 February 2026

Using float values in conjunction with >,>=, < or <= operators on flow filters (in the search or branches) could lead to incorrect resolving of the conditions. It could happen that only the integer values were compared. This behaviour has been fixed. VersionAvailable frombeta21st January 2026early21st January 2026stable28th January 2026 

In some cases, existing Flow configurations could not be saved when changing the event trigger. This error has been fixed.VersionAvailable frombeta19 January 2026early19 January 2026stable19 January 2026

The change from summer time to winter time was not taken into account, causing time-based flows to be executed at the wrong time. This issue has been fixed. All flows activated from now on will be executed in the user's time zone. Flows already active will not be changed and will continue to run in UTC (Universal Time).  VersionAvailable frombeta11 December 2025early7 January 2026stable14 January 2026

Previously, the date of the document could only be determined during manual document creation.It is now also possible to select the date of the document in the Create document Flow action.  VersionAvailable frombeta9 December 2025early7 January 2026stable7 January 2026

If multiple users had the same email address, this caused problems in the “Send email” action in the flows. If you had selected all emails, you could not deselect them using “Deselect all”; you had to deselect each option individually. This has been fixed: Each email is only listed once, even if different users have the same email address.  VersionAvailable frombeta2 December 2025early3 December 2025stable7 January 2026

All Netto actions in Flow were faulty and could not be executed. This issue has been resolved. VersionAvailable frombeta14 November 2025early14 November 2025stable14 November 2025

The “DHL Packstation/Post office” filter did not work correctly. This is because we combined two of the filters from the event procedures in Flow.We have introduced the option “No DHL Packstation/Post office,” which returns TRUE if neither a correct nor an incorrect DHL Packstation/Post Office is specified at the delivery address.  VersionAvailable frombeta30 October 2025early5 November 2025stable12 November 2025

In some cases the event-based trigger Document created >> Receipt did not work as intended. This behaviour has been fixed. VersionAvailable frombeta22. October 2025early29. October 2025stable05. November 2025

The filter for the warehouse did not work as expected in the order search control element.For this reason, the filter of the order search control element was split into a Warehouse (Order) filter and a Warehouse (Purchase order) filter.The branch filter remains unchanged.If you are already using the current Warehouse filter in the order search, it will be migrated to the Warehouse (Order) filter, as this is the current function of the filter. If you do not want to search for orders in this case, you will need to adjust the newly added Warehouse filter. VersionAvailable frombeta22 October 2025early22 October 2025stable29 October 2025

A new setting is available in all actions that allows you to decide whether or not an error trigger should be triggered in the event of an error in an action. The default behavior is not to trigger an error trigger.  VersionVerfügbar abbeta31 October 2025early5 November 2025stable12 November 2025

Under certain circumstances, inactive procedures were not displayed in the event procedures overview. This behaviour has been fixed.VersionAvailable frombeta20. October 2025early22. October 2025stable29. October 2025

An action called Change order owner was added to the Order group in Flow Studio. VersionAvailable frombeta17. October 2025early22. October 2025stable29. October 2025

When a user added two nested filters in an event-based flow and later changed the operator from OR to AND, the filters were deleted upon saving.This issue has been fixed — nested filters are now retained correctly when changing operators.VersionAvailableBeta10.10.2025Early15.10.2025Stable22.10.2025

Flows with the trigger “Order created” were not always executed correctly.As a result, some flows did not perform related actions, such as setting tags for guest orders.This issue has been fixed — flows are now triggered reliably for all relevant order types, including Sales order, Credit note, Delivery order, Return, and Incomplete order.VersionAvailableBeta09.10.2025Early09.10.2025Stable22.10.2025

A new filter group named SEPA has been added to Flow Studio. The new group contains the following filters: Type of debitType of SEBA mandatePayment frequencyIBAN, BICSEPA direct debit mandateVersionAvailable frombeta09. October 2025early15. October 2025stable22. October 2025