Automations let one template adapt to each product. Each automation checks a condition on the product's data and, when it matches, shows, hides or changes an element. The same design can show a "Sale" ribbon on one product and hide a "Free shipping" badge on another, with no editing per product.
Automations — conditional rules for your template
Automations let one template adapt to each product by showing, hiding or changing elements based on product or project data. Build rules like a sale-price swap or a seasonal badge.
Updated November 6, 2026
How an automation works#
An automation has three parts:
- When: the conditions to check, for example a price, availability, a category or a date.
- Then: the actions to take when the conditions match.
- Otherwise: what happens when they don't.
Actions#
- Show makes an element or placeholder visible.
- Hide makes an element or placeholder invisible.
- Set replaces a placeholder's value. It doesn't change whether the element shows, so to show a badge and change its text to "Clearance", use Show and Set together.
When the condition doesn't match#
The Otherwise dropdown decides what happens:
- Otherwise, reverse show/hide (the default): Show becomes Hide and Hide becomes Show, so an element that shows when the condition matches is hidden when it doesn't. Set actions don't run.
- Otherwise, do nothing: nothing changes. Use this for an action that this rule should never undo.
- Otherwise…: add separate actions with Add action, for example a "Sale" badge on discounted products and a "New" badge on the rest.
Conditions#
A condition compares product or project data with a value.
Custom attributes. To test an attribute your feed carries beyond the standard fields, pick it from Custom attributes in the condition's field menu. See Custom attributes.
Numbers. Type numbers plain: 1000, not 1 000 or 12 kr. See Typing a number.
Dates. A date condition reads is before, is on or before, is after, is on or after or is between. You pick a date and time in your own time zone, and the condition uses that exact moment: Today's date is before 27 Sep 2026 23:00 stops matching at 23:00 your time on that day, not at midnight.
You can compare with something other than a fixed date:
- Another date, such as the sale end date: click the { } button next to the date. If Renable can't read a date you typed there, Publish stops and names the rule.
- A day counted from today: click the clock button next to the date and choose days ago, days from now or today, for example Sale end date is before 7 days from now. It's checked when the product's ad is next rendered, not at midnight. See Rules that depend on dates.
The Automations panel#
The Automations panel is docked on the right by default, with Elements and Settings, and you can move it anywhere. It lists every automation on the template. Click one to edit it, or use Add Automation to create one.
Automations run in list order, so a later one can override an earlier one. Drag them to reorder.
See what acts on one element#
Select an element and the Properties panel lists every automation that changes it, under Automations. Each one starts with what it does to that element (Shows this element, Hides this element, Sets text to …), then its conditions, then what the element gets Otherwise. If the element only changes when the conditions are not met, the conditions read Unless instead of When.
Test an automation#
You don't need a real product that happens to match. Flip the Simulate automation switch beside an automation in the panel to force it on or off on the canvas.
While you preview a product, each automation in Properties says whether it's Active or Inactive for that product. To try the other case, switch it from Auto to On or Off. It turns amber to show it's simulated, and Auto returns it to the product's own result. Picking another product sets every automation back to Auto.
A Disabled automation never runs. Open it and switch Enabled on to use it.
Automations or fallback elements?#
When the question is whether a product has something, such as a lifestyle photo or a second image, you don't need an automation. Give the element a fallback element to show in its place, or set it to hide when its content is missing. Keep automations for decisions about the product's data: a sale, a badge, a category, a season.
The two work together: automations run first, then fallback elements pick what to show.
Common patterns#
Sale price. When the product's sale price is lower than its regular price, Set the price text to the sale price. To show a "was" price in its own element, add a second automation with the same condition and a Show action.
Seasonal badge. When today's date falls within your campaign, Show a seasonal badge or banner.
Stock or category. When the product is out of stock, Hide the "Add to cart" badge. When it belongs to a category, Show a callout for that category.
Switching to a fallback layout. When the product is on sale, Hide an element that has fallback elements. The first fallback with its content is shown in its place, even for a product that has the element's content. If none of the fallbacks has its content, the product is missing content. A Show doesn't work the other way round: it never brings back an element that's missing content. See Fallback elements and automations.
Where to go next#
- Placeholders: what Set changes and what Show and Hide act on.
- Sizes and formats: automations are shared across every size on a template.
- Studio overview
- Working with Aimée: ask her to "hide the badge when the product is out of stock".