/decisions · 2026-05-11 · board backfill · squarely

Squarely Amazon ads — approve sensors-build approach

Decision logged from the Notion task board. Click an action to fire an iMessage back to the Ray session with the decision encoded.

Founder-named critical component 2026-04-30. Three capability paths (Amazon Ads API vs Helium 10/Sellics/Perpetua vs scrape Seller Central). Founder picks the path Ray builds against.

Context

Critical Component flag on this ticket. 'Done' = programmatic visibility into ACoS, ROAS, impressions, clicks, conversion, spend-by-campaign + daily/weekly snapshot.

Path options:

  1. Amazon Advertising API (registration + approval; not trivial)
  2. Helium 10 / Sellics / Perpetua programmatic export (paid third-party)
  3. Scrape Seller Central reports (fastest, fragile)

Cross-bet payoff is HIGH — same capability serves any future Amazon-channel bet.

Lock in

Approve

Greenlight the action with optional context (instructions, scope notes, anything Ray should carry into execution).

Approve + send
Archive

Drop this from the active board. Add a one-line reason so the kill is on the record.

Archive + send
Split

Keep part, defer part. Use the two fields to describe each.

Split + send
Defer

Push this out to a specific date.

Defer + send