Amazon competitor analysis checklist: evidence, review, and handoff

By Scoutvo · Published October 16, 2026 · Updated October 16, 2026 · 6 min read

Use the checklist as a release gate for decisions

This Amazon competitor-analysis checklist helps a researcher or manager decide whether an analysis is ready to use. Each item needs a status and evidence, not merely a tick. Use “verified,” “not applicable,” “pending,” or “unavailable,” and name the person responsible for unresolved work.

The checklist complements the seven-step analysis guide. It does not replace the underlying observations, and completing it does not validate a sales forecast. Its purpose is an accountable handoff: someone else should understand the sample, inspect the evidence, and know what remains uncertain.

Start a worksheet with analysis ID, decision owner, decision deadline, marketplace, target ASIN, collection dates, version, and evidence-folder location. Add a row for each check below with its evidence reference, reviewer, status, and follow-up date. Keep the worksheet with the report.

A. Confirm the decision brief

• State the decision in one sentence: revise copy, investigate price position, assess an assortment option, or inspect an offer change.
• Define the target product, condition, marketplace, delivery context, and relevant customer use.
• Record the available product specifications and authorized account reports.
• Set the scope of the analysis and name exclusions, such as advertising profitability or competitor sales that are not directly observed.
• Agree what evidence would be enough to act and what would require more research.

Acceptance condition: the recipient can describe the intended action without relying on an unexplained score. If the brief mixes a product-range decision with minute-to-minute repricing, separate the questions first.

B. Verify the competitor sample

• Record selection sources: documented search queries, category boards, and deliberate benchmark products.
• Distinguish organic results, sponsored placements, category ranks, and manually added references.
• Retain child ASIN, known parent, brand, product type, timestamp, and inclusion reason.
• Deduplicate repeated ASINs and identify children sharing a family.
• Separate close substitutes, premium or adjacent references, accessories, bundles, and out-of-scope products.
• Record inaccessible listings and exclusions rather than silently replacing them.

Acceptance condition: the counts reconcile at each level. Ten child observations from three families are ten children and three families, not ten independent sellers. Use the competitor-selection guide when the sample boundary is unclear.

C. Check offers, prices, and identity

• Keep product, brand, seller, and fulfillment provider separate.
• Record seller ID, observed Featured Offer context, condition, availability, and delivery promise.
• Capture item price, mandatory shipping, currency, tax context, and conditional promotions separately.
• Compare the same child and offer context over time; keep category comparisons within meaningful product groups.
• Mark successful observations, failures, unavailable offers, and stale carried-forward values distinctly.
• For seller-location work, retain profile and register evidence and preserve unresolved classifications.

Acceptance condition: a reviewer can reconstruct what the displayed total meant for the recorded context. An address does not establish manufacturing costs, and an observed Featured Offer does not establish a seller's daily sales share. Amazon's Featured Offer guidance is relevant to offer interpretation.

D. Review listing, keywords, and feedback

• Check product facts before recommending attributes or copy.
• Distinguish an applicable empty field from an unavailable collected field or a non-applicable attribute.
• Define the corpus, field set, normalization, matching rule, and denominator for keyword coverage.
• Label vocabulary gaps separately from query demand, indexing, observed position, and conversion.
• Trace review themes to sampled text; state dates, languages, products, and whether counts mean reviews or mentions.
• Check variation themes and functional differences against current category guidance before proposing a family change.

Acceptance condition: every recommendation is compatible with the actual product. A common competitor claim remains unsuitable without product-specific evidence. The keyword-gap worksheet makes the approval path explicit.

E. Reconcile metrics and evidence classes

Every number should identify its unit, denominator, period, source, and evidence type. Preserve a provider's definition rather than relabeling a model output as a measurement.

Illustrative reconciliation: a worksheet contains 12 child products from seven families and prices for ten children. Its price summary uses ten priced children; its family summary uses seven families. These teaching values are not a Scoutvo dataset. A missing price is not zero, and neither count reveals units sold.

Acceptance condition: no percentage changes denominator without explanation, no selected rows are presented as a complete census, and no rank is converted into observed revenue. See Amazon's BSR explanation for the distinction between relative rank and other measures.

F. Prioritize actions and hand off responsibility

Choose a small actionable set. For each item, record the finding, evidence reference, intended correction or test, product or policy prerequisite, owner, due date, measurement, and stopping condition. Separate verified factual corrections from experiments and longer-term commercial research.

Acceptance condition: the person receiving the report can start a bounded task. “Improve visibility” is not a complete assignment. “Verify the supported capacity, correct the applicable field, and inspect the selected child” is.

Close the review without hiding unresolved work

Before approving the report, sample-check source records and internal links, read the main recommendation alongside its caveats, and ensure tables use explicit units. Check that the executive conclusion does not promise more than the evidence sections support.

Keep blocking items visible. Unsupported product claims block publication of those claims; unavailable competitor accounting does not block a carefully limited listing audit. Assign the missing export, product check, or source confirmation to an owner instead of inventing a replacement statistic.

Record the version approved for the decision, who reviewed it, and when the sample should be refreshed. Preserve earlier versions so changes in methodology or product membership can be distinguished from market changes. The Scoutvo methodology provides a reference for evidence boundaries.