Price Drop Annotations on Google Shopping: How They Work
Two different badges can appear next to a product on Google Shopping, and they are not the same feature. One you earn by lowering a price and letting Google notice. The other you submit through your feed, with a documented percentage range and a minimum history behind the original price.
Confusing them is why stores drop a price, see nothing, and assume the feed is broken. This guide separates them, sets out the exact reference periods, and covers why a badge you should qualify for still does not appear.
Quick Summary
Price drop annotations are badges Google adds to a product listing when its current price is meaningfully lower than the average price you listed over the previous 60 days. You do not submit them. Google works them out from your own price history, and the badge shows the new price with the previous one for comparison.
- The reference period is 60 days. Google compares the current price against the average price listed over the previous 60 days.
- Google only shows the badge when the drop is significant. The threshold is not published, so there is no number to engineer against.
- You cannot submit a price drop annotation. It is derived from your price history, unlike a sale price annotation.
- Sale price annotations are a separate feature with their own requirements, including a discount greater than 5% and less than 90%.
- A sale price needs history behind the original price. In the US on Shopping ads, the base price must have been charged for 5 days in the past 30, or 15 days in the past 200.
- Qualifying is not the same as showing. Google prioritises whichever annotation performs best, so eligibility only buys you a chance.
The two badges, side by side.
| Feature | Price drop annotation | Sale price annotation |
|---|---|---|
| Who creates it | Google, from your price history | You, through the feed |
| Reference period | Average price over the previous 60 days | Base price history, varies by country |
| What you submit | Nothing | Original price in price, discounted in sale price |
| Published threshold | None, Google calls it significant | Greater than 5% and less than 90% |
| Landing page requirement | Not stated as a separate rule | Both prices shown, sale price most prominent |
| Guaranteed to appear | No | No |
Table: documented differences between the two annotations, from Google Merchant Center Help.
Badges not appearing on products that should qualify? Talk to Seller Splash about Google Shopping management.
What Is a Price Drop Annotation?
A price drop annotation is a badge Google adds to a product listing to show that the price has fallen. It appears alongside the new price with the previous price shown for comparison, so a shopper can see the change without opening the product page.
You do not control it directly. Google derives it from the price history it has already recorded for that product, which means the badge is a consequence of pricing behaviour rather than something you switch on in Merchant Center.
Two details are worth knowing early. The badge colour varies depending on the surface it appears on, so it will not look identical everywhere. And it displays in the local currency and language of the shopper, which matters for anyone selling across more than one market.
Google also documents vehicle price drop annotations as a separate thing with separate requirements. If you are not selling vehicles, that documentation does not apply to you, and mixing the two is a common source of wrong answers.
How Does Google Decide a Price Has Dropped?
By comparing the current price against the average price you listed over the previous 60 days. That average is the baseline, not the price last week and not the highest price you have ever listed.
This has three practical consequences that catch stores out.
- A price that has been drifting down slowly may never qualify. If the average is already close to the new price, there is no meaningful gap to annotate.
- A price you raised recently works against you. Raising then cutting back to the old level moves the 60 day average up, but the current price has to beat that average, not the brief peak.
- Recent history matters more than old history. A product whose price changed last month carries that change inside the window for 60 days.
Google adds one condition on top of the comparison. The badge is shown only when the drop is significant, and it does not publish what significant means. There is no percentage to target, which is a deliberate design choice rather than missing documentation.
How Is It Different From a Sale Price Annotation?
They are separate features with separate requirements, and Google says so directly. A price drop annotation is calculated from your price history. A sale price annotation is something you submit in the feed and must support on the landing page.
The visible result differs too. A sale price annotation shows the sale price as the current price with the original struck through, plus a sale badge, and it can appear in Google Search, Shopping ads and the Shopping tab.
One more distinction is easy to miss. Google states that sale prices should not be submitted as promotions. Promotions are a third mechanism with their own setup, so a discount can be expressed three different ways and only one of them is correct for a straightforward markdown.
What Do You Submit for a Sale Price Annotation?
Two prices, in two attributes, and both of them have to appear on the landing page. The original price goes in the price attribute and the discounted price goes in the sale price attribute.
- Keep submitting the original price in price. During the sale, that attribute still carries the pre sale figure. Overwriting it removes the comparison Google needs.
- Put the discounted figure in sale price. It must be lower than the base price.
- Keep the discount above 5% and below 90%. Google states the discount must be greater than 5% and less than 90%, so very small and very deep markdowns are both outside the range.
- Show both prices on the landing page. The sale price has to be the most prominent of the two.
- Do not submit the same discount as a promotion. Google states that sale prices should not be submitted as promotions.
Meeting every requirement still does not guarantee the annotation. Google prioritises whichever annotations are performing best, so the feed work buys eligibility rather than a placement.
How Long Must the Original Price Have Been Live?
This is where most sale price annotations fail, and the answer depends on the country and on whether the listing is free or paid. The base price needs a documented history, otherwise the discount has nothing credible to be measured against.
| Listing type and market | Base price requirement |
|---|---|
| Free listings in the US, Australia, Canada, Japan | No separate base price duration beyond the core requirements |
| Free listings in Brazil, France, Germany, India, Italy, Korea, Netherlands, Spain, UK | Valid for 30 days within the past 200, not necessarily consecutive |
| Shopping ads in the US | Charged for 5 days within the past 30, or 15 days within the past 200, whichever is met first |
| Shopping ads in Australia, Brazil, Canada, France, Germany, India, Italy, Japan, Korea, Netherlands, Spain, UK | Valid for 30 days within the past 200 |
Table: base price duration requirements for sale price annotations, from Google Merchant Center Help.
Local inventory ads follow their own version of this. If you are enabled for product pages with in store availability or pickup later, the Shopping ads rules above apply. For store specific product pages that carry in store availability and price, the base price must be valid within that store for 60 days within the past 200. If the product has been active for less than 200 days, it must have been valid for 60 consecutive days instead.
The planning point is simple. A product launched into a discount has no base price history, so it cannot carry a sale price annotation in most markets. Launch at the intended price, let it sit, then discount.
Why Is the Price Drop Badge Not Showing?
Work through the mechanics before suspecting a feed error, because most of the causes are about history and thresholds rather than data quality.
The usual causes
The 60 day average is too close to the new price. The comparison is against the average, not against the last price you listed. A small cut against a recently lowered average leaves no gap.
The drop is not significant enough. Google only shows the badge for a significant drop and does not publish the threshold. A technically correct but small reduction can simply not qualify.
You are looking at the wrong annotation. If you submitted a sale price, you are waiting on a sale price annotation, which has its own rules and its own failure modes.
The landing page does not match. For sale price annotations, both prices must appear on the page with the sale price most prominent. A page that shows only the discounted figure fails the requirement.
The discount is outside the 5% to 90% range. Below 5% or at 90% and above, the sale price annotation is not eligible.
Another annotation is winning. Google prioritises the best performing annotations, so a product can be eligible and still show something else, or nothing.
A price mismatch between the feed and the landing page is worth ruling out separately, because that breaks the listing itself rather than just the badge. If products are disapproved rather than merely unbadged, the problem is item level data, and Merchant Center suspension territory rather than annotation territory.
How Do You Check Which Products Have the Badge?
Merchant Center has a filter for exactly this, so there is no need to guess from spot checks on live search results.
- Open Products, then All products.
- Open the Filter control.
- Select Has price drop badge.
- Set it to Yes.
That gives you the eligible set rather than a sample. Comparing that list against the products you actually discounted is the fastest way to see whether your markdowns are registering at all, and it is a far better signal than refreshing a search results page.
The same check is useful in reverse. If a large markdown is missing from the list, the question becomes what the 60 day average looked like before the cut, which is usually answerable from your own price change records.
Should You Cut Prices to Earn the Badge?
No, and treating the badge as a target is how margin disappears. The annotation is a reflection of a pricing decision, not a reason for one. Google does not publish the significance threshold, so there is no efficient cut to aim at.
A more useful way to think about it is sequencing. If a markdown is already planned, the documented rules tell you how to get credit for it: let the original price build history first, keep submitting it during the sale, keep the discount inside the 5% to 90% band, and show both prices on the page.
- Plan the markdown on margin, not on badges. Start from break-even ROAS and work out what the discount does to the number you actually need.
- Let new products establish a price. No base price history means no sale price annotation in most markets.
- Avoid price sawing. Raising then cutting moves the 60 day average and makes the next genuine drop harder to register.
- Fix the feed first. An annotation sits on top of a listing that has to be approved and accurate before anything else matters.
Which Mistakes Cost the Badge?
The five worth avoiding
Overwriting the price attribute during a sale. The original price has to keep being submitted. Replace it with the discounted figure and there is nothing to compare against.
Launching a product straight into a discount. With no base price history, there is nothing for the annotation to measure, and in most markets that is a hard requirement rather than a preference.
Submitting a markdown as a promotion instead of a sale price. Google states these are different mechanisms, and a sale price should not be submitted as a promotion.
Showing only the sale price on the landing page. Both prices have to be visible, with the sale price most prominent. This is a page requirement, not a feed one.
Treating the badge as guaranteed once you qualify. Google prioritises the best performing annotations. Eligibility is the entry condition, not the outcome.
Why Ecommerce Brands Choose Seller Splash
Seller Splash is an ecommerce marketing agency in New York working with product brands on Google Ads, Shopping, Merchant Center and marketplace advertising. Annotation and feed questions like these come up constantly during promotional periods, usually a week after the markdown has already gone live, which is the hardest point to fix them.
If discounts are running and nothing is showing in Shopping, that is a short diagnostic across the feed, the landing pages and the price history. See how we work or look at results for other product brands.
Where Should You Go Next?
- If the feed underneath is the real issue, start with Google Shopping feed optimization.
- If products are disapproved rather than unbadged, read Merchant Center suspension.
- If you are new to the platform, see what Google Merchant Center is.
- If campaign structure is the question, read Google Shopping campaign priority.
- If reviews and ratings are also on the list, see Google product ratings.
- If you are setting a return target around a sale, start with break-even ROAS.
- If the same products run on Microsoft, read Bing Shopping ads.
About the Author
Seller Splash is an ecommerce marketing agency based in New York, working with product brands on Google Ads, Shopping, Merchant Center, paid social and marketplace advertising. Feed rules, annotations and promotional setup sit inside that work, which is where the cautions described here come from. More on who we are, or see what the work produced for other product brands.
Frequently Asked Questions
What is a price drop annotation on Google Shopping?
It is a badge Google adds to a product listing when the current price is meaningfully lower than the average price listed over the previous 60 days. It shows the new price with the previous price for comparison, and it appears in the shopper's local currency and language.
How does Google calculate a price drop?
Google compares the current price against the average price you listed over the previous 60 days. That average is the baseline, so a small cut against an already low average may not register at all.
How big does a price drop have to be?
Google only says the drop must be significant and does not publish a threshold. There is no percentage to target for price drop annotations. Sale price annotations are different and do have a published range, greater than 5% and less than 90%.
Can I submit a price drop annotation through my feed?
No. Price drop annotations are derived from your own price history and cannot be submitted. If you want to submit a discount, that is a sale price annotation, which uses the price and sale price attributes.
What is the difference between a price drop and a sale price annotation?
Google documents them as different features with separate requirements. A price drop annotation is calculated by Google from your price history. A sale price annotation is submitted in the feed, needs both prices on the landing page, and needs the discount to be greater than 5% and less than 90%.
How long does the original price need to be live before a sale?
It depends on the market and the listing type. For Shopping ads in the US, the base price must have been charged for 5 days within the past 30, or 15 days within the past 200, whichever is met first. For Shopping ads in several other countries, the base price must be valid for 30 days within the past 200.
Why is my sale price annotation not showing?
Common causes are overwriting the original price attribute during the sale, a discount outside the 5% to 90% range, a landing page that does not show both prices with the sale price most prominent, insufficient base price history, or Google prioritising a better performing annotation instead.
How do I check which products have a price drop badge?
In Merchant Center, open Products, then All products, open the Filter control, select Has price drop badge and set it to Yes. That returns the eligible set rather than a sample from live search results.
Should I submit a sale as a promotion instead?
No. Google states that sale prices should not be submitted as promotions. Promotions are a separate mechanism with their own setup, so a straightforward markdown belongs in the sale price attribute.
Does qualifying guarantee the badge will appear?
No. Google prioritises whichever annotations are performing best, so meeting every documented requirement buys eligibility rather than a placement. A product can be eligible and still show a different annotation or none.
Get an expert audit of your brand's visibility in AI search and Google
Full AI Visibility Audit or Deep Growth Audit, with a prioritized fix list for your store.
AI search and ads readiness checklist
25 checks for Amazon, Walmart and Shopify sellers: tracking, product feeds, Google, Bing and Meta ads, and getting cited by ChatGPT, Perplexity and Google AI Overviews. Two pages, about 20 minutes.
- Break-even ROAS table by margin
- The AI search (AEO) checks most stores miss
- A simple score that tells you what to fix first
No spam. We use your email to send the checklist and follow up about it.
Want to see where your store stands in AI search? Get the Full AI Visibility Audit for $99 or the Deep Growth Audit for $249.
Get your AI visibility audit

