Google's 'Deal Ends' Shopping Badges: How Indian D2C Brands Earn the Festive Countdown in 2026

Urgency has always been the cheapest lever in a festive sale. A visible countdown next to a price does more for conversion than another 5% off, because it moves the decision from "later" to "now". The trouble is that most Indian D2C brands can only create that urgency on their own store — a banner, a timer, a "sale ends tonight" popup — and none of it shows up at the moment a shopper is comparing products in Google. That gap just closed.

Google has started adding its own countdown badges directly onto Shopping ads — small "3 days left" or "5 hours left" markers under the price — pulled automatically from the sale data in your Merchant Center feed. You don't design them and you can't turn them on; Google decides which products qualify based on your feed. India is eligible while the UK and EU are not. So the entire game becomes making sure your festive discounts are structured the way Google wants, because a correctly-configured feed earns free urgency and a sloppy one earns nothing. Here's exactly how it works and what to fix before Diwali.

What the 'Deal ends' badge actually is

The annotation is a short, real-time urgency signal Google renders beneath the price on a product listing ad. Reporting from Search Engine Land and Search Engine Roundtable, based on Google's help documentation, describes badges like "3 days left" and "5 hours left" that count down toward a deal's expiry. Google's stated aim is straightforward: make expiring deals more prominent so they improve click-through rate and conversions.

It's automatic, and you can't opt in or out

This is the part that trips people up. The badge is experimental, and there's no switch for it — you can't request it, and you can't suppress it. Google generates it from the promotions and sale-price data you already submit, and there's no dedicated reporting column for it yet, so you won't see a neat "Deal ends impressions" metric. Your only real control is upstream: whether the product's feed data meets the eligibility rules. Get the data right and Google may add the badge; get it wrong and the product simply never shows one.

Why this matters more for Indian D2C than most

Two things make this unusually relevant here. First, eligibility: Google runs the feature globally except in the European Economic Area and associated countries, Switzerland, and the United Kingdom. India sits inside the eligible zone, which means your Shopping ads can carry a live countdown that a brand selling into London or Berlin can't put on theirs.

Second, timing. The Indian D2C year is front-loaded into the festive quarter, and Google's stricter "holiday" ruleset runs from roughly 15 October to 5 January — almost exactly the Dhanteras-to-New-Year stretch where you make your numbers. So the badge's peak-eligibility window overlaps your peak-revenue window. Getting your feed compliant before mid-October isn't a nice-to-have; it's the difference between your discounted hero products wearing a countdown through Diwali and sitting there looking like everyone else's.

The eligibility rules, in plain numbers

Google applies two different bars depending on the season, and both reward a real, recent markdown over a cosmetic one. The table lays them side by side.

The logic behind every row is the same: Google is protecting shoppers from fake urgency. The discount has to be genuine (a real percentage off), recent (the lowest that product has actually been), and finite (it truly ends within a week). The repeat interval stops you running a permanent "ending soon" countdown, which would train shoppers to ignore it — the exact problem fake timers on stores already have.

The trap: struck-through MRP isn't a discount

A lot of Indian D2C feeds show a high MRP with a permanent "sale" price beneath it. Under these rules that pattern earns nothing, because the sale price isn't a recent low — it's the everyday price dressed up. To qualify, the product's current sale price genuinely has to be its lowest in the last 60 days (festive) or 15 days (regular). If you bounce prices up before a sale to make the discount look bigger, Google's 60-day lookback catches it and disqualifies the badge.

How to configure your feed before the festive rush

The badge is built from two feed inputs, so your job is to get both clean.

Set sale price and its effective date correctly

The single most common mistake is lowering the main price for a sale and never setting the sale_price and sale_price_effective_date attributes. Without an effective date, Google has no expiry to count down to, so no badge. Set sale_price to the true discounted price and sale_price_effective_date to a real start-and-end window that closes within seven days. That end date is what powers the "3 days left" countdown.

Check what your Shopify feed is really sending

If you're on Shopify, your Google channel or feed app may be silently dropping the effective-date field even when you've scheduled a sale in Shopify itself. Pull your feed in Merchant Center and confirm the sale-price and effective-date columns are actually populated for the products you're discounting. This plumbing — clean feed attributes, honest price history, correctly-dated promotions — is exactly the unglamorous work our performance marketing team audits first on a D2C Shopping account, because it's where free eligibility quietly leaks.

Plan discounts as short, real, staggered windows

Because a deal must expire within seven days and can't repeat for weeks, structure your festive calendar as a series of genuine short bursts — a Dhanteras drop, a Diwali-weekend deal, a post-Diwali clearance — each a real markdown on a defined window, rather than one flat month-long "sale" price. That both satisfies the rules and, honestly, converts better than a discount that never ends.

Measuring something Google won't report for you

Because there's no dedicated metric, you can't open a report and see "Deal Ends drove X sales". That doesn't mean you fly blind — it means you measure it the way you'd measure any change you can't isolate natively.

Use custom labels to build a control group

Tag your genuinely-discounted festive SKUs with a Merchant Center custom label, and tag a comparable set of non-discounted products with another. During the sale window, compare click-through rate and conversion rate between the two groups. If your discounted, badge-eligible products pull a noticeably higher CTR than your control set — beyond what the discount alone would explain — that's the countdown doing its job. It's a rough read, not a clean attribution, but it's enough to know whether feed compliance is paying off.

Eyeball your live listings on mobile

The simplest check is to search for your own products on a phone during an active, qualifying sale and look for the badge under the price. Most Indian D2C traffic is mobile, and the annotation renders in the live results, so a two-minute manual check tells you whether Google actually decided your product qualified. If a deeply-discounted hero product isn't showing a countdown, that's your signal to go back and audit the sale_price_effective_date on that item — the feed data is almost always the reason.

The takeaway

Google is now placing urgency on your Shopping ads for free, right where shoppers compare products, and India is on the eligible list while much of Europe isn't. But it only shows up for brands whose feed says the discount is real: a genuine markdown, the lowest in 60 days, expiring within a week, with the sale price and effective date set correctly in Merchant Center. There's no button to press and no report to watch — the work is entirely in your feed hygiene and your discount planning. Fix the sale_price and sale_price_effective_date attributes, keep your price history honest, and structure your festive deals as short real windows, and your best products can wear a live countdown straight through the season your whole year depends on.

Sources: Search Engine Land — "New Google help doc details Deal Ends annotations for Shopping ads" (badges such as "3 days left" / "5 hours left" generated automatically from Merchant Center promotions and sale-price data; experimental with no opt-in/opt-out; holiday vs non-holiday eligibility thresholds). Search Engine Roundtable — "Google Merchant Center PLA Deal Ends Experimental Annotation" (available globally except the EEA and associated countries, Switzerland and the United Kingdom; holiday window ~15 Oct–5 Jan requiring ≥10% discount, lowest price in 60 days, expiry within 7 days, ~60-day repeat interval; non-holiday ~5% discount, lowest price in 15 days, ~15-day interval; requires sale price and effective-date attributes). Feed-configuration and discount-planning steps are Digistex4u's applied guidance.