Which Amazon Reports Can Claude Actually Analyze?

If the question is which ASIN lost sales

Use seller Sales and Traffic ASIN summaries for two separate complete weeks in the same marketplace. Request date-level totals separately for the trend check. Amazon's report schema separates the date and ASIN arrays; it does not give you an ASIN-by-day table in one array. That detail matters when someone asks Claude for daily ASIN winners and losers from a weekly summary.

Start a 1stPage-connected Claude session by checking list_accounts. It shows which accounts and tool families the signed-in user can use. Seller ASIN changes belong in seller_analytics; vendor shipments belong in vendor_analytics; paid clicks require advertising_analytics and an authorized Ads account. Selecting a tool still does not fill a missing report or turn an account with no synced rows into zero sales.

An order-item extract poses a different question. Decide whether to count orders, items, ordered amounts, shipped amounts or refunds before grouping. Repeated order IDs across items are expected, not necessarily duplicate purchases. Data Kiosk can return a separately defined query as JSONL, but the query's fields and grain must be inspected rather than assumed equivalent to a Seller Central CSV.

If sessions are absent, you cannot compute a defensible session-to-order conversion measure from ordered sales alone. If one ASIN is missing in one period, check report filters and availability before treating absence as a zero. A useful output identifies the ASINs driving the observed change and leaves the cause for another source.

If the business supplies Amazon as a vendor

Vendor Analytics sourcing view covers directly sourced ASINs. Manufacturing view covers manufactured ASINs and includes ordered measures not present in sourcing view. Record which vendor group, view and marketplace produced each figure. Seller ordered sales and vendor shipped units should not be spliced into a single weekly growth rate just because they share a brand name.

The vendor dataset guide warns that recent periods can contain null values. An end-of-period inventory snapshot is stock at a point in time; summing seven daily snapshots does not produce a week's unit sales. Likewise, a missing vendor row may be a rights or coverage issue. Map identifiers deliberately when comparing seller and vendor ASINs, and show unmatched rows instead of joining by product title.

If the question is about paid media or shopping queries

For Sponsored Products spend or CPC, use the separately authorized Amazon Ads reporting scope and a report with spend and clicks. CPC is spend divided by clicks. Check the reporting lag, currency and attribution setting before reading attributed sales beside seller ordered sales. The same order can appear in different reporting windows; those sales figures are not independent totals.

For search behavior, eligible Brand Registry sellers with the Brand Analytics role can request Search Query Performance for selected ASINs and a valid WEEK, MONTH or QUARTER. Its query and ASIN measures include impressions, clicks, cart adds and purchases. Amazon defines its WEEK as Sunday through Saturday. An ASIN purchase share for a selected query is not a claim of overall category market share, and a one-ASIN request is not the whole brand.

Amazon Marketing Cloud is a separate option for an eligible advertiser with permitted pseudonymized inputs and aggregate outputs subject to privacy thresholds. Ask which datasets its instance has. Do not replace missing AMC access with an invented shopper path from a campaign CSV. For a quick question, choose the narrowest authorized report that actually contains the needed measure.

The permission check belongs to the specific report

The Selling Partner API assigns roles to operations and resources. Amazon documents 403 responses when the required role is missing, and report types have their own roles. Brand Analytics Search Query Performance requires the seller's Brand Registry eligibility and the Brand Analytics SP-API role. Seller permission does not create vendor or Ads rights. A person seeing a report in a console is not proof that a third-party application was approved for its API operation.

Write down whether the report exists for this account, the role is absent, the marketplace is outside its coverage, or the selected period has no available rows. Amazon's US-store Claude plugin beta does not assert universal access to these reports. The list here describes possible sources, not 1stPage product coverage.

Make the failure mode explicit in the request

For a US seller asking why two ASINs diverged, supply two completed weeks at ASIN grain and a source total for reconciliation. Ask Claude to mark missing rows, then calculate the observed difference. If the suspected cause is ad spend and no Ads report is supplied, its answer should stop before causal attribution. No broad marketplace trend can substitute for the absent advertiser record.

For vendor shipments, state sourcing or manufacturing and leave incomplete recent days out. For search demand, specify the query, selected ASIN set and Amazon's period boundary. For campaigns, hold the reporting and attribution windows steady. The useful report is the one that can survive this concrete question, not the one with the most impressive name.