Skip to content
EncryptTechBD
Home Industries Our Work Blog Pricing About Contact Discuss Your Project
বাংলা (BN)
Industry Playbooks 6 min read

Pharmacy inventory and POS integration: problems and fixes

Why pharmacy stock drifts from the shelf, why expiry losses appear late, and how to fix batch, unit and sync problems at the counter.

E
EncryptTechBD · 0 comments
Cranes above a building under construction
Photo: 贝丽儿 NG / StockSnap

A pharmacy counter is a harder integration target than a retail till. The same product may be sold as a strip, a box or a carton. Every unit carries a batch number and an expiry date. Purchase prices move, suppliers take back short-dated stock, and some items cannot be sold without a prescription. A POS that only knows the product name and a selling price will drift from the shelf within weeks.

This guide covers the problems that appear most often when a pharmacy connects inventory software to a point-of-sale system, and the fixes that hold up under daily use. It is written for the owner or manager who signs off on the system, not only for the developer building it.

What makes pharmacy stock different

  • Batch identity. Two boxes of the same medicine are not interchangeable if one expires in March and the other in September.
  • Unit conversion. Purchases arrive in packs; sales leave in strips or single tablets. The conversion must be exact and visible.
  • Expiry and recall. Stock must be traceable to a batch so it can be quarantined or returned.
  • Price changes. Purchase rates and MRPs change, sometimes mid-stock. The POS needs an effective date, not an overwritten number.
  • Controlled and prescription items. Some sales need a prescription reference and a named dispenser.

Problem 1: The system says stock exists, the shelf says otherwise

Likely causes: sales posted only when the POS is online; loose-unit sales recorded as full packs; transfers between branches not recorded; returns put back without a batch; stock adjustments made directly in the database.

Fix: make every stock movement an event with a type, quantity, batch and user. Give the POS an offline queue that replays sales with an idempotency key, so a reconnect does not double-post. Add a unit-of-measure table and force the counter to choose the selling unit. Run a weekly cycle count on the fastest-moving lines rather than an annual full count.

Problem 2: Expiry losses are discovered too late

Likely causes: expiry stored on the product record instead of the batch; no first-expiry-first-out rule; short-dated goods accepted at receiving; no quarantine location.

Fix: store batch number, expiry date and quantity on every receipt. Make first-expiry-first-out (FEFO) the default picking rule. Configure alerts at 180, 90 and 30 days, but send them to a person, not only to a dashboard. Create a quarantine bin so expired or recalled stock cannot be sold while it waits for supplier return or disposal. Record the destruction or return with a witness and a document reference.

Problem 3: The counter charges the wrong price

Likely causes: the POS keeps its own price list; purchase price updates do not flow to the shelf price; discounts are applied as free text; old stock keeps an old MRP.

Fix: keep one price master with an effective date and an audit trail. Let the POS read the price, not maintain it. Treat discounts as rules with a reason code and an approval limit. When a supplier changes a rate, the new price should apply to new receipts while the existing batch keeps its recorded cost, so margin reporting stays honest.

Problem 4: Purchase entries do not match the supplier invoice

Likely causes: goods received in one screen and the invoice entered in another; free quantities ignored; trade discounts posted as negative lines; returns netted manually.

Fix: receive against a purchase order, scan the batch barcode, and match quantity and cost before the invoice is approved. Post free quantity as a separate line so the true cost per unit is visible. Keep supplier returns as their own document, linked to the original receipt and batch. A three-way match between order, receipt and invoice prevents most payment disputes.

Problem 5: Refunds break the stock record

Likely causes: refunds processed as a negative sale without a batch; returned medicine put straight back on the shelf; no reason code.

Fix: make the refund reference the original sale line and batch. Route returned stock to a quarantine location until someone confirms the pack is intact and within expiry. Use reason codes such as wrong item, damaged pack, customer return and supplier return. Only the last one should create a payable adjustment.

Problem 6: Prescription items are dispensed without a check

Likely causes: no field for the prescription; any user can override; no record of who dispensed.

Fix: mark restricted items in the product master, require a prescription reference and dispenser identity, and log overrides with a reason. Role permissions should be enforced at the server, not hidden in the POS screen. Review the override report weekly.

Problem 7: POS totals disagree with accounts

Likely causes: transaction date versus settlement date; card and MFS fees; rounding; refunds posted in a different period.

Fix: close the till daily and reconcile tender by tender. Store the provider's settlement reference on the payment, not only the sale. Post fees to their own ledger line. Investigate any difference the same day, while the cashier still remembers the transaction.

Problem 8: The POS slows down at peak hours

Likely causes: every screen calls the central server; large product searches; synchronous stock checks; no local cache.

Fix: cache the catalogue locally, batch the sync, and make stock checks asynchronous where the business can tolerate it. Keep a documented offline mode with a clear reconciliation step. Test the system at peak volume before rollout, not after.

Diagnostic sequence

  1. Pick ten fast-moving products and compare shelf, POS and inventory reports.
  2. Trace one sale and one purchase end to end, including batch and unit conversion.
  3. List every manual adjustment made in the last month and who made it.
  4. Check offline behaviour by disconnecting the POS for an hour in a test environment.
  5. Reconcile one day of cash, card and MFS settlements against the till.

Metrics to watch

  • Stock accuracy on a sample of fast-moving lines.
  • Value of stock expiring within 90 days.
  • Unmatched purchase receipts older than seven days.
  • Refunds without an original sale reference.
  • Daily till variance by cashier.

Where this fits in our work

Pharmacy integration is usually a custom-software problem because the batch, unit and prescription rules are specific to the business. Our Custom Software & Integrations division builds these workflows around the systems you already run; the pricing page explains how scope is set. For a wider comparison of inventory options, read inventory management software compared.

Sources

Services that deliver this

Want this implemented properly?

Pricing →

Every engagement starts with a written scope. If a requirement is outside it, we quote it separately before starting.

Responses (0)

No comments yet. Add the first one below.

Leave a response

Your email address will not be published. Required fields are marked *.

Keep reading

More field notes