Skip to content
DT Nova
Services

Pharmacy automation software for robots, rules and the work around them

Pharmacy automation is more than the robot in the back room. The robot stores and picks packs; the work around it, verifying every pack, checking prescriptions, ordering stock, chasing expiry dates and reminding patients, is still done by hand in many pharmacies. We build pharmacy automation software that connects your robot, scanners and pharmacy management system, runs the verification and stock rules every time, and leaves pharmacists the decisions only they can make.

  • You see the result before it goes live
  • Fixed price for the agreed scope, in writing before work starts
  • Source code, domain and accounts in your company's name

Request a quote

What pharmacy automation covers

Pharmacy automation has two halves. The hardware half is dispensing robots, automated dispensing cabinets on hospital wards, multi-dose packaging machines and counting devices, made by specialised manufacturers such as BD Rowa, Omnicell or Swisslog Healthcare. The software half is everything that tells that hardware what to do and makes sense of what it reports, and the checks and admin that no machine touches. That half is where we work, which is also why the term pharmacist automation is a useful one: the aim is to take repetitive checks and paperwork off the pharmacist, not to automate the pharmacist.

Our pharmacy work is for community pharmacies and pharmacy chains, hospital pharmacies, online pharmacies and companies serving pharmacies, such as wholesalers and software suppliers who need a development team.

What we build

The rules that shape pharmacy software

Pharmacy software runs inside some of the strictest rules in retail. We do not give legal or regulatory advice; your responsible pharmacist and advisers decide what applies. The rules we build for most often are these (all read on 11 November 2026):

Where automation pays back first

The best first project is the one where staff do the same check many times a day and an error is costly. In community pharmacies that is usually one of three things: the gap between the robot's stock and the pharmacy system's stock, which leads to manual counts and failed picks; expiry and shortage management, which ties up money and staff time; or prescription preparation for repeat customers, where a reminder and an order ahead turn a queue at the counter into a pickup. In hospital pharmacies it is often ward stock: cabinet data that already exists but is not used to plan replenishment.

We measure the time spent on the chosen task before we start, and again after go-live, so the result is a number from your own pharmacy rather than a promise.

Built around your pharmacy system

A pharmacy runs on its pharmacy management system, and it should stay that way. Replacing it is a large, risky project with national certification behind it. Automation around it is not: we connect through the interfaces the system and the robot supplier provide, or through the standard formats they already exchange, and we add the logic they do not have. When an interface does not exist, we agree with the supplier how to get one, rather than working around their system in ways that break with the next update.

Medical device or not?

Most pharmacy automation, such as stock, ordering, verification, reminders and dashboards, is not a medical device. Software that calculates doses, checks interactions to recommend treatment or decides which patient receives which medicine can be. For each feature, the question is answered in writing with your regulatory adviser before it is built, because a device needs a quality management system from the first line of code. Our guide to hospital mobile apps explains the EU and US rules on medical software.

How we build it

  1. Floor walk. We watch a normal day at the counter, in the back room and at stock-in, and list the checks staff repeat.
  2. Scope and fixed price in writing. One process, the systems it touches, the rules it must follow and what it leaves out.
  3. Test against the suppliers' test systems. Robot, pharmacy system and verification interfaces are tested in their test environments before any live data is touched.
  4. Pilot in one pharmacy. Run alongside the current way, with the responsible pharmacist signing off before the old way stops.
  5. Roll out and measure. To the rest of the chain, with the time saved and the error rates tracked per site.

You own it

As a standard term, the source code is in a repository in your company's own account, and hosting runs in an EU region in your company's name, with patient data under a written data processing agreement. You can keep us for maintenance, run it yourself or hand it to another team. For delivery of medicines to patients' homes, read our guide to medicine delivery app development. For automation of other administrative work in healthcare, read RPA in healthcare; for pharmacy and clinic staff rosters, see healthcare scheduling software; for automation across the business, see business process automation. For batches, expiry dates and stock across locations, see inventory management software. See prices. For GxP systems at manufacturers and laboratories, see pharmaceutical software development.

Questions we get

Do you sell dispensing robots?

No. Robots and dispensing cabinets come from specialised manufacturers. We build the software around them: the integration with your pharmacy management system, stock and ordering logic, verification flows, dashboards and the patient-facing apps. That keeps you free to choose the hardware.

Will you replace our pharmacy management system?

Usually not. The pharmacy management system remains the record for prescriptions and dispensing. We connect to it through its interfaces and automate the work around it, so staff do not type the same data into several systems.

How does the software handle FMD verification when the national system is down?

The Delegated Regulation allows for this: when technical problems prevent verification at the time of supply, the pharmacy records the unique identifier and verifies and decommissions it as soon as the problem is solved. The software queues those scans automatically and reports what is still pending.

Can patients get refill reminders and order ahead?

Yes. A patient app or web page can remind people when a repeat prescription is due, let them reserve the medicine for pickup and get a message when it is ready, without exposing more health data than the reminder needs.

Is pharmacy software a medical device?

Most pharmacy automation, such as stock, ordering, verification and reminders, is not. Software that calculates doses or recommends treatment can be. We answer that question for every feature in writing before building it, with your regulatory adviser.

Who owns the software and the data?

Your pharmacy or company. The code is in your own repository, hosting is in an EU region in your company's name, and patient data is processed under a written data processing agreement.

Get a written quote

Tell us in a few lines what you need. We reply within one working day with a written quote: scope, timeline and a fixed price or an hour estimate. Asking is free and commits you to nothing.

See every price · Contact details

Request a quote