How to Get Amazon Sales Data for Competitor Analysis

Getting Amazon sales data for competitor analysis comes down to a split workflow: Amazon gives you precise first-party data on your own ASINs through Seller Central and Brand Analytics, while competitor revenue has to be modeled from Best Sellers Rank (BSR) movement and pulled at scale through third-party marketplace APIs — Amazon never publishes exact unit sales for someone else's listing. The skill worth developing is knowing which figure is measured, which is estimated, and how to layer both with off-Amazon signals such as TikTok Shop creator GMV so the benchmark survives contact with reality.

What Amazon Sales Data Actually Is (and What You Can Realistically Access)

Two very different things get called "Amazon sales data," and conflating them is the fastest way to build a competitor model on sand.

The first is first-party data you own: order counts, sessions, conversion, units ordered, buy box percentage, returns, and settlement details for your own products. This lives in Seller Central reports and, for Brand Registry members, in Brand Analytics. It is accurate because Amazon is reporting on transactions it processed for you.

The second is third-party estimation for competitor ASINs. Amazon does not disclose how many units a rival sold last month. Any number you see for a competitor's revenue is a model output — typically a category-specific curve that maps BSR to daily unit velocity, multiplied by price. Directionally useful, never accounting-grade.

For competitor analysis, the data types that actually earn their place in a dashboard are:

• BSR and category rank trends — the raw signal everything else is derived from, and more informative as a time series than as a snapshot.
• Estimated monthly units and revenue — the headline figures, best read as ranges rather than point values.
• Price history — including coupon and deal-adjusted prices, since a 20% clipped coupon quietly rewrites the revenue math.
• Review velocity — new reviews per week is a rough but stubbornly reliable proxy for unit movement.
• Buy box share — critical on listings where multiple sellers compete, because listing-level revenue can hide who actually captured it.

Set expectations early with your team: rank-to-sales models carry a real margin of error, and that error widens in small categories, around Prime Day and Q4, and on variation-heavy parent-child structures. The goal is directional benchmarking — is this competitor growing, flat, or fading, and by roughly how much — not precision to the unit.

Method 1: Mine Amazon Brand Analytics and Seller Central for First-Party Signals

The Brand Analytics reports worth opening first

Brand Analytics requires Brand Registry, which immediately limits it to your own brand — but it still tells you a great deal about competitors because it describes shopper behavior, not just your sales.

• Top Search Terms shows the highest-volume queries in each category with click and conversion share by ASIN, so you can see which competitor listings are capturing demand on the keywords you care about.
• Search Query Performance breaks impressions, clicks, cart adds, and purchases down by query, exposing where you lose the click versus where you lose the conversion — often two different competitors.
• Item Comparison reveals which ASINs shoppers compare against yours, which is effectively Amazon telling you who your real competitive set is.
• Market Basket Analysis shows what else gets bought alongside your products, useful for spotting adjacency plays and bundling threats.

None of these report competitor revenue. What they give you is the traffic and cross-shopping context that makes a revenue estimate interpretable.

Business Reports and the Reports Repository

In Seller Central, Business Reports offers Detail Page Sales and Traffic by ASIN and by Child Item — sessions, page views, unit session percentage, units ordered, and ordered product sales. Export to Excel or Sheets and you have a clean baseline for benchmarking your own ASINs against the category leaders you're tracking. The Reports Repository is where you schedule and retrieve the heavier datasets (orders, inventory, returns) for anyone building a repeatable comparison rather than a one-off read.

Where the limits bite

Brand Analytics describes search and comparison behavior on Amazon's side of the wall; it does not contain competitor sales. Treat it as the context layer that tells you why a competitor's rank is moving, then pair it with an estimation method for the how much.

Method 2: Estimate Competitor Sales with BSR Models and Third-Party Tools

BSR-to-sales estimation works on a simple premise with a complicated implementation. Within a category, rank and daily unit velocity follow a steep, non-linear relationship — the gap between rank 50 and rank 500 is enormous, the gap between rank 5,000 and rank 5,450 is not. Tools build category-specific curves from historical observation, map a competitor's current rank onto that curve to get estimated daily units, then multiply by the current selling price to estimate revenue. Sub-category, size, and seasonality all shift the curve, which is why two tools can hand you different numbers for the same ASIN on the same day.

The mainstream options are well known in Amazon product research circles. Jungle Scout pairs a sales estimator with a product database and opportunity scoring; Helium 10 bundles estimation into a much broader suite of listing and advertising tools — the practical home for using keyword data to estimate competitor sales — while SellerApp leans toward a lighter research and analytics workflow. Free estimator utilities exist as well and are fine for a sanity check on a handful of ASINs, though they typically lag on data freshness and offer no history.

Accuracy caveats to keep in front of you:

• Seasonal spikes distort curves trained on annual averages — a Q4 rank means something different in July.
• Category size differences mean the same rank implies wildly different volume in Beauty versus Industrial Supplies.
• Variations are the most common source of error: parent-level rank with child-level sales gets misallocated constantly.
• Coupon-adjusted prices matter because revenue estimates built on list price overstate actual take.

Triangulate before you trust

Never act on a single estimator's output. Cross-check the BSR-derived figure against review velocity (a listing adding reviews fast is moving units), the "bought in past month" badge where Amazon displays it, and stock-out patterns — a competitor who sells out every three weeks is telling you more about demand than any model. When three independent signals agree, you have a number worth putting in a slide.

Method 3: Pull Amazon Sales Data at Scale with APIs

The Amazon Selling Partner API (SP-API) is the official programmatic route — for your own data. Orders, inventory, pricing, settlements, and reports are all available, and it is genuinely powerful for automating your own reporting. It is also the source of a persistent misconception: SP-API does not expose competitor sales. It authenticates you as a seller and returns what belongs to you. No amount of clever endpoint work changes that.

For competitor data at scale, teams use third-party marketplace data APIs that normalize product, pricing, rank, and sales-estimate data across marketplaces. This is the route Deviantly API is built for: rather than a single-channel Amazon report, it is designed to serve Amazon, TikTok Shop, and DTC data through one interface, so a competitor set can be tracked on a schedule instead of being scraped by hand. That matters more than it used to, because competitors increasingly scale off-Amazon first — a brand that looks mid-tier on Amazon may be doing serious volume through TikTok Shop creators.

A short compliance note: scraping Amazon directly runs into Terms of Service restrictions, rate limits, and CAPTCHA defenses, and the maintenance burden compounds as pages change. For agencies and developers, a managed API is usually the safer and cheaper operational choice — and it keeps the data pipeline from becoming someone's full-time job.

Turning Raw Sales Data into Actual Competitor Insight

Data collection is the easy half. A practical Amazon competitor analysis framework that produces insight looks like this:

• Share of voice by keyword — track which competitor ASINs hold click share on your priority queries, and how that shifts month to month.
• Price and rank movement over time — plot both on the same axis; a rank climb that coincides with a price cut tells a very different story than one that does not.
• Competitor archetypes — segment rivals as category leaders (defend against), fast followers (differentiate from), or price disruptors (compete on bundle and content, not price).

Then layer in cross-marketplace signals. A competitor gaining TikTok Shop creator traction is often a competitor about to gain Amazon rank, and the reverse holds too. Deviantly Trends offers marketplace analytics for spotting fast-moving products before they show up in rank data, while Creator Intelligence tracks creator and affiliate performance so you can see which partners are driving a rival's growth. Because Deviantly is positioned as AI e-commerce intelligence spanning TikTok Shop, Amazon, and DTC brands, this layering happens inside one workflow rather than across three unrelated dashboards.

Cadence matters as much as method. Take weekly rank and price snapshots for movement detection, refresh revenue estimates monthly so noise doesn't masquerade as trend, and run quarterly deep dives on two or three priority competitors. Daily data invites overreaction to what is usually variance.

Common Pitfalls and a Practical Step-by-Step Workflow

The recurring mistakes are predictable: treating an estimate as an exact figure, comparing ASINs across mismatched categories, ignoring variations and parent-child structures, and forgetting seasonality entirely. One more subtle trap — a lesson the TikTok Shop API changes taught the wider market — is that marketplace API-derived data needs validation before it feeds a benchmark. Attribution gaps in platform reporting mean a raw number can be structurally wrong even when it is delivered cleanly.

A repeatable workflow:

1. Define the competitor ASIN set — a tight list of 10 to 30 ASINs beats a sprawling scrape.
2. Pull Brand Analytics for search and comparison context, so you know which queries and rival listings actually matter.
3. Generate sales estimates via a research tool or a marketplace data API, recording the method and date.
4. Validate against review velocity, badges, and stock-out patterns; flag anything that disagrees by more than you're comfortable with.
5. Document assumptions and refresh on a fixed schedule so comparisons stay like-for-like.

Choosing a tool stack

Apply the same filter Deviantly uses when reviewing analytics platforms: pick the metrics that drive views and revenue, not the largest possible metric volume. For most teams that means BSR trend, estimated revenue, price history, review velocity, and one off-Amazon growth signal — which is enough to know whether a competitor is genuinely pulling ahead, and enough to act on before the next quarterly review rather than after it.

by Olivia Bennett Carte, Senior Social Commerce Journalist & Ecommerce Research Analyst

Olivia Bennett Carter is a Canadian ecommerce journalist specializing in social commerce, creator marketing, and competitive intelligence. Her research focuses on TikTok Shop, Amazon marketplace trends, affiliate discovery, and advertising analytics. She translates complex platform developments and emerging retail trends into accessible, actionable insights that help online sellers and digital marketers make informed decisions.