If Getting started with Renable is the "do this, then this" walkthrough, this article is the map — a one-level-deeper look at how Renable's pieces relate, so the rest of the knowledge base makes sense as you branch out.
The core idea#
Renable keeps a live link between your raw product data and the ad creative built from it. You describe the rules once — which products, which layout, which feed — and Renable keeps re-applying them as your product data changes, instead of you re-exporting a feed by hand every time a price or image changes.
That means each piece in the pipeline is really a binding, not a one-time export:
Catalogs — where product data comes from#
A catalog is one product-feed source: a store, a brand, or a market. It holds the feed connection (URL or live API import), your locale and currency formatting, and which AI-enrichment features are turned on. Products from a catalog import on a schedule — you don't re-import them by hand.
Transforming — fixing and shaping the feed before it becomes ads#
Raw feed data rarely arrives ad-ready: a category is mislabeled, titles carry wording an ad network won't allow, some products can't be advertised, or the stock levels live in a separate feed. So between import and enrichment there's a shaping step. In the catalog workspace you clean and reshape the feed with rules (conditions plus actions that fix values, exclude products, or split variants), line your feed's columns up with the fields channels expect through mapping, and pull in extra data from a second feed with a lookup. Every change stays in a draft until you Publish, so nothing reprocesses or reaches your ads until you're ready.
When several catalogs need the same cleanup, those rules can live in a ruleset you maintain in one place and apply to each of them, so one edit updates them all.
See Transforming your feed and Working with rulesets.
Enrichment — turning raw feed rows into usable content#
Raw feed data is often incomplete for advertising: no lifestyle image, no compelling ad copy, no distilled review quote. Within a project, Renable matches the same product across your catalogs by SKU and shows it once in the UI — so if you sell the same item through two catalogs in a project, you manage its content in one place instead of duplicating the work. Edit a piece of content once (an image, a headline) and it applies to every catalog with that exact content, automatically — including a catalog you add to the project later. On top of that, Renable runs AI enrichment: image reconciliation and background removal, ad-copy generation, review-fragment extraction, and category prediction.
Anything you mark as reviewed is locked in — future AI runs won't silently overwrite your edits.
See Reviewing and approving content and Image background removal and classification.
Projects and product sets — scoping which products#
A project is the operational hub for a campaign: it selects which catalogs are in scope and which products within them (a product set) should be used. A product set can be an explicit list or a saved query (e.g. "in stock AND price > 20"). A project also holds campaign-level fallback content — images, video, or copy to use when a specific product is missing something.
See What is a project and Product sets and product queries.
Templates — designing what the ad looks like#
Templates are built in Studio, Renable's canvas editor. A template isn't a static design — it's a layout with placeholders bound to product or project data, plus optional automations (show/hide/change a value based on product attributes, like hiding a "sale" badge when a product isn't discounted). One template renders differently per product.
See Studio overview and Placeholders.
Channels — exporting the feed#
A channel combines a project (which products), a template (what the ad looks like), and field mappings into an actual feed file (RSS or CSV) hosted for your ad network to fetch. Edits to a channel's fields or automations land on a draft first — nothing changes in your live feed until you publish.
See Working with channels and Publishing a channel.
Ad networks — where the feed is consumed#
The channel's feed URL is what you register with Meta Catalog Manager, Google Merchant Center, or TikTok. From there, the ad network runs dynamic product ads using Renable's rendered creative and product data.
See Connecting a channel to Meta, Google, or TikTok.
Why this shape matters#
Because each stage is a live binding rather than a one-time export, a single change propagates automatically:
- Update a product's price in your feed → it flows through enrichment untouched → the next channel export reflects it, no manual re-export.
- Edit a template's layout → every channel using that template re-renders.
- Change which products are in a product set → the channel picks up the new set on its next scheduled export.
Understanding this — data flows down through catalogs → transformation → enrichment → projects → templates → channels, and changes propagate automatically — is the key mental model for everything else in this knowledge base.
You can also ask Aimée to make changes directly in a catalog, a template, or a channel instead of doing it by hand.