Rule preview — read the sentence before you save

When you build an automation rule in Sellerwerk, the page shows a sentence above the bool builder — for example: “ACoS greater than 30% and clicks at least 5 over the last 7 days.”This is the natural-language preview. It's the same JSON the worker reads, rendered as a sentence. If the sentence reads wrong, the rule fires wrong; if it reads right, the rule is right.

Why we built this

The bool builder (AND / OR / NOT groups, lookback windows, thresholds) is power-user UI. It lets you build complex rules, but for most sellers reading their own rule it's harder than necessary. The preview gives you a one-line check: read it out loud — does it match what you intend?

How to read the sentence

• Metric — the leftmost word: ACoS, clicks, spend, ROAS, conversion rate, or one of the inventory metrics.
• Operator— “greater than”, “at least”, “less than”, “at most”, “exactly”, “not”, “between”.
• Value — formatted with the right unit: percentages get %, money gets €, ROAS gets x, days get days, plain numbers get the locale separator.
• Joiners — multiple conditions joined by and (all_of), or (any_of), or not (...) for negation.
• Lookback — at the end: “over the last N days”. This is the time window the metrics are evaluated against.

Examples

Pause a wasteful keyword:

“ACoS greater than 30% and clicks at least 10 over the last 7 days”

Reads as: fire if both conditions hold — ACoS above 30% (so the keyword is unprofitable) AND at least 10 clicks (so we have enough data to be confident).

Boost a strong performer:

“ROAS greater than 4x and conversion rate at least 8% over the last 14 days”

Reads as: very profitable AND consistently converting. Action: raise bid 15%.

Inventory protection:

“days of stock remaining less than 14 days or out-of-stock state exactly 1”

Reads as: stock is running low OR already gone. Action: pause ads so we don't waste budget driving traffic to a sold-out listing.

Nested groups

Complex rules show parentheses around nested groups so the structure is unambiguous. Example:

“ACoS greater than 30% and (clicks at least 10 or spend at least €20) over the last 7 days”

Reads as: ACoS over 30% AND (one of: 10+ clicks or €20+ spend). The parens tell you the OR is evaluated first, then combined with the ACoS condition.

What if the preview shows “value missing”?

If you see “ACoS (value missing)”, you haven't entered a threshold yet. The rule won't save until every condition has a value — fill in the empty field.

What if the preview shows “no condition yet”?

You haven't added any condition to the bool builder yet. Add at least one with the Add condition button.

The 3-second sanity check

Before you save a rule, do this:

1. Read the sentence out loud.
2. Ask: “If this fires, will the action make sense?”
3. If yes, save. If not, the bool builder is wrong — fix it there, the sentence updates live.

It sounds simple but catches almost every rule-building mistake before it touches a campaign.

Where is this preview shown?

Everywhere a rule is edited:

• The new-rule wizard at /rules/new.
• The edit page for an existing rule at /rules/[id]/edit.
• On a rule's detail page (read-only) so anyone reviewing the rule sees what it does without parsing JSON.

Related: Automation basics for triggers and actions overall, and Schedule rules safely for the four guards (templates, Dry Run, cooldowns, audit-log review).

For questions: support@sellerwerk.de.