Running a pharmacy in Pakistan in 2026 is no longer a question of stocking medicines and operating a cash drawer. It is a regulated operation overseen by the Drug Regulatory Authority of Pakistan (DRAP), the Federal Board of Revenue (FBR), provincial health departments and — for any pharmacy above the FBR e-invoicing threshold — a digital reporting regime that demands every sale be transmitted to the government in real time. A general-purpose POS, no matter how slick its interface, cannot keep your pharmacy on the right side of any of these regimes.
This guide is the practical compliance playbook we wish every pharmacist had before they shortlisted POS software. We cover the three legal regimes a Pakistani pharmacy must satisfy in 2026 — DRAP, FBR and prescription tracking — and translate each into the exact features your pharmacy POS software in Pakistan must provide. We then map those features to a buyer’s checklist, show what EloERP Suite does out of the box, and finish with a 30-day implementation roadmap.
This is a pillar resource for our pharmacy industry vertical. If you are deciding between systems, also read our complete guide to pharmacy inventory management and our 2026 ranking of the top 10 cloud POS in Pakistan.
The Three Regulatory Regimes a Pakistani Pharmacy Must Satisfy
Before any feature discussion, it is worth seeing the regulatory map at one glance. A Pakistani pharmacy in 2026 has obligations to three different authorities, and each one is enforced separately. Failing one does not insulate you from the others.
- Drug Regulatory Authority of Pakistan (DRAP) — administers the Drugs Act 1976, the DRAP Act 2012 and the Drug Sale Rules. Controls who can sell what, batch traceability for recalls, expiry handling, and the schedules under which controlled substances must be dispensed.
- Federal Board of Revenue (FBR) — administers the Sales Tax Act 1990 and the e-invoicing regime under SRO 1525(I)/2023 and its 2024–2026 amendments. Pharmacies above the registration threshold must integrate with the PRAL (Pakistan Revenue Automation Ltd.) e-invoicing platform.
- Provincial Health Departments and Pakistan Medical Commission — enforce prescription rules, the licensing of pharmacists and the requirement that prescription-only medicines (POMs) be dispensed against a valid prescription with a documented patient record.
A compliant pharmacy POS is the single tool that can keep all three regimes satisfied without manual paperwork. Below, we break down what each regime requires and translate that into a feature spec for your software.
1. DRAP Compliance: What Your POS Must Track
DRAP is the regulator most pharmacy owners think about first, and rightly so. DRAP inspections — both scheduled and surprise — focus on what you stock, how you stock it, and how you sell it. A POS that cannot answer DRAP’s questions in seconds is a liability.
1.1 DRAP Registration Tracking
Every medicine sold in Pakistan must carry a DRAP registration number, granted under Section 7 of the Drugs Act 1976. Your POS should store the DRAP registration number against every SKU and surface it on receipts and stock cards. If DRAP issues a recall, you must be able to filter your inventory by registration number in seconds, not hours.
POS feature requirement: A dedicated DRAP Registration No. field on the medicine master, searchable in reports and printable on receipts and audit logs.
1.2 Schedule G, H, X and Controlled Substances
Pakistani drug law classifies medicines into schedules. Schedule G drugs require pharmacist supervision; Schedule X (narcotics, psychotropics) and certain Schedule H drugs require a separate dispensing register with patient name, prescriber details, prescription number, and quantity dispensed. The 1976 Act makes the pharmacy personally liable for unaccounted Schedule X stock.
POS feature requirement: A schedule flag on every SKU. When a Schedule X or controlled-substance item is added to a sale, the POS must (a) require the cashier to enter prescription and prescriber details, (b) write a row to a separate dispensing register, and (c) refuse to complete the sale without those fields.
1.3 Manufacturer Batch Numbers
DRAP-mandated recalls operate at the batch level, not the SKU level. If a manufacturer recalls batch L-23H-8821 of a paracetamol product, you must know exactly how many units of that batch you sold, to whom (where prescription was attached), and how many remain. A POS that does not capture batch number at goods-receipt and propagate it through every sale is a recall nightmare.
POS feature requirement: Batch-level inventory tracking. Each purchase receipt creates a distinct batch record (with batch number, manufacturing date and expiry). Every sale deducts from a specific batch (FEFO recommended). A recall report can isolate one batch and trace every sale.
1.4 Expiry Date Handling
Selling expired medicine is a criminal offence under the Drugs Act 1976 and is one of the most common findings in DRAP inspections. The pharmacy POS must (a) block sale of any batch that has crossed its expiry date, (b) issue a 60-day expiry warning to the manager dashboard, and (c) produce a monthly expiry write-off report for audit and accounting.
POS feature requirement: First Expiry, First Out (FEFO) dispensing as the default, with hard blocks on expired stock and configurable alerts at 90/60/30 days to expiry.
1.5 Cold Chain and Storage Conditions
Insulin, vaccines and biologics must be kept at 2–8°C. DRAP inspectors increasingly ask to see refrigerator temperature logs alongside sale records. A modern pharmacy POS can integrate with Bluetooth temperature loggers and store the temperature trail alongside the relevant batches.
POS feature requirement: An optional cold-chain flag per SKU and the ability to log or import temperature data linked to the storage period. This is a “nice to have” for small pharmacies and an “absolute requirement” for any pharmacy that dispenses Hep-B vaccines, insulin or oncology biologics.
2. FBR Sales Tax Invoicing: The 2026 Reality
The second regulatory regime is FBR. In 2023, FBR notified SRO 1525(I)/2023, which mandated real-time digital invoicing for Tier-1 retailers — including pharmacies — through PRAL’s e-invoicing platform. By 2026, the threshold has been extended to additional pharmacy categories. A non-integrated pharmacy can be fined under Section 33 of the Sales Tax Act and lose input tax credit on its purchases.
2.1 PRAL E-Invoicing Integration
Under the 2026 regime, an FBR-registered pharmacy must transmit each sale to the PRAL e-invoicing service and print the returned IRN (Invoice Reference Number) and QR code on the receipt. The QR code lets any customer verify the invoice on the FBR Tax Asaan app — a credibility signal that real shoppers now look for.
POS feature requirement: Native integration with the PRAL POS Integration Service. Each completed sale must call the PRAL API, store the IRN and QR payload, and reprint the receipt with both. Retries on network failure must be transparent to the cashier — the customer should never wait at the counter for an FBR roundtrip.
2.2 GST Exempt vs Taxable Medicines
Not every medicine is taxed the same way. The Sixth Schedule of the Sales Tax Act exempts most life-saving drugs, while many over-the-counter products carry the standard 18% rate. Vitamins, nutraceuticals and certain dermatological products often attract 17–18% sales tax. A pharmacy POS must hold the correct tax rate per SKU and split the invoice line accordingly.
POS feature requirement: Per-SKU tax-rate configuration with at least three categories — exempt, reduced, standard — and clear tax breakdown on the receipt. Mass-update tools to reclassify SKUs when FBR notifies a schedule change.
2.3 Sales Tax Returns (Annexure C)
Monthly sales tax returns require Annexure C — the supply register — and Annexure A for purchases. Pulling these from a manual spreadsheet on the 18th of every month is the leading cause of late-filing surcharges for pharmacies. A compliant POS should export Annexure C in PRAL’s expected format with one click.
POS feature requirement: Built-in Annexure A and Annexure C exports in the exact CSV format that PRAL accepts, with date-range and tax-rate filtering.
2.4 Withholding Tax on Pharmaceutical Purchases
Under Section 153 of the Income Tax Ordinance, pharmacies above a certain turnover threshold must withhold tax on payments to suppliers and deposit it via the CPR (Computerised Payment Receipt) system. The POS should track these obligations against each supplier ledger so your accountant can issue CPRs on time.
POS feature requirement: Per-supplier withholding tax configuration and a withholding-payable report at month-end.
3. Prescription Tracking: The Third Pillar
Pakistan’s prescription regime is loosely enforced compared to the EU or UK, but the legal obligations remain — and provincial health departments have been tightening enforcement, especially after the 2024 push to reduce antibiotic resistance. A compliant POS makes the difference between an inspection with a clean record and one that ends in a sealing notice.
3.1 Prescription-Only Medicines (POMs)
Any medicine listed in Schedule G or marked “Pharmacy-only — Caution: To be sold by retail on the prescription of a Registered Medical Practitioner” must not be dispensed without a valid prescription. In practice, antibiotics, antihypertensives, antidiabetics, antipsychotics and many cardiovascular drugs fall into this group.
POS feature requirement: A POM flag per SKU. When a POM is added to a sale, the cashier must capture prescriber name, prescription number and patient identifier before the sale will close. A scanned image of the prescription, attached to the sale, is the gold standard.
3.2 Refill Limits and Dispensing Frequency
Many chronic-medication prescriptions explicitly limit refills (for example, three months of supply, two refills). A modern pharmacy POS should track refills per patient and flag the cashier if a refill is being attempted outside the prescribed window.
POS feature requirement: Patient master with prescription history, refill counter, and a configurable rule that warns the cashier when a refill is being dispensed earlier than the prescribed interval.
3.3 Pharmacist Authentication
Schedule G and Schedule X dispensing must be done by, or under direct supervision of, a registered pharmacist. The POS should capture which pharmacist authorised the sale. In a multi-cashier pharmacy, the system should require a pharmacist’s PIN or fingerprint on the controlled-substance dispense screen even when the cashier transacting the sale is a counter assistant.
POS feature requirement: Multi-level user permissions with a “pharmacist override” prompt on scheduled-drug sales. Audit log preserves which pharmacist authorised what, when.
4. The Controlled Substances Register
The Control of Narcotic Substances Act 1997 governs narcotic and psychotropic substances. Pharmacies dispensing these must keep a register — historically a hand-written ledger — recording every inward and outward movement. Provincial inspectors routinely demand to see this register, and the gap between a tidy register and a chaotic one is the difference between a clean inspection and a sealing order.
POS feature requirement: Auto-generated, tamper-evident narcotics register tied to inward purchase receipts and outward dispenses. Each entry captures date, drug, batch, quantity, prescription, prescriber, patient and authorising pharmacist. Daily, monthly and on-demand exports must be available as PDF.
5. The Compliance Feature Checklist
Stitching the three regimes together produces a single checklist you can use when evaluating any pharmacy POS in Pakistan. Print this list and walk through it with the vendor’s sales engineer; insist on a live demo of every item before signing a contract.
- DRAP registration number field per SKU, searchable and printable.
- Schedule classification per SKU (G, H, X, K, narcotic).
- Manufacturer batch tracking — every receipt creates a batch; every sale deducts from a specific batch.
- FEFO dispensing by default with hard block on expired stock and 90/60/30-day alerts.
- Cold-chain temperature logging support (optional but recommended).
- Native FBR PRAL e-invoicing with IRN + QR on every receipt.
- Per-SKU tax classification (exempt / reduced / standard) with mass-update tools.
- Annexure A and Annexure C exports in PRAL CSV format.
- Withholding tax tracking per supplier.
- POM (prescription-only) workflow capturing prescriber, prescription number, patient.
- Refill rules per patient with early-refill warnings.
- Pharmacist authentication for scheduled-drug sales.
- Auto-generated narcotics register with tamper-evident audit log.
- Recall report by batch number — every sale of an affected batch surfaced in one click.
- Multi-branch consolidation if you run more than one outlet, with per-branch DRAP licence reference.
- Offline mode — the POS must keep selling during internet outages and reconcile with FBR when connectivity returns.
6. How EloERP Suite Handles Pharmacy Compliance
EloERP Suite was built with the Pakistani pharmacy market as a primary use case, not a bolt-on. Every item on the checklist above is supported out of the box, and the pharmacy module is included in the standard Cloud Business plan at PKR 9,500 per month per outlet.
- DRAP-aware product master. The medicine SKU template includes DRAP registration number, schedule, generic name, manufacturer, strength and pack size as first-class fields. Bulk import from your existing supplier price list is a 10-minute task.
- Batch-and-expiry tracking by default. Every purchase invoice creates a batch record. Sales deduct from the oldest unexpired batch (FEFO). Expired stock cannot be sold, and the expiry dashboard surfaces every SKU within 90 days of expiry.
- Native PRAL FBR integration. EloERP Suite is listed on the FBR-approved POS integrator panel. Every completed sale is transmitted in real time, the IRN and QR are printed on the receipt, and Annexure C is one click away on the 18th of every month.
- Prescription workflow. When a POM is scanned, the cashier interface prompts for prescriber, prescription number and patient. The optional prescription-image attachment lets staff snap a photo of the doctor’s prescription and store it against the sale.
- Pharmacist override. Schedule X and narcotic sales require a pharmacist PIN before the transaction closes, regardless of which cashier is at the counter. The audit log preserves who authorised every controlled-drug dispense.
- Narcotics register. A separate, tamper-evident register populates automatically from inward and outward movements. PDF export is available daily and monthly; inspectors can be handed a printed register on demand.
- Recall reports. The “Trace Batch” report takes a batch number and returns every purchase, every sale and every remaining unit — in under five seconds even on multi-year history.
- Offline mode. The cashier interface continues to operate through power and internet outages. Sales queue locally and sync to FBR when connectivity returns.
- Urdu cashier UI. Counter staff who are more comfortable in Urdu can switch the interface — useful in neighbourhood pharmacies where pharmacist-only English is a barrier.
- Pakistani support. Phone, WhatsApp and on-site engineers in Karachi, Lahore, Islamabad and Faisalabad during PKT business hours.
7. A 30-Day Compliance Implementation Roadmap
Pharmacy POS implementation is not a one-day swap. The roadmap below has been used successfully by EloERP Suite customers running single-shop and chain pharmacies, and it isolates compliance work into the first 30 days so the new system stands up cleanly against any inspector who walks in during go-live.
Week 1: Data and Licence Audit
- Export the existing medicine master to Excel. Add a column each for DRAP registration number, schedule and tax rate, and complete the data for the top 200 SKUs by volume.
- Locate and digitise your pharmacy DRAP licence, FBR registration certificate, NTN and sales tax registration. These will be referenced by the POS during setup.
- Identify the pharmacist (or pharmacists) who will authorise scheduled-drug sales. Create their user accounts in the POS with the pharmacist role.
Week 2: System Configuration
- Import the cleaned medicine master into EloERP Suite. The system will warn on any SKU without a DRAP number or tax classification.
- Configure FBR PRAL integration. EloERP Suite’s onboarding engineer will guide you through the PRAL portal registration if you have not already integrated.
- Set up cold-chain SKUs and link them to a Bluetooth temperature logger (optional but recommended for vaccine-stocking pharmacies).
Week 3: Staff Training and Dry Run
- Train cashiers on the POM workflow — including the case where a customer asks for an antibiotic without a prescription.
- Train at least one pharmacist on the Schedule X dispensing flow and narcotic register exports.
- Run a one-week dry-run with the new system in parallel to the old: every sale is rung up in both systems, and the totals reconciled at end of day.
Week 4: Go-Live and First Inspection Pack
- Cut over fully to the new POS. Decommission the old system at the start of business on go-live day.
- Print the first FBR-compliant receipt and verify the QR code resolves correctly on the Tax Asaan app.
- Print the first weekly narcotic register and file it as the new compliance baseline.
- Run the first Annexure C export and confirm the totals match your sales tax return.
Customers who follow this roadmap typically pass their first post-implementation DRAP and FBR checks without findings. The system does the compliance work; the staff only need to follow the prompts.
8. Recommended Next Step
If you are evaluating pharmacy POS software in Pakistan in 2026, do these three things before signing a contract:
- Run a live FBR PRAL test in front of you. Ask the vendor to ring up a real sale and show the IRN and QR returning from PRAL on the receipt. A vendor who cannot do this on demand is not compliant in 2026.
- Demand a controlled-substance demo. Have the vendor add a Schedule X item to a sale and walk through the prescription, pharmacist authentication and register generation. This is where weak products fall apart.
- Visit an existing pharmacy customer. Every credible Pakistani pharmacy POS vendor in 2026 can introduce you to a live customer. Vendors who cannot should not be on your shortlist.
If you would like to start with EloERP Suite, you can book a free pharmacy demo. Bring your existing medicine master CSV and a sample week of sales — we will show you the full DRAP-compliant, FBR-integrated, prescription-tracked sale cycle on your own data inside 30 minutes.
Frequently Asked Questions
Is FBR e-invoicing mandatory for pharmacies in Pakistan in 2026?
For pharmacies registered as Tier-1 retailers under SRO 1525(I)/2023 and its 2024–2026 amendments, real-time PRAL e-invoicing is mandatory. Smaller pharmacies below the turnover threshold are not yet required to integrate, but FBR has signalled a phased extension and many pharmacies are integrating early to avoid the inevitable cutover.
What is a DRAP registration number and where do I find it?
A DRAP registration number is the unique identifier DRAP assigns to every registered medicine under Section 7 of the Drugs Act 1976. It is printed on the manufacturer’s pack and listed on the DRAP website. Your POS should capture this number against every SKU so that recalls can be processed instantly.
Does my POS need to print prescription details on the receipt?
For prescription-only medicines, yes. The receipt should reference the prescription number, the prescribing doctor’s name and the dispensing pharmacist’s name. The full patient prescription is stored on the system and can be retrieved on demand.
Can I use a general retail POS in my pharmacy if I print the DRAP number on the receipt?
You can dispense over-the-counter items that way, but the moment you sell a Schedule G, H or X drug you are exposed. A general retail POS does not capture prescriber details, does not maintain a narcotic register, and does not enforce pharmacist authentication. DRAP and provincial inspectors increasingly fine pharmacies for these gaps.
How does FEFO (First Expiry First Out) work in practice?
FEFO means the POS automatically deducts from the batch closest to expiry first. If you have three batches of paracetamol — one expiring in March, one in June, one in December — every sale will deduct from the March batch until it is exhausted. This minimises expiry write-offs and is the only legally defensible dispensing order.
How much does compliant pharmacy POS software cost in Pakistan in 2026?
For a single-outlet pharmacy, expect to budget PKR 4,500–10,000 per month for a cloud POS that covers DRAP, FBR and prescription tracking properly. Add a one-time PKR 25,000–50,000 for PRAL onboarding if the vendor charges separately. EloERP Suite’s Cloud Business plan at PKR 9,500 per month per outlet includes all three regimes with no additional onboarding fee.
Can the POS handle multi-branch pharmacies with separate DRAP licences?
Yes — and it must, if you operate more than one branch. Each branch carries a separate DRAP licence and FBR registration, and the POS should hold both, default the correct values per branch, and consolidate reporting upward for the parent business. EloERP Suite’s Enterprise plan supports unlimited branches with central management.
What happens if my pharmacy POS is offline during a sale and FBR cannot be reached?
A properly designed POS queues the transaction locally and submits it to PRAL as soon as connectivity returns, all within the SRO-permitted retry window. The customer’s receipt prints with a “pending IRN” reference; the final IRN is then attached on retry. EloERP Suite handles this transparently. International POS products without Pakistan-specific offline handling typically fail this scenario.
Does the POS help with my monthly sales tax return?
Yes — a compliant pharmacy POS produces Annexure A (purchases) and Annexure C (sales) exports in the exact CSV format that PRAL accepts. Your filing on the 18th of every month becomes a one-click upload rather than a multi-day reconciliation exercise.