Resources

Drug Recall Procedure for Clinic Pharmacies in India: Batch Traceability, Stock Freeze, and Patient Follow-Up

A supplier calls about a recalled medicine batch. The pharmacy has six packs on the shelf, but the inward invoice originally contained twenty. Some tablets were sold as complete strips, some as loose units, and some were dispensed against prescriptions.

In this guide16 sections
  1. 01Treat every alert as a signal to verify
  2. 02Match the exact product and batch
  3. 03Stop dispensing and quarantine affected stock
  4. 04Open one recall case
  5. 05Follow the stated recall classification and level
  6. 06Reconcile the batch quantity
  7. 07Trace where the affected batch went
  8. 08Make patient contact clinician-led and notice-specific
  9. 09Coordinate with the supplier and authorities
  10. 10Record returns and final disposition
  11. 11Keep recall stock states separate
  12. 12Keep every decision attributable
  13. 13Rehearse a mock recall
  14. 14Test the workflow during a software demonstration
  15. 15Questions to ask CliniKite
  16. 16Conclusion

Treat every alert as a signal to verify

A recall may reach the clinic through:

  • A manufacturer or marketing company
  • The pharmacy's supplier or distributor
  • A Central or State Drugs Control Authority
  • A CDSCO public alert or notice
  • A report that a product is not of standard quality
  • A product complaint
  • A patient or clinician reporting an unexpected concern
  • An internal observation involving packaging, appearance, storage, or labelling

The CDSCO publishes drug alerts and information concerning products identified as not of standard quality, spurious, adulterated, or misbranded. Its SUGAM consumer portal also provides a searchable NSQ-drug interface. These are useful official monitoring channels, but a clinic must still verify the exact product, batch, authority, notice, and required action. CDSCO alerts and CDSCO SUGAM consumer information.

Do not search only by medicine name and stop every product with a similar brand. One strength, dosage form, manufacturer, or batch may be affected while another is not.

An internal concern is also not permission to invent a recall classification. Isolate suspect stock, stop using it where appropriate, escalate it through the pharmacy's approved process, and obtain qualified instructions.

Match the exact product and batch

Record the identification details directly from the notice, package, supplier document, and inventory record.

Capture:

  • Brand and generic name
  • Dosage form
  • Strength
  • Pack size
  • Manufacturer
  • Marketing company, when different
  • Batch or lot number
  • Manufacturing date, when relevant
  • Expiry date
  • Product code or barcode
  • Supplier
  • Inward invoice number and date
  • Recall-notice reference
  • Issuing organisation
  • Date and time the clinic received the information

Compare characters carefully. A zero and the letter O, or a one and the letter I, can lead staff to freeze the wrong stock or overlook the affected batch.

A barcode may identify the product without identifying the batch. Do not treat a successful product scan as proof that the batch matches.

Where the package, invoice, and software record disagree, preserve the discrepancy. Do not silently change the inventory entry merely to make it match the recall notice.

Stop dispensing and quarantine affected stock

Once the affected batch is reasonably matched, prevent it from reaching another patient.

The operational response should cover both the software and the physical shelf:

  • Block the batch from prescription-linked and over-the-counter dispensing
  • Remove it from FEFO recommendations
  • Stop transfers and purchase returns until the approved route is confirmed
  • Count the affected physical stock
  • Move it to a secure, clearly labelled quarantine area
  • Preserve any stated storage conditions
  • Restrict access to authorised staff
  • Record who performed the freeze and when

The CDSCO's 2024 recall guideline says retailers should maintain the notice received, stock position, stock-freezing procedure, and return records. It also describes recalled goods being quarantined separately in a secure area pending further decision. CDSCO Recall and Rapid Alert System for Drugs, 2024.

A software block without physical segregation is incomplete. A handwritten quarantine label without a system block is also incomplete because another staff member may still select the batch during billing.

Do not destroy, relabel, or transfer recalled stock unless the applicable notice and authorised process support that action.

Open one recall case

Do not manage the event through scattered calls, sticky notes, and stock adjustments.

Create one recall case with a unique reference number. Link every related action to it.

The case should contain:

  • Product and affected-batch identity
  • Source notice and attachments
  • Recall classification and level, if supplied
  • Date and time received
  • Person who received it
  • Immediate stock-freeze time
  • Physical quantity found
  • System quantity at the time of the freeze
  • Supplier and inward transactions
  • Dispensing and sale transactions
  • Patient or customer follow-up tasks
  • Communications sent and received
  • Stock returned
  • Return acknowledgement
  • Quantity awaiting instruction
  • Unresolved discrepancies
  • Responsible pharmacist or owner
  • Closure decision and date

Preserve the original notice. If a corrected or expanded notice arrives, retain both versions and identify which one is currently active.

The medical-record correction workflow explains the same principle for clinical information: make the current state clear without erasing the history needed to reconstruct what happened.

Follow the stated recall classification and level

The CDSCO guideline describes three recall classes based on relative health hazard and three potential levels: consumer or user, retail, and wholesale.

Its retail-level description includes retail pharmacies, hospital pharmacies, dispensing physicians, clinics, and nursing homes. The guideline also describes Class I recalls extending to consumers, retail, and wholesale; Class II to retail and wholesale; and Class III to wholesale.

The document gives the following system timelines:

  • Class I: stop sale or distribution within 24 hours and complete physical recall within 72 hours
  • Class II: up to 10 days
  • Class III: up to 30 days

These are important regulatory workflow details, but clinic staff should not independently assign a recall class or reinterpret an official notice. Follow the issuing authority's or authorised supply-chain party's instructions and obtain professional guidance where the scope is unclear.

Regardless of classification, record when the clinic received the notice and when dispensing was actually stopped. Do not backdate the freeze to make the response appear faster.

Reconcile the batch quantity

A recall cannot close merely because the shelf is empty.

Build a batch-level reconciliation: Quantity received, minus supplier returns before the recall, quantities dispensed or sold, documented damage or earlier adjustments, and stock transferred out, equals expected quantity on hand.

Then compare the expected quantity with the physical quarantine count.

Account separately for:

  • Complete packs
  • Open packs
  • Strips
  • Loose tablets or units
  • Damaged stock
  • Stock already marked expired
  • Previous patient returns
  • Stock in another cabinet or branch
  • Units whose location cannot yet be explained

Do not force the system quantity to match the physical count using an unexplained adjustment. Record the variance, investigate it, and keep the correction attributable.

This is where pack-to-strip and loose-unit conversion matters. If an inward entry records ten boxes but dispensing records only “quantity 1” without a unit, the clinic may be unable to tell whether one tablet, strip, or box left the pharmacy.

The broader clinic pharmacy software guide explains why batch, expiry, inward, dispense, return, and adjustment records must stay connected.

Trace where the affected batch went

Search dispensing and sales by the exact batch, not only by medicine name.

For every affected transaction, review:

  • Dispensing or sale date
  • Quantity and unit
  • Prescription-linked or over-the-counter status
  • Patient or customer identity available to the clinic
  • Prescribing doctor, where applicable
  • Invoice or receipt
  • Staff member who completed the dispense
  • Contact details recorded at that time
  • Return or cancellation status
  • Whether the transaction was later corrected

Do not assume that the patient associated with the prescription received the entire quantity. Partial dispensing, substitutions, returns, and family collection can change what actually happened.

Keep uncertainty visible. “Batch selected in the software” is different from “confirmed as supplied to the patient.”

A batch trace should use the minimum patient information needed for the approved response. Avoid exporting an unrestricted patient list into a general spreadsheet or sharing it through an unauthorised channel.

Make patient contact clinician-led and notice-specific

A patient-level recall may require communication with people who received the affected batch. That communication should follow the recall notice and the clinic's professional process.

The workflow should distinguish:

  • Patient identified
  • Contact details verified
  • Contact attempted
  • Patient reached
  • Notice explained
  • Clinician or pharmacist review required
  • Replacement or return instructions provided
  • Patient reports medicine already consumed
  • Patient reports a symptom or concern
  • Follow-up completed
  • Unable to contact

Do not let an automated message provide patient-specific treatment advice or tell every recipient to stop a medicine without authorised clinical wording.

If a patient reports illness, lack of efficacy, an adverse event, or uncertainty about continuing treatment, route the conversation to the responsible clinician or pharmacist. Software can create the task and record its outcome; it should not make the clinical decision.

When using WhatsApp or another messaging channel, confirm the number and message category before disclosing medicine information. The CliniKite WhatsApp operations guide provides a broader consent, opt-out, and staff-handoff framework.

Coordinate with the supplier and authorities

The CDSCO recall guideline says distributors, marketing companies, and retailers should communicate their stock position to the immediate supplier or manufacturer and their area Drugs Inspector. The exact route and documentation for a real clinic may also depend on the notice, licence, product, and State authority.

Maintain a communication log containing:

  • Recipient
  • Organisation
  • Date and time
  • Communication channel
  • Person sending it
  • Batch and quantity reported
  • Instructions received
  • Documents attached
  • Next action
  • Due date
  • Acknowledgement or reference number

Do not rely only on a telephone conversation. Record the call and obtain written confirmation where appropriate.

Also distinguish a supplier sales representative from the authorised recall contact. Confirm where stock should be held or returned and who will issue the acknowledgement.

Record returns and final disposition

Returned stock should remain linked to the recall case and affected batch.

Record:

  • Return date
  • Quantity and unit
  • Physical condition
  • Storage condition while held
  • Destination
  • Transport or handover details
  • Supplier acknowledgement
  • Credit note or financial adjustment
  • Quantity still awaiting return
  • Person approving the movement

Do not combine the physical return with an ordinary purchase return if that would erase the recall reason.

The CDSCO guideline describes reconciliation of distributed and recovered quantities and keeping recalled goods quarantined until an authorised disposition decision. WHO good storage and distribution guidance similarly recommends a written recall procedure, segregated and clearly labelled recalled products, accessible distribution records, and a final reconciliation. The WHO document is international guidance, not an Indian legal substitute. WHO Good Storage and Distribution Practices, TRS 1025 Annex 7.

Financial closure is not operational closure. Receiving a supplier credit note does not prove that affected patients were reviewed or that every unit was accounted for.

Keep recall stock states separate

A reliable system should distinguish:

  • Available
  • Near expiry
  • Expired
  • Damaged
  • Returned by patient
  • Purchase return pending
  • Quarantined for investigation
  • Recalled
  • Returned to supplier
  • Destroyed under authorised instruction
  • Unaccounted variance

These states have different meanings and approval requirements.

Changing recalled stock to zero without a movement record destroys the reconciliation trail. Marking it expired can also hide why it was removed from sale.

If the clinic later corrects a quantity, preserve the earlier value, reason, actor, and approval. A recall should not become an excuse to overwrite an unrelated inventory discrepancy.

Keep every decision attributable

Recall activity can involve the pharmacist, owner, doctor, supplier, front desk, and outside authority. Each person needs the information required for their responsibility, not unrestricted access to everything.

The audit history should show:

  • Who created the recall case
  • Who matched the batch
  • Who blocked dispensing
  • Who performed the physical count
  • Who changed a quantity
  • Who viewed or exported a patient trace
  • Who contacted each patient
  • Who released or returned stock
  • Who approved closure
  • Which records were changed after closure

Shared accounts make this evidence unreliable. Use the role-based access guide to define who can freeze stock, adjust quantities, export affected transactions, communicate with patients, and close the case.

Preserve the notice, trace report, communication log, return acknowledgement, reconciliation, and final review according to the clinic's applicable record policy.

Rehearse a mock recall

A clinic should learn whether its records work before a real urgent notice arrives.

Create a synthetic batch and test whether staff can:

  • 1. Find the inward invoice.
  • 2. Block the batch without blocking unrelated batches.
  • 3. Count complete packs and loose units.
  • 4. Identify every dispense linked to the batch.
  • 5. Produce a restricted contact worklist.
  • 6. Record a fictional return.
  • 7. Reconcile received, dispensed, quarantined, returned, and unresolved quantities.
  • 8. Export an understandable recall record.
  • 9. Restore ordinary availability only through an authorised action.

WHO guidance recommends checking recall-procedure effectiveness annually. Treat that as an international quality-system reference, not a declaration that every Indian clinic has the same mandatory rehearsal interval.

Choose a review frequency with the clinic's pharmacist and qualified advisers. Repeat the exercise after material changes to suppliers, branches, inventory software, pack conversion, or staff responsibility.

Test the workflow during a software demonstration

Use fictional data.

Create an inward for 100 tablets across two batches with different expiries. Dispense 37 tablets from the affected batch through three prescription-linked sales and one over-the-counter sale. Include one partial return and one unexplained unit.

Then issue a fictional recall notice for only that batch.

Ask the vendor to demonstrate:

  • Exact batch search
  • Immediate dispensing block
  • Physical quarantine recording
  • Pack, strip, and loose-unit reconciliation
  • Patient and transaction tracing
  • Restricted export
  • Supplier-return recording
  • Credit-note linkage
  • Staff attribution
  • Approval and closure
  • Preservation of the full history

Try to dispense the recalled batch after the freeze. Confirm that another batch remains available.

Finally, export the case and check whether someone outside the application can understand the notice, quantities, actions, unresolved variance, and closure.

Questions to ask CliniKite

CliniKite's public feature page describes prescription-linked and over-the-counter dispensing, FEFO recommendations, batch numbers, expiry dates, pack and loose-unit sales, inwards, suppliers, returns, adjustments, statutory registers, role-based access, audit logs, backups, and exports. CliniKite features.

These capabilities provide relevant recall context. They do not, by themselves, establish automatic CDSCO-alert matching, recall classification, authority reporting, automated patient outreach, or a complete recall module.

During a demonstration, ask:

  • Can one batch be blocked without blocking the medicine?
  • Does the block cover prescription and over-the-counter dispensing?
  • Can the system reconcile boxes, strips, and loose units?
  • Can staff find every sale associated with a batch?
  • How are patient returns recorded?
  • Can recalled stock remain physically and digitally quarantined?
  • Are recall returns separate from ordinary purchase returns?
  • Who can adjust the recalled quantity?
  • Does the audit history show old and new values?
  • Can patient trace reports be restricted by role?
  • Can communication attempts and outcomes be recorded?
  • Can the recall notice and supplier acknowledgement be attached?
  • Can the clinic export the complete case?
  • Do backups preserve earlier recall states?
  • Which parts of the workflow remain manual?

Ask for the answers to be demonstrated with synthetic data.

Conclusion

A dependable drug recall procedure begins with exact batch identification, not a broad medicine search.

Freeze the affected stock in the system and on the shelf. Preserve the notice, reconcile complete packs and loose units, trace relevant dispensing, follow authorised communication instructions, and record every supplier, patient, return, and closure action.

The strongest test is reconstruction. After the event, the clinic should be able to explain what arrived, what was dispensed, what was quarantined, what was returned, what remains unresolved, and who made each decision.

Evidence used

Sources and claim notes

  • CDSCO Recall and Rapid Alert System for Drugs, 2024

    Supports the descriptions of recall scope, classes, levels, timelines, retailer responsibilities, stock freezing, records, quarantine, returns, and reconciliation.

  • CDSCO alerts

    Supports the statement that CDSCO publishes drug, NSQ, spurious-product, and related alerts. An alert is treated as a verification source, not automatically as a complete instruction for every clinic.

  • CDSCO SUGAM consumer information

    Supports the availability of the official NSQ-drug search interface.

  • CDSCO Drugs Rules repository

    Provides the official current repository for the Drugs Rules and amendments. The article does not attempt to restate every applicable licence condition.

  • WHO Good Storage and Distribution Practices, TRS 1025 Annex 7

    Supports the international quality-system discussion of written recall procedures, segregation, records, reconciliation, and effectiveness checks.

  • WHO policy paper on medical-product traceability

    Supports the general role of product identification, production identification, data capture, and exchange in traceability systems.

  • CliniKite features

    Supports only the stated public descriptions of batch-aware dispensing, FEFO, pack and loose-unit sales, inwards, suppliers, returns, adjustments, roles, audit logs, backups, and exports.

  • CliniKite security and data

    Supports the proposed questions about access, attribution, exports, backups, deployment, and connected-service boundaries.

A useful next step

Test a batch recall in a CliniKite demonstration

Bring the real clinic workflow, current plan and people who run the day. We will show the connected path and its limits clearly.

This article provides general clinic-pharmacy operations, software-evaluation, inventory-control, information-governance, and recall-readiness guidance. It is not medical, pharmaceutical, legal, regulatory, licensing, pharmacovigilance, patient-safety, disposal, or professional advice. Follow the applicable recall notice and obtain instructions from authorised regulators, suppliers, pharmacists, clinicians, and qualified advisers for the specific product, batch, patient, and jurisdiction.