Magidoc

Smart Groups

Use Smart group to merchandise an Experience with product groups that you define in Cloudshelf Manager . Smart groups are available on Standard and Premium. Each group belongs to one Experience. Nothing is created or changed in your online store.

A condition tests one product against a fixed value. There is no viewed product to compare with.

Quick example: Levi's under £50

#

  1. Open your Experience's Homescreen → Tiles settings and click Add Product Group.
  2. Choose Smart group, then Continue.
  3. Enter a name and select a tile image using the usual image editor.
  4. Choose Match all. Add Vendor → Equal → Levi's and Price → Less than → 50.
  5. Check the live count and the first 20 products for your selected preview location.
  6. Click Confirm to apply the drawer to your Experience draft, then Save the Experience.

Discard restores the saved Experience. During creation, Change type returns to the chooser and preserves your unfinished smart-group draft. Existing groups cannot change type. Reorder smart-group tiles alongside other tiles.

What can a condition compare?

#

Match on
Data used
What you enter
Product tag
The product's tags
A tag or a pattern using * .
Product metafield
Product-level stored text
Separate namespace and exact key, plus a value or a pattern using * .
Vendor
The product's vendor
A value or a pattern using * .
Product type
The product's type
A value or a pattern using * .
Product name
The product's name
A value or a pattern using * .
Price
An eligible variant's current selling price
Amounts in the store's currency.
Discount
Original price minus current selling price
An amount in the store's currency, or a percentage of the original price.

Product name, price and discount are available only in smart groups. Variant options, variant metafields, schedules, nested conditions, multiple rules, and manual product pinning or exclusions are not supported.

What each comparison means

#

Text comparison
Meaning for one product
Equal
A tag or field value matches the entered value or wildcard pattern.
Doesn't Equal
No tag or field value matches the entered value or wildcard pattern. Missing and blank fields pass.

Letter case and outer whitespace are ignored; internal spaces matter. Both comparisons support * as variable text. Other characters (including % and _ ) are literal. A pattern with * must cover nonblank text: Range:* matches Range:Trade , but not the bare value Range: . Use Equal → \* for a nonblank field and Doesn't Equal → \* for a missing or blank field.

Metafields use their namespace and exact key. custom.range and global.range are different. An empty namespace defaults to global ; namespace case and outer spaces are ignored, but key case and spaces matter. Rules use stored product-level text, without display transformations or extracting values from JSON objects or lists. Variant metafields are not used.

Prices and eligible variants

#

Price comparison
Meaning
Less than
Strictly below the amount.
Greater than
Strictly above the amount.
Between
Includes both amounts; the first must be lower than the second.

All price and discount comparisons are positive conditions. Prices use the current selling price, including sale prices. Normal catalogue and stock restrictions determine which variants are eligible at the kiosk or selected preview location.

With Match all, the same eligible variant must satisfy every price or discount condition. A product with £30 and £100 variants does not match “over £40 and under £80”. An excluded £30 variant cannot qualify a product for “under £50”. Opening product details retains the usual variant selection.

Discounts

#

Choose Discount, then Less than, Greater than, or Between, and select Percentage (%) or Amount in your store's currency. Between includes both endpoints. For example, a variant reduced from £100 to £80 has a £20 or 20% discount. Use 10–20% to match that inclusive percentage range, or Amount → Greater than → 50 for more than £50 off.

Only variants whose original price is greater than their current selling price qualify. Undiscounted variants and zero original prices do not match discount conditions. Percentage inputs must be between 0 and 100.

Combining conditions

#

  • Match all requires every condition, including exclusions, to pass.
  • Match any requires at least one positive condition. Exclusions neither create a match nor block a positive match.

A positive condition is Equal, or any price or discount comparison. Every rule needs at least one. Use Match all for “green products that aren't jeans”: Product tag → Equal → Green, and Product type → Doesn't Equal → Jeans.

The summary describes the actual rule. Example chips beneath conditions illustrate values or patterns; they are not catalogue results.

Checking the preview

#

Counts are shown only in the editor preview, not in the Experience tile list. The count and scrollable preview show eligible products after the Experience's draft restrictions and selected preview location. The preview shows the first 20 products in stable product-ID order. While Counting… is visible, the previous result is stale; count and products update together. Invalid conditions show a dash and a corrective message.

Updates, empty groups and troubleshooting

#

  • No products match: you can save the group, but its tile stays hidden. There is no fallback. A later catalogue update or rule edit can restore matches through the normal publishing and kiosk update flow.
  • A metafield is no longer synced: the rule is preserved and marked Needs attention, and the tile is hidden. Restore that field in Catalog settings, wait for fresh metadata to sync, and allow recalculation to complete.
  • Updating: new or edited rules stay hidden until their first successful calculation. Routine changes use the existing catalogue publication schedule: a five-minute trailing delay with a fifteen-minute maximum. Smart groups do not add extra background jobs or change that schedule.
  • A refresh fails: an unchanged valid rule retains its last successful membership while Manager reports the error. A new or edited rule stays hidden until calculation succeeds.
  • Plan changed: a downgrade preserves definitions, hides tiles and pauses processing. Returning to Standard or Premium recalculates groups before restoring them.
  • Preview differs by location: check stock and Experience restrictions. A matching product alone does not guarantee an eligible matching variant at every location.

Editing or deleting a smart group never changes the ecommerce platform. Removing its tile and deleting its definition are separate actions. Duplicating an Experience creates independent smart-group definitions; deleting the Experience removes its groups.