Overview
When creating a translation job in Elovate, the rule builder allows you to precisely define which entities (products, categories, CMS pages, etc.) should be included.
This helps you avoid translating unnecessary data and focus only on the content that matters.
1. Where to find the rule builder
You will see the rule builder in the “What do you want to translate?” section of the translation job setup.
It works the same way as in imports, exports, and content enrichment, so you can reuse familiar logic.
2. Filtering options
You can filter on any native Magento attribute, such as:
Products: status, visibility, attribute set, brand, category, stock status, description, etc.
Categories: name, URL key, parent category, etc.
CMS pages/blocks: title, identifier, content status, etc.
3. Available conditions
Conditions vary depending on the attribute type:
Text fields: equals, not equal to, contains, does not contain, is empty, is not empty, starts with, ends with, in
Booleans (Yes/No): equals, is not equal to, in, is empty, is not empty
Numbers (e.g., price, stock): equals, not equal to, greater than, less than, greater or equal, less or equal, between, in
Multiselect attributes: equals, in, is not equal to, contains one of, contains all of, is empty, is not empty
4. Examples
Example 1 – Translate only enabled products without descriptions
Condition 1: Status equals Enabled
AND Condition 2: Description is empty
Example 2 – Translate only products in certain categories
Condition 1: Category equals Shoes
OR Condition 2: Category equals Bags
Example 3 – Translate a specific SKU list
Condition: SKU in SKU-001, SKU-002, SKU-003
5. Groups and complex rules
You can create groups to combine multiple conditions with AND/OR logic.
Example:
Group 1: Status equals Enabled AND Description is empty
Group 2: Category equals “Sportswear” OR Category equals “Running Shoes”
This ensures the translation job includes only items meeting either group’s criteria.
6. Live result count
While building rules, Elovate shows a live result count at the bottom.
This tells you exactly how many entities match your criteria before running the job.