Track-and-Trace Is Coming to More States.

Two years ago, QR-based track-and-trace for liquor was a handful-of-states story. Today it's a spreading pattern.

Uttar Pradesh, Telangana, Maharashtra — and the states you're not yet compliant in are watching the ones you are. If you distribute liquor across more than two or three states, this is the year the compliance map gets genuinely complicated, not simpler.

Jharkhand is next

Jharkhand's Excise and Prohibition Department has sent a team to study Uttar Pradesh and West Bengal's existing track-and-trace implementations, with a report due to the Excise Minister on next steps. The stated goals are familiar to anyone who's followed this pattern in other states: stop counterfeit and illegal liquor from reaching consumers, and plug revenue leakage that untracked distribution channels create.

The mechanism under consideration is a QR-code system where scanning a bottle gives immediate proof of authenticity — the same basic pattern already live in the states ahead of it. What's notable is the specific choice to study UP and West Bengal rather than starting from scratch: this suggests Jharkhand is looking to adopt a proven implementation quickly rather than spend years on a bespoke system, which historically has meant faster time-to-notification once a state commits to the fact-finding stage.

For brands distributing into Jharkhand, this isn't a "someday" consideration anymore. States that send fact-finding missions to existing implementations tend to move from study to notification faster than the multi-year timelines legacy compliance projects assume. If Jharkhand is a meaningful part of your distribution footprint, start the internal conversation about what a QR retrofit would take now, rather than after the notification lands with a tight compliance window.

Haryana just expanded scope

Haryana already had a QR-based track-and-trace system for IMFL (Indian Made Foreign Liquor) and country liquor, introduced in 2023-24. The update: this system is now extending to cover imported foreign liquor as well — a category that previously sat outside the tracking requirement.

This is a meaningful shift in scope, not a minor technical update. Imported liquor brands that were operating in Haryana without a track-and-trace obligation now need to bring their packaging and distribution data into the same system that domestic and IMFL brands have been using for two years. Depending on how import documentation and customs data currently flow into your supply chain records, this may require new integration work, not just a labeling change.

Brands in other states with similar carve-outs for imported products, duty-free allocations, or specific licensing categories should read Haryana's move as a signal, not an isolated event. Exemptions in excise policy tend to close over time as tracking infrastructure matures, rarely the other way around.

A related shift worth tracking: FSSAI's reclassification

Separately, FSSAI updated its labeling framework to replace references to "low alcohol" with "ready-to-drink alcohol" as a defined category — beverages between 0.5% and 15% ABV made from a spirit base — and added "Indian liquor" as a distinct classification bridging food safety law and state excise definitions.

FSSAI aligned the effective date with the start of the excise year (April 1 or July 1, depending on state) specifically to avoid mid-year label reprinting costs. This detail matters beyond the labeling change itself: it signals FSSAI is deliberately timing future labeling harmonization around excise-year boundaries, which means brands should expect the next round of labeling updates to also land at an excise-year start rather than an arbitrary calendar date — useful for planning your compliance calendar going forward.

The compliance math for multi-state brands

If you distribute across even three or four of the states above, you're likely already running separate compliance workflows for each state's specific QR/labeling requirements — different portals, different data formats, different audit cadences. That's the real cost here, and it compounds with every new state that adopts its own system: not any single state's requirements, but the fragmentation of running N different systems for N different states.

This fragmentation cost is often underestimated in initial compliance budgeting, because each individual state's requirement looks manageable in isolation. It's the cumulative operational overhead — separate vendor relationships, separate reporting cadences, separate staff training per state — that erodes margin over time.