1
Evidence attached
Every row carries the numbers that justified it — spend, clicks, window. You judge the case, not the robot.
PUBLISH QUEUE · APPROVAL-FIRST
Every change staged. Nothing ships without you.
Lookouts and assistants propose; the queue holds every change with its evidence until you approve it — row by row, in your browser.
QUEUE · 2 PROPOSALS WAITING Sample data
- LOOKOUT Lower bid €0.42 → €0.31 — “dog gifts” spent €6.80, returned €0 Approve Reject
- CLAUDE Add negative “free svg” — 214 clicks, 0 sales, 90 days Approve Reject
2
Row by row, never blind
Approve, skip or reject each row. Publish all only sends the rows you already approved.
3
Provenance on every row
Where a row came from — a Lookout, an assistant or you — stays on it through Done and Failed.
What is sent to Amazon today. Of the changes described here, MerchPPC sends the kinds it has confirmed against Amazon: a target's bid, a campaign's budget, a negative keyword and a new Auto campaign. Not sent yet: an ad group's default bid; a campaign's placement adjustments; a campaign's bid strategy; a campaign's audience bid adjustments; pausing or enabling a target, an ad, an ad group or a campaign; a negative product; removing a negative keyword; removing a negative product; promoting a search term to a keyword; adding a product target; adding a product to an ad group; adding products to a new ad group; a new manual campaign; a new Sponsored Brands campaign; one Auto campaign per product from a selection; splitting a campaign; a Sponsored Brands keyword's bid; a Sponsored Brands target's bid; a Sponsored Brands theme's bid; pausing or enabling a Sponsored Brands campaign, ad group or ad; a Sponsored Brands negative keyword; a Sponsored Brands negative product; a price change; adding a missing product; republishing a product; deleting a product. The extension shows those as “Not available yet” and holds them back until each one is confirmed.
Stage, approve, publish
One queue. You hold the button.
Sample data
Pending3
Bid · "funny cat shirt"$0.62 → $0.41
Budget · Cat Mom, auto$10 → $6
Staged by ClaudeNegative "free shirt"
Approved1
Pause · Hoodies, manualEnabled → Paused
Done2
Bid · "axolotl shirt"$0.35 → $0.42
Budget · Dog Dad, auto$5 → $8
Failed1
Bid · archived targetAmazon refused it
Where rows come from
Four ways in. One way out.
Whoever staged it, a change lands in the same queue and waits the same way.
YouFrom the console or a product page
LookoutsProposals from every sync
CatalogA selection, one action
Claude or ChatGPTWaits for its own OK
Publish queue
Pending until you approve
You decide
Amazon
Only after Publish all
Anatomy of a row
Everything you need to say yes or no.
Staged byLookout
Target"funny cat shirt"
Spend · 30d$18.40
ACoS61.4%
Break-even41.3%
Bid$0.62 $0.41
Queued
1Who staged itYou, a Lookout, a Catalog action or an assistant.
2The evidenceThe numbers that made the case, with their window.
3Now and nextThe value today and what it would become.
4Not yetQueued means nothing has reached Amazon.
Two roads to Amazon
Ads go straight. Merch changes, you can watch.
Advertising changes
Bids, budgets, negatives and campaigns go through Amazon's API the moment you press Publish all.
Merch changes
Prices and new products run in an automation tab that opens in front of you, one design at a time. Close it and the rest goes back to the queue.
The rules
Six things the queue never does.
-
01
Now and next, side by side
Each row shows the value now, what it would become, and that it has not happened.
-
02
Four groups
Pending, Approved, Done and Failed, so you always know where a change stands.
-
03
Nothing on a timer
Publish all runs when you press it, and at no other time.
-
04
Failures stay visible
Anything Amazon refuses keeps its reason and is not retried behind your back.
-
05
Merch changes you can watch
Prices and new products run in a tab that opens in front of you.
-
06
Assistants wait longest
A row Claude or ChatGPT staged needs its own approval; Publish all skips it.
Use cases
How a change gets to Amazon.
1After a bad week
Ten targets went over break-even at once.
- Stage a lower bid on each, from the console or a Lookout.
- Read the rows: now, next, and why.
- Approve them in bulk and press Publish all.
Ten changes, one review, sent when you decide.
Pending10 bids
Approved10 bids
Done10 bids
Sample data
2An assistant's idea
Claude suggested three changes while you were away.
- Open Publish and find the rows it staged.
- Approve each one on its own row.
- Or delete it, and nothing happens.
An assistant's change never rides along with Publish all.
Staged byClaude
Negative"free shirt"
Waits forIts own OK
Sample data
3Amazon said no
One change could not be applied.
- Find it under Failed.
- Read the reason Amazon gave.
- Fix it and stage it again, or let it go.
Nothing is retried behind your back, and nothing fails silently.
Bid$0.48 → $0.39
FailedTarget archived
RetriedNever on its own
Sample data
Questions
Good to know.
What if I delete a pending row?
Nothing happens. That is the point of the queue.
Do Lookouts change anything by themselves?
No. A Lookout proposes, and its proposals land here like any other change.
What if I close the automation tab?
The rest of the run goes back to the queue instead of being lost.
Why not apply changes automatically?
Because you know things the data does not, like a design you are about to relaunch.
Works with
Better together.
Automation that waits for your click.
The queue is where trust in the whole system is built.