The counter, the shelf and the ledger in one workspace — point of sale, FEFO dispensing, batch and expiry control, and a regulatory trail that writes itself.
Twelve pharmacy screens across ten sections, in four parts — from the moment stock is received to the moment the sale lands in the general ledger.
One unbroken line becomes a capsule, takes its seal, and ends in a point of light — supply, dose, record, handover.
Stock arrives. Nothing has been dispensed yet.
The dose takes form — an item, a batch, a price.
Batch, expiry and control are written onto it.
Dispensed, witnessed where the law asks, and posted.
Most pharmacy software sells, then exports a file for the accountant. Web Pharmacy is a pharmacy-shaped surface over one shared accounting core — the sale, the stock movement and the journal entry are the same event, written once.
Every browser call carries an X-Product-Scope header, so the database tags the invoice and the journal entry as the pharmacy's. Warehouses are filtered to the pharmacy scope — a pharmacy drug cannot be dispensed from another product's store.
Balance, available, batches, expiry, cost, supplier, barcode and drug attributes — with FEFO dispensing off the batch, not off a stock figure.
HR and payroll are deliberately not forked. They stay at establishment level and open inside the pharmacy shell, because a pharmacy is not a separate legal entity with a separate payroll engine.
A pharmacy-only permission set, isolated from the clinic's. A server guard runs before any data loads and mirrors a database guard on every write — typing the URL directly does not get you in.
The pharmacy counter runs on the platform's shared POS engine — sessions opened and closed, cash in and out, credit sales, receivable collection and a shift summary. Nothing about the money is a separate spreadsheet.
Open a session, sell against it, take payments in and out, then close it and read its summary — the till is part of the accounting system, not a drawer.
Sell on account and collect against the receivable from the same screen, both posting to the ledger.
Every call from the browser carries the pharmacy scope, so the invoice and its journal entry are the pharmacy's from the moment they exist.
A prescription here is a retail record, not a clinical encounter: a customer, the prescriber's name, the drugs, an image of the script — and dispensing that draws from the correct batch by FEFO.
Dispensing takes the batch that expires first, so the shelf empties in the order it should.
An image of the prescription is stored against the record, so the paper and the movement are one thing.
A prescription containing a controlled substance cannot be dispensed without a witness — a member other than the dispenser. The check is enforced in the database, not only in the screen.
Medicines are managed as real inventory: balance and available, batches with their expiry, cost, supplier, barcode and drug attributes, with low, out, near-expiry and expired surfaced as they happen.
Shortages are read as on-hand below reorder point; expiry is read per lot. Both are dedicated screens, not a badge somewhere.
Balances, stocktake, adjustments, transfer between warehouses, and valuation with cost — the standard engine, scoped to the pharmacy.
Purchase invoices, returns, orders and requisitions sit in the same shell, so receiving stock and paying for it are one flow.
For every drug classified as narcotic, psychotropic or otherwise controlled: an opening balance and every movement in and out — with date, batch, reference, the responsible person and a running balance. Derived from stock movements, so it cannot drift from what actually happened.
The register is derived, not typed. There is no screen where a number in it can be edited into agreement.
It prints through the platform's isolated report engine, so what you hand an inspector is generated from the same rows.
Near-expiry and expired lots are surfaced continuously beside shortages, so stock is written off deliberately rather than found.
The pharmacy reports its own profitability inside its own scope, on top of the platform's full statement set — trial balance, income statement, balance sheet and cash flow.
The pharmacy-scope figure is an internal management number. The establishment return is what is actually filed, against one tax registration. They are two separate items because they are two different things.
The dashboard's numbers come from actual sales, with the organisation's real currency symbol — not a hardcoded one, and never a blank where a value is missing.
No chat box bolted onto a database. Three deterministic engines run where a pharmacy actually loses money — buying blind, letting stock expire, and losing controlled substances. None needs an external AI provider or an API key, so nothing leaves the system to produce them.
Forecasts what to stock from the clinic's upcoming appointments — visit type against what was historically dispensed for that type — rather than from last month's sales.
This is not better accuracy. It is information from the future, available only to someone who owns the clinic and the pharmacy in one tenant.
A visit type below the minimum sample is excluded and named. Every row carries how many upcoming and how many historical visits it rests on.
Predicts waste at the batch level and recommends a graduated discount as expiry approaches — tying a pricing decision to a logistics event with an accounting consequence.
Expiry is a write-off that was visible for months. Pricing against it turns a loss into a margin decision.
Batches without a usable sales rate are reported as such rather than discounted on a guess.
Flags abnormal controlled-substance dispensing as patterns — prescriber against drug against frequency — instead of reacting to single large amounts.
Diversion does not look like one big number. It looks like a normal number, repeated.
Below a minimum number of distinct prescribers there is no basis for a pattern, and the engine says so instead of returning a clean zero.
All three are deterministic and produce recommendations for a pharmacist — never an automatic decision.
Separation here is structural, not a setting.
Pharmacy resources are a separate namespace from the clinic's, so access to one grants nothing in the other.
A server-side guard runs before any data loads, mirroring a database guard on every write.
Reads go through pharmacy-scoped procedures; browser calls carry the product scope so writes are tagged at the database, not the UI.
Personally identifying details on parties live in a separate identity table behind stricter permission than the party record itself.
Described from the product's own access-control implementation. No compliance certification is claimed.
Web Pharmacy is one product in the Web Mister AI family, forked from the clinic pack and sharing its accounting core. That shared core is exactly why a clinic's upcoming appointments can tell the pharmacy what to buy — and why a dispensed item moves stock and posts revenue in one action.
Web PharmacyAccountingClinicRestaurantSalonHotelSchoolHuman resourcesProducts listed are verticals present in the platform. Web Pharmacy is the product described on this page.
The fastest way to judge Web Pharmacy is to follow one box of stock — received, batched, sold, and posted.
