Move rules you keep repeating into a ruleset, apply it to every catalog that needs them, and bridge column names where feeds differ — so one edit updates all of them.
Updated August 25, 2026
If you keep writing the same cleanup rules on catalog after catalog, move them into a ruleset: one place to edit, applied to as many catalogs as you like. This walkthrough takes rules you already have on one catalog and turns them into a ruleset the rest of your catalogs share.
Before you start: have the rules working on one catalog. It's much easier to move rules you've already proven than to write them blind in an empty ruleset.
Open Rulesets in the top navigation and choose + Create manually. The new ruleset opens straight away — name it at the top of the page, after what it does ("Nordics base cleanup") rather than after the catalog you're copying from.
You can also just describe the rules you want in the box at the top of the Rulesets page and let Aimée build them.
If a prepared ruleset already covers your case, Start from a preset gives you your own editable copy instead of a blank one.
Add the rules in the ruleset the same way you would on a catalog: conditions, then actions. The editor is identical — see Fixing your feed data with rules.
Keep the order in mind. The rules run top to bottom in whichever catalog applies the ruleset, so a rule that builds a value must sit above the rule that reads it.
Choose Publish. Until you do, catalogs that apply this ruleset get nothing from it — the rules only go live on the ruleset's own publish.
On a catalog's Rules tab, choose Apply ruleset and pick yours. Put the card where the shared rules should run: rules above it run first, rules below it run after.
Then remove the now-duplicate rules from that catalog — otherwise the same work happens twice, and a later local rule can quietly override what the ruleset just did.
Repeat for each catalog that needs the same cleanup.
Your feeds don't all name their columns the same way. When a catalog's feed calls a column something else, add a Set field rule ABOVE the apply rule that copies it across — for example set productname to {{title}}.
Do this on the catalog, never inside the ruleset. Renaming a column inside the ruleset to fit one catalog breaks it for every other catalog using it.
Renable warns you on the rule card when a ruleset reads a column this catalog doesn't seem to have — that warning is your cue to add the bridging rule, and it clears once you do.
On the catalog's Rules tab, open a product trace and check the values the shared rules produced are what you expect. On the ruleset itself you can do the same with Preview with catalog — pick one of the catalogs using it and the preview runs against that catalog's real feed.
Then publish the catalog.
Edit the rule in the ruleset, publish the ruleset, and every catalog using it is reprocessed. The publish confirmation names those catalogs first.
If you've also changed a catalog, publish in this order: ruleset first, catalog second. A catalog always uses the ruleset's last published rules, so publishing the catalog first ships the old ones.