Using Advanced Filters

Filters let you add conditional logic to services in the app, such as the Order Routing Engine. By defining conditions on records like orders, shipments, or products, you control how the app processes those records, for example, which fulfillment location is selected for an order.

Some tables in Pipe17 support advanced filtering in addition to the surface-level quick filters. This article covers advanced queries done using filters.

Screenshot 2024-08-08 at 4.21.48 PM.png

How it works

Each filter is built from two components:

  • Entity type: The record the filter applies to. Filters support a range of entity types, including orders, destinations (order regions), products, locations, fulfillments, shipments, arrivals, and returns. The entity type determines which fields are available as conditions. For example, a filter with the entity type Orders can only reference fields that exist on an order.
  • Operators: The conditions that determine when the filter applies. You can add multiple conditions and combine them with AND or OR logic:
    • AND: All conditions must be met for the filter to apply.
    • OR: The filter applies when at least one condition is met.

How to create a filter

  1. Navigate to Settings → Saved Filters.
  2. Click Create in the top right corner.
  3. Select an Entity Type, such as Orders or Products.
  4. Add one or more conditions using the available operators.
  5. Choose AND or OR to define how multiple conditions combine.
  6. Save the filter by clicking Create.

How to apply a filter in the Order Routing Engine

Filters are most commonly used in the Order Routing Engine to determine which location fulfills an order. The two filter types you'll work with most in routing rules are:

  • Order filters: Conditions on the order itself (entity type Orders), such as the order total or sales channel.
  • Destination filters: Conditions on where the order ships, such as the destination state or country.

Other entity types, such as products or locations, are generally used for filtering table views elsewhere in the app rather than in routing rules.

To add a filter to a routing rule:

  1. Navigate to Integrations and open your Order Routing Engine.
  2. Go to Routing Rules.
  3. Click Add Filter.
  4. Define your conditions in the pop-up window. The logic works the same way as in the Filters section.
  5. Save the rule. The filter now applies to the locations covered by that routing rule.

Example

Suppose you want orders over $200 shipping to California to route to your West Coast warehouse. On the routing rule that points to the West Coast location, add an order filter with the condition order total is greater than 200, and a destination filter with the condition state is California. The rule then applies only to orders that meet both.


Advanced filters on table pages

Some tables in the app, such as the Products table, support advanced filtering in addition to the quick filters at the top of the page. Advanced filters use the same condition logic described in How it works, and support more precise queries. The examples below use the advanced filter on the Products table.

Filter for bundles containing a specific SKU

Suppose a bundle product, EMOCK-BNDL, has two bundle items: EMOCK-TEAPOT and EMOCK-TEACUP. To find all products where EMOCK-TEAPOT is a bundle item:

  1. Set the filter field to Bundle Items SKU.
  2. Enter EMOCK-TEAPOT as the value.
  3. Select Contains as the operator. Because this field is an array of SKUs, Contains matches any product where EMOCK-TEAPOT is one of the SKUs in its bundle items.
Screenshot 2024-08-08 at 4.46.06 PM.png

Filter for products with mapped SKUs

Products can have channel SKUs that map the Pipe17 SKU to the equivalent SKU in a target integration when the two differ. To find all products with at least one channel SKU defined:

  1. Set the filter field to Published SKU.
  2. Select regex as the operator.
  3. Enter . (a period) as the value. In regex, a period matches any single character, so the filter returns every product with at least one published SKU.
Screenshot 2024-08-08 at 4.50.40 PM.png

Any vs. all conditions

Table filters combine multiple conditions using the same AND/OR logic described in How it works, labeled All and Any:

  • All: Results must match every condition (AND). This is the default.
  • Any: Results match at least one condition (OR).

For example, to find products that either do not track inventory or are taxable, add both conditions and change the filter setting from All to Any.

Screenshot 2024-08-08 at 5.17.11 PM.png

Need Help?

If you need additional assistance:

We're here to help you succeed with your operations.

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.

Have more questions?
Submit a request
Share it, if you like it.