Product groups
Group products by category, schema or a saved view, and know which of those a price rule, a bulk edit or the API can target.
Updated 23 September 2026
- Why
- Prices, edits and reports are set for sets of products, not one SKU at a time.
- How
- Set the category and schema on import or with Bulk edit, and save a filter as a view on
/app/catalog.
What each grouping reaches
| Grouping | Set by | Used by |
|---|---|---|
| Category | The category core field | Pricing rules and special prices, bulk edit, the category filter on the products API |
| Schema | The product's schema | Pricing rules and special prices, bulk edit, the facet rail |
| Saved view | Views, then a name for the current filters | Reopening a filtered grid and selecting all of it for a bulk edit. Kept for you alone, in this browser |
Save a view
- Step 1.
Filter the Products grid with the facet rail. A text search is not saved in a view.
- Step 2.
Open Views, type a View name and choose Save.
- Step 3.
Open the view later, tick a row and choose Select all … matching to act on every product in it.
The catalogue filter rail over a 300 endmill file, narrowed by end type, flutes, coating and diameter for one request line to the one product that fits it.
From a real test file
A price rule targets a single product, a category or a schema. A saved view is a filter, not a pricing scope: to price a set that is neither, give it a category first with Change category.
Related
- Bulk editingChange many products at once, from a few ticked rows to everything matching a filter, with an audit record of each run.
- Quantity rulesSet a price ladder that lowers the unit price as the quantity rises, for a product, a category, a schema or a service.
- Schemas and fieldsDescribe a product family with a schema of typed fields, and know which fields the AI matches an enquiry on.