Data # Same product, different price: compare shopping apps fairly To compare Blinkit, Zepto and Instamart prices fairly, match the exact pack, use the same delivery area and record the same check time. A gap that survives those three controls is worth a second look. Keep offer conditions, checkout costs and missing readings visible, and never show an unavailable item as free. ![](https://rewalto.com/_next/image?url=%2Fbrand%2Fog%2Fguides-same-product-different-price-across-apps.png&w=3840&q=75) In this guide 1. [Start with a comparable price](#why-the-question-is-hard) 2. [Match the item before matching the name](#match-the-product) 3. [Use the same delivery area](#choose-the-location) 4. [Record when each price was checked](#align-the-time) 5. [Compare like-for-like price types](#separate-the-offers) 6. [Do not make an unavailable item look free](#handle-missing-data) 7. [Make the comparison easy to challenge](#build-a-reviewable-comparison) 8. [Agree on the comparison before collecting prices](#write-a-brief) 9. [Check what the dataset can actually compare](#read-the-dataset) 10. [Separate a finding from a possible explanation](#review-the-result) 11. [Review the result before sharing it](#review-before-sharing) 12. [Choose your next step](#next-step) 13. [Common questions](#questions) [Explore datasets](https://rewalto.com/data) By [Varun Mahajan](https://rewalto.com/about), FounderPublished 18 October 2026Last updated 18 October 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) ## Start with a comparable price Two apps show different prices for what looks like the same product. That is a useful reason to investigate, but it is not yet a fair comparison. Check the variant, pack, delivery location and time before deciding which price is higher. A product price answers what that listing displayed under those conditions. It does not explain who funded an offer or whether a retailer is generally cheaper. A careful comparison keeps the conditions visible and limits the conclusion to the products actually checked. This guide is about comparing one pack across apps. To measure how far a price sits below the MRP, start with [discount depth](https://rewalto.com/guides/discount-depth). For why an app price is not the pack price, read [why a Blinkit price is not the price](https://rewalto.com/blog/why-a-blinkit-price-is-not-the-price). The word itself is defined in the glossary under [price parity](https://rewalto.com/glossary/ecommerce/price-parity), and the free [price parity check](https://rewalto.com/tools/price-parity) shows the readings Rewalto holds for one product across apps. Three things usually explain a gap before anything else does. Each app sets its own price. Each delivery area is served by its own dark store, which can carry its own price and stock. And offers change during the day, so two readings an hour apart can disagree without either being wrong. A fair comparison controls all three before it names a cheaper app. ## Match the item before matching the name Product names are convenient labels, but a name can hide a different quantity, flavour, formulation or bundle. Compare the pack and variant first. When a reliable product identifier is supplied, use it alongside the description rather than replacing the description with a guess. Keep bundles separate from single items unless the comparison has a defensible unit conversion. A promotional extra can change what the customer receives. A similar photograph or nearly identical title is not evidence that two listings contain the same product. ## Use the same delivery area Quick-commerce prices and availability belong to a location. Select the delivery area before recording a price, and keep that location in the result. Comparing one app in a central neighbourhood with another at an airport address answers a different question. If the source only supplies a pin code rather than the exact store serving the order, say so. Do not infer a store identity from location alone. A city-level heading should describe the locations checked, rather than suggesting complete city coverage. ## Record when each price was checked Offers can change between checks. Read the source time and collection time separately when both are supplied. A recently downloaded record may still describe an earlier source reading. For a one-off comparison, keep the check window narrow and state it. For a history, align comparable periods and retain missing periods as gaps. Do not turn an isolated difference into a trend without enough repeated, comparable readings. ## Compare like-for-like price types Distinguish the listed selling price, MRP, unit price and any offer price. A membership price or bank offer may apply only to some shoppers. Keep the eligibility conditions with the price instead of presenting the offer as universally available. Checkout costs need a separate comparison. Delivery charges, handling fees, minimum baskets and discounts applied to the basket can change the final amount. A listing-price dataset does not automatically contain those checkout details. When quantities differ, a unit price can help if the units are genuinely comparable. Keep the original pack quantity and conversion visible. Do not compare a concentrate and a ready-to-use product purely by their container volumes. ## Do not make an unavailable item look free If an app was not checked, label it not checked. If the source showed the item as unavailable, retain that state. A missing price is not zero, and an unavailable listing is not necessarily a purchasable alternative. An unmatched product is also not evidence that a retailer does not sell it. Keep unmatched and not-listed results apart. Otherwise a naming issue can become a false assortment conclusion. ## Make the comparison easy to challenge A useful worksheet keeps the product and variant, pack quantity, source, location, check time, price type, availability and any offer condition together. Include the source address where supplied so a reviewer can follow the record back to its context. Write the conclusion only after that table is ready. You may find a difference for the same pack across the locations checked, or you may find that the rows are not comparable. Both outcomes are useful if they stop an account team acting on the wrong benchmark. Repeat the same method when you revisit the question. Keep earlier records and explain any change in coverage. That makes a later conversation about pricing specific, rather than a dispute over screenshots taken under different conditions. ## Agree on the comparison before collecting prices Write a short comparison brief that names the products, variants, packs and delivery areas. State whether you want the displayed listing price or the final checkout amount. Explain whether a membership, coupon or payment offer should be included. These choices define the question; leaving them until after the results arrive invites selective comparisons. Choose how to handle unavailable and unmatched products before you make a chart. Keep those records visible with their own states. Do not drop an expensive-looking product because its matching information is incomplete, or include a cheaper-looking bundle without checking its contents. If the work is for an account review, ask the person using the result what they would do differently after seeing it. That helps you decide whether an isolated check is enough or whether a history is needed. ## Check what the dataset can actually compare Read the field definitions before assuming an API price is the amount a shopper would pay. The record may contain a listing price but no delivery fee, basket threshold or membership condition. Ask whether the supplied value is a current reading or the latest known reading. A source address and collection date make a record easier to review, but they do not fill in missing checkout details. If a required field is unavailable, narrow the conclusion. You can compare displayed prices while clearly saying that checkout totals were not compared. Check coverage at the same level as your brief. A retailer being named in a catalogue does not establish that your selected products and locations are present. Inspect the current coverage and sample before requesting a larger delivery. ## Separate a finding from a possible explanation A price gap can start a useful conversation without settling its cause. A promotion might apply to a particular audience, a pack may differ, or the checks may fall on different dates. Look for evidence for each explanation instead of choosing the one that fits the story you hoped to tell. When sharing the comparison, keep the original rows beside the summary. A colleague should be able to inspect the pack, area, date and offer conditions without reconstructing your work. Record any exclusions and why they were made. If a surprising difference disappears after correcting a match, keep that correction in the working notes. It improves the method and helps the team avoid repeating the same mistake. A smaller defensible result is worth more than a dramatic comparison built on unlike items. ## Review the result before sharing it Before sending the result, ask someone who did not collect it to explain what each price represents. If they cannot tell which pack, area and date were compared, improve the presentation. This small review often catches a missing condition before it becomes an unsupported claim in a buyer meeting. Keep the source rows available so the discussion can return to the evidence. ## Choose your next step Continue with [not checked is not empty](https://rewalto.com/guides/not-checked-is-not-empty) or [price consistency across dark stores](https://rewalto.com/guides/price-consistency-across-dark-stores). Visit [Rewalto](https://rewalto.com/) to review current data and access options. ## Common questions ### Which is cheaper, Blinkit, Zepto or Instamart? None is cheaper everywhere. The same pack can differ by pin code, store and time, so compare the same pack at the same pin code and time. ### How many pin codes do I need for a fair comparison? Use the pin codes where your shoppers are, and read each at the same time. One pin code shows one store, not the whole city. ### Does the listed price include delivery or handling fees? No. Rewalto records the item's selling price as the app shows it on the product listing, without delivery, handling or platform fees. Those fees change with the basket and the time of day, so compare them separately if they matter to your decision. ### Can you compare prices collected on different days? You can describe the difference between those dated records, but you should not present it as a simultaneous comparison. If timing matters to the decision, collect or request a more closely aligned set. ### What should you do when a product has no displayed price? Keep the missing value and its reason where supplied. Do not infer a price from another location or retailer unless you are deliberately building an estimate and label the method clearly. This guide describes observed comparisons, not an estimation model. ## 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 from the blog [From the blog ### Why a price per 100 g misleads for coffee and tea, and what the shelf shows Dated shelf readings of coffee and tea show how pack size, format, chicory blend and pin code each move a price per hundred grams, and how to compare fairly. Explore](https://rewalto.com/blog/coffee-unit-price-on-the-shelf) ## Related guides [Data ### Not checked is not empty: read missing data correctly What missing price and availability readings can, and cannot, tell you. Explore](https://rewalto.com/guides/not-checked-is-not-empty) [Quick-commerce shelf ### Price consistency across dark stores Why one SKU can carry different prices across dark stores, a real Blinkit example, and how to check your own products. Explore](https://rewalto.com/guides/price-consistency-across-dark-stores) --- Canonical page: https://rewalto.com/guides/same-product-different-price-across-apps Last content change: 2026-10-18