Turn an Amazon business question into a report-backed Claude analysis without confusing seller sales, vendor data, ads, and shopping queries.
Take the sales-drop question apart
Suppose ordered sales are down for one seller account. Pull two complete weeks from the same US marketplace in Seller Central Sales and Traffic. Compare ordered sales and traffic first; use the report's ASIN summaries to see which products contributed to the difference. If visits held steady while orders fell, inspect conversion and availability before telling the ads team to cut spend. If visits fell, a paid-traffic change is possible, not yet established.
With 1stPage connected to Claude, choose the seller account and ask which ASINs changed across two complete weeks. Check the marketplace and dates on the returned result before using its deltas. If paid traffic becomes the next question, request the account’s Ads data separately. A seller answer does not secretly include advertising rows.
Claude needs the report itself, or access through a tool the account owner has approved. Give it the exact comparison weeks, account, marketplace and metric names. Ask it to show the contributing ASINs rather than declare a cause from an account total. An ASIN absent in one week needs investigation: missing rows are not automatically zero sales. Keep the original report close enough to check the result.
For a different question, change the source. An advertising search-term report can show paid spend and attributed outcomes; it cannot by itself measure organic shopping demand. Brand Analytics Search Query Performance shows eligible query and ASIN funnel measures, not a substitute for seller ordered sales. A vendor's sourcing view is not a seller's sales ledger. One polished answer built from the wrong ledger is worse than an honest unanswered question.
For my US seller account, compare the two complete weeks ending September 19, 2026. Separate a change in visits from a change in conversion. State the report, date range, and denominator used for each claim; mark anything that would require Ads or inventory data as unanswered.
Pick the route that fits the frequency
For a single question, download a permitted report and make a reduced working copy. Ask Claude what its columns and row grain mean before asking why a number moved. A file from last Tuesday does not update itself overnight. If the task becomes a Monday routine, repeat uploads are a manual process with an owner and a refresh step, not a connection.
A recurring setup can expose approved data through tools. Anthropic documents remote custom connectors in Claude.ai, while Amazon documents Selling Partner API permissions and authorization. The application, account owner and supported Claude client all matter. An approved seller grant does not extend to a vendor group, a second store or an Ads advertiser. Ask the operator what that particular connection can read; do not infer coverage from the word ‘connected.’
Amazon announced a Selling Partner plugin in beta with Claude for eligible sellers in its US stores. Amazon also describes Seller Assistant recommendations and approved actions with permission and audit boundaries. That native beta is a separate path from a file upload or a separately authorized connector. Check eligibility and terms rather than writing a universal installation recipe. ‘Seller Assistant’ can also name a different browser extension; neither name supplies a Claude login.
I uploaded the US Sales and Traffic report for September 7–13, 2026. Before analyzing it, list the file's date range, level of aggregation, and available measures. Tell me which questions the report cannot answer on its own.
Use the second report only after the first reveals a gap
If the seller report shows lower visits, pull the matching Ads campaign or search-term report if paid activity is in scope. Compare spend and clicks there, then inspect the relevant attribution setting before comparing attributed ad sales with retail ordered sales. Different event dates can move the same purchase into different weeks. Do not add the two sales figures together as if they were independent revenue streams.
If orders weaken despite steady visits, inspect inventory and offer status for the affected ASINs. Inventory is a separate source, and a snapshot is not a running total. If the real question is whether shoppers changed their search behavior, request eligible Brand Analytics data for the relevant query and ASIN set. Its funnel shares do not prove that a ranking change caused the seller's revenue decline.
This sequence is intentionally uneven. Some questions stop at the sales report. Others need one more authorized source. If access is missing, leave that branch open rather than manufacture a bridge between metrics.
Put a proposed action through one hard check
Before pausing a campaign, verify that its paid report identifies the spend and outcome you mean to change. Before ordering more stock, use current stock, inbound units and your own lead time, not a narrative about falling conversion. Before changing a listing, confirm the affected ASINs and the period in which the issue appeared. Have Claude identify the number that would reverse its recommendation, then locate that number in the source.
Never put an Amazon password, OAuth refresh token or API key in a prompt. Remove fields the question does not need and follow the organization's data-sharing rules. The person who authorized an export or connection should be able to revoke or replace it. 1stPage exposes account-scoped tools for permitted data in supported assistants. That does not mean every report named here is available to every account. A useful answer ends at the evidence the account actually permits.
Sources and boundaries
Check the current permissions and report definitions before acting on an answer. Example prompts are questions, not live account results.