PharmaOS

Retail pharmacy software

Every strip on your shelf has a batch and a date. Your software should know both.

PharmaOS runs the counter, the shelf and the books of a retail pharmacy in Bangladesh. It sells by batch and expiry, keeps the credit ledger, prints a VAT challan, and works in Bangla and English.

The demo carries sample data. Nothing you do in it reaches a real shop.

Near expiry next 90 days
Napa 500 mg tablet 18 days Batch NP-4471 · 240 strips · shelf A1
Seclo 20 mg capsule 41 days Batch SC-9920 · 96 strips · shelf B3
Monas 10 mg tablet 63 days Batch MN-2210 · 30 strips · shelf B1
Fexo 120 mg tablet 88 days Batch FX-1180 · 410 strips · shelf C2

An illustration of one screen, not a real shop's stock.

What it is actually for

Three things cost a pharmacy money quietly, every month, and none of them show up until somebody counts.

Stock expires on the shelf

Because nobody can see which batch is closest to its date. PharmaOS sells the oldest batch first, and tells you what is about to turn while you can still move it.

The credit ledger is a notebook

Half the counter runs on credit. When a customer's dues live in a book, nobody at the counter knows whether to let the next sale go on account.

The books get typed twice

Sales are rung once, then entered again for VAT. Everything PharmaOS prints comes out of the sale that was actually made.

What it does

Written the way the work is done, rather than the way software is usually listed.

At the counter

  • Scan a barcode and the right strip comes up first
  • The oldest batch is picked for you, and you can override it
  • Cash, card, mobile money, or split across them
  • Hold a sale, serve the next customer, come back to it
  • Returns and credit notes against the original sale
  • Receipts in Bangla or English

On the shelf

  • Batch and expiry per product, not one date for everything
  • Shelf locations, so a new hand can find it
  • Low stock and near expiry as lists you can act on
  • Stock takes that record what was counted, not what was assumed

Buying

  • Purchase orders to your suppliers
  • Receive against the order, batch by batch
  • Supplier bills, payments, and what is still owed

Customers

  • Credit limits the counter actually enforces
  • A ledger per customer, with dues and settlements
  • Doctors and prescriptions attached to the sale

The books

  • VAT at 15 percent, and Mushak 6.3 challans
  • Daily sales, and margin by product rather than in total
  • What sold, what did not, and what it cost you

Your staff

  • Roles, so the counter cannot change a price
  • A PIN at the till instead of a shared password
  • Attendance, on the phone already in their hand

How you run it

Two ways, and the software is the same in both.

On our servers

Your shop gets its own address and its own database. We run it, we take a backup every night, and we restore those backups on a rotation to check they work. You need a browser and nothing else.

yourshop.pharmaos.fyi

On your own server

For a pharmacy that would rather its register never left the premises. The same software, on hardware you own, on your own domain, updated when you agree to it.

pharmacy.yourdomain.com

PharmaOS was built alongside a working pharmacy rather than in front of a whiteboard. Their real register came across from the system they had used for years: roughly 26,000 products, with a decade of sales behind them.

That is also why moving your history is a service and not a manual. It is the part most software asks you to do yourself.

See it with your own stock in it

Open the demo first. If it looks like it would suit your counter, send us a backup of what you use today and we will show you your own shop running in it.