Mapping Rules
June 26, 2026
Summary
Mapping rules are mini workflows attached to a single field in a mapping template that conditionally modify a value after it has been mapped, using if/then conditional logic or tiered rule types. Explains Incoming vs Original Value, how rules chain, and how to create, test, and apply them.
What a mapping rule is
A mapping rule is a mini workflow applied to a specific field in a mapping template. Rules modify a value after it has already been mapped by the template, using conditions and actions. Use a rule whenever you want to conditionally change a value that a mapping template produces.
Applies to one field
A rule is attached to a single field in a mapping template (such as Title, Brand, or a price field).
Runs after the template maps
Rules act on the value the template already produced, not on the raw source data.
Can be chained
Multiple rules can run in sequence on the same field; the output of one becomes the input of the next.
Testable before use
Use Test Rule with sample data to confirm the conditions behave as expected before applying it.
Key terminology
| Term | What it means |
|---|---|
| Incoming Value | The value the rule is currently manipulating. It is called "incoming" because when rules are chained, this value transmits through each rule in the chain. |
| Original Value | The original value that was mapped from the field, before any rule changed it. Use it to back out of changes in certain situations. |
How a rule flows
Field mapped by template
→
Rule reads Incoming Value
→
Conditions + actions run
→
Modified value passed on (or to next rule)
Example — apply title cleanups to every brand except "XYZ"
→ Apply cleanups to all titles
→ If
Brand = XYZ → Set Title to Original ValueRule types
| Type | How it works |
|---|---|
| Conditional | Applies changes based on "If" and "Then" conditions, similar to a workflow. When you choose Conditional, you select an Input Type: String, Number, Boolean, or Option Field. |
| Tier | Applies changes based on a tiered list that can be marked up or marked down. For example, a Get Inventory [Primary] rule could be tiered to sentence-case titles. |
Creating, testing & applying rules
Rules are set up like workflows — either with if/then Conditional logic or as a tiered Rule Type. You can create a rule inside a mapping template or on its own, then test it and apply it to a field.
| Step | What to do |
|---|---|
| Create inside a template | Click New Rule on the field. The rule is created and automatically applied to that field. |
| Create outside a template | The rule is not attached to anything yet — you must add it to a field manually (see below). |
| Test the rule | Click Test Rule and supply sample data. You only need to populate the values the rule actually uses — for example, if the rule only touches Brand and the Incoming Value (the title), you only fill in those. |
| Apply to a field | Go to the field you want to modify, then click Rules → View All Rules → Add on the specific rule you want to use. |
Things that trip people up
Rules run after the template, not before
A rule modifies the value the mapping template already produced. If a value looks wrong before any rule runs, the problem is in the template mapping itself, not the rule.
Creating a rule outside a template does not apply it
A rule built outside a mapping template is created but not attached to any field. You must manually add it via
Rules → View All Rules → Add on the target field, or it will never run.Chained rules share one value
When you chain rules on a field, the Incoming Value carries through each rule in order. A change made by an earlier rule is what the next rule sees — so the order of your rules matters.
Use Original Value to undo a change
To exclude specific cases from a rule's effect, set the field back to Original Value under a condition — like applying title cleanups to every brand except one.
Common issues
A rule I created isn't changing anything
If you created the rule outside a mapping template, it is not applied to any field yet. Open the field, then click
Rules → View All Rules → Add on that rule to apply it.Test Rule returns an unexpected result
Confirm the sample data covers every value the rule references. Testing only requires the data the rule actually uses — missing one of those inputs can make the test misleading.
Chained rules give the wrong final value
Remember each rule receives the Incoming Value produced by the rule before it. Re-check the order of the rules on the field, since an earlier rule's output feeds the next.
A condition exception isn't sticking
To leave certain records unchanged, the action should set the field to Original Value under that condition, rather than leaving the previously modified Incoming Value in place.
FAQs
What is the difference between Incoming Value and Original Value?▸
The Incoming Value is the value the rule is currently working on, which transmits through each rule when rules are chained. The Original Value is the value first mapped from the field before any rule modified it, and it can be used to back out of changes.
Can I chain multiple mapping rules on the same field?▸
Yes. Rules can be chained, and the Incoming Value transmits through each rule in sequence — the result of one rule becomes the input to the next.
What is the difference between a Conditional rule and a Tier rule?▸
A Conditional rule applies changes using "If" / "Then" conditions and lets you pick an Input Type (String, Number, Boolean, or Option Field). A Tier rule applies changes based on a tiered list that can be marked up or marked down.
Do I need to fill in every field to test a rule?▸
No. Testing only requires the data the rule actually leverages. If a rule only interacts with Brand and the Incoming Value, you only need to populate those values to test it.
If I create a rule outside a mapping template, is it applied automatically?▸
No. Only rules created inside a template via
New Rule are applied automatically. A rule created outside a template must be added manually to a field through Rules → View All Rules → Add.