Catalogs belong to one project, forever#
A catalog is a single product-feed source (see Working with catalogs for feed setup, locale, and enrichment settings). Every catalog is created inside exactly one project, and it stays there for its whole life — there's no "move this catalog to a different project" or "link an existing catalog here" option.
If you need the same feed available in two projects, you'll create a separate catalog for each — they won't share import history or enrichment state.
Copying a project doesn't move a catalog either: the copy gets its own new catalogs with the same setup, imported again from the feed. Moving a project to another organization takes its catalogs along with it, and they stay in that same project.
Adding a catalog#
- From the project page, go to the Catalogs section and click Add catalog.
- Fill in:
- Name — how the catalog appears in Renable.
- Domain — the store's domain.
- Locale — drives AI content language and number/currency formatting for this catalog's products.
- Add all the catalog products to this project — a convenience checkbox. When checked, Renable automatically creates a product set with a query scoped to this catalog, so its products are in scope immediately without any manual setup.
- Save. Renable begins importing the feed in the background.
Removing a catalog#
There's no plain "remove" — removing a catalog from a project means archiving it, via Archive catalogs in the Catalogs section.
Warning — archiving a catalog is not reversible. Once a catalog is archived, feed import stops for it and its products are permanently deleted after 30 days. There's no restore. Every channel that exports the catalog is emptied at the same time, so Meta, Google and your other destinations stop showing products that would no longer be updated — the channel's Activity tab shows the run as Feed emptied.
Only archive a catalog once you're sure you no longer need its products or import history.
Plan limits#
The number of catalogs you can have is capped by your billing plan — and that cap is shared across your entire organization, not scoped to this one project. Catalogs you've added in other projects count against the same limit, so adding a catalog here can be blocked by catalogs created elsewhere in your organization.
If you're at the limit, adding or unarchiving a catalog shows an upgrade prompt instead of going through. The exact catalog limit depends on your plan — see /billing/plans for current tiers, or Plans and limits for how limits work.