User-defined catalog transformations and preset transformations can both run on the same product title or description. This article explains the order they run in and what conflict detection does and doesn't catch.
Processing order
If you've written a user-defined transformation for a field, it runs before any preset transformations enabled on that same field. Presets then run in their usual order.
Note: This ordering happens automatically and isn't shown as a separate step in the Catalog Rules page's Processing order indicator, which only shows the high-level sequence: Hard Blocks > Transformations > Rules passed.
Conflicts with preset transformations
If a user-defined instruction duplicates what a preset transformation already does on the same field, this is intended to trigger a conflict warning with options to remove the instruction, turn off the conflicting preset, or proceed anyway.
What conflict detection doesn't catch
Conflict detection only compares your user-defined instructions against enabled preset transformations. It does not check for conflicts between two instructions within the same user-defined rule.
If you write instructions that contradict each other, neither will be flagged. Keep in mind that instructions are processed in the order you list them, so later instructions generally take precedence.
This means the AI's output can be unpredictable when instructions conflict, so it's worth keeping your instructions specific and non-overlapping.
Related articles