Pharmacy Software: Stock, Expiry and Prescriptions
Choose pharmacy software with tests for batch expiry, prescriptions and stock. Compare ready-made and custom options with a labeled first-year budget.
Pharmacy software should tell you three things at the counter: which batch of a product you hold, when it expires, and which prescription a dispensed item belongs to. If those records drift apart, a clean sales report will not explain the expired stock on your shelf. This guide gives you a testable buying process for an Indonesian apotek.
I’m Aditya S, Business Development Manager at Synetica, a tech-based business consultancy combining strategy and execution for Dreamers and Growing Businesses. Everything below uses fictional fixtures you can replay in a demo. I am not citing Synetica pharmacy clients, ranking products I have tested, or giving clinical or legal advice.
You’ll follow one batch-tracked sale and one partly filled prescription, compare features by pharmacy size, assign four controls, and run ten acceptance tests. Then we’ll compare a ready-made package, a small integration and a custom core on the same first-year scope.
TL;DR — the whole guide in five lines
- Track stock by batch and expiry: a total count cannot tell you which box to sell first.
- Link every dispensed item to its prescription: a partly filled prescription needs a visible balance.
- Keep reservation, dispensing and payment separate: each answers a different question.
- Buy a package that passes your exceptions: custom development needs a measurable gap.
- Confirm regulatory duties with your pharmacist-in-charge and the authority: software supports compliance; it does not replace it.

What problems should pharmacy software solve?
Start the demo with one sale whose arithmetic you can check. My fixture is fictional: product A has two batches. Batch X has 6 strips and expires on 2027-01-31. Batch Y has 20 strips and expires on 2027-06-30. A customer buys 8 strips at an assumed IDR 12,000 each. These are test numbers, not market prices or a product recommendation.
Selling the earliest-expiring stock first (often called FEFO, first expired, first out) takes 6 strips from batch X and 2 from batch Y. Batch X falls to zero, batch Y to 18, and the receipt totals IDR 96,000. Reprinting that receipt must not deduct stock again.
Open the batch diagram at full size.
Now add a prescription. R-201 asks for 20 units of fictional product B, but only 10 are on hand. The pharmacist dispenses 10 and the record keeps 10 outstanding. Marking the prescription “done” at that point would hide an open obligation.
| Event | Stock record | Prescription / money record |
|---|---|---|
| Sell 8 strips of A | X: 6 → 0; Y: 20 → 18 | Receipt 96,000 |
| Receive R-201 for 20 of B | No stock movement yet | Requested 20 |
| Dispense 10 of B | On hand 10 → 0, linked to R-201 | Dispensed 10; outstanding 10 |
| Receive 10 more of B | Stock in with batch and expiry | Outstanding stays 10 until dispensed |
| Dispense the balance | Linked movement, once | Outstanding 0 |
These are acceptance criteria I recommend, not a claim that every package models partial fills the same way. Map your actual hand-offs in Blueprint & Prototype before requesting a supplier demo.
What is pharmacy software?
Pharmacy software records what a pharmacy buys, stores, sells and dispenses, with batch, expiry and prescription links. In Indonesia it is usually called aplikasi apotek. It overlaps with a cashier app, but a pharmacy needs to remember which batch left the shelf and which prescription authorized it.
A general cashier package can complete a sale. Our cashier app guide covers those transaction controls, which still apply here. What a pharmacy adds is batch-level stock, expiry visibility, prescription handling and, depending on the products you hold, extra reporting duties.
If your apotek sits next to a clinic, the clinical record belongs in a separate system. Our clinic software guide covers that boundary. Decide early which system owns the prescription and which owns stock.
Which pharmacy software features matter at each scale?
Choose features around operational hand-offs, not the number of screens offered. A single apotek serving corporate accounts may need more billing depth than several cash-only outlets.
| Operating model | Minimum capability to demonstrate | Signal to expand scope |
|---|---|---|
| One independent apotek | Batch and expiry stock, prescription log, receipt, supplier purchases, export | Staff cannot say which batches are near expiry |
| Apotek with clinic or doctor referrals | Above, plus prescription intake, partial fills and a clear hand-off from the clinic | Prescriptions are retyped or lost between systems |
| Pharmacy with credit customers or insurers | Above, plus credit rules, invoice cycle and receivables | Completed sales vanish inside unpaid balances |
| Multiple branches | Above, plus branch permissions and matched stock transfers | Dispatch and receipt cannot be reconciled |
For each shortlisted feature, write one observable result. “Has inventory” is vague. “Returning an unopened strip restores the right batch at the right location once” is something your storekeeper can test. Prepare the demo with your inventory owner.
What controls should pharmacy management software include?
Assign an owner to each hand-off so an exception has somewhere to go. The roles below are responsibilities to allocate, not invented interviewees. In a small apotek one person may hold several roles; still require review of sensitive adjustments.
1. Batches and expiry — owned by the storekeeper
Treat the batch as the unit of truth and the total as a convenience.
- Record batch number and expiry date when stock arrives.
- Pick the earliest-expiring sellable batch by default.
- Show a near-expiry list with a threshold you choose.
- Block or require approval to sell an expired batch.
- Record write-offs with a reason and an accountable user.
In the fixture, batch X is the one to sell first and the one to flag. A report that shows only “26 on hand” hides that 6 of them expire first. Demo question: can you show which batches expire within 120 days without a spreadsheet export?
I recommend this because expiry is a stock-control problem before it is a reporting problem. Bring one near-expiry shelf to a scoping discussion.
2. Prescriptions and dispensing — owned by the pharmacist-in-charge
Treat a prescription as a ledger of requested versus dispensed, not a one-time checkbox.
- Capture the prescription reference, prescriber and date.
- Link each dispensed item to its prescription and batch.
- Show requested, dispensed and outstanding quantities.
- Require a named pharmacist for the steps your procedures reserve for one.
- Keep the record retrievable for as long as your rules require.
R-201 is requested at 20, dispensed at 10, outstanding at 10. A later edit cannot quietly turn that into a closed prescription. Demo question: can you show R-201’s dispensed and outstanding quantities after the receipt is printed?
The software supports your pharmacist’s procedure; it does not make clinical decisions. Keep clinical judgment, substitution rules and counseling with qualified staff, and ask the pharmacist-in-charge (apoteker penanggung jawab) to approve the workflow.
3. Purchasing and receiving — owned by the purchasing lead
Make receiving the moment a batch enters the system with its evidence.
- Match each delivery to a purchase order and supplier invoice.
- Capture batch, expiry, quantity and cost at receipt.
- Flag short-dated deliveries before they are shelved.
- Link returns to suppliers to the original batch.
- Keep purchase and sales units explicit, such as box versus strip.
If a box holds ten strips, the conversion must be written down. A wrong conversion makes every later stock number wrong while still looking tidy. Use the stock movement checklist with your own units.
4. Sales and collection — owned by the finance lead
Keep the receipt as a bridge between the item dispensed and the money received.
- Carry dispensed lines into the bill without retyping.
- Apply deposits or partial payments once.
- Restrict discounts, refunds and voids.
- Reconcile each payment channel against settlement evidence.
- Export sales and payments with references back to batch and prescription.
Demo question: can finance explain every difference between the sales total and the cash and transfers collected?
I recommend separate dispensing, payment and stock states because they answer different questions. Scope accounting hand-offs before development.
Validate it in 2 weeks. Blueprint & Prototype maps your risky hand-offs and tests a working prototype with relevant users before you approve production scope. Bring one expired-stock write-off or one disputed prescription.
What compliance should you check before choosing pharmacy software?
Treat regulation as a checklist to verify, not a feature list to trust. Pharmacy practice, controlled-substance handling, record retention, personal-data protection and health-data integration such as SATUSEHAT are all governed by rules that change. The BPOM announcement discussed below gives a verified ownership reference; specific reporting, retention and integration duties still need confirmation for your facility.
| Topic | Question to put to the supplier | Who confirms it |
|---|---|---|
| Controlled-product reporting | Which reports exist, and who signs them? | Pharmacist-in-charge and the authority |
| Record retention | How long is a record kept, and can it be exported? | Your legal or compliance adviser |
| Personal data | Who can see patient and customer data, and is access logged? | Your data-protection owner |
| Health-data integration | Is a connection to national systems needed for your facility, and who maintains it? | The authority and the supplier |
| Pharmacist access | Which steps require a named pharmacist? | Pharmacist-in-charge |
A supplier saying “compliant” is a claim, not evidence. Ask what the software records, what it exports, and which duties remain with your staff. This needs human verification against current official sources before you rely on it.
Assign a reviewer to each required document in your scope.
Should you buy ready-made pharmacy software or build custom?
Start with a package when it passes your must-have tests and lets you take your data out. Custom development earns its cost when a recurring workflow gap has a measurable consequence that configuration cannot address.
| Approach | Good fit | Evidence to request | Main trade-off |
|---|---|---|---|
| Ready-made package | Standard retail, batch stock and prescription log | Replay your exceptions and export full history | Fit is constrained by supplier rules |
| Package plus integration | Core fits; one accounting, clinic or insurer hand-off does not | Supported API, retry behavior and clear data ownership | Two suppliers may share responsibility |
| Custom core | Distinct insurer, multi-branch or compounding rules remain | Prototype, acceptance criteria and operating owner | You fund maintenance and future changes |
For a hybrid system, write down which system owns stock, receipt numbering and payment status. A batch movement must have one authority. An integration failure needs a visible queue and a retry that does not repeat the business action.
Do not choose custom because you have three branches or want your logo on the login screen. Count the exceptions, estimate their cost, and compare that with the extra spend. Read our build-versus-buy framework before committing.
How do you test pharmacy software before buying?
Run the same ten tests in every demo and keep the exported evidence. Use a sandbox with fictional products. These are recommended acceptance tests, not assertions that a particular supplier passes or fails them.
| Test | Required observable result |
|---|---|
| 1. Sell across two batches | Earliest-expiring batch is used first; both movements link to one receipt |
| 2. Reprint and reopen a receipt | No additional stock deduction or duplicate receipt |
| 3. Attempt to sell an expired batch | Customer dispensing blocked; disposal recorded separately |
| 4. Receive a short-dated delivery | Warning appears before the stock is shelved |
| 5. Part-fill a prescription | Dispensed and outstanding quantities stay visible |
| 6. Return an unopened item | Correct batch and location restored once |
| 7. Repeat a payment notification | One payment record and the correct balance |
| 8. Interrupt the connection mid-save | Clear saved or unsaved state; retry creates no duplicate |
| 9. Try a restricted adjustment | Unauthorized user is blocked; allowed adjustment has history |
| 10. Export and reconcile R-201 | Prescription, batch, receipt and payment keep matching IDs |
Agree which failures block adoption. Unexplained stock loss, dispensing an expired batch to a customer, and duplicated money entries should stop the purchase until resolved. A cosmetic report change can be scheduled separately.
Ask the supplier to demonstrate backup recovery and explain access after cancellation, export scope and retention. An export button alone does not prove you can reconstruct your history. Bring the evidence to a vendor review.
How much does pharmacy software cost in the first year?
Compare the same operating scope over twelve months, including implementation. The model below is fictional planning arithmetic, not vendor prices, a market survey or a Synetica offer. Scope: one pharmacy, batch and expiry stock, prescription log, receipts, reporting and one accounting hand-off.
| Assumed cost, IDR million | Package | Hybrid | Custom core |
|---|---|---|---|
| Discovery and configuration | 4 | 8 | 14 |
| Custom development or integration | 0 | 26 | 100 |
| Twelve-month subscription | 8.4 | 8.4 | 0 |
| Additional hosting | 0 | 3 | 6 |
| Migration and staff training | 4 | 5 | 9 |
| Additional support | 3 | 6 | 12 |
| Planned first-year spend | 19.4 | 56.4 | 141 |
| Separate 15% reserve | 2.91 | 8.46 | 21.15 |
| Funding envelope | 22.31 | 64.86 | 162.15 |
The assumed subscription is IDR 700,000/month, or IDR 8.4 million/year. “Additional” means beyond what the subscription includes; remove overlapping support or hosting when comparing real quotes. The reserve is held funding, not an invoice.
The model excludes taxes, devices, scanners, printers, payment fees, message usage and future features. Ask suppliers to itemize these.
Open the budget diagram at full size.
How do you check whether the cost is justified?
Use recoverable operating value and verified loss reduction, with assumptions visible. Suppose staff save an assumed 40 minutes a day across 30 days: 20 hours a month. At an assumed IDR 35,000/hour that is IDR 700,000 of released capacity, which is not automatic cash savings.
That exactly matches the assumed IDR 700,000 subscription, so time value alone justifies nothing beyond break-even. A stronger case may rest on measured expiry write-offs. If you write off an assumed IDR 1.5 million of expired stock a month and better expiry visibility cuts that by 30%, you recover IDR 450,000 a month. Measure your own baseline first and avoid counting one benefit twice. Review the wider application cost drivers with those constraints in view.
How do you roll out pharmacy software?
Activate one pharmacy only after stock, expiry dates and open prescriptions reconcile. Installing software is one task; deciding which records become authoritative is the harder one.
Use four evidence gates. First, map units, batch rules, approval rules and owners. Second, replay the ten tests with the pharmacist, storekeeper, purchaser and cashier. Third, reconcile counted stock, expiry dates and open prescriptions against opening records. Fourth, activate one pharmacy and review its first shift close.
Open the rollout diagram at full size.
Choose a cutover time and one system for live stock movements and payments. Compare read-only reports during the pilot, but never deduct the same batch in two live ledgers. Name the person who can pause activation and the procedure for recovering unfinished transactions.
For agreed custom scope, Synetica’s 2B2G path is Blueprint & Prototype in 2 weeks, then Production Grade Software in 8 weeks, then Launch & Grow on an ongoing monthly retainer. That is ten weeks through prototype validation and production build. Package setup depends on supplier capability and your readiness; it does not inherit this schedule.
Plan the production work after the prototype establishes scope and acceptance criteria.
Why does pharmacy record ownership matter?
Keep the responsible pharmacist in charge of the rules your software supports. In its 4 May 2026 announcement about medicine-management oversight, BPOM describes management activities from procurement through reporting as responsibilities of the pharmacist-in-charge in pharmaceutical service facilities. The announcement provides context for assigning record owners; it does not certify a software package.
“safe, efficacious and quality medicines” — Taruna Ikrar, translated from Indonesian from the same BPOM announcement.
That short excerpt names the public-health purpose of the oversight. Ask your pharmacist to identify the requirements applicable to your products and verify the current regulation before implementation. Our fictional partial-fill example is a data test, not permission to dispense any specific medicine. Include the pharmacist in scope review.
What would I advise a pharmacy owner to do first?
Bring one awkward day to a demo before buying a longer feature list. Choose a sale that spans two batches, a part-filled prescription and a returned item. Ask your next shift to explain each using only the saved records.
- For one apotek: buy the smallest package that passes the critical tests and exports usable history.
- For clinic-linked or multi-branch operations: prove ownership of prescriptions, stock and hand-offs before adding automation.
- For custom scope: name the gap, its operating cost and the person responsible for the new workflow.
My next step would be to book a scoping conversation with that day’s records and its unanswered questions.
FAQ — Choosing pharmacy software
What is pharmacy software used for?
It records purchases, batch-level stock, expiry dates, sales and prescription dispensing. A useful implementation lets staff trace a sold item to its batch and, where relevant, its prescription.
What features should pharmacy software include?
Start with batch and expiry tracking, near-expiry alerts, prescription logging with partial fills, purchasing, receipts, role permissions and export. Add branch transfers or insurer billing when your workflow needs them.
How much does pharmacy software cost?
Get current quotes for your scope. This article’s fictional first-year model totals IDR 19.4 million for a package, IDR 56.4 million for hybrid and IDR 141 million for a custom core, before separate reserves and listed exclusions. These are calculations, not market prices.
Is free pharmacy software enough?
It can be enough for a limited workflow if its current terms, user limits and export cover your needs. Check whether batch and expiry tracking, backups and support are included. A free tier that forces critical records into a spreadsheet may create more work.
Can pharmacy software be customized?
Yes, through supported configuration, integrations or a custom build. First test whether an existing product meets the critical workflow. Custom scope needs clear data ownership, maintenance funding and acceptance tests; branch count alone does not justify it.
Related Posts
Aditya S
Business Development Manager, Synetica.
Put it into practice
Need help putting this into practice?
We turn the ideas in this article into a prototype tested with real users in 2 weeks (from Rp49jt)—or production-grade software in 8 weeks (from Rp100jt).