Legal Metrology E-Commerce Rules Are a Data Problem

India's Legal Metrology (Packaged Commodities) Amendment Rules 2026 took effect on 1 July 2026, and the fastest way to get them wrong is to treat them as a labeling task. Every listing must now carry accurate net quantity, MRP inclusive of all taxes, and the packer or importer's details, and for imported goods your catalog must be searchable and sortable by country of origin. You cannot satisfy a searchable filter with a line of text on one page - the data has to be a clean, structured field that is present and identical on every channel you sell on. That makes it a product-data build, not a page edit.

What the rule actually changed on 1 July 2026

The amendment was issued earlier in 2026 by the consumer-affairs ministry and came into force on 1 July 2026. Two parts of it matter for anyone selling packaged goods online. First, the mandatory declarations a shopper expects on a pack - net quantity, the maximum retail price inclusive of all taxes, the name and address of the manufacturer, packer or importer, and consumer-care details - now have to appear clearly on the online listing itself, before the buyer completes the purchase, not only on the box that arrives later. Second, a new sub-rule requires that imported products be discoverable through a searchable and sortable country-of-origin filter across the catalog.

The word that quietly changes everything is "filter." A label is something you display on a page. A filter is something a shopper can search by and sort by across your entire catalog. You can hand-write a label; you cannot hand-write a filter. A filter only exists if the value behind it - country of origin, in this case - is a real, structured attribute attached to every product, with the same meaning everywhere. And this is a direction, not a one-off: a follow-up amendment already sets further obligations for 1 July 2027, so the sensible read is that online product data is going to keep getting more regulated, not less.

Why this is a product-data problem, not a page edit

The natural instinct is to hand this to whoever edits product pages: add a country-of-origin line, fix the MRP, move on. That works perfectly - for one product, on one channel. It falls apart the moment you have a few hundred SKUs listed across your own store, Amazon, Flipkart, a quick-commerce app and ONDC, because each of those surfaces pulls its listing from a different feed. A filter or a declaration is only correct if the attribute underneath it is present, structured and identical in every one of those feeds at once.

Picture the usual mess. Country of origin sits in a free-text sentence in your store description, is left blank on one marketplace, and carries a slightly different value on a third. MRP shows the pre-discount price on one channel, the current price on another, and a stale number on a listing nobody has touched in six months. Net quantity has a typo from a bulk upload. None of that is unusual - it is the default state of a fast-growing catalog. What the new rules do is turn that everyday inconsistency from a quiet trust problem into a compliance exposure, on the exact channels where most of your volume now lives. This is the same underlying gap that clean product information management is built to close.

The three things that now have to be clean, structured and everywhere

Strip the legal language away and the rule is asking for a small set of attributes to be correct on every listing at all times. The difficulty is not any one field - it is keeping all of them true across channels that each want the data in their own format.

1. Country of origin - the new filterable one

For imported products this is the field that changed status. It is no longer enough to mention the origin in a description; it has to be a structured attribute the platform can build a searchable, sortable filter on. That means one clean value per SKU, chosen from a controlled list rather than typed freehand, so "USA," "U.S.A." and "United States" do not fragment your own filter. If you sell imported beauty, electronics or wellness goods, this is where most of the work sits, and it maps directly to the same product-data discipline behind getting cross-border product data right.

2. Net quantity and MRP

Net quantity and the maximum retail price, inclusive of all taxes, have to be present and accurate on the listing and match the pack. The common failures are boring and expensive: MRP that drifts between channels because each was edited separately, and net-quantity errors that slip in through bulk spreadsheet uploads. When the same SKU shows two different prices on two of your channels, you now have both a trust problem and a declaration problem, and the only durable fix is to stop editing prices per channel and push one authoritative value to all of them - the point of proper multi-channel data sync.

3. Manufacturer, packer or importer identity

The name and address of the manufacturer, packer or importer must be shown - and for imported goods the importer's details are the ones that count. This is classic master data: it belongs on the product or vendor record once, not retyped into every listing where it can be got wrong. Held properly, it flows onto every channel automatically, which is exactly what a resilient store-to-Odoo integration and a clean order and inventory backbone are for.

A five-step plan to get ready and stay ready

None of this requires re-platforming. It is data work you can do methodically, and every step pays off well beyond one regulation.

1. Inventory every listing, on every channel. Pull a real list of what you sell and where - your store, each marketplace, quick commerce, ONDC. You cannot fix declarations you have not counted, and most brands find more live listings than they expected.

2. Give each SKU one structured home for its declarations. Capture net quantity, MRP, manufacturer or importer identity, and country of origin as proper fields on the product record - not sentences buried in a description. This is the product-information layer everything else reads from.

3. Make one system the source and push it out. Decide that your ERP owns these attributes and every channel receives them from it. The moment two systems can each edit MRP, they will drift, and you are back to inconsistent declarations.

4. Turn country of origin into a real attribute. Move it from free text to a controlled field with a fixed list of values, so a searchable, sortable filter can actually be built on it and your own catalog stops fragmenting across spellings.

5. Add a standing check, not a one-time cleanup. New SKUs, new suppliers and new channels will reintroduce gaps, and the rules themselves move again in 2027. A simple recurring audit that flags any listing missing a mandatory field keeps you compliant without a fire drill each time.

The India and D2C cut - plus an AI bonus

Three things make this sharper for an Indian D2C brand than the headline suggests. First, most brands here are genuinely multi-channel - the same catalog lives on a store, two or three marketplaces and a quick-commerce app - so a data gap is not contained to one page, it is amplified across every surface at once. Second, imported goods are common in exactly the fast-growing categories - beauty, personal care, electronics, wellness - which puts the new country-of-origin filter squarely in scope for the brands scaling fastest. Third, non-compliant listings are not a soft risk: the underlying Act carries penalties, repeat-offence escalation and seizure of non-compliant stock, and a marketplace can pull a listing that fails its checks, so a data problem can quietly cost you both a fine and your shelf space, the same class of listing risk that reliable marketplace listing integration is meant to remove.

Here is the part worth the effort on its own. The exact attributes the law now forces you to expose - clean, structured country of origin, accurate net quantity, correct price - are the same structured product data that AI shopping surfaces read when they decide whether to recommend you. When a catalog is machine-readable and consistent, it is both compliant and discoverable; when it is messy free text, it fails the regulator and the algorithm at the same time. That overlap is why getting your catalog ready for AI shopping agents and making sure AI crawlers can actually read your storefront are not separate projects from this compliance work - they are the same clean-data build, done once. The physical side of it, your pack and shipment labels, is a distinct but related job covered by an Odoo packaging and labeling setup.

Frequently asked questions

We only sell India-made goods. Does this apply to us?

The searchable country-of-origin filter is aimed at imported products, so if you sell nothing imported that specific requirement is lighter for you. But the mandatory declarations - net quantity, MRP inclusive of tax, and packer identity shown clearly on the listing - apply to packaged goods generally, so the core data-hygiene work still lands on you. And the moment you add a single imported SKU, the filter requirement switches on.

Isn't this the marketplace's responsibility, not ours?

The platform has to ensure the information is displayed, but the accurate data has to come from the seller. In practice that means you are responsible for supplying correct, complete declarations for every SKU, and the marketplace enforces that you do. Treating it as someone else's job is how listings get pulled. Owning the data yourself is the only reliable position.

We run Shopify and Odoo. Where do we start?

You are well placed, because Odoo can hold these declarations as structured product attributes and feed them to Shopify and your marketplace channels from one place. Start by making Odoo the owner of net quantity, MRP, importer identity and a controlled country-of-origin field, then push those to every channel rather than editing each listing by hand.

What actually happens if we ignore it?

Non-compliant listings expose you to penalties under the Legal Metrology Act, escalating for repeat offences, and to seizure of non-compliant stock, alongside the everyday risk of a channel de-listing a product that fails its checks. Set against that, cleaning the data once is cheap - and it makes you more discoverable at the same time.