Quick-commerce shelf # Competitor promo lag: catching a rival's discount on time A rival's price cut on Blinkit or Zepto is not announced, so you only see it by checking the same product at the same pin code on a fixed schedule. Without that, a 20% discount can run for days before your team notices. Log each change with its date. ![](https://rewalto.com/_next/image?url=%2Fbrand%2Fog%2Fguides-competitor-promo-lag.png&w=3840&q=75) In this guide 1. [What promo lag costs a brand](#the-lag) 2. [How often prices actually change, week to week](#how-often-prices-move) 3. [Why a week-to-week comparison, not a single snapshot](#why-week-to-week) 4. [How to check a competitor's price without guessing](#check-a-competitor) 5. [What a price reading cannot tell you](#caveats) 6. [Acting on what you find](#acting-on-it) 7. [Common questions](#questions) 8. [Notes](#notes) [Explore commerce data](https://rewalto.com/data/commerce) By [Varun Mahajan](https://rewalto.com/about), FounderPublished 30 September 2026Last updated 30 September 2026Part of the [price against mrp and discounts](https://rewalto.com/guides/discount-depth) guideMore on [quick commerce](https://rewalto.com/insights/category/quick-commerce) ## What promo lag costs a brand A competitor dropping a price on Blinkit or Zepto is not an announcement. There is no press release, no email, sometimes not even a banner. The price on the listing simply changes. If nobody on your team is checking that specific SKU on that specific app, the discount runs for as long as it takes someone to notice by accident, often days. One team described the problem plainly in a public forum thread on tracking competitors on Blinkit and Zepto: finding a rival’s discount only after it had been live for a week, by which point the promotional window that mattered had mostly passed.[1](#note-1) That gap between a price moving and a team noticing is what this guide calls promo lag. The cost is not just a missed price match. A key-account team walking into a review without knowing a retailer showed a competitor at a steep discount for most of the quarter is arguing from a position they did not know they had lost. A pricing team setting next month’s promotional calendar without knowing how often a rival already moves is setting it against a guess rather than a measured rate. Both problems trace back to the same gap: nobody was checking on a schedule that matched how often the market actually changes. Closing it does not require watching every SKU in a category. It requires knowing how often prices actually move, so a check schedule can be set against that rate rather than against a guess. ## How often prices actually change, week to week Rewalto compared the observed selling price for the same SKU across two consecutive seven-day windows, personal care category, on Blinkit and Zepto. Blinkit · 6,829 matched SKUs20.6%Zepto · 262 matched SKUs34% Share of matched SKUs whose observed selling price changed, personal care category, week of 16 to 23 September 2026 against week of 23 to 30 September 2026. Blinkit: 6,829 matched SKUs. Zepto: 262 matched SKUs, a far smaller sample than Blinkit's, read that way. Source: Rewalto's own pin-code readings of the apps, never a third party's data. Source and measurement notes.[2](#note-2) Read the two bars against their own sample. Blinkit’s comparison covers 6,829 matched SKUs, a large enough set that 20.6% is a reasonable working rate for how often a price in this category moves from one week to the next. Zepto’s comparison covers 262 matched SKUs, a real figure, but small enough that 34.0% should be treated as a rough signal rather than a fixed rate until a longer run of weeks confirms it. Either way, the practical point holds: a meaningful share of prices in this category moved inside a single week. A check run once a month, or once a quarter, would have missed most of those moves entirely, and a competitor’s discount that runs for five days out of thirty is easy to miss on any check slower than weekly. It is also worth noticing what the two numbers do not say. A changed price is not automatically a discount. Some of those moves will be increases, some will be MRP corrections carried through to the selling price, and a few will be pack-size changes that look like a price move in a raw comparison. The rate tells you how often to look; it does not replace looking at what actually changed, which is exactly the calculation [discount depth](https://rewalto.com/guides/discount-depth) sets out. ## Why a week-to-week comparison, not a single snapshot A single price reading tells you what a listing showed at one moment. It cannot tell you whether that price is new or has held for a month. Comparing the same SKU across two windows is what turns a snapshot into a rate: how often, not just what. A week is a practical unit for this because it is short enough to catch a promotion that runs for a few days and long enough that a single missed read does not throw the whole comparison off. A shorter window would need more frequent checking to stay reliable; a longer one would blur together several separate price moves into one comparison, and a competitor who cuts a price for four days and reverts it would vanish entirely from a monthly comparison while still having run the promotion your own team needed to see. The same three-state discipline that applies to stock applies to price: a SKU that was not read in one of the two windows is a gap in the record, not evidence that its price held steady. Rewalto’s comparison only counts SKUs read in both windows, which is why the matched count is smaller than the full catalogue. ## How to check a competitor's price without guessing Rewalto’s free price parity checker, opening shortly, runs the same kind of comparison this guide describes for one product across the apps you choose, so you can see whether a competitor’s price has moved without setting up a spreadsheet first. No account with the retailer and no relationship with the competitor is needed. A public listing is checked the same way any shopper reads it. 1. Name the products that matter: your own hero SKUs, and the direct competitor SKU each one is compared against by shoppers. 2. Pick the apps and pin codes where that comparison actually happens for your buyers. 3. Record the selling price and the MRP together, with the pin code, the app and the time ,not price alone, because a discount is the gap between the two. 4. Save the page with every reading, the same evidence discipline [pin-code shelf truth](https://rewalto.com/guides/pincode-shelf-truth) asks for. 5. Repeat on a fixed schedule set against the rate you measure, not a guess. If a category moves on roughly one SKU in five each week, a monthly check is not close to enough. Keep the comparison narrow at first: two or three competitor SKUs against your own hero products is enough to see whether the method surfaces anything useful before you widen it. A brief that tries to cover an entire category from day one tends to produce a spreadsheet nobody keeps updating past the second week, which defeats the point of setting a schedule at all. ## What a price reading cannot tell you A logged-in shopper can be shown a price or an offer that a logged-out reading does not show, so state how a reading was taken before comparing it against a competitor’s public price. And a price change is not automatically a promotion. An MRP correction, a pack-size change or a routine repricing can move a number without any discount behind it. Check the MRP alongside the selling price before calling a move a promo. A reading also says nothing about why a price moved: a funded promotion, a platform decision or a distributor’s own call all look identical from the shopper’s side of the app. The reading is what you bring to a pricing or key-account conversation; it is not the explanation on its own. One more caveat is worth stating because it is easy to skip when a comparison looks clean: matching the right SKU on both sides matters as much as reading the price correctly. Pack sizes that look identical in a listing title can differ once you check the fine print, and a retailer’s own private-label alternative can sit beside a national brand in search results looking like a fair comparison when it is not one at all. Confirm the pack before you compare the price, the same discipline [pin-code shelf truth](https://rewalto.com/guides/pincode-shelf-truth) asks for on your own listings. ## Acting on what you find A single price move is worth a note. A pattern, the same competitor, the same category, repeated discounts that land before your own team notices, is worth a standing check rather than an occasional one. A pattern is also the more defensible thing to raise internally: a one-off price difference can be argued away as a fluke of timing, but three weeks of readings showing the same rival consistently undercutting a set of SKUs on the same day of the week is a fact a pricing meeting can plan around. Read a price move next to the discount depth method so it becomes a percentage against MRP rather than a bare number. A rival cutting a selling price by ten rupees means very different things on a budget SKU and on a premium one, and a percentage against the printed MRP is what makes those two comparable across a whole catalogue rather than only within one product line. Keep the note factual rather than speculative: what changed, on which app, in which pin codes, and on which date. A pricing team reading that note later can decide what it means for its own calendar far more easily than it can reconstruct a vague recollection of “the competitor was cheaper for a while last month”. If you are weighing whether an alert service is worth setting up at all, read [what a good out-of-stock, price or rank alert proves](https://rewalto.com/guides/oos-price-rank-alerts) first. The same evidence bar (product, app, pin code, time, source) applies to a price alert as to a stock one. Whoever owns this on your team, give them a short, repeatable brief rather than an open-ended instruction to “watch the competition”. Name the SKUs, name the apps, name the pin codes, and name the day of the week the check runs. A vague brief produces an occasional glance; a specific one produces a record you can act on and, over a few months, a rate you can plan a promotional calendar against instead of reacting to. ## Common questions ### How often do prices actually change on Blinkit and Zepto? It varies by app and by category, and the only way to know is to measure it rather than assume it. In Rewalto's own personal care reading across two consecutive weeks, about one in five matched Blinkit SKUs changed price and about a third of matched Zepto SKUs did, from a much smaller Zepto sample. See the chart on this page. ### What is 'promo lag'? The gap between a competitor's price move landing on an app and your team noticing it. A rival can run 20% off for days before anyone checks, because nobody is looking at that specific SKU on that specific app on a set schedule. ### Can I track a competitor's price without an account on their brand? Yes. Price and stock on Blinkit and Zepto are shown to any shopper who sets a delivery address, logged in or not (allowing for the note on logged-in offers below), so a competitor's public listing can be checked the same way your own is. ### How is this different from discount depth? Discount depth is how far one reading sits below MRP at one moment. This guide is about the moment a price changes at all, and whether your check schedule would have caught a competitor's move before it had been live for days. See [Discount depth](https://rewalto.com/guides/discount-depth) for the first question. ## Notes 1. The forum framing this guide opens with is from a public thread on r/indianstartups, 2026, on tracking competitors on Blinkit and Zepto. Quoted for the shape of the problem, not as a Rewalto reading. [Back to text](#ref-1) 2. The chart’s figures are Rewalto’s own, measured 30 September 2026 from [digital shelf readings](https://rewalto.com/data/commerce) over the personal care category, taken by Rewalto itself and never bought from a third party, comparing the seven days to 23 September 2026 against the seven days to 30 September 2026. A product counts when it was seen in both weeks, and it counts as changed when the last selling price we saw in the second week differed from the last one in the first. [Back to text](#ref-2) ## Start with the question you need to answer Check the current data catalogue, then review the coverage and dates against your question. The research in an older guide does not establish that a service is available today. [Explore Rewalto data](https://rewalto.com/)[Explore current data](https://rewalto.com/data) ## Related guides [Quick-commerce shelf ### Discount depth: reading the gap between selling price and MRP How to calculate discount depth and read it without over-claiming. Explore](https://rewalto.com/guides/discount-depth) [Quick-commerce shelf ### Pin-code shelf truth: price and availability on Blinkit and Zepto Price and stock on Blinkit and Zepto belong to one pin code at one moment. What that means for how you read them. Explore](https://rewalto.com/guides/pincode-shelf-truth) [Quick-commerce shelf ### What a good out-of-stock, price or rank alert proves What evidence an out-of-stock, price-floor or search-rank alert should carry, and where ours stands. Explore](https://rewalto.com/guides/oos-price-rank-alerts) --- Canonical page: https://rewalto.com/guides/competitor-promo-lag Last content change: 2026-09-30