This guide explains how to effectively use the filtering mechanism within Fozzels to precisely select a subset of products based on attribute values, ensuring content generation is targeted and efficient.
1. Accessing the Filtering Options
Filtering options are available in two primary locations:
Content Flow Creation: To define the specific product batch a flow will process, edit an existing flow (or create a new one) and go to the "Flow Selection & Prompt" tab.
Product Catalog:
2.1 Enable the "Advanced filter" toggle. This opens a panel where you can add "Add condition" and "Add condition group" for complex logic.
2.2 Inline Filtering: Filter products using input fields or dropdown lists located directly in the column headers of the product table (available for attributes with the Filterable flag enabled).Crucially: In the Catalog, you can combine inline filters by applying conditions to multiple columns simultaneously (e.g., filtering by SKU AND by Brand).
2. Filtering by Value Conditions
This filtering type applies to text, numerical, and multi-select attributes.
Equal: The attribute value must exactly match the entered value. Example: Show only products where
Color
equalsBlue
.Not equal: Show all products except those that exactly match the entered value. Example: Show all products where
Material
is notCotton
.Is empty: Show only products where the selected attribute has no value (is blank). Example: Find products with an empty
Short Description
.Is not empty: Show only products where the selected attribute contains a filled value. Example: Find products that have a filled
Manufacturer
name.Contains: The attribute value must contain the entered fragment of text or number. Example: Find all products where
Name
contains the wordSummer
.Doesn't contain: The attribute value must not contain the entered fragment of text. Example: Exclude products whose
SKU
does not containDISCOUNT
.In / Not in: The attribute value must match one of the multiple values entered (separated by commas) or must not match any of them. Example (In): Show products where
Size
isS, M, L
.Begins with / Ends with: Find products by the starting or ending characters of the value. Example: Find products whose
SKU
begins withP_
.Is null / Is not null: Technical conditions to correctly handle system-level empty or non-empty values.
3. Filtering by Date Conditions
This type applies to attributes with a date format, allowing you to filter based on chronology (e.g., created_at
, updated_at
).
Is empty / Is not empty: Shows records where the date field is absent or filled. Example: Find all products without an
update date
.Equal: Shows records where the value exactly matches the entered date. Example: Find all products created on
2024-01-01
.Less: Shows records where the date value is chronologically before the entered date. Example: Find all products updated before
last month
.Greater: Shows records where the date value is chronologically after the entered date. Example: Find all new products updated after
yesterday
.Less or equal / Greater or equal: Includes the entered date in the result set. Example: Find all products updated on or after
01-01-2024
.
4. Filtering by Product Images
This special filtering type is available in the Catalog via the inline filter in the Thumbnail column. It is critically important for content generation initiatives that use multimodal models.
Image Exists: Show only those products that have an attached image.
Image Missing: Show only those products for which an image is missing.
5. Grouping Conditions (Advanced Logic)
You can build highly specific product batches using multiple conditions and groups.
Adding Multiple Conditions: To filter by several attributes (e.g.,
Color = Blue
ANDSize = M
), simply click "Add condition" multiple times.Condition Group: Clickin “Add condition group” allows you to combine conditions using complex logic (e.g., (
Category = Shirts
ANDPrice > 50
) OR (Category = Jackets
)).
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article