Skip to content

How the economics resolve

Break-even ACOS, Target ACOS and Max bid can each be set in four places. When a decision needs one of them, the App takes the most specific value that exists. Two places in Automation resolve them differently; see Where these values are used.

How an economic value resolves Four stacked levels, most specific at the top. The ASIN override is checked first, then the Product Group, then the Product Line, then the account default. The first level that has a value wins. 1 · ASIN override Set on the row itself. Beats everything. 2 · Product Group Applies to every ASIN in the group. 3 · Product Line The default for everything on the line. 4 · System default A built-in fallback, not something you set. The first level that has a value wins. An empty level is skipped, not treated as zero.

Resolution runs top to bottom and stops at the first level that has a value. A level you have left blank is skipped rather than counted as zero.

Each value in the ASIN table carries a badge naming the level it resolved from. A line badge means nothing more specific was set, so the Product Line’s default is in force.

That is how you tell an inherited 50% from a deliberate 50%. They look identical in the column and behave differently the next time you edit the line.

Leave it inherited when the ASIN behaves like its line. An inherited value keeps following the line, so when your costs move you change one number instead of forty.

Override when the ASIN genuinely differs — a size whose margin is not like its siblings, a product you are defending, a variant that attracts a different shopper. An override stops listening to the line permanently, which is the point, and also the cost.

The common mistake is overriding to make one bad week look better. That value is still there six months later, quietly ignoring every update you have made since.

The AI Analyst reads them when it builds proposals:

  • Break-even ACOS is the ACOS above which ads lose money. The Agent uses it to find keywords that waste spend.
  • Target ACOS is the ACOS the Agent moves bids toward.
  • Max bid derives the bid ceilings that proposal bids must stay inside. See Creating a Product Line.

Automation rules do not read them. A Bidding rule takes its Target ACOS and its Min and Max Bid from the rule itself, and an Import rule its own minimum and maximum bid. See Bidding rule.

Automation still shows them for reference, and resolves them its own way:

  • The Whitelist’s Recommended keywords rank terms against a Target ACOS taken from the Product Group first, then the ASIN override, then the Product Line, then 50%. A group value therefore beats an ASIN override there.
  • The Automated ASINs table shows the ASIN override’s Break-even ACOS, or else the Product Line’s. It does not read a Product Group value, and with neither the cell is empty.

The bottom level is a system default, not one of yours — so a badge reading default on a row means the opposite of what it looks like: nothing you configured supplied a value, and a built-in fallback did.

In that four-level order, Break-even ACOS and Target ACOS always resolve to something for that reason, and so does Max bid: its built-in default is $2.60. The bid limits on AI Analyst proposals are another matter. They come from a Product Line — its base-bid cap, worked out from the Max bid set on the line (see Product Lines) — so an ASIN with no Product Line gets no cap, and its proposals are not limited. Setting an account default Product Line, with a Max bid, is what stops that happening for unassigned ASINs.