New in the Profi plan: staff scheduling and NFC time tracking. Learn more

Custom or white-label pharmacy app?

A white-label pharmacy app uses an existing product and appears under your brand. A custom-built app can support specialised workflows. Start by checking whether an existing solution covers your essential features. Then compare first-year costs and who handles integrations, updates and operations.

Custom build, white-label or platform: the three routes

With a custom build, you commission an agency to program an app for your pharmacy alone. You decide every feature, but you also carry maintenance, updates and integrations yourself.

With a white-label solution, many pharmacies share the same technical foundation. Each gets an app with its own name, logo and colours. The provider takes care of the technology and updates.

With a platform app, by contrast, your pharmacy appears inside another provider's app, next to other pharmacies. Which platforms and white-label providers exist is covered in Pharmacy app providers compared.

How do you compare first-year costs?

Compare written quotes for the same scope. Add one-time charges, twelve monthly fees and usage-based charges. Ask what changes from year two.

CostCustom buildWhite-label
One-timeDesign, development, testing and releaseSetup, branding and migration of existing content
IntegrationsSeparate quote items for the webshop, pharmacy software and E-RezeptIncluded connectors and extra modules
RecurringHosting, maintenance, support and any developer accountsSubscription, support and any add-on or transaction charges

How long does a pharmacy app take to launch?

An existing platform can shorten setup. For either option, content, pharmacy software integration, acceptance testing and app store review affect the release date. Agree separate milestones for the demo, a pilot and the public launch.

Responsibilities for E-Rezept, app stores and operations

E-Rezept and CardLink

CardLink requires connection to a gematik-approved solution. For remote redemption via PoPP, gematik specifies an approved PoPP module. Whether the transition requires work on the app, the connector or the underlying service depends on the integration. For either model, confirm who will handle the work and how it will be billed.

App store rules

Apple guideline 4.2.6 requires the content provider to submit apps built from commercial templates or app generators directly. For highly regulated fields such as healthcare, Apple calls for the responsible legal entity to submit the app. Google Play requires a Health apps declaration. Agree who controls the developer account, supplies review information and submits updates.

Data protection and operations

Prescriptions and some orders contain health data. For either model, clarify privacy roles, legal grounds, data access and how security incidents are handled. If a provider processes data on your pharmacy’s behalf, a binding agreement under Article 28 GDPR is required. Agree who handles hosting, security updates, support, export and deletion.

General information, not legal advice

This article does not replace an assessment of your specific case. The final assessment of contracts, data protection and app store requirements rests with your pharmacy and your legal advisers.

Custom build and white-label side by side

CriterionCustom buildWhite-label solution
Upfront costProject quote for the requested scopeSetup and optional modules
Running costsMaintenance, hosting, integrations and any developer accountsSubscription and any add-on or transaction fees
Time to launchDepends on development, integration and reviewDepends on setup, integration and review
FeaturesFreely designedSet by the provider
E-Rezept and PoPPInclude integration and migration in the project scopeCheck migration and fees in the contract
DependencyOn the agencyOn the provider

The table shows that both routes create a dependency. With a custom build, it lies with the agency that knows the code. With white-label, it lies with the platform provider. What matters is how well you secure that dependency in the contract.

When a custom build can pay off

A custom app can make sense if your pharmacy needs features no provider offers, for example a large group with its own brand. In that case, budget, maintenance and a fixed contact person should be secured for years.

If an existing solution meets your needs, white-label can reduce setup work. In a demo, check how the app appears under your brand and how orders reach your pharmacy system.

Frequently asked questions

Do I own a white-label app?

Usually not in a technical sense. You use the app under your name, while the technology stays with the provider. Before signing, clarify what happens to the app, customer accounts and domain if you switch.

Can I switch from white-label to a custom build later?

You can switch. Apple and Google allow eligible apps to transfer to another developer account. Check whether your provider permits the transfer and whether you can keep the app identifier, customer accounts and data. If a transfer is unavailable, customers may need to install a new app.

What does a pharmacy app cost per year?

For the first year, add setup or development, twelve monthly fees and any extra costs for integrations, CardLink or developer accounts. For later years, compare custom maintenance and hosting with the white-label subscription, add-ons and renewal terms.

Conclusion

Compare both routes against the same requirements. For a custom build, get a quote for development, integration and operations. For white-label, look at the full package cost, who owns updates and what happens if you switch providers.

Sources

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.