FMCG Price Monitoring in India: The Complete Guide to Pack-Size, Per-Unit Price and Hourly Alerts (2026)

Introduction

FMCG price monitoring in India is no longer a weekly spreadsheet job. The same shampoo or biscuit can sell at different prices on BigBasket, Blinkit, Swiggy Instamart, Zepto and DMart Ready, and the price often changes by pincode and by hour. Worse, the pack you compare against may not be the same size.

Direct answer: FMCG price monitoring in India means capturing the MRP, selling price, pack size and stock status of your SKUs and competitor SKUs on each platform, at pincode level, several times a day. You then convert every price to a common unit (per 100 g, per 100 ml or per piece) and trigger alerts when the gap crosses agreed thresholds.

This guide is written for brand, sales and revenue-management teams. It focuses on the part most trackers skip: pack-size normalisation, multipacks, combo packs and shrinkflation, plus how to design hourly alert rules that people actually act on.

Why does pack size break FMCG price comparisons?

India removed its schedule of standard pack sizes. When the Department of Consumer Affairs amended the Legal Metrology (Packaged Commodities) Rules in 2021, it omitted Rule 5, which had prescribed pack sizes for various commodities, with effect from 1 April 2022. Brands can now launch a 67 g, 82 g or 115 g pack freely.

Price points matter too. In 2022, an Edelweiss analyst quoted by PTI said Re 1 to Rs 10 packs account for 25–35% of sales in most FMCG categories, and companies cut grammage to protect those price points instead of raising them. A rupee-only tracker will show such a pack as 'price unchanged' even when the value per gram has fallen.

So a raw price comparison between a 75 g pack on one app and an 80 g pack on another tells you very little. Useful FMCG price monitoring compares like with like: the same unit, the same pincode and the same time window.

Which platforms should FMCG brands monitor, and how do they differ?

Each platform shows price in a different context, so FMCG price monitoring has to follow the platform's structure. Quick-commerce apps serve a delivery address from a nearby dark store, so price and stock depend on the pincode. Scheduled grocery apps show a city or store-catchment view. Your collection plan should follow that structure.

Cadence suggestions are Actowiz practice guidance, not platform rules. Capture only publicly visible prices; no logged-in or member-only data.

For context on scale, Bain and Flipkart estimate that India's quick-commerce GMV reached $10–11 billion in 2025, served from more than 7,000 micro-fulfilment centres in over 200 cities.

What data fields does FMCG price monitoring need?

• Capture context. Platform, pincode, serving store or city, date and time of capture (IST). Without these, two prices cannot be compared fairly.
• Product identity. Platform product ID, title, brand, variant, image URL and category path. These feed SKU matching.
• Declared quantity. Net quantity as shown (for example '2 x 75 g'), parsed into number of units, quantity per unit, total quantity and unit of measure.
• MRP and selling price. Both values in rupees, plus the discount the platform displays, so you can recompute it rather than trust a badge.
• Unit price. Price per 100 g, per 100 ml or per piece, calculated by you, plus the unit price the platform shows if it displays one.
• Offer and pack type. Single, multipack, combo or bundle; offer text such as 'Buy 2 at Rs 99'; and any free item.
• Availability. In stock, out of stock, or not listed for that pincode. These are three different states and should never be merged.
• Change flags. Previous value, new value and time of change for price, MRP and net quantity.

How do you normalise pack size and compute price per 100 g?

Normalisation is the core of FMCG price monitoring: it turns messy listing text into a clean, comparable number. The steps below work for most food, home-care and personal-care categories.

• Parse the quantity string. Read patterns such as '500 g', '1 kg', '2 x 75 g', '(Pack of 3)', '180 ml + 20 ml free' and 'Combo: shampoo 340 ml + conditioner 180 ml'.
• Convert to a base unit. Grams for weight, millilitres for volume and pieces for count items such as diapers, tea bags or eggs.
• Compute total quantity. Units per pack multiplied by quantity per unit. Decide once, as a written rule, whether 'free' quantity counts. Most brand teams count it, because the shopper gets it.
• Compute unit price. Selling price divided by total quantity, multiplied by 100 for per-100 g or per-100 ml, rounded to two decimals.
• Match the SKU. Link listings to your master SKU list using brand, variant and declared quantity, with manual review for low-confidence matches.
• Store the raw text. Keep the original title and quantity string. When a parsing rule changes, you can recompute history.

Illustrative worked example with round numbers to show the method – not observed platform prices.

The last row shows why per-unit price matters. The shelf price is still Rs 20, but the price per 100 g has risen by about 12%. A rupee-only tracker would miss it.

How should multipacks and combo packs be handled?

Treat a same-product multipack as a variant of the parent SKU, with its own unit price. Treat a combo of different products (shampoo plus conditioner, noodles plus sauce) as a separate 'bundle' record. Allocate its price across components only if your team agrees a rule, such as allocation by each item's standalone selling price on the same capture.

How do you detect shrinkflation automatically?

Track net quantity as a time series for every matched SKU. Flag a shrinkflation event when the declared quantity falls while the selling price and MRP stay flat or rise. Confirm against the product image or title before alerting, because a platform may simply have mapped a new variant to an old listing.

MRP vs selling price: what should brand teams track?

MRP is the printed ceiling, inclusive of all taxes; selling price is what the shopper pays in the app. The 2021 amendment made MRP declaration in Indian rupees, inclusive of all taxes, mandatory. Both numbers should be captured on every observation.

• Discount depth. (MRP − selling price) ÷ MRP. Compare it with the trade terms and promotions you agreed with each platform.
• MRP mismatches. The same pack showing different MRPs across apps usually means an old batch, a mapping error or a new MRP rolling out unevenly.
• Selling price above MRP. This should not happen; treat it as a data or listing issue to escalate.
• Price-floor breaches. Selling price, or unit price, below your agreed minimum in a pincode – the most common alert brand teams ask for.

How should hourly price and pack-size alerts be designed?

Hourly data creates noise unless every alert has an owner, a threshold and a cool-down. Start with a small rule set and tune it after two to four weeks.

• Use consecutive captures. Requiring two hourly hits before alerting filters out one-off glitches.
• Group by pincode cluster. One message for 'Bengaluru South, 14 pincodes' beats 14 separate messages.
• Send to where teams work. Email digests, Slack or Teams messages, or a webhook into your BI tool.
• Log actions. Record who acted and when, so you learn which rules are worth keeping.

For store-level availability alongside price, see our guide to dark-store pricing and availability tracking.

Is FMCG price monitoring legal, and what does Legal Metrology require?

Collecting publicly displayed prices for competitive analysis is a common practice, but it should be done responsibly. Capture only public product pages, avoid logins and personal data, respect each site's terms and keep request rates modest.

Legal Metrology is relevant because it shapes what you see. The 2021 amendment introduced a unit sale price declaration on pre-packed commodities so shoppers can compare prices. As amended in 2022, the rule asks for unit sale price per gram below one kilogram and per kilogram above, with parallel rules for millilitres, litres and items sold by number. The government has also issued notices to e-commerce entities for not displaying mandatory declarations such as MRP and net quantity.

For FMCG price monitoring in India, this means the declared net quantity and MRP on a listing are compliance data, not just marketing data. A monitor that flags missing or inconsistent declarations helps your team correct listings quickly. This is general information, not legal advice; confirm specifics with your legal team.

Should you build FMCG price monitoring in-house or buy it?

Many brand teams start with a pilot: two or three cities, a few hundred SKUs, five platforms and hourly captures, then expand once alert rules have been tuned. See how a similar setup worked in our FMCG quick-commerce price monitoring case study.

Frequently Asked Questions

What is FMCG price monitoring?

It is the regular capture of MRP, selling price, pack size, offers and stock status for your products and competitors across online retail and quick-commerce platforms, converted into comparable unit prices and alerts.

How often should prices be captured on Blinkit, Zepto and Instamart?

For priority SKUs and pincodes, hourly captures are common because quick-commerce prices and stock change within the day. Less volatile SKUs can be captured every two to four hours.

Can a price monitor detect shrinkflation?

Yes. By storing net quantity as a time series for each matched SKU, the monitor can flag cases where the declared quantity drops while the price stays flat or rises, then confirm with the product title or image.

Which pincodes should a brand track?

Start with pincodes that drive the most sales or where distributors report issues, then add a sample from each city zone. Quick-commerce prices are set per serving dark store, so city averages can hide problems.

Does Actowiz collect logged-in or member-only prices?

No. Actowiz collects publicly visible product information only, without logins or personal data, and in line with site terms.

You can also reach us for all your mobile app scraping, data collection, web scraping, and instant data scraper service requirements!