/ rule 96 · schedule h2 readiness

two of these obligations are already in force.

Codes on API packs have been required since January 2023, and on the listed Schedule H2 brands since August 2023. Vaccines, narcotics, anti-cancer products and antimicrobials follow. We are the manufacturer's side of that project — we scope what is covered, write the specification you put to vendors, and qualify what gets installed.

We do not sell printers or software, and we hold no vendor agreements. That is the point of asking us.

the obligations, with the rule behind each one.

Four separate obligations, created by three instruments, on four different dates. They are not one deadline and they do not all reach the same products.

In force now

active pharmaceutical ingredients

since 1 January 2023

A machine-readable code at every packaging level of every API manufactured in or imported into India, carrying the product identification code, API and brand name, manufacturer, batch number and size, manufacturing and expiry or retest date, the shipping container code and the licence number.

Instrument
G.S.R. 20(E), notified 18 January 2022
Rule
Rule 96(5), Drugs Rules 1945

the listed ~300 drug brands (schedule h2)

since 1 August 2023

A bar code or QR code on the primary label — or the secondary label where there is not enough space — storing the product identification code, generic and brand names, manufacturer name and address, batch number, manufacturing and expiry dates and the manufacturing licence number.

Instrument
G.S.R. 823(E), notified 17 November 2022
Rule
Rule 96, Drugs Rules 1945 — Schedule H2 inserted

Coming

vaccines · narcotics and psychotropics · anti-cancer drugs

1 July 2027

Schedule H2 extended from a named-brand list to whole therapeutic categories, so coverage no longer depends on whether a specific brand was scheduled.

Instrument
Reported as G.S.R. 506(E), 22 June 2026
Rule
Rule 96(6)–(7), Drugs Rules 1945
Status
Confirm against the Gazette before relying on this date.

antimicrobials

1 July 2028

The same category-wide extension, on a later date — the single largest tranche by SKU count for most general-range manufacturers.

Instrument
Reported as G.S.R. 506(E), 22 June 2026
Rule
Rule 96(6)–(7), Drugs Rules 1945
Status
Confirm against the Gazette before relying on this date.

Dates for the category extension are taken from published reporting of the June 2026 amendment. We check them against the Gazette as part of a scope assessment rather than asking you to act on a secondary source — and we will tell you if what we find differs from this page.

four things worth getting straight.

Each of these turns up in vendor material. Each is wrong in a way that costs money or credibility.

“India has a serialization and track-and-trace mandate.”

For the domestic market it does not. Rule 96 is a labelling and authentication requirement — a code on a pack that resolves to product data. There is no national movement-reporting hub for domestic supply, no Indian equivalent of EU FMD, US DSCSA or UAE Tatmeen. Exports are a separate regime with their own track-and-trace requirements.

“The deadline is 2027, so there is time.”

Two obligations are already in force. APIs have required a code at every packaging level since January 2023, and the listed Schedule H2 brands since August 2023. If either applies to you and the code is not on the pack, the exposure is present-tense, not a planning item.

“GS1 Sunrise 2027 is a regulatory deadline.”

It is a GS1 industry readiness target for retail point-of-sale systems to read 2D codes, enforced by retailers through supplier agreements rather than by any regulator. It matters commercially, and it is not CDSCO. Treating the two as one timeline is the fastest way to lose a regulator's confidence.

“The vendor's system will make us compliant.”

Compliance attaches to the holder of the manufacturing licence, not to the supplier of the equipment. A printer that marks the right data on the wrong pack level, or a code that is not reproducibly readable at end of line, is the licensee's finding to close at inspection.

five pieces of work, taken together or singly.

Most sites start with the first and stop to think. Each is scoped and priced on its own.

scope assessment

Which of your SKUs are caught, by which obligation, and on what date — resolved product by product rather than category by category.

Practice area: Regulatory Compliance

  • SKU-level mapping against the Schedule H2 list and the category extensions
  • API packs assessed separately — a different rule, already in force
  • Products you make under loan licence or for another marketer, where responsibility has to be agreed in writing
  • Export SKUs separated out, because the destination's requirements are not these
  • A dated obligation register per site, naming the rule behind each line

code content and artwork

Deciding what the code must carry, where it goes, and getting the artwork through change control without breaking the rest of the label.

Practice area: Regulatory Compliance

  • Data element list per product, checked against the rule rather than the vendor's template
  • Primary versus secondary placement, and the space case where primary is not feasible
  • Interaction with the rest of the mandatory label — schedule cautions, Legal Metrology declarations, MRP
  • GS1 identifier structure where you also sell into retail or export
  • Artwork change control, version history and the batch-record consequences

requirement specification

A written user requirement specification you can put to vendors — so quotes come back comparable, and so what arrives is what you asked for.

Practice area: Business Strategy

  • URS covering print, verification, reject handling, reconciliation and data retention
  • Line-by-line constraints: speed, substrate, pack format, available space on the line
  • Comparable vendor evaluation criteria — scored, not impressionistic
  • Reading quotes against the URS and naming what each one has left out
  • Acceptance criteria written before purchase, not after installation

vendor and system qualification

Qualifying the supplier and the installed system the way an inspector will expect to see it qualified.

Practice area: Quality Assurance

  • Supplier qualification and approved-vendor-list entry
  • Design, installation, operational and performance qualification protocols and reports
  • Code print-quality grading and the end-of-line readability check
  • Computerised system validation and data integrity expectations under the revised Schedule M
  • Challenge testing — what happens to a bad code, a mis-feed, a reprint

procedures and inspection readiness

The SOPs, records and training that turn a working machine into a defensible compliance position.

Practice area: Quality Assurance

  • SOPs for code generation, reconciliation, rejects, reprints and downtime
  • Batch record changes and the reviewer's checklist
  • Deviation, OOS and CAPA handling for coding failures
  • Operator and QA training against the new procedures
  • A mock inspection of the coding line and the records behind it

What we do not do. We do not supply, install or commission printers, vision systems or serialization software, and we do not resell anyone's platform. We write what you need, help you judge what you are being offered, and qualify what you install. The equipment contract is between you and your vendor.

the spec is worth more than the machine.

We do not sell you the equipment

Savison Life holds no vendor agreements and takes no commission on hardware or software. The specification you get is written for your line, not for a product someone needs to move. When we say a quote is over-specified, there is nothing in it for us.

The licensee carries the finding, so the licensee sets the spec

Responsibility for what is on the pack sits with the holder of the manufacturing licence. Writing the requirement yourself — rather than accepting a vendor's standard scope — is what makes that responsibility defensible at inspection.

Scoped to the problem, priced against it

A scope assessment is a different size of job from a full qualification programme. Engagements are scoped and priced per problem; there is no retainer to buy into before anyone looks at your situation.

Downtime is a specification decision

Most line disruption traces back to a requirement nobody wrote down — a substrate the printer cannot hold a code on, or a reject path that was never designed. The cheapest place to find that is on paper, before purchase.

request a scope assessment.

Tell us what you make and how many lines are involved. We will come back with which obligations reach your products, on what dates, and what a first piece of work would look like.

If this is not something we can help with, we will say so rather than take a meeting.

Prefer to describe it in your own words? Use the general contact form.

Product categories

We reply to every enquiry, usually within one business day. Nothing on this page is regulatory or legal advice.

  • G.S.R. 20(E), notified 18 January 2022 — Rule 96(5), Drugs Rules 1945 · effective 1 January 2023
  • G.S.R. 823(E), notified 17 November 2022 — Rule 96, Drugs Rules 1945 — Schedule H2 inserted · effective 1 August 2023
  • Reported as G.S.R. 506(E), 22 June 2026 — Rule 96(6)–(7), Drugs Rules 1945 · effective 1 July 2027 · pending Gazette confirmation
  • Reported as G.S.R. 506(E), 22 June 2026 — Rule 96(6)–(7), Drugs Rules 1945 · effective 1 July 2028 · pending Gazette confirmation

The regulator is the Central Drugs Standard Control Organisation (CDSCO), headed by the Drugs Controller General of India, under the Drugs and Cosmetics Act 1940. This page is general information about published requirements and is not regulatory or legal advice. Verify every instrument against the Gazette of India before acting on it.