Legal Metrology 2026: New Country-of-Origin Rules for E-commerce Sellers.

If your FMCG brand sells through e-commerce marketplaces, a new compliance deadline is landing this year — and it's specific enough that "we'll figure it out later" isn't really an option. Here's what actually changed, and why enforcement risk on this one is unusually high.

What actually changed

On February 13, 2026, the Ministry of Consumer Affairs, Food and Public Distribution notified the Legal Metrology (Packaged Commodities) Amendment Rules, 2026, via G.S.R. 128(E). The amendment inserts a new sub-rule, 6(10A), into the existing Legal Metrology (Packaged Commodities) Rules, 2011.

In plain terms: every e-commerce entity selling imported products must provide product listings with a searchable and sortable filter specifying Country of Origin. Not just a disclosure buried in product description text — an actual functional filter a shopper can use to sort and search by. This is a meaningfully higher bar than most current e-commerce listing practices, where origin information, if present at all, tends to live as unstructured text somewhere in the product description.

There's already a second amendment

A Second Amendment, notified April 27, 2026, goes further — it substitutes the original sub-rule (10A) with an expanded version, still centered on the country-of-origin filter requirement for imported products, with its own compliance date of July 1, 2027.

The pattern here is worth noting: this is not a one-and-done rule change. The government amended it twice within three months. Brands treating the July 2026 date as the finish line risk being caught flat-footed by the July 2027 follow-up. If your compliance roadmap only has one milestone marked for this rule, add a second one now.

Who this actually affects

• E-commerce marketplaces and inventory-based online retailers
• Direct-to-consumer brands importing finished goods
• Importers listing products on any digital platform
• Cross-border sellers operating in the Indian market
• Platform operators responsible for search and listing architecture — not just the sellers using the platform

That last point deserves emphasis: if you operate your own D2C storefront rather than selling exclusively through a third-party marketplace, the obligation to build and maintain this filter falls on you directly. You can't rely on a marketplace's compliance work to cover your own site.

Why enforcement risk here is unusually high

Legal commentary on this amendment flags something specific: because the requirement is objectively verifiable through simple platform testing — does the filter exist, does it work, is it accurate — enforcement doesn't require complex investigation. A regulator, or a competitor filing a complaint, can check compliance in minutes by simply visiting the listing and trying to use the filter.

That combination of low-effort verification and legal exposure is exactly the profile that tends to generate early, visible enforcement actions once a grace period ends. Compare this to a rule requiring detailed financial audits to verify compliance — this one requires nothing more than a browser and five minutes, which materially changes the incentive calculus for regulators looking for early, easy-to-prove enforcement wins.

What to prepare now

• Backend data restructuring — country-of-origin data needs to exist as a structured, filterable field, not free text in a description
• Front-end UI/UX changes — the actual filter/sort interface needs to be built and tested on every marketplace you list on, since each platform's technical implementation will differ
• Seller onboarding updates — if you operate a marketplace yourself, your seller onboarding flow needs to capture this data at the point of listing, not retrofit it later across an existing catalog
• Data governance — someone needs explicit ownership of keeping origin data accurate as your supply chain and sourcing changes over time, not just accurate at initial launch

Where verifiable batch data helps beyond this one rule

Country-of-origin is just one data point regulators are increasingly expecting to be structured, verifiable, and consumer-accessible. The same underlying discipline — clean, authenticated, batch-level product data tied to every unit — is what makes this kind of compliance requirement straightforward to satisfy rather than a scramble each time a new rule lands.

Ratifye's authentication layer captures exactly this kind of structured product data on your existing GS1 barcode, so origin, batch, and authenticity information is already there and verifiable — not something you're reconstructing under deadline pressure the next time a regulator asks for it in a new format.