Skip to content
European companyFounded in 2014Built and operated in EuropePayments secured by Card payments run through Stripe. Your card details never reach our servers.
GRADAX

Repeat prescriptions are the relationship

Websites, ordering and reminder systems for independent pharmacies, built around repeat scripts and the services beside the counter.

Sold as
One contract
Starts with
A free review

The vendors we build on, operate and resell.

  • Cisco
  • HPE
  • Dell
  • Lenovo
  • Veeam
  • WordPress
  • WooCommerce
  • Google
  • Stripe
  • Zoho
  • Atlassian

An independent pharmacy competes with chains on convenience and loses on price, so the ground it can win on is the repeat prescription: knowing what is due, having it ready, and telling the patient it is ready. That is a service problem, not a stock problem.

The second front is the services beside dispensing. Vaccinations, health checks, travel clinics and consultations carry real margin, and most independents offer them without anybody outside the shop knowing they exist.

The search side is not separate from that. "Pharmacy near me" and "pharmacy open now", plus service searches like flu vaccination or travel vaccinations with a town. Ranking for those means the pages exist, the business is verified where it operates, and the reviews are real and recent.

How a repeat prescription moves through a pharmacy

The patient sees one collection; behind it are four handovers where a repeat can go missing.

  1. Repeat requested

    It stalls when the patient phones or calls in to ask, and it moves when they request it from their phone in a minute.

  2. Prescription arrives

    It stalls when the pharmacy chases a missing script by phone, and it moves when outstanding requests are visible in one list.

  3. Dispensed and checked

    It stalls when stock is short and nobody tells the patient, and it moves when a message says what is delayed and when it will be ready.

  4. Ready to collect

    It stalls when the patient arrives too early and comes back twice, and it moves when they are told the moment the bag is on the shelf.

What people in this trade ask us

Is this allowed with patient data?
What we build handles requests and notifications, not clinical records, and it holds the minimum needed to do that. Anything touching dispensing stays inside your regulated system.
Will patients use online ordering?
The ones on regular repeats will, quickly, because it saves them a wasted trip. That group is also the most valuable and the easiest to lose to a chain with an app.
How do we get people to book the services?
By having a page for each one that says what it costs and when you are free. Most independents have neither, which is why the chains take that work.
Can we take bookings for vaccinations online?
Yes, with the consent questions asked at booking so the consultation starts with the answers already there. Seasonal clinics fill far better when patients can pick a time themselves.
Can we offer delivery to housebound patients?
The ordering and scheduling side can be built so drivers have a route and patients a delivery window. What you deliver, and the checks on handover, stay under your own procedures.

The infrastructure under it

Managed by the engineers who build the software, on the same contract and the same bill.

Cyber Security

Repeat requests carry names, addresses and medicines, which is exactly the data a pharmacy must not expose.

Two monitors showing security logs in a dark room.

Backup & Recovery

Service consultation records and consent forms have to be produced on request long after the patient has left.

A storage unit with a row of drive bays.

What one contract covers

  • One contract. The build, the infrastructure and the work that brings people to it, on one invoice.
  • A named team. The person on the first call stays on the project. No account managers, no handoffs.
  • Operated, not delivered. We keep it running after launch: patching, backups, monitoring and the phone when it breaks.
  • European hosting. Servers in Europe, run by us, with the data staying where you expect it to.
  • Monthly reporting. What changed, what it cost and what it produced, in language you can forward to a board.
  • No lock-in. The code, the domains and the accounts are yours. Leaving is a handover.

See what is costing you customers before you spend anything.

A senior engineer walks your site, your search presence and the way enquiries reach you, then writes down the three things worth fixing first.

  1. 01You tell us what is not working
  2. 02We review the site, the search presence and the enquiry path
  3. 03You get the three fixes worth doing, and what each is worth

Your quote list

Your quote list is empty

Add the services you are interested in, in the size that fits. We send one written quote for all of them.

Browse the catalogue

Start with a category

  • No payment, no commitmentThis is a request. You decide after the written quote.
  • Sold and delivered by GRADAXOne contract and one team, whoever does the work.
  • Your data stays in the EUNothing is moved outside the union to be processed.

Cookie preferences

Choose which cookies you allow. Necessary cookies cannot be turned off: the site needs them to work.