Use the Flow controls

In Flow Studio, controls are one of the two element types that you use to configure flows. The other element type: The actions).

The following control types are available:

The Search control is typically used at the beginning of a time-driven or manual flow. However, it can be placed anywhere in the flow, and can therefore be used to to cover a wide ranging use cases.

Search retrieves all orders in the system that match the respective filter settings. It then transfers them as a batch into the next flow step.

Additional settings for the Search control

Practical examples for the Search control:

Examples will be added later.

2. The Branch control

The Branch control is typically used in flows where the flow run occurs sequentially for individual orders (stream processing). This is the case for event-driven flows.

The Branch control creates two possible flow branches at the respective flow point, determining as follows:

  • If the order meets the set filter criteria, it flows into the True branch.

  • If the order does not meet the set filter criteria, it flows into the False branch.

Note: If the order does not meet the set filter criteria and there are no actions in the False branch, then the flow run aborts for the order concerned.

Additional settings for the Branch control

Setting Explanation

The name of the branch is "True" / "False"

Here you can optionally enter a name for the True and False branches. If you don’t enter anything, the branches will keep the names True and False.

Object type

Here, you select the dataset type that the control will evaluate. Currently, the only option available is Order, which is selected by default. This is because Flow currently processes orders only. Later down the line, Flow will be expanded to support other dataset types.

Note: PlentyONE Flow was designed for gradual expansion. In future, its capabilities will extend beyond order handling alone.

Filter settings

Here, you set the criteria for the transition to the True branch.
Note: The filter settings are mandatory settings.
Note on moving branches

The branch element is considered a Flow step that can comprise several actions as a control element. Branches can be placed within other branches, but there is one restriction: Due to logical relationships, a parent branch cannot be moved below its child branch using drag and drop.
Practical example for the Branch control:

For a simple example of the branch element, let’s take a flow that checks incoming orders by order value and, depending on the order value, either sets a tag or sends an email to the sales department. The flow starts with the trigger Order of the type Sales order.

The Branch control element then checks if the order value is less than 100. If the value is less than 100, the flow goes to the True branch and a tag is set for this order with the next action. If the value is more than 100, the flow goes to the False branch and an email is sent to the sales department with the next action.

Example for a branch

3. The Start control

The Start control is used to trigger an additional parallel flow for the orders that reach the flow step.

Additional settings for the Start control

Setting Explanation

Additional flow

Select the flow from the dropdown list that will be triggered in addition at that flow step.

Processing type

From the dropdown list, select whether the additional flow is to use batch processing (all data sets processed together, as in time-based flows) or stream processing (data sets processed individually in sequence, as in event-based flows).
Practical examples for the Start control:

Examples will be added later.

4. The Adapter control

The Adapter control introduces a new, related object type into the flow.

For example: You initially set your flow up to process return orders. At a certain point in the flow, you want the subsequent steps to apply to the related sales orders. To introduce the related sales orders to the flow, you would use the Adapter control.

Depending on your settings, the steps after the Adapter are executed either for both the current and new object types, or exclusively for the new object type.

What does the term "object type" mean?

The term “object type” refers to the category of data being processed by the flow. For example, *return order”, “sales order” and “credit note” are all different object types.

Additional settings for the Adapter control

Setting Explanation

Aktion type

Select the type of action to be performed.

Available actions:

Add object type
Adds a new object type to the current object type. Subsequent steps are executed for both the current and the new object type.

Replace object type
Replaces the current object type with the new, related object type. Subsequent steps are executed exclusively for the new object type.
Note: If the current order has no relation to an object of the selected type, the steps after the Adapter are skipped and a warning message for the flow run is displayed in Flow Tracker. The flow run will not be marked as Completed.

Replace object type, if available
Replaces the current object type with the new, related object type, provided such relation exists. Subsequent steps are executed only for the new object type.
Note: If the current order has no relation to an object of the selected type, the current object remains in the flow and all further steps are applied to it, as if the Adapter did not exist.*

From
(only applicable when replacing an object type)

Select the object type to be replaced.

To
(only applicable when replacing an object type)

Select the object type that will replace the current object type.

Notes:

  • If the Adapter control is used in a simple, branchless flow, it applies to all subsequent steps. This means that if you use it to replace an object type, the flow for the replaced object type ends there.

  • If the Adapter is used within a branch, it applies only to the steps inside that branch and that come after the Adapter.
The Adapter control is set to be gradually extended

Currently, the Adapter control allows you to add related origin orders to the flow.

For example: If the flow is processing a return order, the Adapter can be used to supplement or replace the return order with the original sales order to which it relates.

The Adapter is set to be gradually extended to allow for switching between a wider range of object types.
Practical examples for the Adapter control:

Examples will be added later.

5. Adding a control to a flow

To add a control to a flow, proceed as follows:

  1. Open an existing flow or create a new flow in the Automation » Flow Studio menu.

  2. Identify the flow position at which to place the control.
    Note: The available positions are the empty white fields or the spots where the plus signs appear.

  3. Open the Controls tab in the left-hand column.
    → The tab with the available controls opens.

  4. Select the appropriate control. Refer to the explanations for the controls Search, Branch, and Start flow

  5. Add the control to the flow by dragging it to the appropriate flow position.

  6. Perform the additional settings for the control. These appear in the column to the right of the canvas. Refer to the explanations for the controls Search, Branch, and Start flow

  7. Make the filter settings for a control of type Search or Branch. Refer to the explanations in the section Using filter settings for the Search and Branch controls

6. Using filter settings for the Search and Branch controls.

When you open the filter settings for the Search or Branch control as described in the section Adding a control to a flow, the following window appears:

Automation flow control filters window
Explanation of the structure of the Filter settings window

  • 1. Filter: Here, you select the appropriate filters. Information about the available filters can be found in the section Available filters.
    Note: The selection of filters is larger for Branch than for Search.

  • 2. Operator: Use an operator to define the relationship between the order-specific field to be checked by the filter and the value entered in the input field (4). You can find more details about the available operators in the section Using operators.

  • 3. Entry field: Here, you enter or select the values to filter by. For more information on the input field of a specific filter, refer to the Explanation column in the table Using filters.

  • 4. AND & OR, conditions, and nested levels: Here, you define the filter conditions. You can find detailed information about the four functions in the section Using AND & OR, conditions, and nested levels.

6.1. Available filters

You select the filters for the Flow controls Search and Branch from a dropdown list. There, the filters are divided into categories. Click on one of the following filter categories for explanations of the available filters.

Customer filter category

Table 1. Customer filter category
Filter Explanation

Age rating invoice address

Filters orders based on whether the invoice address has been assigned an age rating.

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Select the age approvals by which to filter from the dropdown list.

Customer class

Filters orders by customer class.

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Select the customer class to filter by from the dropdown list.

Customer rating

Filters orders by customer rating.

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Select the customer ratings to filter by from the dropdown list.

Note: Customer ratings must be set up in the menu to appear in the dropdown list.

Customer type

Filters orders by customer type.

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Select the customer types to filter by from the dropdown list.

Number of orders

Filters orders based on the number of orders previously placed by the respective customer.

Additional settings:

Setting 1:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Enter a value to filter by it.

Setting 2:

  • Select Is in (IN) or Is not in (NIN) from the dropdown list. Refer to the explanations in the section Using operators.

  • Select the order types to filter by from the dropdown list.

Document filter category

Table 2. Document filter category
Filter Explanation

Available documents

Filters orders based on whether they contain certain documents.

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Select the document types to filter by.

Global filter category

This filter category contains filter options of a global nature that cannot be assigned to any of the other categories.

Table 3. Global filter category
Filter Explanation

Active user

Filters orders by the person who triggers the process activated by the event.

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Select the persons to filter by from the dropdown list.

Day of month

Checks the day of the month on which the flow run occurs and, based on this, moves directs to the next flow step.

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Enter the respective day of the month as a number.+

Example of how to use the filter Day of month
Filter Operatoren Heute +/- Tage

Day of month

Is less than (<)

15

If the flow step is configured with these settings, the following occurs:
If the flow run occurs before the 15th of the month, orders reaching this step are directed to the True branch. Otherwise, they are directed to the False branch.

Month

Checks the month in which the flow run occurs and, based on this, directs orders to the next flow step.

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Select the appropriate month from the dropdown list.

Example of how to use the filter Month
Filter Operatoren Heute +/- Tage

Month

Is in (IN)

December

If the flow step is configured with these settings, the following occurs:
If the flow run occurs in December, orders reaching this step are directed to the True branch. Otherwise, they are directed to the False branch.

Weekday

Checks the weekday on which the flow run occurs and, based on this, directs orders to the next flow step.

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Enter the respective day of the week.+

Example of how to use the filter Weekday
Filter Operatoren Heute +/- Tage

Day of month

Is in (IN)

Monday

If the flow step is configured with these settings, the following occurs:
If the flow run occurs on a Monday, orders reaching this step are directed to the True branch. Otherwise, they are directed to the False branch.

Order filter category

Table 5. Order filter category
Filter Explanation

Offer valid until

Filters orders based on their Offer valid until date.

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Enter a number of days relative to today (today = day of the flow run) to filter data sets whose offer valid until date is on the corresponding day or within the corresponding period.
    Note: The number 0 represents today, -1 yesterday, +1 tomorrow, etc.

Examples of using the Offer valid until filter:
Filters Operators Today +/- days

Offer valid until

Is less than (<)

-1

If these settings apply and a flow run occurs on 10 November, then the flow step will filter only orders whose Offer valid until date is before 9 November.

Filters Operators Today +/- days

Offer valid until

Is equal to (=)

(Feld leer lassen)

If these settings apply and a flow run occurs on 10 November, then the flow step will filter only orders whose Offer valid until date is 10 November.

Note: The valid until date for an offer is stored in the menu Orders » Orders » [Select order type "Offer"] » Portlet: Offer Details.

Invoice amount

Filters orders by their invoice amount.

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Enter the appropriate invoice amount.

Items included

Filters orders by contained items.

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Enter the item IDs to filter by.

Open invoice amount

Filters orders by their open invoice amount.

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Enter the values to filter by.

Order with return package number

Filters orders based on whether they contain return package numbers.

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Select Yes or No from the dropdown list to filter data records with or without return package numbers.

Order tags

Filters orders based on the tags assigned to them.

Additional settings:

  • Choose from the following operators:

    • Orders without tags

    • Orders without these tags

    • Orders with exactly these tags

    • Orders with at least these tags

    • Orders with at least one of these tags

  • Depending on the selected operator, you choose the appropriate tags from the dropdown list.

Order entry date (days)

Filters orders by order entry date.

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Enter a number of days relative to today (today = day of the flow run) to filter data sets whose order entry date is on the corresponding day or within the corresponding period.
    Note: The number 0 represents today.

Examples of using the Order entry date (days) filter:
Filters Operators Today +/- days

Order entry date

Is less than (<)

-1

If these settings apply and a flow run occurs on 10 November, then the flow step will filter only orders whose Order entry date is before 9 November.

Filters Operators Today +/- days

Order entry date

Is equal to (=)

(Feld leer lassen)

If these settings apply and a flow run occurs on 10 November, then the flow step will filter only orders whose Order entry date is 10 November.

Order weight

Filters orders based on the total weight of all items contained in the order.

Additional settings:

Setting 1:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Enter a value.
    Note: It is only possible to insert whole numbers.

Setting 2:

  • Select the operator is equal to (=).

  • Select the weight unit (g or kg) to filter by.

Order status

Filters orders by order status.

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Select the statuses to filter by from the dropdown list.

Order type

Filters orders by order type.

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Select the order types to filter by from the dropdown list.

Click and Collect

Filters orders based on the shipping method Click & Collect.

Additional settings:

  • Select the operator is equal to (=).

  • Select Yes or No from the drop-down list.

Note: Click & Collect can only be used for orders that are referred from eBay UK and have the UK as their delivery country. For further information, refer to the chapter on Click & Collect.

DHL Packstation/Post office

Filters orders based on whether the delivery address contains a valid or incorrect DHL Packstation or post office.

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Select Valid or Invalid from the dropdown list.

Order property

Filters orders based on their order properties.

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • From the dropdown list, select the properties to be applied for the filter.

Guest order

Filters orders based on whether they are guest orders.

Additional settings:

  • Select the operator is equal to (=).

  • Select Yes from the dropdown list to filter for guest orders, or No to filter for data sets that are not guest orders.

Referrer

Filters orders by their referrer.

Additional settings:

  • Select Is in (IN) or Is not in (NIN) from the dropdown list. Refer to the explanations in the section Using operators.

  • Select the referrers to filter by from the dropdown list.

Note: The overview of the order referrers is in the menu Setup » Orders » Order referrer

Warehouse

Filters orders by their warehouse ID and/or warehouse type

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Select the warehouse IDs to filter by from the dropdown list.

  • Select the operator is equal to (=).

  • Choose whether to filter by Incoming items warehouse or Outgoing items warehouse.

Last status change (days)

Filters data records based on the date of their last status change.

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Enter a number of days relative to today (today = day of the flow run) to filter data sets whose last status change is on the corresponding day or within the corresponding period.

Examples of using the Last status change (days) filter:
Filters Operators Today +/- days

Last status change

Is less than (<)

-1

If these settings apply and a flow run occurs on 10 November, then the flow step will filter only orders whose Last status change is before November 9th.

Filters Operators Today +/- days

Last status change

Is equal to (=)

0

If these settings apply and a flow run occurs on 10 November, then the flow step will filter only orders whose Last status change date is November 10th.

Supplier

Filters orders based on the assigned supplier.

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Select the suppliers to filter by from the dropdown list.

Delivery country

Filters orders by delivery country.

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Select the countries of delivery to filter by from the dropdown list.

Dunning level

Filters orders by dunning level.

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Select the dunning levels to filter by from the dropdown list.

Client

Filters orders by client (Webshop).

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Select the clients to filter by from the dropdown list.

Postcode

Filters orders by postcode.

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Enter a number to filter by the corresponding postcode/postcode ranges.
    (You can, for example, filter by specific postcodes, by those starting with a certain digit, or by those smaller than 3000.)

  • Select the operator is equal to (=).

  • Select the address type of the postcode. (For example, should the filter apply to the postcode in the billing address or the shipping address?)

Redeemed coupon code

Filters orders according to whether a specific coupon code was used for them.

Additional settings:

  • In the Operator field, select Is equal (=).

  • Enter the corresponding coupon code.

Return date (days)

Filters orders by return date.

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Enter a number of days relative to today (today = day of the flow run) to filter data sets whose return date is on the corresponding day or within the corresponding period.

Examples of using the Return date (days) filter:
Filters Operators Today +/- days

Return date

Is less than (<)

-1

If these settings apply and a flow run occurs on 10 November, then the flow step will filter only orders whose Return date is before November 9th.

Filters Operators Today +/- days

Return date

Is equal to (=)

0

If these settings apply and a flow run occurs on 10 November, then the flow step will filter only orders whose Return date is November 10th.

Outgoing items status

Filters orders based on whether the goods dispatch is still open or already booked.

Additional settings:

  • Select the operator is equal to (=).

  • Select Open or Booked from the dropdown list.

Phone number

Filters orders by telephone number.+

Additional settings:
This filter option consists of three settings:

Setting 1:

  • Select the operator is equal to (=).

  • Select from the dropdown list Exists or Does not exist to filter by the presence of a phone number.

Setting 2:

  • Select the operator is equal to (=).

  • Choose Invoice address or Shipping address to filter data sets based on which address contains the phone number.

Setting 3:

  • Select the operator is equal to (=).

  • Enter the minimum length of the phone number. Example: If you enter 4 as the minimum length, the system will filter for phone numbers that consist of 4 or more digits.

Loyalty program

Filters orders by loyalty program.

Additional settings:

  • Select Is in (IN) or Is not in (NIN) from the dropdown list. Refer to the explanations in the section Using operators.

  • Select the loyalty programs by which you want to filter.

Available loyalty programs
Table 4. Available loyalty programs
Operator Explanation

=

ALL

All orders will be filtered.

Without

Only orders not belonging to any loyalty program are filtered.

Amazon SameDay

Only Amazon orders that have to be shipped on the same day are filtered.

Amazon NextDay

Only Amazon orders that have to be shipped on the following day are filtered.

Amazon SecondDay

Only Amazon orders that have to be shipped on the day after tomorrow are filtered.

Amazon Prime

Only Amazon Prime orders will be filtered.

Amazon Prime SameDay

Only Amazon Prime orders that have to be shipped on the same day are filtered.

Amazon Prime NextDay

Only Amazon Prime orders that have to be shipped on the following day are filtered.

Amazon Prime SecondDay

Only Amazon Prime orders that have to be shipped on the day after tomorrow are filtered.

eBay Plus

Revenue

Filters orders by revenue.

Additional settings:
This filter option consists of three settings:

Setting 1:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Enter the value to filter by it.

Setting 2:

  • Select the operator is equal to (=).

  • Select the time period from the dropdown list to filter by.

Setting 3:

  • Select the operator is equal to (=).

  • Select the order type from the dropdown list to filter by.

VAT number

Filters orders based on the presence of a VAT number.

Additional settings:

  • Select the operator is equal to (=).

  • Select from the dropdown list Available or Not available to filter based on the presence (or absence) of a VAT number.

Variations included

Filters orders by the variations they contain.

Additional settings:

  • Select Is in (IN) or Is not in (NIN) from the dropdown list. Refer to the explanations in the section Using operators.

  • Enter the variation IDs to filter by.

Agreement of data transmission to the shipping service provider

Filters orders based on whether an agreement for data transmission to the shipping service provider exists for them.

Additional settings:

  • Select the operator is equal to (=).

  • Choose from the dropdown list Granted or Not granted to filter orders based on whether the consent for data transmission to the shipping service provider has been granted or not.

Shipping method

Filters orders by shipping method.

Additional settings:

  • Select Is in (IN) or Is not in (NIN) from the dropdown list. Refer to the explanations in the section Using operators.

  • Choose from the dropdown list the shipping method to filter by.

Shipping costs

Filters order by their gross shipping costs.

Additional settings:

Setting 1:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Enter the value to filter by it.

Setting 2:

  • Select the operator is equal to (=).

  • Choose from the dropdown list Granted or Not granted to filter orders based on whether the consent for data transmission to the shipping service provider has been granted or not.

Shipped

Filters orders based on whether they are shipped, not shipped, or scheduled for future shipping.

Additional settings:

  • Select the operator is equal to (=).

  • Select the value from the drop-down list to filter by it.

Estimated delivery date (days)

Filters orders by estimated delivery date.

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Enter a number of days relative to today (today = day of the Flow execution) to filter data records whose expected delivery date is on the corresponding day or within the corresponding period.
    Note: The number 0 represents today, -1 yesterday, +1 tomorrow, etc.

Examples for the use of the filter Expected shipping date (Days)
Filters Operators Today +/- days

Estimated delivery date

Is less than (<)

-1

If these settings apply and a flow run occurs on 10 November, then the flow step will filter only orders whose estimated delivery date is before November 9th.

Filters Operators Today +/- days

Estimated delivery date

Is equal to (=)

(Feld leer lassen)

If these settings apply and a flow run occurs on 10 November, then the flow step will filter only orders whose estimated delivery date is November 10th.

Estimated shipping date (days)

Filters orders by estimated shipping date.

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Enter a number of days relative to today (today = day of the flow execution) to filter data records whose expected shipping date is on the corresponding day or within the corresponding period.
    Note: The number 0 represents today, -1 yesterday, +1 tomorrow, etc.

Examples for the use of the filter Expected shipping date (Days)
Filters Operators Today +/- days

Estimated shipping date

Is less than (<)

-1

If these settings apply and a flow run occurs on 10 November, then the flow step will filter only orders whose estimated shipping date is before November 9th.

Filters Operators Today +/- days

Estimated shipping date

Is equal to (=)

(Feld leer lassen)

If these settings apply and a flow run occurs on 10 November, then the flow step will filter only orders whose estimated shipping date is November 10th.

Outgoing items booked on date (days)

Filters data records by the date on which their outgoing items were booked.

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Enter a number of days relative to today (today = day of the flow run) to filter data records whose date of outgoing items is on the corresponding day or within the corresponding period.
    Note: The number 0 represents today, -1 yesterday, +1 tomorrow, etc.

Examples of using the Outgoing items booked on date (days) filter:
Filters Operators Today +/- days

Outgoing items booked on date (days)

Is less than (<)

-1

If these settings apply and a flow run occurs on 10 November, then the flow step will filter only orders whose*Outgoing items booked on date (days)* is before November 9th.

Filters Operators Today +/- days

Outgoing items booked on date (days)

Is equal to (=)

(Feld leer lassen)

If these settings apply and a flow run occurs on 10 November, then the flow step will filter only orders whose*Outgoing items booked on date (days)* is November 10th.

Payment method

Filters orders by payment method.

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Select the payment methods to filter by from the dropdown list.

Payment due date (days)

Filters orders by payment due date.

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Enter a number of days relative to today (today = day of the flow run) to filter data records whose payment due date is on the corresponding day or within the corresponding period.
    Note: The number 0 represents today, -1 yesterday, +1 tomorrow, etc.

Examples of using the Offer valid until filter:
Filters Operators Today +/- days

Payment due date (days)

Is less than (<)

-1

If these settings apply and a flow run occurs on 10 November, then the flow step will filter only orders whose*payment due date* is before November 9th.

Filters Operators Today +/- days

Payment due date (days)

Is equal to (=)

(Feld leer lassen)

If these settings apply and a flow run occurs on 10 November, then the flow step will filter only orders whose*Payment due date* is November 10th.

Order item filter category

Table 6. Order item filter category
Filter Explanation

Number of warehouses

Filters orders by the number of associated warehouses.

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Enter the number of warehouses to filter by.

Number of positions

Filters orders based on the number of order items they contain.

Additional settings:

Setting 1:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Enter the number of order items to filter by.

Setting 2:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Enter the type of order items to filter by.

Order item type

Filters orders based on the order item types they contain.

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Enter the type of order items to filter by.

Property of the order item

Filters orders based on the properties of the order item contained.

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Select the properties by which you want to filter.

Quantity of order items

Filters orders based on the number of order items of a specific order item type that they contain.

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Enter the number by which to filter.

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Select the order item types to filter by from the dropdown list.

Item type included

Filters orders based on whether they contain certain item types.

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Select the item types to filter by from the dropdown list.

Value of order items

Filters records by the value of the order items that they contain.

Additional settings:
This filter option consists of two settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Enter an item value to filter by.
    +

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Select from the dropdown list whether to filter by gross value or net value.

Payment filter category

Table 7. Payment filter category
Filter Explanation

Payment receipt date

Filters orders by Incoming payment date.

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Enter a number of days relative to today (today = day of the flow run) to filter orders whose payment receipt date is on the corresponding day or within the corresponding period.

Examples of using the Payment receipt date filter:
Filters Operators Today +/- days

Incoming payment date

Is less than (<)

-1

If these settings apply and a flow run occurs on 10 November, then the flow step will filter only orders whose*incoming payment date* is November 10th.

Filters Operators Today +/- days

Incoming payment date

Is equal to (=)

(Feld leer lassen)

If these settings apply and a flow run occurs on 10 November, then the flow step will filter only orders whose*incoming payment date* is 10 November.

Payment status

Filters data sets by payment status.

Additional settings:

  • Select the appropriate operator. Refer to the explanations in the section Using operators.

  • Select the payment status to filter by from the dropdown list.

6.1.1. Using AND & OR, conditions, and nested levels

Table 8. Operators in the Flow filter settings
Setting Explanation

Adding conditions and sub-conditions:

Condition(playlist_add)

Use a condition to define the criteria that the orders to be filtered must meet. The first condition is already added and ready to be set. Use playlist_add to add additional conditions.

Nested level (library_add)

Use the nested levels to create sub-conditions within a condition. This allows you to build complex hierarchies within conditions.

Defining the relationships between the conditions:

AND

Select AND if the orders to be filtered must meet all linked conditions.

OR

Select OR if the orders to be filtered must meet one of the linked conditions.
Example of a widget restriction

image:

In this example, the filter first checks whether the orders meet condition 1. If this is the case, the filter then checks whether either the orders meets subcondition I or subcondition II.

6.1.2. Using operators

Use the operators listed below to define within the filter settings how the value in the order to be checked is compared with the value in the input field.

Note: For many of the filters in Flow, only some of operators listed below are available.

Table 9. Operators in the Flow filter settings
Operator Explanation

=

Is equal to
Filters for orders whose value matches the value specified in the input field.
Example:_I filter by orders whose ID is _10.

IN

Is in
Filters for orders that contain one of the values specified in the input field.
Example: I filter for orders that contain at least one of the following items: 102, 103, 104.

NIN

Is not in.
Filters for orders that do not contain any of the values specified in the input field.
_Example:* I filter for orders that do not contain any of the following items: 102, 103, 104.

>=

Is greater than or equal
Filters for orders whose value is equal to or greater than the value specified in the input field.
Example: I filter for orders where the postcode in the invoice address is 2000 or greater.

⇐

Is less than or equal to
Filters for orders whose value is equal to or less than the value specified in the input field.
Example:* I filter for orders where the postcode in the invoice address is _2000 or smaller.

>

Is greater than
Filters for orders whose value is greater than the value specified in the input field.
Example:_I filter for orders whose total weight is _greater than 5 kg.

<

Is less than
Filters for orders whose value is less than the value specified in the input field.
Example:_I filter for orders whose total weight is _less than 5 kg.

[]

Is between
Filters for orders whose value lies between the value specified in the input field.
Example: I filter for orders that were received between 1 and 30 July 2022.

Starts with
Filters for orders whose value begins with the value specified in the input field.
Example: I filter for orders where the postcode in the invoice address begins with 3.

Does not start with
Filters for orders whose value does not begin with the value specified in the input field.
Example: I filter for orders where the postcode in the invoice address DOES NOT begin with 3.

∃

Exists
Filters for orders that contain a value in the field that corresponds with input in the Filter field.
Example: I filter for orders that contain an _Offer valid until _date.