Google Shopping Deal Ends Annotation: How Urgency Badges Work and How to Qualify

What the Deal Ends Annotation Is

In August 2026 Google published a help document describing an experimental Shopping feature called Deal Ends. It displays urgency labels such as "3 days left" or "5 hours left" beneath eligible product prices on Product Listing Ads. According to Search Engine Land's coverage of the document, the annotations are generated from existing promotions and sale price information you already submit through Merchant Center, so no new technical integration is needed. The feature is experimental and works globally except the EEA, Switzerland and the United Kingdom.

That last point matters. If you sell only in those regions, this is not for you yet. Everyone else can benefit by getting their sale data right.

The Data Google Reads

Deal Ends builds on two things you probably already have: your sale_price data and your promotions. The sale price attribute tells customers what you charge during a sale. The sale_price_effective_date attribute defines the date range. A badge counting down to the end of a deal logically needs a correct end date, which is why that attribute deserves care.

• price: the regular full price when the item is not on sale.
• sale_price: the discounted price, which must be lower than the price attribute.
• sale_price_effective_date: the start and end of the sale.
• Merchant promotions: if you run promotions through Merchant Center, those schedules can also feed urgency signals; see our promotions guide and advanced promotions guide.

Sale Price Requirements From Google

Google's documentation lists minimum requirements for sale price. They are worth restating because urgency badges raise the stakes of any mismatch.

• The sale price must be lower than the regular price, and the difference must be visible in your product data.
• Keep submitting the full non-sale price in the price attribute alongside the sale price.
• The sale price you submit must match what is displayed on the landing page and at checkout.
• Clearly display both the non-sale and sale prices on the landing page, and only the sale price at checkout. The original price can remain in a larger font.
• If you advertise a coupon code, it must be accessible to all users, and the sale price must stay consistent throughout checkout.
• If the product is on sale and you do not submit sale_price, submit the sale price as the value of price.

For a deeper dive on what price mismatches look like in practice, read Price Accuracy Violations: Causes and Fixes.

The Fake Urgency Problem

An urgency badge is a promise: when it reaches zero, the deal should end. Merchants who run perpetual "limited time" sales will have a problem. If your site shows the same sale price month after month, or a countdown timer that resets, you are creating a deceptive urgency claim.

That behavior is bad for three reasons. It can violate consumer protection law in many jurisdictions, it can contradict Google's misrepresentation policy, and it will not qualify for a badge based on real sale dates anyway. The safest practice is simple: when the sale ends, the price goes back up, and your feed reflects it the same day.

How to Qualify: A Practical Process

1. Audit current sale data. Export your feed and list every product with a sale_price. Check that each has an effective date range.
2. Confirm price integrity. Compare the sale price, landing page price and checkout price for a sample of products.
3. Set real end dates for each sale in the sale_price_effective_date attribute, in the format Google specifies.
4. Schedule feed updates frequently enough that expired sales drop out promptly. Daily is a minimum for active promotions; hourly is better for flash sales.
5. Use promotions properly if your sale is code-based. Align the promotion dates with your site messaging.
6. Monitor Diagnostics for price mismatch warnings once your sale begins, and fix them immediately.

Timing for the Holiday Season

The holiday period is exactly when sale data is most likely to go wrong: many overlapping promotions, rushed price changes, and teams who forget to update the feed. Before Black Friday, assign someone to own sale price data. Our BFCM 2026 checklist covers the broader preparation, and our holiday product data readiness guide covers feed quality overall.

Common Mistakes That Block Badges and Cause Violations

• Missing end dates. Without them, Google cannot know when the deal ends.
• Sale price equal to or above the regular price. That is invalid.
• Feed updates lag the site. The site shows a sale ending Sunday, but the feed still shows the sale on Monday.
• Coupon-only discounts presented as sale prices. If a code is needed, use promotions, not a sale price.
• Time zone confusion. A sale that ends at midnight in your time zone may end at a different local time than a shopper expects.

A free scan at gmcunbanned.com flags many pricing and landing page consistency risks before Google does.

Deal Ends Checklist

Urgency Claims and Consumer Protection Law

Urgency badges sit in a legally sensitive area. Regulators in many markets, including the US FTC and consumer authorities in several other countries, have taken action against fake countdown timers, false scarcity messages and sales that never really end. Even though Google generates the Deal Ends badge from your data, you are the party responsible for the truth of the underlying offer.

Practical safeguards: keep records of the dates and prices of every sale so you can show that the price was genuinely higher before the sale; avoid reference prices that were never actually charged; and do not run a sale that is permanently renewed under a new name. If you sell in the EU or UK, the rules on price reductions are stricter still, though note that Google states the Deal Ends experiment is not available in those regions.

This is general information, not legal advice. If you run frequent promotions, have counsel review your pricing practices once, then build the rules into your merchandising process. It is far cheaper than a complaint, and the same discipline also protects your Merchant Center account, since price and offer mismatches are core misrepresentation triggers.

A Worked Example

Suppose you sell a backpack at a regular price of 100 and run a weekend sale at 80 from Friday morning to Sunday midnight. Your feed should carry price 100, sale_price 80 and an effective date range spanning exactly that window. The landing page should show both 100 and 80, checkout should charge 80, and on Monday morning the feed and page should both return to 100. If instead the sale quietly continues for a week because you forgot to update the feed, Google may still be showing a countdown that no longer matches reality, and shoppers who click on Monday will see a different price than advertised.

The fix is procedural, not technical: put the sale end on a calendar, assign someone to revert prices, and verify the feed the next morning.

Frequently Asked Questions

Will meeting the requirements guarantee a badge? No. Google says sale annotations may not always appear even when requirements are met, and Deal Ends is experimental.

Do I need to change my integration? Per the coverage of Google's document, the annotation uses existing promotions and sale price data, so no new integration is described.

Where is the feature unavailable? The EEA, Switzerland and the United Kingdom.

What happens if my sale price does not match checkout? That is a price mismatch, which can lead to disapproval and, if repeated, account-level issues.

How can I check my pricing consistency quickly? Run the free scan at gmcunbanned.com.