Amazon retires Rufus and makes Alexa for Shopping the default

What's happening

Amazon has folded the standalone Rufus chat experience into Alexa for Shopping, the unified AI assistant that combines Rufus and Alexa+ into a single shopper-facing surface inside the Amazon search bar. Retail Dive covered the rebrand in a piece titled "Rufus who?" and Modern Retail's Marketplace Briefing on June 14, 2026 framed it as Amazon trading the Rufus chatbot for an Alexa shopping agent. The change is not a feature toggle. It is the default search behavior for a growing slice of Amazon traffic.

For sellers, the operational read is simple. A shopper-facing agent that answers questions, compares products, and routes intent before the PDP is rendered reshapes the discovery funnel that Amazon SEO and Sponsored Products have been optimized for since 2015. The change rewards listings that an agent can quote cleanly and punishes listings that only render well to a human eye.

Why it matters for Amazon brands

In the old funnel, a search query landed on a results page, the shopper read titles and images, then opened a PDP. In the new funnel, the agent answers part of the question on the way in. The shopper sees a recommended set, a comparison, or a single best answer, and only opens a PDP when the agent's framing does not satisfy them. That shifts the leverage from keyword-stuffed titles toward structured attributes, bullet content the agent can lift verbatim, and review signals it can summarize.

The early signal at SKU level is a sessions drop that does not match a BSR drop. Traffic gets pre-answered or pre-routed elsewhere before it lands on the listing. Reading sessions and BSR together over a four-week window is the cleanest way to spot the pattern before it becomes a revenue story.

What you should do now

1. 1.

   Audit your top 20 ASINs for agent-readable content

   Bullets should answer a clear shopper question on their own. Attributes should be fully populated. Reviews need enough volume for an agent to summarize. If a bullet only makes sense next to a hero image, an agent will not lift it.

2. 2.

   Watch sessions and BSR together, weekly

   A sessions decline with a stable or improving BSR is the fingerprint of pre-answered traffic. Track it in day-to-day analytics and the BSR tracker on the same dashboard.

3. 3.

   Read winners and losers over 7 and 28 days, not just 28

   Shifts driven by agent routing show up first in a short window. Use the winners and losers view to spot SKUs that move out of pattern in a 7-day frame before the 28-day average smooths them out.

4. 4.

   Plan PPC for an agent-led funnel

   Sponsored Products spend stays product-level. The change is what the agent does with the impression once it is awarded. Track product-level ACoS and contribution margin against ad spend in PPC analytics, and stop treating last year's branded-term volume as the baseline.

How Nova helps

Nova reads sessions, units, BSR, ads and contribution at SKU level across the 21 Amazon marketplaces it supports. Brand managers and agencies can read the agent-funnel impact in day-to-day analytics, the BSR tracker, and PPC analytics inside the same view rather than across four tabs.