Schedule H Compliance for Indian Pharmacies [2026]

Schedule H and Schedule H1 medicines are among the most inspection-sensitive lines in Indian retail and hospital pharmacies. The rules are public law under the Drugs and Cosmetics Act, 1940 and the Drugs and Cosmetics Rules, 1945—not vendor marketing. This guide explains what the schedules require, why multi-branch groups face higher risk, and how software can support registers without replacing your pharmacist’s judgment or your licence obligations.

Multi-branch pharmacy groups in India often grow faster than their compliance systems. Schedule H discipline is where that gap shows up first—because the penalty is not only financial but licence reputation. This article is for owners, superintendent pharmacists, and operations leads who need a practical register strategy, not a law school lecture.

What Are Schedule H and Schedule H1 Drugs?

Schedule H lists prescription drugs that may be sold by retail pharmacies only against a prescription from a registered medical practitioner. Schedule H1 is a tighter subset with additional record-keeping requirements for certain habit-forming and monitored medicines. The schedules are notified under the Drugs and Cosmetics Rules; the exact drug entries change through gazette updates, so your compliance lead should verify current notifications rather than relying on memory.

Examples commonly found in Schedule H include many antibiotics, anti-hypertensives, and other therapies that should not be sold OTC. Schedule H1 includes specified molecules subject to stricter dispensing registers and quantity limits as notified. The purpose is public health: prevent casual sale of medicines that need professional diagnosis, monitoring, and traceability.

Prescription requirement is the core control. A valid prescription identifies the prescriber, patient context, drug, strength, and directions. Pharmacies must retain prescriptions or authenticated copies per applicable rules and state inspection practice. Selling scheduled drugs without prescription on file is a serious compliance failure—not a “small shop” exception.

State drug controllers and inspection teams may also review whether the pharmacist on duty is registered and whether supervised dispensing occurs for scheduled lines. Software cannot register your pharmacist; it can make non-compliance visible earlier through mandatory fields and exception reports.

Record-Keeping Requirements for Schedule H Dispensing

Dispensing registers must capture who received what, when, in which quantity, from which batch, and against which prescription. Patient name, address where required, drug name, batch number, expiry, bill reference, and date are typical fields inspectors expect to reconstruct. Hospital pharmacies add ward and admission context in their SOPs; retail shops use prescription-linked sales.

Retention periods follow applicable central and state rules and inspection practice—operators should confirm current requirements with their compliance adviser rather than assuming one national number for all record types. Incomplete registers—missing batch numbers, blank patient fields, or prescriptions filed days later—create inspection risk even when the underlying sale was legitimate.

Electronic records are acceptable when they are searchable, tamper-evident in practice, and printable for inspection. Paper registers still work if disciplined; the failure mode is hybrid chaos—some lines on software, some on paper, none complete.

Quantities matter for Schedule H1: rules may cap supply per prescription or require additional declarations. Billing software should warn when a sale exceeds configured limits rather than silently completing the bill.

Why Multi-Branch Pharmacies Face Higher Compliance Risk

Each pharmacy branch is typically a separate licensed premise under state drug law. Schedule H compliance is evaluated per site, not per brand logo. A group with ten shops has ten registers, ten prescription files, and ten inspection surfaces.

Cross-branch transfer of scheduled stock is not a casual stock movement. Transfers need documentation—invoice, gate pass, batch trace, and receiving branch records—aligned with your state’s practice and your licence conditions. Software that treats branches as isolated silos without transfer audit trails invites reconciliation gaps.

Owners who cannot see dispensing registers remotely depend on branch managers’ WhatsApp photos before inspections. That does not scale. Centralised, branch-scoped search—who dispensed Schedule H1 last Tuesday at Branch 4—is operational governance, not IT luxury.

Franchise models compound the problem: franchisees may buy software independently while the brand shares one visual identity. Compliance liability still sits with the licensed premise. Central templates for Schedule H workflows reduce variance between franchisee stores.

Common Compliance Failures and How to Prevent Them

Failure: dispensing without a valid prescription on file. Prevention: block bill completion for scheduled drugs until prescription reference is captured; superintendent pharmacist review for overrides.

Failure: incomplete batch records on the register. Prevention: tie billing line items to batch selection at dispense; forbid “default batch” habits during rush hour.

Failure: expired or near-expiry scheduled drugs dispensed. Prevention: FEFO enforcement at billing (see our FEFO guide); near-expiry quarantine workflows.

Failure: records not producible during inspection. Prevention: daily backup, exportable register per branch, and rehearsed inspection drill—pull last month’s Schedule H1 lines in front of the inspector without leaving the counter for two hours.

Failure: locum pharmacists unfamiliar with branch SOPs. Prevention: short scripted workflow in software plus written SOP; no verbal-only training on scheduled drugs.

Failure: internet outages pushing staff to “manual bypass” without later reconciliation. Prevention: offline-first billing that still enforces prescription capture locally before print.

CDSCO and state inspections increasingly expect traceability from purchase to patient handover for scheduled lines. That chain includes supplier invoices, batch storage, dispensing register, and patient bill. Weakness anywhere looks like systemic neglect even if your intent was sound.

What to Look for in Pharmacy Software for Schedule H Compliance

Software should flag Schedule H and H1 SKUs at item master level, prompt for prescription details before bill finalisation, and write dispensing lines into a searchable register per branch. Overrides need user identity and reason. Audit export should be filterable by date, drug schedule, and branch.

• Schedule drug flagging on masters—not only on printed reports
• Prescription capture fields mandatory before bill completion
• Batch number and expiry on each scheduled line
• Branch-scoped registers with headquarters search
• Transfer documentation support between licensed premises
• Export for inspection without manual retyping

Training beats policy binders. New cashiers must practice one Schedule H sale end-to-end—prescription capture, batch pick, register line, print—before solo shifts. Software prompts help; they do not replace the registered pharmacist’s responsibility.

Hospital pharmacies should align with medical records teams on prescription validity and ward orders. Retail chains should align with doctors on accepted prescription formats. Software cannot fix invalid prescriptions; it can stop silent dispensing without documentation.

Keep a single source of truth for the scheduled drug list in your item master. When the gazette updates, update masters before counters open—selling a newly scheduled molecule without flags is an avoidable error.

Inspection rehearsals: pick one week, export Schedule H and H1 lines for every branch, and verify prescription files exist for each line. Fix gaps before an inspector does.

Document retention should include who changed master flags, who approved overrides, and which terminal printed each scheduled bill. When inspectors ask “show me last month,” speed of retrieval signals maturity more than glossy shop fit-out.

Link scheduled drug compliance with FEFO: dispensing the wrong batch for a scheduled line doubles risk—regulatory schedule plus expiry failure. Operators who fix FEFO first often find Schedule H registers easier because batch fields are already mandatory at billing.

Treat Schedule H compliance as ongoing operations, not a one-time SOP PDF. Registers are living evidence—if they are wrong on a quiet Tuesday, they will be wrong on inspection Monday.

If you operate hospital and retail under one brand, keep licence boundaries clear in software—scheduled drug rules apply per licensed premise, not per logo.

Ask software vendors for a sample Schedule H register export before you buy—PDF pretty demos are not the same as filterable audit data your compliance lead can search during prep.

Hayati is designed to support Schedule H flagging in inventory and dispensing workflows; exact configuration depends on your licence category and SOPs—validate during walkthrough with your compliance lead. See pharmacy inventory and FEFO features for batch discipline that supports scheduled drug traceability.