Transformations change a selected value before export: they remove unwanted characters, replace text, calculate prices, fill empty values, or clear one field.
Open the settings of the value you want to change, find Transformations, and click Add rule. A rule defines which value to inspect, when it should run, and what it should do.
The same rule logic applies regardless of where the source data came from. Only the screen used to open the value is different. The three output options are shown below in plain terms. price, stock, and Debit are example names; your fields may be named differently.
Where to open transformations
Table Editor
In the table editor, open a transformation from the result column. Click the needed header or cell, then open the value settings.
XML Snapshot
In the XML snapshot, hover the needed value inside the structure, for example the text between <section_path> and </section_path>, then click it. The value settings window opens, and the transformation result is reflected directly in the snapshot.
JSON Editor
In the JSON editor, select a key or value in the result tree. The settings open for the selected JSON block.
Consolidated Catalog
In the consolidated catalog, open a transformation from the catalog field binding. Click the selected field, for example "Name [NAME]" or "SKU [SKU]", then open the value settings.
For more about these screens, see table result, JSON result, and XML result.
What one rule contains
Each row in Transformations answers three questions:
- Which value should be checked? This is usually Current value. Another source field can be selected when needed.
- When should the action run? For example, Any, Empty, Equals, or Contains substring.
- What should happen? For example, Trim spaces at edges, Replace with, Remove substring, Increase by %, or Round.
A simple text-cleaning rule is Current value → Any → Trim spaces at edges. The value Desk lamp becomes Desk lamp.
When the rule is ready, click Save.
The screenshot below is a separate example with two rules for Debit. It demonstrates rule order, not the preceding space-trimming example.
Debit example shows that rules run top to bottom and the arrow buttons change their order.Why rule order matters
Current value changes after every matching row. For example, use Trim spaces at edges first, then Collapse repeated spaces, and finally Remove substring. Put the rules in the required order with the up and down arrow buttons.
To inspect the original, unchanged data, select its source field instead of Current value. See Values from other fields in transformations for using neighboring fields.
What transformations can do
| Task | Approach | Ready example |
|---|---|---|
| Clean text | Trim spaces at edges, Collapse repeated spaces, Remove substring, or Remove HTML tags. | Clean an SKU |
| Normalize different labels | Check with Equals or Contains substring, then use Replace with. | Normalize stock text |
| Add text to a value | Use Add to beginning or Add to end while keeping the original part. | Add an SKU prefix and suffix |
| Fill an empty value | Empty → Replace with → a default value. | Fill empty values |
| Calculate a price | Increase by %, Add, Subtract, Multiply, or Round. | Add a markup and round |
| Split one amount into two values | Check the sign with Less than or equal and Greater than or equal, clear with Do not export field, then use Remove substring. | Credit and Debit |
The full condition list and usage examples are in Transformation rule conditions.
Change one value or exclude a whole record
A transformation acts on the selected value. Do not export field clears only that value and ends its rule chain; the table row, JSON object, or XML record remains.
To decide whether a field, row, or whole element should be exported, use the separate Export conditions block. See Export conditions for scopes and differences. A complete-record example is zero price or empty stock.