And / Or Conditions

When setting up automations and return rules, you define when a specific rule should be triggered. To do this, you use the logical operators AND and OR. Choosing the right one is critical for a flawless workflow.

2. Practical Examples

To better understand the difference, let’s look at how to include or exclude specific product colors in your return process.

A. The AND Condition (Restrictive)

Use AND when you want to stack multiple criteria that a product must meet simultaneously.

• Rule: Product is NOT red AND product is NOT blue.
• Result: Only products with a different color (e.g., green or yellow) are accepted. A red product will be rejected because it fails the "is NOT red" requirement.

B. The OR Condition (Inclusive)

Use OR when there are multiple separate scenarios where the rule should apply.

• Rule: Product is red OR product is blue.
• Result: The rule triggers as soon as the product is red OR as soon as it is blue.

3. The "Logic Trap" with Exclusions

Be very careful when using OR in combination with negative statements (is NOT / does NOT contain).

Important: If you set a rule as "Product is NOT red OR NOT blue," the result will always be true.

• A red product is not blue (so the OR condition is met).
• A blue product is not red (so the OR condition is met).
• A green product is neither (so the OR condition is met).

Golden Rule: If you want to exclude multiple specific items, always use AND.

4. Configuration Checklist

Ask yourself these questions before saving a rule:

1. Does the product have to meet every single requirement in this list? → Use AND.
2. Is it enough if only one of the requirements in this list applies? → Use OR.
3. Am I using "is not" or "does not contain"? → Double-check that you haven't used OR where AND was intended.