Automation basics

Automations in Sellerwerk follow a simple pattern: if a metric crosses a threshold over a window, take an action. No ML black box — just rules you can read.

The parts of a rule

• Target — what to evaluate: keyword, ad group, campaign, search term, or ASIN.
• Condition — one or more metric comparisons, e.g.ACoS > 50% AND spend > €20.
• Window — the time range to evaluate over: 7, 14, 30, or 60 days.
• Action — what to do when the condition holds: pause, adjust bid ±%, change budget, set status to negative.
• Schedule — how often to check: every run of the daily sync, or a cron you define.

Example: pause bleeding keywords

Target: keywords on Sponsored Products campaigns. Condition: spend ≥ €20 AND 0 sales over the last 14 days. Action: pause the keyword. Schedule: daily.

This rule is aggressive on conversion signal and conservative on volume — it won't pause a keyword that only spent €3, because the sample size is too small.

Why every action is logged

We don't take hidden actions. Every automation write hits the Audit Log with the rule name, the values that triggered it, and a link to the Amazon API response. You can undo any action from the log within the same day.

Scheduling and windows

By default, automations run once after each daily Amazon sync (around 04:00 CET). For time-sensitive rules — e.g. Prime Day bid-raises — you can define a cron expression. We recommend not running cheaper than every 15 minutes to stay well within Amazon rate limits.