Loading

Preparing your content

Article Details
2026-11-12BXT Data Editorial

Pixel 11 hides in the strike-through on one marketplace

Pixel 11 hides in the strike-through on one marketplace article image

A price gap on the same phone, in the same week, in opposite directions. As of November 12, 2026, the Pixel 11 sits at 899 dollars on Amazon after a promotion ended, while Best Buy cut the same handset to 699 dollars; of 65 tracked price moves that week, 29 were cuts, 33 were sales ending and only 3 were increases (iDevice). Nothing about the product changed. What changed is which listing a shopper happened to open.

Two listings, one shelf price

Known factsUnverifiedNeeds verification
The Pixel 11 returned to 899 dollars at Amazon while Best Buy cut it from 899 to 699 dollars in the week ending November 12Whether either retailer will match the other before the holiday cutoffPrice-match policy wording per retailer
Amazon labels a reference price as List Price, usually the maker's suggested price, or Was, an earlier priceHow often the Was value reflects a price that actually transactedThirty-day price history for the same SKU
In one tracked best-seller list on November 12, the median price of 99 priced items was 39.99 dollars and 28 of 100 cards had under 1,000 reviewsWhether review counts move price sensitivity more than discounts doConversion by review-count band

The mechanics are simple and easy to miss. A marketplace listing carries two prices that shoppers read as one: the current price and the reference price behind the strike-through. When a promotion ends, the current price climbs back and the reference stays put, which makes the discount look smaller. When a competitor cuts, the gap between the two listings becomes the story, and the gap is often wider than any single promotion.

For anyone running price monitoring, this is the week's most useful artefact. It shows that price position is not a property of a product on a given day; it is a property of a product-store-time triple. Reporting a single market price for a SKU hides exactly the variation that determines whether a shopper buys.

The reference price is the weak link

Retail guidance published the same day is blunt about the label: a list price is usually the maker's suggested price and is not always what an item normally sells for, so a percentage off a list price can overstate the saving (Canada News Media). Multiply that across a season and the arithmetic compounds: the deeper the reference, the larger the advertised cut, and the less the number tells a buyer about the street price.

Marketplaces have a second lever that catalogues rarely show: review stock. In the data-storage top 100 tracked on November 12, 28 of 100 listings carried fewer than 1,000 reviews, and the median price across 99 priced items was 39.99 dollars (ParseShelf). Thin review bases and low prices travel together, because both are symptoms of a listing that has not accumulated history. A price monitor that ignores review count will keep flagging these listings as anomalies when they are simply young.

PatternWhat it looks like in the feedLikely cause
Sale ended, reference unchangedCurrent price rises, strike-through staysPromotion expiry, not a price increase
Channel divergenceSame SKU, 200 dollars apart across two retailersIndependent promo calendars
Reference inflationDiscount depth grows while street price is flatList price used as the anchor
Young listingLow price, few reviews, sudden rank jumpsNew entrant, not a price war

How to report a gap without misleading yourself

Start from the SKU, not the category, and store the full history rather than the latest snapshot. A gap that appears for four hours on a Tuesday means something different from a gap that persists for two weeks, and only a stored series distinguishes them. Second, record the reference price alongside the current price, because promotions that end quietly look like increases when the reference is dropped from the extract.

Third, split the report by channel identity. A marketplace listing sold by a third party and a first-party listing behave differently even when they show the same product image, and mixing them produces a gap that no one can act on. Fourth, set an alert threshold in currency, not in percentage, because a 20 percent gap on a 30 dollar accessory and on a 900 dollar handset are not the same problem for a buyer or for a category manager.

What the gap is worth to a brand

A persistent gap between two authorised retailers is usually a signal about channel inventory, not about demand. One retailer is clearing, the other is holding, and the brand's price architecture is being decided by whichever warehouse is fuller. Brands that watch only their own listing see a stable price and conclude nothing is happening, while shoppers compare two tabs and conclude the brand is inconsistent.

Action list

  1. Step 1: freeze a SKU list of the fifty highest-revenue items and record price daily (evidence: daily extract).
  2. Step 2: capture the reference price label and value next to the current price (evidence: listing screenshot with timestamp).
  3. Step 3: flag gaps above a currency threshold, not a percentage (evidence: alert log).
  4. Step 4: review flagged gaps with channel owners every Monday (evidence: gap review notes).
DateFieldExample valueOwnerEvidence linkStatus
2026-11-12channel price gap200 USDPricing - M.listing capturechecked
2026-11-12reference labelList PricePricing - M.listing capturepending

FAQ

  • Is a wider gap always a pricing problem?

    No. It often reflects different promotion calendars or one channel clearing stock. The gap becomes a problem when it persists and the reference price is not adjusted.

  • Should alerts be set in percentage or currency?

    Currency. A percentage threshold treats an accessory and a handset as equivalent when the buyer impact differs by an order of magnitude.

  • Why track reference prices at all?

    Because advertised discounts are computed against them. Without the reference you cannot tell an expiry from a genuine price change.

Sources