Claude for Amazon

Business reports

Read the account before the morning gets busy

Summarize supplied Business Reports-style data into a daily or weekly operator brief. Claude compares traffic, order activity, sales, and Buy Box signals while preserving the report period and data limitations.

Try in Claude

Works with Amazon

Read the account before the morning gets busy illustration

Describe the task

Start with a bounded request

Summarize supplied Business Reports-style data into a daily or weekly operator brief. Claude compares traffic, order activity, sales, and Buy Box signals while preserving the report period and data limitations.

Prompt 
Create a [DAILY / WEEKLY] Amazon operator brief from the supplied Business Reports-style data for [BRAND / MARKETPLACE]. Compare matching periods across sessions, page views, units ordered, sales, and Buy Box percentage where available. Incorporate the promotion, stock, price, and listing-change notes I provide. Rank the changes that deserve attention, show the source rows, and distinguish correlation from a confirmed cause.

Do not change campaigns, prices, inventory, or listings.
Ask Claude

Provide the working context

Bring the source material Claude should trust

  • A current report containing sessions, page views, units ordered, sales, and Buy Box percentage where available
  • A prior comparison period with matching definitions
  • Known promotions, stock events, price changes, or listing edits during those periods

Review what Claude does

Inspect the reasoning and the proposed output

  • Normalizes current and comparison periods before evaluating movement
  • Ranks material ASIN changes by traffic, order activity, sales, and Buy Box signals
  • Connects known operational events to the timing without claiming causation
  • Returns a short watchlist and questions for the operator

Ready to run it?

Open the prepared prompt, then keep the final call with the operator.

Try in Claude

FAQ

Review the working boundaries

What should an operator brief surface first?

It should lead with the account changes that can alter today's priorities, while preserving the period and source behind each observation. Traffic, order activity, sales, and Buy Box signals should be compared on matching definitions. Known stock, price, promotion, and listing events add context but should not be presented as proven causes.

What context should I provide first?

Start with a current report containing sessions, page views, units ordered, sales, and Buy Box percentage where available. Then provide a prior comparison period with matching definitions. Keep dates, marketplaces, ASINs, and source definitions attached to the material so Claude can distinguish current evidence from background context.

What should be reviewed before acting?

A compact account brief with notable movements, likely lines of inquiry, and an ASIN watchlist tied to source data. Before approval, check the source records, stated assumptions, and every proposed change against the current account context.