Channel rules
A channel's rules change what it sends per product. A rule can set a field, mark a product so you can find it, or exclude it from this channel, and rules run top to bottom each time the channel runs.
Updated November 18, 2026
A channel rule says when this is true, do that, and Renable applies it to each product every time the channel runs.
Rules live on the channel's Rules tab, and your changes go live when you
publish the channel. Studio templates have Automations instead, which
work in a similar way but have different actions.
Typical uses:
- Set a field to a different value when stock runs out.
- Fill a sale-price field only when the product is on sale.
- Set a product's status so the destination stops showing it when required content is missing.
- Exclude sold-out or discontinued products from this channel.
Adding and editing rules#
- Click + Add rule, or click an existing rule to expand it.
- Set the When condition, then what happens under Then.
- Publish the channel.
Drag a rule to reorder it. To delete one, click Delete in the expanded rule and confirm. You can't delete a
field that a rule still uses, so remove or repoint the rule first.
Where the channel holds several fields under one name, the pickers number them (image · #1, image · #2), as the
Fields tab does.
A condition can also test a custom attribute of the product, whether or not the channel has a field
for it. Pick it from the Custom attributes group of the condition's field menu, or choose Use another attribute…
and type its name as your feed spells it. The value is compared as text, and a product without the attribute reads as
empty, so is blank is true for it.
What a rule can do#
- Set field writes a different value into one field for the products the rule matches. To leave a field blank, set
it to an empty value.
- Mark product marks the product so you can find it, and changes no field. The product still ships. Turn on Show
only marked products on the Preview tab to spot-check them, for example every product a rule marked as low-stock.
Marked isn't the same as flagged content, which failed an automatic quality
check.
- Exclude product removes the product from this channel's file, so the destination never sees it. Other channels
and your catalog aren't affected. Each run shows how many products rules excluded, and Trace reports a product as
excluded by a rule.
To remove products from every channel, exclude them on the catalog instead. If the
real question is which products the channel covers at all, change its
product sets.
Show and Hide are Studio actions and aren't offered here. If the Activity tab reports a leftover Show or Hide
on an older rule, it does nothing to the feed: open the rule and remove it.
The rules a channel starts with#
Most channel types come with some rules, which you can edit or delete:
- Availability sets the availability field to out-of-stock when a product's stock count is zero. Except
on Meta and TikTok channels, it also triggers when required content is missing.
- Sale price sets the sale-price field whenever the current price is lower than the original price.
- Status (Meta and TikTok channels) sets the status field to archived when required content is missing, and falls
back the image field so the destination isn't left with a broken reference.
The Meta Advantage+ supplementary feed and Google Shopping supplementary feed types start with no stock, price or
status fields, so they have no rules. If you want these behaviours there, add the fields and rules yourself.
The order rules run in#
Rules run from top to bottom, once each per product, and each rule sees the product as the rules above it left it:
- If two rules set the same field, the lower one wins.
- A rule can read what an earlier rule set.
Missing content is checked at each rule's turn. If a rule supplies what was missing, such as a fallback image, the
rules below no longer see the product as missing content. If a rule sets a field to something that comes out empty, the
rules below see missing content on a product that had none. A design whose image isn't ready yet is not missing
content.
To see what happened to one product, click Trace on the Fields or Rules tab. It walks the rules in the order
they ran and shows what each one changed, including a row such as Missing content: yes → no on the rule that moved it.
Fields that hold several values#
A field with Allow multiple values on carries all of a product's values at once, such as every extra image, and a
rule sees the whole set:
- A condition matches if any value matches. "Extra images contains
placeholder" is true if one of them does.
- A "does not" condition is true only if no value matches.
- A field with nothing in it counts as blank, and every "does not" condition is true for it.
Setting one of these fields replaces all of its values. If the value you set resolves to one thing, the field ships
that one thing. If it resolves to several, the field ships them all in order, with duplicates dropped.
Steps: changing a value before it is used covers how steps treat a field with several values.
Rules that trigger on a date#
A rule can trigger on a date, for example "sale ends on 30 November". When the date arrives, Renable runs the published
channel so the rule takes effect right away, without waiting for a product change to start a run. This only works once
you've published the rule; a date rule in a draft schedules nothing. A date counted from
today, such as 60 days ago, starts no run of its own: the rule is checked whenever the channel next runs.
Replacing a nested block#
A rule that targets a nested field replaces the whole block for the products
it matches. Every other product keeps the block the field describes.
Pick the nested field as the rule's target and the value editor shows the same sub-field list as the Fields tab,
starting as a copy of the field's own block. Add sub-field and the remove button work as they do there, and a block
carries at most one image or video sub-field.
- The block keeps the field's name, so the element in your feed and the design name an ad pins don't change.
- The rule's block is a copy. If you later rename a design or change its marks for Stories or Reels, the rule keeps the
old tags, and the next run warns you which ones differ. Update whichever side is wrong.
- The block repeats the same way as its field. On a field that repeats, you can point a sub-field at the current item.
- Nested fields aren't offered as rule targets on CSV or TSV. Switch the format to XML or JSON on the Settings tab.
You can also ask Aimée for what you want, such as "use the Black Friday design for products on sale".
Seeing what a rule did to a block#
Open Trace and pick a product. The rule's step lists each sub-field with its value before and after, and sub-fields
the rule left alone are dimmed. A design shows its name, so a swap reads Summer Sale — Square → Black Friday — Square,
and other sub-fields show the expression they're bound to. Unavailable design means the design can't be named, for
example because it was deleted, and Summer Sale — Unavailable size means the design is fine but its size is gone.
What the product actually got is in the Feed entry table further down the same dialog.
Where to go next#