Export conditions decide whether the selected part of the data gets into the final export.
For example, you can skip an empty description, remove an empty XML tag, or skip a table row without an SKU.
Where to open export conditions
| Where you work | How to open it | What is checked |
|---|---|---|
| Table | Open the settings of the required column. | The condition checks the value in the row. If the check fails, the row is not exported. |
| JSON | Click the required key or value in the JSON editor. | The condition checks the selected key or value. You can choose whether to remove only this node or the whole parent item. |
| XML | Click the required tag, attribute, or value in the XML editor. | The condition checks the selected part of the XML. You can choose whether to remove only this node or the whole XML element. |
What to choose: “For node” or “For whole element”
In JSON and XML, the export conditions block has a scope choice. It defines which part of the data is removed from the export when the condition fails.
- For node removes only the selected key, tag, attribute, or value. The rest of the record stays in the export.
- For whole element removes the full item that contains the selected part. Use it when an empty or invalid value makes the whole record unnecessary.
- Tables do not have this choice: an export condition always applies to the whole row.

What a condition contains
| Setting | Meaning |
|---|---|
| Checked source | The current value, another XML/JSON node, a neighboring table column, or a system value. |
| Timing | Before transformations or after transformations. If the value is cleaned or calculated first, the check is usually done after transformations. |
| Operator | Empty, not empty, equals, greater than, contains substring, regular expression, and other checks. |
Result examples
JSON: remove an empty description key
The condition is set in the description value settings: Current value, before transformations, not empty. The value is empty, so the description key is omitted from the result entirely.
Input
JSON{
"sku": "SKU-1001",
"name": "Jacket",
"description": ""
}Export result
JSON{
"sku": "SKU-1001",
"name": "Jacket"
}XML: remove an empty description element
The condition is set on the description element: Current value, before transformations, not empty. The value is empty, so the <description> tag is removed from the result entirely.
Input
XML<?xml version="1.0" encoding="UTF-8"?>
<offer>
<sku>SKU-1001</sku>
<name>Jacket</name>
<description></description>
</offer>Export result
XML<?xml version="1.0" encoding="UTF-8"?>
<offer>
<sku>SKU-1001</sku>
<name>Jacket</name>
</offer>Table: skip a row with an empty required field
In the sku column settings, set a not empty condition. If sku is empty, the whole row is not exported.
| sku | name | Export result |
|---|---|---|
SKU-1001 | Jacket | The row is exported. |
| No SKU item | The row is not exported. |
How this differs from an action in transformations
Transformation rules include an Export control group. It is an action inside the transformation chain of the selected value, not a structural filter for a row, JSON node, or XML element.

- Do not load field is applied as a rule action for the current value. Depending on the format, the result can look like an empty value, but it is not a row or parent-object filter.
- Skip skips the current transformation rule and continues with the next rules.
- To remove the current JSON node, XML element, or table row, use the Export conditions block.
Which mechanism to use
| Task | Use this |
|---|---|
| Remove an empty key from JSON | Export condition on that JSON value: not empty. |
| Remove an empty tag from XML | Export condition on that XML element: not empty. |
| Skip a table row with an empty SKU | Export condition in the sku column settings: not empty. |
| Only change a field value | A rule in Transformations. |