Amazon Glance Views: Diagnose Flat Vendor Sales

Use the Selling Partner MCP to compare Amazon glance views with matching Sales and Inventory reports in Amazon Retail Analytics (ARA), then separate fewer Retail sales opportunities from weaker units per view and worsening availability. That's the first useful answer to “traffic is up, so why are sales flat?” The result is an Amazon Standard Identification Number (ASIN) diagnostic report with a next check for each finding. It gives your team a defensible investigation before anyone changes a bid or rewrites a page.

ChatGPT, Claude, and Perplexity know nothing about your business out of the box. Your competitors use the same tools. Kuudo gives those tools your data, your rules, and your way of working: your account as it is right now through MCP connections, your judgment running every time through Skills, and your call before anything changes through approval controls. Amazon Agent Atlas grounds the Amazon rules. Your ASIN priorities, comparison tolerances, and decisions belong to you.

Start with this diagnostic matrix. OOS means out of stock. These are investigation rules, not causal findings from Amazon:

“Steady” means within your team's existing tolerance. Without one, show the changes and leave the classification provisional.

A matched reporting scope comes before diagnosis

A missing row is an unresolved comparison, not a zero. Check that both periods contain the same marketplace, ASIN cohort, and dates before explaining any movement.

The Amazon Retail Analytics playbook distinguishes Sourcing from Manufacturing: Sourcing covers products Amazon sources from the vendor group; Manufacturing covers the manufacturer's products regardless of supplier. Traffic, Net Pure Product Margin (PPM), and Forecasting dashboards are only displayed to manufacturers. If an eligible account lacks Traffic access, contact your retail partner or Vendor Central's Contact Us route. An MCP connection does not change that entitlement.

For this workflow, request GET_VENDOR_TRAFFIC_REPORT, GET_VENDOR_SALES_REPORT, and GET_VENDOR_INVENTORY_REPORT. The Selling Partner MCP's Reports_createReport, Reports_getReport, and Reports_getReportDocument request the reports, check completion, and retrieve their contents. The Amazon Retail Analytics EDI/API integration playbook maps these report types to their dashboard metrics.

Use MANUFACTURING and RETAIL for Sales and Inventory. Traffic's report options require reportPeriod; don't add the Sales and Inventory view options to Traffic. Record each report's scope before joining its rows.

Compare two complete Sunday–Saturday weeks. Amazon's current Analytics Reports documentation gives weekly reports a 48-hour availability window after the week closes, through the end of Monday. Non-Saturday daily reports have a 72-hour window. Premature requests can return FATAL, so “the week has ended” is not sufficient evidence that its reports are ready.

Inspect report completion and lastUpdatedDate. Keep missing ASINs visible: they can reflect no data for the period, a view mismatch, or vendor hierarchy and mapping issues. Resolve the scope or mark that comparison unavailable.

Amazon glance views measure Retail sales opportunities

Amazon glance views in ARA count ASIN detail-page views when Amazon Retail is the featured seller, also called the featured offer. They are neither unique shoppers nor advertising clicks.

That restriction changes the diagnosis. A drop in glance views could reflect less demand or fewer opportunities with Retail as the featured seller. The Traffic series alone cannot separate them. The dashboard is a useful starting point because it makes traffic changes visible; that does not establish an earlier refresh than other dashboards.

Keep Advertising reports beside this analysis as context. They measure ad impressions and clicks using different inputs and filters. There is no reason to require their totals to equal ARA glance views, and ad clicks do not belong in the denominator of an ARA units-per-view calculation.

If your Amazon Ads MCP connection is available, ask for a separate campaign context section. A change in ad engagement can suggest where to investigate the traffic mix. It does not turn the ARA comparison into advertising attribution.

Units per view and revenue per view answer different questions

Ordered units divided by glance views is a unit-based conversion proxy. Ordered revenue divided by glance views is currency per view. Neither measures the probability that a unique shopper buys.

Amazon's own Amazon Retail Analytics playbook uses conflicting numerator wording: its general dashboard section describes conversion with ordered units, while its Traffic subsection describes it with ordered revenue. Preserve that conflict in the report's metric notes. Explicit column names are more useful than choosing one formula and calling it “conversion.”

The unit-based ratio is not bounded like a purchase probability: units are not unique buyers. The revenue ratio is not a percentage. Label its currency, and retain the ordered basis throughout. Mixing shipped units with ordered revenue answers a different question. The ARA Sales dashboard guide explains those sales bases.

If units increase while revenue stays flat, examine derived ordered revenue per unit and the product mix. Don't call that calculation Amazon's shipped average selling price (ASP) metric.

For a group of ASINs, sum the included numerators and denominators first, then divide. Averaging individual ASIN ratios gives a small ASIN the same weight as a large one. Use the same included cohort in both periods, and return unavailable when the denominator is zero or a required input is absent.

Availability needs its exact out-of-stock cohort

The Inventory report returns procurableProductOutOfStockRate; it does not return a field named Sourceable Product OOS. Those labels must stay separate.

The Amazon Retail Analytics metric glossary defines Sourceable Product OOS using out-of-stock glance views on sourceable ASINs divided by total glance views. Procurable Product OOS uses out-of-stock glance views on procurable ASINs divided by total glance views. Procurability considers whether Amazon can source the product without a purchase-order delay, including known vendor supply and the customer promise.

Preserve the reported rate and its exact name. If you supply Sourceable Product OOS from an eligible dashboard or export, retain it as a separate field with its source and cohort. The available evidence does not establish that the two cohorts are interchangeable. Don't reconstruct either OOS rate from Traffic glance views unless you have validated the denominator and cohort equivalence.

Rising Procurable Product OOS points toward an availability investigation. Sellable on-hand describes physical condition; it does not guarantee a buyable offer. A blank OOS metric is unknown, and Sourcing view can omit metrics available in Manufacturing. Stable weekly OOS also leaves room for stockouts within the week. The rate does not prove how many sales were lost.

Request the diagnostic report

Copy this prompt into your connected AI client. The requested artifact is an analysis report, with one reviewable finding per ASIN:

Using my authorized Selling Partner MCP, produce an ARA traffic-and-sales
diagnostic report for the ASINs and marketplace in this conversation.
Ask for any missing inputs before requesting reports.

Compare the latest two complete, available Sunday–Saturday weeks using
GET_VENDOR_TRAFFIC_REPORT, GET_VENDOR_SALES_REPORT, and
GET_VENDOR_INVENTORY_REPORT. Set reportPeriod=WEEK on all three.
Traffic has no distributorView or sellingProgram option. For Sales and
Inventory, set distributorView=MANUFACTURING and sellingProgram=RETAIL.
Confirm dates, marketplace, cohort, report completion, and lastUpdatedDate.
Ground definitions in Amazon Agent Atlas's Amazon
Retail Analytics, Amazon Retail Analytics metric glossary, and Amazon
Retail Analytics EDI/API integration playbooks.

For each ASIN, show both periods and changes for glance views, ordered
units, ordered revenue with currency, ordered units per glance view,
ordered revenue per glance view, and procurableProductOutOfStockRate.
Preserve any supplied Sourceable Product OOS separately. Mark missing
rows, zero denominators, and incomplete comparisons unavailable.
Aggregate only ordered-units/view and ordered-revenue/view by dividing
summed numerators by summed denominators for the same included cohort.
Preserve reported OOS rates. Do not average them or rebuild them from
Traffic views; any OOS aggregation needs validated native denominators.
Label count and currency changes as absolute and relative percent.
Label ratio-change units explicitly. Confirm the reported OOS scale,
then show OOS changes in percentage points. Leave relative change
unavailable when its base is zero.
Note Amazon's conversion wording conflict.

Triage incomplete comparisons first. Falling views with steady units/view
nominate demand and featured-offer checks. Rising views with falling
units/view nominate availability checks if OOS rises; if OOS is steady,
check offer, price, page, and traffic mix. Units up with revenue flat
nominates price and product mix. Treat these as candidate explanations.

Include the next check, missing evidence, owner, and approval state.
Use my materiality thresholds if supplied; otherwise show deltas without
inventing cutoffs. Put Advertising context in a separate section if my
Amazon Ads MCP connection is available.
Produce the report for review. Hold commercial changes for my approval.

What happens next

Review availability deterioration before recommending more traffic. When OOS is steady and units per view fall, assign the offer, price, detail-page, and traffic-mix checks. A weaker ratio does not establish that page copy caused the decline. Each finding should end with an owner and the evidence that would change the decision.

Once your team accepts the comparison rules, save them in a user-owned Skill. A weekly run should wait for complete, available reports before comparing them. Amazon Agent Flow connects these MCP reads, Skills, Atlas grounding, and approval controls through the Amazon Agent Data layer. Your team's tribal knowledge becomes part of the next report instead of another correction in a chat.

Next, use the ARA inventory health guide to examine the inventory position behind an availability finding.