Reviewing and approving content

Content is the text and media Aimée creates or selects for your products — the raw material that flows into your templates and channels. It includes:

• Images, with backgrounds automatically made transparent where appropriate
• Ad copy, headlines, and reasons to buy — written by prompts or extracted from your product descriptions
• AI-discovery content — product highlights, enriched descriptions, and use-case phrases, written by the AI discovery prompts and tagged so it stays separate from your other copy
• Voice scripts for text-to-speech
• Short quotable fragments extracted from customer reviews
• AI-generated lifestyle images and videos

Click any product's name to open its product page and see everything selected for it — images, ad copy, user reviews, and its product feed entries — and edit or add to it directly. The product page is also where you browse the customer reviews behind the extracted quotes and approve more of them. You can also add content at the project level (fallback images, videos, and ad copy) for cases where you need something available even before a product has its own — see What is a project.

If the same product is sold through more than one catalog in this project, it shows up once here rather than once per catalog, and an edit applies to every catalog sharing that content automatically. See How Renable works for how that SKU-based matching works.

An image card lists the catalogs whose feed carries that file at that position, so a "Main" card is the main image in every catalog it names. When one catalog's feed lists the same picture at a different position — as its second image, say — it gets its own card, and both cards carry a Same file row naming the other one: the position it sits at there ("Main", or "#1") and which catalogs, shortened to just the part that tells them apart when they all start the same way. The same pair of rows appears when two catalogs process one picture differently, and when you borrow a picture into another catalog — the original and the borrowed copy each name the other. Hover a row to see the card it names outlined, and click it to jump there. If the other card is hidden by a filter you have on, the row says so when you click it — it still tells you the two are one file, because an edit here reaches the hidden one just the same. The tooltip spells out the full catalog names and exactly what the two cards share. They are one source file, so setting it as primary, rejecting it, changing its category, tagging it, picking a version or moving its focus point on either card always applies to both. Approving is the one thing that depends on what the two cards actually show: when both show the same processed picture, approving one approves the other; when they show different renderings of the file — two catalogs whose processing differs, or the same file under two categories — each rendering has to be approved on its own. Each row's tooltip says which of the two you are looking at.

The Content page#

Every project has a bulk Content page for reviewing and approving content across many products at once. From the project's overview page, in the Products section, click See content (or the content-review icon in the same toolbar).

The page lists every product in the project straight away — including ones with no content yet, which simply show nothing on them until Renable's automatic processing fills them in — and shows the approval status of the content Aimée has selected. You don't have to wait for products to appear; they're already listed.

Switch between two layouts with the view toggle:

• Table view — one row per product, with count columns for Images, Awards, Lifestyle images, Videos, and user reviews (labeled "AUR"), plus a toolbar to approve content, add text content, and open the product's image or review galleries. A product sold through several catalogs in this project is a single row, and its counts cover everything selected for it across those catalogs. The Awards column counts images tagged as award content; the gallery it links to isn't built yet, so treat that count as informational for now.
• Gallery view — a card-based view better suited to visually scanning images.

Filters let you narrow the list down to Show archived, Show only primary images, Show only marked products (products a channel rule marked), Show only unapproved content, or Show only flagged content.

Products with no content yet#

A product Renable hasn't processed yet is listed like any other, just with nothing on it: no images, no ad copy, nothing to approve. Its name is still a link — opening the product page shows its feed entries right away, and its content fills in automatically as Renable works through the catalog. There's nothing you need to trigger: content is created and refreshed as part of the automatic feed processing that runs whenever your catalog imports — and whenever you publish a change to a catalog's settings, a prompt, or the project, the affected products are brought up to date within minutes.

Seeing mostly empty products is normal on a project whose catalogs were connected recently. The review hotkeys do nothing on an empty product, and including empty ones in a bulk approve is harmless — there's simply nothing on them to approve.

Review hotkeys#

With a product row focused, these keys speed up review:

Bulk actions#

Approving a batch of products. Each row in table view has a checkbox. Tick the products you want, and an approve button appears in the toolbar above the table — it approves all content on every selected product at once. It respects the filters you have on, so if you're showing only unapproved content, that's what gets approved and nothing else is touched. Products with no content yet can be ticked along with the rest — they just have nothing to approve.

The page-level ⋯ menu (available in both table and gallery view) lets you:

• Approve all visible items — mark every unapproved item currently shown as approved.
• Make all images transparent (v1 / v2 / v3) — force a specific background-remover version across every image shown, overriding whatever the catalog's default pipeline chose. See Image background removal and classification.
• Change category — reassign the content category (Information, Product, Lifestyle, Staged, Feature, and the text categories) for every selected image, review, and ad copy item at once.

Approving content#

AI-created or AI-selected content starts out unapproved. You'll see the info banner "Automatically created by Aimée, but not yet approved by a human" until someone reviews it. Approve a single item by opening it and confirming, or use the thumbs-up icon or hotkeys on the Content page for faster bulk review.

By default, unapproved content is used in your templates and channels exactly like approved content — there's no need to review everything before it goes live. That covers AI-discovery content too: product highlights and enriched descriptions arrive unapproved and reach your Google feed the same way, so review them here if you want to read them before they go out. If you need tighter editorial control, open a specific placeholder in Studio or a channel field and turn on Only use content approved by a human. Only then does that placeholder skip unapproved content in favor of a fallback (or nothing, if none is set). See Placeholders for how to configure this per placeholder.

Approving an item also locks in a specific choice against Aimée's automatic decisions — for example, approving an image locks which background-removal version and category are shown for it, so a later automatic run never changes them. It does not lock the image against your own catalog settings: if you change the catalog's background-remover pipeline, the image is rendered again and shows as unapproved until someone looks at it. See Image background removal and classification for the exact nuance, including the one case where an approval survives a pipeline change.

Archiving and deleting your own content#

Archiving hides a content item from your templates and channels without losing it — it stays available under the Show archived filter and can be unarchived. That applies to everything: feed images, AI-generated content, and content you added yourself. One nuance for feed images: if an archived image has also disappeared from your product feed, it's cleaned up automatically about a month after leaving the feed. Content you added yourself is never cleaned up automatically — it stays archived until you delete it.

Content you added yourself — an uploaded image or video, or ad copy you wrote — can also be deleted permanently, from the ⋯ menu on its card. Unlike archiving, deleting can't be undone — the item is removed from the product entirely. The Delete option only appears on content you added: images and text that come from your product feed or from Aimée can only be archived, since Renable would simply derive them again.

Flagged content#

Some content is checked automatically after it's produced. Flagged content failed an automatic quality check. Approving it clears the flag. Today the check that runs is on images — when background removal produces a result the automatic check isn't confident about, that image is flagged.

Flagged content is always a subset of unapproved content, so it's never a separate pile to work through — it's the part of your unapproved backlog most worth looking at first. Two places surface it:

• Your dashboard shows a "N flagged" count on each project card, and a Flagged filter in the card mode selector to see just the clients affected.
• The Content page's Show only flagged content filter narrows the list to those products.

Like unapproved content, flagged content is still used in your ads by default — a flag is a "worth a look", not a block. If you'd rather a specific placeholder skipped it, open that placeholder in Studio (or the equivalent channel field) and turn on Skip content flagged by quality checks. Approving the content clears the flag and makes it usable again everywhere.

Don't confuse flagged with marked: marked products are ones a channel rule singled out for you to look at, which is about feed rules rather than content quality.