Ecommerce Website Development in Pune: Meeting the 2026 Legal Metrology Rules on Your Product Pages
Ecommerce website development in Pune now has a hard compliance deadline to build against: the Legal Metrology (Packaged Commodities) Amendment Rules, 2026, notified by the Ministry of Consumer Affairs on 13 February 2026 and effective from 1 July 2026, which require specific declarations — MRP, net quantity, manufacturing date, manufacturer or importer details, and for imported goods, a searchable country-of-origin filter — to actually appear on your product listing pages, not just on the physical package a customer receives days later. If your store's product templates were built before this rules change, or by a developer unfamiliar with it, there's a real chance your listings are non-compliant right now regardless of how good the packaging itself is.
This is not a niche or symbolic rule. It carries actual penalties — up to ₹25,000 for a first offence and up to ₹1 lakh for repeat violations under the Legal Metrology Act, 2009 — and responsibility sits with both the seller and the e-commerce platform or website operator, which means a business selling through its own custom-built store carries this obligation directly, with no marketplace compliance team standing between the rule and the listing.
What the rule actually requires
The amendment extends declarations that have long applied to physical packaging into the digital listing itself. In practical terms, every product listing needs to clearly display:
- The retail sale price (MRP), inclusive of all taxes, exactly as it would appear on the physical package
- Net quantity — weight, volume, count, or whatever unit is appropriate to the product
- The manufacturing or "best before"/expiry date, where applicable to the product category
- Name and address of the manufacturer, packer or importer, not merely the brand name shown for marketing purposes
- For imported products specifically, the country of origin — and from 1 July 2026, this needs to be presented as a searchable and sortable filter on the listing pages, not just printed text somewhere on the page, meaning a shopper needs to be able to filter or sort a category by country of origin
That last requirement is the one most likely to catch an existing store off guard, because it's not a labelling change — it's a functional requirement on the storefront's search and filter architecture, which means it's a development task, not just a content-entry task for whoever manages product listings.
Why this is a website development problem, not just a content problem
It's tempting to treat this as something the merchandising or catalogue team can handle by adding text to product descriptions, and for the simpler declarations — MRP, net quantity, manufacturer details — that's largely true, provided the product page template actually has a defined, consistent field for each of them rather than relying on whoever writes each listing to remember to include it manually every time.
The country-of-origin filter is different. It requires:
- A country-of-origin field in the product data model for every SKU, populated accurately — not defaulted to "India" or left blank, both of which are compliance risks in their own right
- A filter or facet on category and search pages that lets a shopper narrow results by country of origin, alongside existing filters like price, size or brand
- Consistency between what a product page states and what a bulk category listing or search-result grid shows, since a compliant product page next to a non-compliant category grid still leaves the store exposed
For any store built on a platform like WooCommerce, Shopify or a custom stack, this is a real, scoped development task — adding a structured attribute, building or adjusting a filter component, and auditing the product catalogue to make sure the data behind it is actually accurate rather than a placeholder value entered under time pressure at the original build stage.
A practical audit checklist
For a Pune business auditing its existing store before or shortly after the 1 July 2026 effective date, this is roughly the order to check things in:
- Pull up ten product pages across different categories and check each one against the five declarations above. Note anywhere a declaration is missing entirely versus present but inconsistent — different products showing manufacturer information in different formats or locations on the page is its own quiet risk, because it suggests the requirement isn't structurally enforced by the template.
- Check whether MRP shown online matches MRP on the physical package for a sample of products. A mismatch, even an accidental one from an old catalogue update, is a compliance and customer-trust problem simultaneously.
- Confirm whether your catalogue data actually has a country-of-origin field, and if it does, whether it's populated accurately for imported SKUs specifically, not just for show.
- Test whether a shopper can actually filter or sort a category page by country of origin — not whether the information exists somewhere on an individual product page, but whether the functional filter requirement is met at the listing level.
- Check your CMS or catalogue import process for whether these fields are mandatory at the point a new product is added, or optional and therefore likely to be skipped under deadline pressure by whoever manages the catalogue day to day.
Where this intersects with the checkout, not just the catalogue
The declarations mostly live on product and category pages, but a full compliance pass should also check the order confirmation and invoice generation flow, since GST-related pricing display rules (inclusive-of-tax pricing, correctly itemised invoices) sit alongside these Legal Metrology requirements and are frequently audited together in practice, even though they come from different pieces of legislation. A store that's fixed its product pages but still generates an invoice that doesn't clearly itemise tax and net price consistently hasn't closed the loop on the broader compliance picture a customer or regulator would actually look at.
Who this applies to
The rule applies to e-commerce entities and sellers dealing in packaged commodities sold to Indian consumers — which covers the overwhelming majority of physical-product online stores, from a D2C skincare brand to a grocery delivery platform to a small business selling handmade goods through its own website. Services businesses without a packaged physical product, and platforms dealing purely in digital goods, generally fall outside its scope, though anyone uncertain about their specific category should confirm with a compliance professional rather than assume based on a general reading of a blog article — this piece is a starting checklist for the conversation with your developer and compliance advisor, not a substitute for legal sign-off on your specific catalogue.
What this costs to fix
For a store with clean, structured product data already, adding the missing declaration fields and a country-of-origin filter is a bounded, scoped development task — typically a matter of days for the technical build, plus however long it takes to actually populate accurate country-of-origin data across an existing catalogue, which is often the longer part of the job for a store with hundreds or thousands of SKUs and imperfect legacy data. For a store with an inconsistent or ad hoc product page template, where similar information is entered differently for different products, the more valuable (and more expensive) fix is standardising the underlying data model first, so that all future compliance requirements — this one and whatever follows it — can be enforced structurally rather than manually re-checked by hand every time a rule changes.
A quick reference table
| Declaration | Where it typically lives on a page | Common gap in older stores |
|---|---|---|
| MRP (inclusive of tax) | Product price display | Price shown excludes a charge added later at checkout, creating a mismatch |
| Net quantity | Product title or a dedicated specification field | Buried in a description paragraph rather than a consistent, scannable field |
| Manufacturing/expiry date | Specification table or a dedicated field for perishables | Often missing entirely for categories where it's genuinely required |
| Manufacturer/packer/importer name and address | Specification table or a "product details" section | Only the brand name is shown, not the legal manufacturer or importer entity |
| Country of origin (imported goods) | Specification field, ideally also a filter | Present as text on some products, absent as a functional filter across the category |
Common mistakes stores make
Treating this as a one-time content update rather than a structural fix. Manually editing a batch of product descriptions to add missing declarations solves the problem for today's catalogue but not for the next hundred products someone uploads next quarter, unless the fields are made mandatory in the product template itself.
Assuming a marketplace listing and your own website need different treatment. If you sell both on your own site and through a marketplace, the declarations need to be accurate and consistent in both places — a marketplace's own compliance tooling doesn't extend to your independent website.
Defaulting country of origin to "India" to avoid leaving it blank. This is arguably a worse failure mode than an honest blank field, because it actively misrepresents an imported product rather than simply lacking the data, and is a more serious compliance and consumer-trust problem if discovered.
Not auditing variants separately. A product with multiple size or pack variants may have different net quantities or even different manufacturers per variant; a single declaration applied to the parent product listing without variant-level accuracy is a common, easy-to-miss gap.
Losing track of which SKUs were actually audited. For a catalogue of any real size, an ad hoc "we checked some products" pass isn't defensible if questioned later. A simple spreadsheet or catalogue flag marking each SKU as audited, with the date, is a low-effort way to demonstrate a genuine compliance process rather than a one-off scramble.
How enforcement typically plays out in practice
Legal Metrology enforcement in India has historically focused on physical retail and packaging first, with digital listings a newer and still-developing area of active inspection. That's a reason to fix this properly, not a reason to deprioritise it — a rule with growing enforcement attention and a defined penalty structure tends to catch up with businesses that treated an early compliance deadline as optional, and the cost of fixing it after a complaint or inspection (potential penalties, plus the reputational cost of a public compliance failure) is considerably higher than the cost of a planned technical fix now.
Frequently Asked Questions
Does this apply to a small business selling on Instagram or through WhatsApp rather than a full e-commerce website?
The rule is framed around e-commerce entities and digital networks used for commercial transactions broadly, which plausibly extends beyond a full storefront to any digital sales channel — but enforcement focus and practical risk are naturally higher for structured e-commerce platforms with visible, searchable catalogues. If most of your sales happen through informal channels, it's still worth checking with a compliance professional rather than assuming you're exempt.
What happens if my catalogue has hundreds of SKUs and incomplete country-of-origin data?
This is a common and genuinely time-consuming problem, not a quick fix. The practical approach is prioritising your highest-selling and highest-traffic SKUs first, then working through the remaining catalogue systematically, rather than either ignoring the gap or attempting to backfill an entire large catalogue with unverified guesses, which creates its own accuracy risk.
Is a mismatch between the price on my website and the price on the package a Legal Metrology issue or a different regulation?
MRP accuracy sits squarely within Legal Metrology's core purpose, so a genuine mismatch is very much within its scope, separate from GST invoicing rules, which govern how tax is itemised rather than what price is being charged in the first place. Both matter, and a mismatch on either front is worth fixing regardless of which specific regulation technically governs it.
Can my website's shopping cart or CMS platform handle this automatically?
Some e-commerce platforms have added or are adding fields and filter support for this specifically because of the 2026 rule change, but "the platform supports it" and "your specific store has it configured and populated correctly" are different things. Confirm with whoever manages your store's technical setup that the feature exists and has actually been turned on and populated, not assumed to be handled by the platform in the background.
Does this rule apply retroactively to products already listed before July 2026, or only new listings?
The rule governs what a listing must display, not when the product was first added to the catalogue, so existing listings need to be brought into compliance by the effective date the same as any new one — there's no grandfathering for products already on the site before the rule took effect.
We use a marketplace's own storefront tools, not a custom-built site — does any of this still apply to us?
Yes. The obligation to declare this information accurately sits with the seller regardless of which platform hosts the listing, and a marketplace's storefront tools providing a field for a declaration doesn't mean the field is filled in correctly unless someone on your side actually checks it. Treat a marketplace listing with the same audit discipline described here for a self-built store.
Who is legally responsible if a product listing is non-compliant — me, or the developer who built the site?
Legal responsibility for the accuracy of declarations sits with the seller and the e-commerce entity operating the platform, not with the developer who built the technical capability to display them. A developer can build a fully compliant template with all the right fields and filters; if inaccurate or incomplete data is then entered into that template, the compliance failure is a data and process problem, not a coding one.
Related Reading
This sits alongside the broader tax and compliance picture your checkout needs to handle — our checklist on GST, invoicing and legal compliance for e-commerce websites in India covers the tax side of the same product and checkout pages in more depth.
How We Approach This at Govindani Infotech
Our e-commerce development team treats MRP, net quantity, manufacturer details and country-of-origin as mandatory, structured fields in the product data model for every store we build, not optional text a merchandising team might remember to add — which means the compliance requirement is enforced by the template itself rather than depending on someone's memory during a busy catalogue upload. Our checkout system work checks the same discipline extends through to order confirmation and invoicing, so the two don't drift out of sync with each other.
If you're auditing an existing store against the 2026 rules, or building a new one and want these requirements handled correctly from the first product upload, get in touch through our contact page to talk through your specific catalogue.
Sources: Mondaq — Legal Metrology (Packaged Commodities) Amendment Rules, 2026: Enhancing Transparency And Consumer Protection In E-Commerce, SCC Online — New Rule Requires E-commerce Platforms to Clearly Display Country of Origin for Imported Products, Chambers and Partners — LMPC Rules Amended: New Compliance for E-Commerce, SS Rana — Legal Metrology Compliance for E-Commerce Businesses