What Are Quality Rules?
Quality rules are the conditions your product data must satisfy to pass Quality Guard checks. Each rule defines what you are checking, which products it applies to, and what happens when a product fails. You can create rules from scratch or start from a template.Rules are evaluated automatically during exports, syncs, and publishes. Products that fail a rule are handled according to its severity level: blocked, skipped, or warned.
Managing Your Rules
The Rules page shows all your quality rules in a single list. For each rule, you can see:- Name and description — what the rule checks
- Status — whether the rule is active or in draft mode
- Severity — Block, Skip, or Warn
- Conditions count — how many conditions make up the rule
- Created/updated dates — when the rule was last modified
Available Actions
From the rules list, you can:- Toggle active/inactive — Enable or disable a rule without deleting it. Inactive rules are not evaluated during quality checks.
- Duplicate — Create a copy of an existing rule as a starting point for a new one.
- Delete — Permanently remove a rule you no longer need.
- Edit — Open the rule builder to modify any aspect of the rule.
Creating a Rule
To create a new rule, click the Create Rule button. The rule builder walks you through four sections:Basic Information
Give your rule a name and optional description. Choose whether the rule should be active immediately or saved as a draft.
Conditions
Add one or more conditions that define what the rule checks. You can combine conditions with AND (all must match) or OR (any must match) logic.
Scope
Choose which products the rule applies to: all products, specific categories, certain channels, or a price range.
Condition Types
Conditions are the core of every rule. You select a field, an operator, and optionally a value. Here are the field groups available:Basic Information
Product Name, SKU, EAN/GTIN, Brand, Supplier. Check for missing identifiers, required fields, and format validation.
Content
Description, Short Description. Validate length requirements, required keywords, or forbidden content.
AI Enrichment
Enriched Name, Enriched Description, Has Any Enrichment. Ensure products have been processed by AI before export.
SEO
Meta Title, Meta Description, Meta Keywords. Enforce SEO best practices like character length limits.
Pricing & Stock
Price, Sale Price, Stock Quantity, Weight. Validate pricing ranges, stock availability, and shipping data.
Media
Images (count), Main Image. Require a minimum number of images or ensure a primary image exists.
Organization
Categories, Product Family. Ensure products are properly categorized before export.
Translation
Has Translation, Translation Complete, Missing Translation. Verify localization readiness for international channels.
Operators
Each field supports a set of operators that define the comparison. Common operators include:| Operator | Description | Example |
|---|---|---|
| is empty | Field has no value | Product Name is empty |
| is not empty | Field has a value | EAN/GTIN is not empty |
| length is at least | Text has minimum length | Description length is at least 100 |
| length is at most | Text has maximum length | Meta Title length is at most 60 |
| contains | Text includes a substring | Description contains “warranty” |
| does not contain | Text excludes a substring | Name does not contain “test” |
| matches pattern | Text matches a regex | EAN matches ^\d{13}$ |
| is greater than | Number exceeds threshold | Price is greater than 0 |
| is between | Number falls within range | Price is between 5 and 500 |
| has at least (images) | Minimum image count | Images has at least 3 |
Scope Options
Scoping lets you target rules to specific subsets of your catalog:- All products — The rule applies to every product in your project.
- Categories — The rule only applies to products in selected categories.
- Channels — The rule only applies when exporting to specific channels (e.g., Shopify, Amazon).
- Price range — The rule only applies to products within a given price range.
Channel-scoped rules are especially useful for marketplace-specific requirements. For example, Google Shopping requires a GTIN for most products, but your own webshop might not.
Severity Levels
Severity determines the consequence when a product fails the rule:| Severity | Behavior | Best For |
|---|---|---|
| Block | Product cannot be exported. It is quarantined until the issue is fixed. | Critical requirements like missing GTINs or empty names. |
| Skip | Product is silently excluded from the export. Other products proceed normally. | Non-critical exclusions where you do not want the export to stall. |
| Warn | Product is exported, but a warning is logged in the audit log. | Nice-to-have improvements that should not block the export. |
Rule Preview
Before saving, you can click Preview to see a summary of your rule configuration — conditions, scope, severity, and status — all in one place. This helps you verify everything is correct before the rule goes live.Condition Logic
When a rule has multiple conditions, you choose how they are combined:- AND — The product must satisfy all conditions to pass the rule. Use this for strict requirements.
- OR — The product must satisfy at least one condition to pass. Use this for flexible requirements.
Best Practices
- Start with templates — Pre-built templates for popular channels give you a solid foundation quickly.
- Use descriptive names — Name rules clearly (e.g., “Google Shopping - GTIN Required”) so your team understands them at a glance.
- Begin with Warn severity — Start new rules as warnings to see their impact before upgrading to Block.
- Review top failing rules — Check the dashboard regularly to see which rules cause the most failures, then fix the underlying data.
- Keep rules focused — Each rule should check one logical requirement. This makes troubleshooting easier.