How Renable works

How catalogs, rules, AI enrichment, projects, product sets, templates and channels fit together, and what happens when something changes.

Updated November 16, 2026

This article explains how Renable's pieces fit together. For step-by-step setup, see Getting started with Renable.

You set up once which products to use and how the ads should look. Renable keeps applying that as your product data changes, so you never re-export a feed by hand when a price or an image changes.

Catalogs: where product data comes from#

A catalog is one product feed: a store, a brand or a market, created inside a project. It holds the feed connection, the catalog's language, and which AI features are on. Products import on a schedule.

See Working with catalogs.

Rules: fixing the feed before it becomes ads#

Feed data rarely arrives ad-ready. A category is mislabeled, a title carries wording a destination won't allow, some products can't be advertised, or stock levels live in a separate feed.

In the catalog workspace you fix this with Rules, which change values, exclude products or split variants. Mapping lines your feed's columns up with the fields channels expect, and a lookup pulls in data from a second feed. Your changes stay in a draft until you Publish.

When several catalogs need the same cleanup, keep those rules in a ruleset and apply it to each of them, so one edit updates them all.

See Transforming your feed and Working with rulesets.

Enrichment: adding what the feed lacks#

Renable writes ad copy, removes backgrounds, pulls out review quotes and predicts categories.

If you sell the same product through two catalogs in a project, Renable shows it once, so you edit its content in one place. Your edit applies to every catalog with that content, including one you add later. That's one product and two feed items, and your plan's import limit counts feed items. See Feed items vs. products.

Approving locks that exact content against automatic decisions. When a product's data changes and a prompt writes new text, the new text replaces it and starts unapproved. See Reviewing and approving content and Image background removal and classification.

Projects and product sets: which products#

A project brings together your catalogs and the products you want to use from them. A product set selects those products, as a hand-picked list or a saved query such as "in stock and price over 20". A project also holds fallback content: images, video or copy a placeholder can ask for when a product is missing something.

See What is a project and Product sets and product queries.

Templates: what the ad looks like#

You build templates in Studio, Renable's canvas editor. A template is a layout with placeholders that fill in from product or project data, plus optional automations, such as hiding a sale badge when a product isn't discounted.

See Studio overview and Placeholders.

Channels: sending products to a destination#

A channel combines a project's products, a template and field mappings into a feed file (XML, CSV/TSV or JSON) that Renable hosts for a destination to fetch. Edits to a channel's fields or rules stay in a draft, and your live feed doesn't change until you publish.

See Working with channels and Publishing a channel.

Destinations: where the feed is used#

You register the channel's feed URL with Meta Commerce Manager, Google Merchant Center or TikTok. From there, your product data and the images and videos Renable rendered can run as dynamic product ads.

See Connecting a channel to Meta, Google, or TikTok.

What happens when something changes#

  • A price changes in your feed: the channel's next run picks it up.
  • You publish a template change: every channel using the template runs again with the new layout, within about five minutes.
  • You publish a product set change: the channels that use the product set run again, within about five minutes.

You can also ask Aimée to make changes in a catalog, a template or a channel for you, for example "hide the sale badge when a product isn't discounted".