What Is a Project?

A project brings together your catalogs, product sets, channels, prompts and fallback content. It's where you decide which products get enriched and exported, and where they go.

Updated November 6, 2026

A project brings together everything for one marketing effort:

  • Catalogs: one or more product feeds.
  • Product sets: which products from those catalogs are in scope.
  • Channels: what exports your product sets to Meta, Google Shopping, TikTok or a custom destination.
  • Prompts: what writes ad copy and selects content for this project's products.
  • Fallback content: project-level images, videos and ad copy that a placeholder can use when a product doesn't have its own.

Creating a project#

  1. On the Projects list, click + New project. The project is created and opens.
  2. Name it at the top of the page. Until you do, it shows as "Untitled project".

A new project has no catalogs, so the next step is adding a catalog.

Project settings#

At the top of the project page you can click the name or the optional description to change it. There are no start or end dates: a project keeps running until you archive it.

Copying a project#

Use the copy icon in the project toolbar, or Copy… in the project's row menu on the Projects list. You get an independent copy of the project as it was last published. The name field suggests one, such as "Spring sale copy". If you belong to more than one organization the menu item reads Copy or move… and the dialog offers Copy and Move, so pick Copy.

What gets copied:

  • Catalogs. Each live catalog's setup (feed URL, mapping, rules, image processing) is copied as a new catalog, and its products are imported again from the feed. Import history doesn't carry over.
  • Product sets, channels and prompts. The copy's channels get their own feed URLs, so a destination reading the original keeps reading the original. Prompts are copied switched off, so nothing generates or spends credits until you turn them on.
  • Content edits. Approvals, rejections, primary image choices and content you uploaded carry over to the same products in the copy.
  • Fallback content: the project's images, videos and ad copy.

What doesn't get copied:

  • Archived catalogs, channels and prompts.
  • Unpublished changes. Publish first if you want them in the copy.

The new catalogs and channels count against your plan's limits, so a copy is refused if your plan can't fit it.

Copying into another organization#

If you belong to more than one organization, the dialog also lets you copy the project into another of your organizations, which is useful for reusing a proven setup across clients. The templates its channels render and the rulesets its catalogs apply are copied there too, so the copy works on its own. Switch to that organization to find it. If the copy's channels are used with Renable Options, connect Meta in that organization as well.

Moving a project to another organization#

Move takes the whole project, with its catalogs, channels, prompts, product sets, content and edits, to another organization you belong to. Its products and content stay as they are: it's the same project with the same feed URLs, so your destinations keep working with no change on their side. The templates and rulesets it uses are copied into the new organization, and the originals stay where they are.

Move only appears if you belong to more than one organization.

  1. Click the copy icon in the project toolbar, or Copy or move… in the project's row menu on the Projects list.
  2. Switch to Move.
  3. Choose the Target organization.
  4. Read the warning the dialog shows, then click Move project. The move starts when you click, with no second confirmation.

Afterwards the project sits on that organization's Projects list.

Four things change:

  • Access. Members of the old organization who aren't members of the new one lose access to the project. Invite them there if they still need it.
  • Meta. Integrations belong to an organization, so Meta has to be connected in the new organization before Renable Options can show the project's designs again. Your feeds never stop, and nothing has to be re-pointed at your destinations.
  • Monitors. A monitor in the old organization that watched this project's catalogs or channels loses them. One that watched only this project is switched off, and one that watched more keeps the rest. Set up the watching you still want in the new organization.
  • History. Aimée conversations and credit history stay with the old organization. The project's catalogs and channels count against the new organization's plan from now on, and the move is refused if that plan can't fit them.

A move can't be undone from the old organization. Once the project has moved, only someone in the new organization can move it back.

Archiving a project#

Archive a project from the Projects list:

  1. Open the ⋯ menu at the right end of the project's row.
  2. Choose Archive.

The archive happens immediately, with no confirmation prompt, so double-check before clicking.

Archived projects are hidden from the list. To see them, or to unarchive one from the same ⋯ menu, click the filter button next to the search field and switch on Show archived.

Warning. Archiving a project archives every catalog inside it, and every channel exporting those catalogs is emptied, so your destinations stop showing those products. The catalogs' products are permanently deleted after 30 days.

Unarchiving the project doesn't unarchive its catalogs. Each one has its own Unarchive.

Where to go next#