Amazon Sales
Analyze connected Amazon sales data from Claude with Launch Fast MCP.
Analyze connected Amazon sales data from Claude with Launch Fast MCP.
Amazon Sales lets Claude review sales, orders, daily trends, and top products from Amazon Seller Central/SP-API data that has been connected and synced into Launch Fast. Use it when you want a plain-language readout of what sold, which products drove revenue, and how sales changed over a specific period.
Connect Amazon Seller Central/SP-API in Launch Fast Settings -> Authentication and wait for reporting data to sync before using this tool.
Tool Details
| Field | Value |
|---|---|
| MCP tool | amazon_sales_lookup |
| App UI | ui://launchfast/amazon-sales |
| Behavior | Read-only |
| Amazon account required | Yes — Seller Central/SP-API connection |
| Best for | Sales summaries, ASIN sales checks, daily sales trends, top product review |
When To Use It
| Use case | What it helps you answer |
|---|---|
| Account sales summary | How much sold across the selected date range. |
| Top product review | Which ASINs or SKUs drove sales or orders. |
| Product-level check | How one ASIN or SKU performed. |
| Daily trend review | Which days had spikes, drops, or unusual order volume. |
| Cross-tool follow-up | Whether sales trends should be compared with inventory, finance, rankings, or ads. |
| Order sample review | What recent order examples look like when available. |
| Account change review | What changed in your account over a specific window. |
What It Returns
| Result area | What Claude can summarize |
|---|---|
| Sales summary | Sales summary for the selected date range. |
| Totals | Order and revenue totals. |
| Daily series | Daily sales and order trend data. |
| Top products | Top products by sales, revenue, or orders. |
| Product breakdowns | ASIN-level or SKU-level sales details. |
| Order samples | Recent order samples when requested and available. |
| Account coverage | Account or connection coverage details when multiple accounts exist. |
The exact fields may vary based on synced Amazon data and the filters used.
Actions
| Action | Use when | Required inputs | Optional inputs |
|---|---|---|---|
summary | You want an account-level sales summary and top products. | None | date_from, date_to, seller_id, connection_id, sku, include_orders, order_limit |
by_asin | You want sales details for one ASIN. | asin | date_from, date_to, sku, seller_id, connection_id, include_orders, order_limit |
by_date | You want sales and order details for a specific date or date range. | None | date_from, date_to, asin, sku, seller_id, connection_id, include_orders, order_limit |
Inputs
| Input | Required | Notes |
|---|---|---|
date_from | No | Inclusive start date in YYYY-MM-DD format. Defaults to a recent window if omitted. |
date_to | No | Inclusive end date in YYYY-MM-DD format. Defaults to today if omitted. |
asin | Required for by_asin | Amazon ASIN to inspect. |
sku | No | Optional seller SKU filter. Useful when one ASIN has multiple SKUs. |
seller_id | No | Optional Amazon seller account filter. Useful when multiple seller accounts are connected. |
connection_id | No | Optional Launch Fast Amazon connection filter. |
include_orders | No | If true, includes a small recent order sample when available. Defaults to false to keep responses concise. |
order_limit | No | Maximum recent order rows to include when include_orders is true. Supports 1-10. |
Example Prompts
Single ASIN sales check:
Analyze my Amazon sales for B07HQM6NH8 from April 27 to April 28, 2026.Recent account summary:
Summarize my Amazon sales for the last 7 days and show the top products.Daily trend review:
Show my Amazon sales by date for the last 30 days and explain any spikes or drops.SKU-specific check:
Analyze sales for SKU DEMO-SKU-001 over the last 14 days.Top products:
Show which ASINs drove the most sales this month.Sales with order sample:
Summarize sales for B07HQM6NH8 last week and include recent order examples if available.Cross-tool follow-up:
Compare sales for my top ASINs with inventory risk and Sponsored Products spend.How To Read The Results
A sales result is most useful when you look at both totals and trend.
| Signal type | Look for |
|---|---|
| Positive signals | Sales increasing over the selected period, multiple products contributing to revenue, stable daily order volume, top products matching expected best sellers, or sales growth that lines up with ads or ranking improvements. |
| Risk signals | Revenue concentrated in one ASIN, sudden sales drops, sales spikes followed by inventory pressure, strong sales with weak profitability in Finance, sales growth driven by heavy ad spend without enough margin, or no sales for products receiving ad spend. |
Common Analysis Patterns
Use Claude to connect sales data to decisions.
| Pattern | Ask Claude to identify |
|---|---|
| Top product review | Which products drove most of your revenue. |
| Trend explanation | What changed day by day. |
| ASIN check | How one ASIN performed in an exact date range. |
| Inventory follow-up | Whether top sellers have enough stock. |
| Finance follow-up | Whether fees or settlements reduced profit on these sales. |
| Ads follow-up | Which sales may be connected to Sponsored Products spend. |
| Exception review | Which products sold less than expected. |
Suggested Workflow
Start With Summary
Run summary for the last 7 or 30 days.
Identify Top Products
Review the top ASINs or SKUs by sales and orders.
Inspect Product Sales
Use by_asin for deeper product-level sales analysis.
Review Trend Changes
Use by_date to inspect daily movement or specific sales windows.
Check Inventory
Follow up with Inventory to check stock pressure.
Check Finance
Follow up with Finance to understand fees and settlements.
Compare Ads
Follow up with Amazon Ads tools to compare paid spend against sales.
Common Empty Result Causes
Empty or thin results may mean no matching synced rows were found.
| Cause | Recovery |
|---|---|
| Seller Central/SP-API is not connected. | Connect Seller Central/SP-API in Settings -> Authentication. |
| Data has not synced yet. | Wait for sync to finish. |
| Date range is outside available data. | Try a broader or more recent date range. |
| ASIN or SKU had no orders. | Broaden the query or remove the product filter. |
| SKU spelling differs in Amazon. | Check the exact seller SKU and retry. |
seller_id or connection_id does not match. | Remove account filters and let Claude inspect available data. |
| Filters are too narrow. | Remove ASIN, SKU, seller, and connection filters. |
Try this recovery prompt:
Try the same sales analysis for the last 30 days and remove ASIN, SKU, seller, and connection filters.Safety Notes
Amazon Sales is read-only.
| It can inspect | It does not change |
|---|---|
| Synced sales, orders, daily trends, top products, ASIN/SKU breakdowns, and optional order samples. | Prices, listings, inventory, refunds, customers, orders, or Seller Central settings. |
Claude can summarize and recommend follow-up analysis, but any account changes must be made manually outside this MCP tool.
Limits And Notes
| Area | Note |
|---|---|
| Connection | Requires a connected Amazon Seller Central/SP-API account. |
| Rate limit | Amazon SP-API reporting tools allow 120 reads/min per user. |
| Data availability | Results depend on reporting data synced into Launch Fast. |
| Date format | Dates should use YYYY-MM-DD. |
| Order samples | Use include_orders only when order examples are needed because order rows add more detail to the response. |