Skip to main content

Managing Branch Pharmacies Digitally: Several Locations in One System

The Pharmacy Supply Further Development Act (ApoVWG) has redefined the conditions for branch pharmacies (Zweigapotheken) in rural regions. Since 2 July 2026, the competent authority can approve the operation of a branch pharmacy in a remote town or district where the supply of medicines is significantly limited.

For pharmacy owners who want to run such a branch, a practical question arises alongside the legal and staffing requirements: how can several pharmacy locations be managed digitally without having to maintain information and processes more than once?

What is a Zweigapotheke?

In legal terms a branch pharmacy is not the same as an ordinary subsidiary pharmacy (Filialapotheke). It serves the supply of medicines in remote towns or districts where an existing pharmacy cannot guarantee adequate provision.

The assessment considers in particular the distance to the nearest pharmacy and how well it can be reached by public transport. Approval is granted by the competent authority and is tied to statutory conditions.

Under the new rules, up to two branch pharmacies may be operated in addition to the permitted subsidiary pharmacies. The permit is issued for ten years and can subsequently be renewed.

Why several locations don't need several digital islands

Anyone operating main, subsidiary, and branch pharmacies has to provide a great deal of information for each location. That includes, for example:

  • opening hours
  • contact details
  • services offered
  • collection and delivery options
  • orders
  • location-specific notices
  • contact people and availability

If separate websites, apps, or administration systems are used per location, the maintenance effort grows. Information has to be updated repeatedly, different systems require their own logins, and changes may not be applied everywhere at the same time.

A centrally structured system can bundle the shared components while still keeping location-specific details separate.

One website for several pharmacy locations

A shared website can present all locations under one consistent brand. Patients select the pharmacy they want and then see the matching information.

That can include:

  • address and directions
  • opening hours
  • telephone number
  • services offered
  • delivery area
  • collection options
  • current notices

General content, such as information about the pharmacy or its pharmaceutical services, can be maintained centrally. Differing opening hours or local services, by contrast, are assigned to the individual location.

A patient app with location selection

A shared patient app can also make sense, provided it separates the locations unambiguously.

Before placing an order or submitting a prescription, patients should be able to see clearly:

  • which pharmacy their request is sent to
  • where collection takes place
  • which location handles delivery
  • which opening hours apply
  • who to contact with questions

An understandable location selection prevents misrouting and creates a consistent user experience.

Assigning orders and e-prescriptions correctly

With several locations, unambiguous assignment is especially important. Orders and digital prescription workflows must not be sent to the wrong pharmacy by accident.

A suitable system should therefore document for every transaction:

  • which location the patient selected
  • which team is handling it
  • which collection or delivery option applies
  • what processing status the request has

Access rights and responsibilities must be clearly regulated. A shared technical platform does not automatically mean that every member of staff may access all data from all locations.

Only show stock levels with a suitable interface

A cross-location view of product availability can make handling requests easier. It requires, however, that the merchandise management systems in use support the necessary data exchange both technically and legally.

Where such a connection exists, pharmacies can see which location has a product in stock, for example. Where no interface exists, no supposed real-time stock levels should be displayed to patients.

Before selecting a platform, it is therefore worth checking:

  • Which merchandise management system is used at each location?
  • Is a suitable interface available?
  • How current is the transferred stock data?
  • Which access rights can be defined?
  • How are reservations assigned to a location?

Consistent branding, local information

Several locations should be recognisable externally as one pharmacy group. Logo, colours, tone of voice, and basic service information can therefore be managed centrally.

At the same time, every location needs room for its own details. These include, for example:

  • differing opening hours
  • location-specific services
  • local contact people
  • delivery areas
  • promotions
  • directions and parking information

The aim is a shared brand world that does not obscure the differences between the individual pharmacies.

Central administration with defined roles

A multi-location system should not only bundle information but also support different roles.

The owner may need an overview of all locations. Location managers, by contrast, should mainly work with the data and transactions of their own pharmacy. Other staff may only need access to particular tasks.

A role and permission concept helps map responsibilities cleanly and avoid unnecessary data access.

Checklist for managing several locations digitally

Before introducing a solution, pharmacies should clarify the following questions:

Can main, subsidiary, and branch pharmacies be presented separately?
Can shared content be updated centrally?
Can opening hours and services be maintained per location?
Are orders assigned unambiguously to one pharmacy?
Does the patient app support an understandable location selection?
Can roles and access rights be defined?
Which merchandise management interfaces are available?
Can further locations be added later?
How are data protection and responsibilities mapped?
What does each additional location cost?

How Mediloon can support several locations

Mediloon connects website, patient app, and digital communication functions within one shared platform. Pharmacy groups can therefore present their brand consistently while maintaining location-specific information such as opening hours, contact details, and services separately.

Which further functions are available for a specific multi-location setup depends on the merchandise management systems in use, the interfaces required, and the access rights agreed.

Before implementation, it is therefore worth reviewing together:

  • which locations will be included
  • which data is managed centrally or locally
  • how orders and e-prescriptions are assigned
  • which roles the respective teams need
  • which interfaces are technically available

The result is a digital structure that matches how the pharmacy group is actually organised.

Conclusion

The new rules on branch pharmacies open up additional ways to secure the supply of medicines in remote regions. A Zweigapotheke is not an ordinary extra outlet, however, but an officially approved form of operation with particular conditions. Anyone running main, subsidiary, or branch pharmacies together should plan the digital infrastructure early. A central platform can reduce maintenance effort, create a consistent appearance, and make location-specific processes clearer. What matters is unambiguous location assignment, well-defined access rights, and technically dependable interfaces. Only once those conditions are met do several locations become one functioning digital system.

About Mediloon

Mediloon is a Leipzig-based healthtech company building digital infrastructure for German pharmacies — including E-Rezept integration, pharmacy apps, Click & Collect, Botendienst coordination, and the Medi AI assistant. This article is part of Mediloon's pharmacy digitalisation guide series. It is intended as general operational and regulatory information. For specific legal or compliance queries relating to AI systems in your pharmacy, consult your regional Apothekerkammer or a qualified legal advisor.