What a product set is#
A product set is a named rule that decides which products belong in scope. Every channel exports one or more product sets, and the Content review page can filter by them too.
Every project has one mandatory set called All products. It can't be renamed, deleted, or archived, and it automatically includes every product matched by every other active set in the project — so as you create more product sets, "All products" grows to cover them too. It's a union, not a separate list you maintain.
Two ways to build a set#
Sets are built from either or both of these, added together:
- Explicit picks — you individually add specific products to the set. Good for a hand-curated list (e.g., a promo). A project can have up to 1,000 individually-picked products in total.
- A query (a "dynamic" set) — you define a filter, and the set automatically includes whatever matches as your feed changes over time. Query-based sets are capped at 25 active queries per project.
A single product set can combine both: some explicitly-added products plus a query, unioned together.
What you can filter on#
The query builder — on the Product selection page, where you build and edit sets — supports:
- Product name — free-text match.
- Brands — pick from brand values found in your catalogs' feeds.
- Catalogs — restrict to one or more catalogs in the project.
- Product IDs — match specific feed product IDs.
- EAN/UPC/MPN IDs — match specific barcode/manufacturer IDs.
- Price range — list price (at least / less than) and sale price (at least / less than), independently.
- Google Categories — Google product taxonomy values from your feeds.
- Categories — your catalogs' own category values.
- Attributes — generic product attribute values from your feed.
- Availability — free-text match (e.g., in stock / out of stock, depending on your feed's values).
- On sale toggle.
Brand, category, Google category, product ID, and attribute filters are all first-class fields directly in this dialog — you don't need to fall back to a manual selection to use them.
A note on the barcode filter: EAN/UPC/MPN IDs only narrow down which products a query matches — they don't merge or deduplicate products across catalogs. Matching for content purposes (so the same product shows up once within a project) is by SKU; see How Renable works.
This is a different, richer set of fields than the read-only filter on the project's "Products used by this project" table or the Content review page, which filter an already-resolved list (by content type, image position, date added, or review state) rather than define a saved query.
Where product sets are used#
- Channels pick one or more product sets to export as a feed — see Working with channels.
- Content review can be filtered down to a specific product set.
- The project's Products used by this project table shows the resolved contents of a set (defaulting to "All products").
To actually build and edit sets — search feed entries, add/remove products, and publish your changes — see Selecting and publishing products.