A system change is rarely difficult because of one till, one payment terminal or one software setting. It becomes difficult when the counter is busy, a patient is waiting, a price query needs answering and the team is trying to remember a new process. This pharmacy system migration guide sets out how UK community pharmacies can move to a new EPOS environment with less disruption, clearer accountability and a stronger first day of trading.
Why pharmacy migrations need a pharmacy-first plan
A generic retail POS change can focus mainly on products, prices and card payments. A pharmacy migration has more moving parts. Your counter system may need to work alongside PMR information, supplier ordering, C&D pricing data, Pharmacy First activity, stock controls, rear displays, kiosks and multiple payment devices.
The aim is not simply to replace ageing equipment. It is to give the team faster access to the information they need at the counter, reduce avoidable administration and protect the continuity of patient service. That means planning around actual pharmacy workflows, not around a supplier’s standard installation timetable.
Migration is also a commercial decision. A new system should make it easier to see sales by category, identify stock that is not moving, manage promotions and understand payment costs. If the new setup adds complexity without improving visibility or service, the change has missed its purpose.
Pharmacy system migration guide: start with the operating plan
Before any data is moved or hardware is ordered, map how the pharmacy operates now. Walk the counter at different points in the day. Observe what happens during a prescription collection rush, a Pharmacy First consultation referral, a delivery query and a card-payment issue. The small exceptions are often where a migration succeeds or fails.
Define what is changing
Be precise about the scope. You may be replacing the full counter estate, including EPOS, screens, scanners, receipt printers, cash drawers, payment terminals and customer-facing displays. Or you may be retaining some equipment and changing the software, payment provider or stock process.
Write down the integrations that must work from day one. For many pharmacies, these include PMR access at the till, accurate medicine and retail pricing, supplier ordering, patient-service prompts and business reporting. Distinguish between functions that are essential for opening the doors and improvements that can follow once the team is comfortable.
Give each decision an owner
The pharmacy owner or superintendent should set the business priorities, but a branch manager or nominated project lead needs authority to make day-to-day decisions. They should be able to confirm product ranges, approve pricing rules, arrange staff availability and sign off testing.
Your technology provider should have a named implementation contact too. A full-service partner can coordinate site survey, supply, delivery, installation, configuration, training and support. That reduces the risk of several suppliers each assuming somebody else is resolving a problem.
Clean the data before you move it
A migration will expose issues that have been hidden in the old system: duplicate products, inconsistent descriptions, discontinued lines, missing barcodes and outdated prices. Moving all of that into a new EPOS simply recreates the problem in a newer format.
Start by agreeing which data needs to transfer. This commonly includes retail product records, barcodes, current stock quantities, supplier information, price files, departments, VAT treatment, promotional rules and customer accounts where applicable. Set a clear cut-off date for changes to this data, otherwise the old and new records will quickly drift apart.
PMR data needs particular care. An EPOS may provide counter access to relevant PMR information through an approved integration, but that is different from copying clinical records into a till system. Confirm exactly what is accessed, where it is stored, who can see it and how user permissions are controlled. Your existing PMR supplier and EPOS provider should be clear about their respective responsibilities.
It is worth running sample checks before go-live. Take a selection of fast-moving OTC lines, prescription-related charges, higher-value products, exempt and VAT-rated items, and commonly ordered stock. Check the barcode, description, price, tax treatment and supplier route. This takes time, but it is faster than correcting a whole catalogue while serving patients.
Prepare the site, hardware and payments
Counter hardware affects every transaction. Confirm the physical layout before installation: where scanners, printers, cash drawers, displays and payment terminals will sit; where cables will run; and whether power and network points are sufficient. A well-positioned customer display can support clearer payment conversations and promotion visibility. A poorly positioned one becomes counter clutter.
Check network resilience as well. Payment acceptance, web reporting, supplier services and integrations rely on a stable connection. Ask how the system behaves during a short internet interruption and what staff should do if a payment terminal goes offline. A documented fallback process is essential, particularly for branches with limited connectivity.
Payment processing deserves its own review. Compare rates, contract terms, settlement timing, terminal replacement arrangements and support routes. The cheapest headline rate is not always the lowest operational cost if the service is difficult to reach when a terminal fails on a Saturday.
Configure around the counter workflow
A new system should feel logical to an experienced dispenser or counter assistant within a short period, but it should not be assumed that this will happen automatically. Configure buttons, prompts, user permissions and screen layouts around the work the team performs most often.
For example, a pharmacy may want quick access to common retail departments, prompts for relevant patient services, clear indicators for controlled stock processes, and a simple route to PMR information where the integration permits it. Another branch may prioritise multi-buy promotions, local health campaigns or stock ordering. The right setup depends on the pharmacy’s mix of dispensing, services and retail activity.
Test real scenarios, not just logins
A successful test is not simply proving that the system turns on. Ask staff to process realistic transactions from start to finish. Include a barcode scan, manual product search, split payment, refund, age-restricted sale, receipt reprint, cash discrepancy and a price query. Test a patient collection workflow and any Pharmacy First prompts that the pharmacy expects to use.
For multi-site groups, test branch-specific requirements too. One site may have a kiosk, another may use rear displays, while a third has a wider front-shop range. Standardisation is valuable, but it should not force every branch into an unsuitable process.
Train by role and protect time for practice
Training works best when it is practical and role-specific. Counter staff need confidence with sales, payments, returns, product lookup and basic troubleshooting. Managers need stock, ordering, reports, price maintenance and user controls. Pharmacists and dispensers need to understand the counter-facing PMR and service workflows relevant to them.
Avoid training everybody in one large session if the pharmacy can prevent it. Shorter sessions at the equipment, followed by supervised practice, are more likely to stick. Give staff a simple written escalation route for the first week: what they can resolve themselves, what goes to the manager and when to contact support.
Schedule training away from the busiest dispensary and counter periods. The cost of releasing staff for an hour is usually lower than the cost of a pressured team learning live in front of a queue.
Plan go-live as a controlled handover
Choose a go-live date with care. Avoid known peak trading days, major local events, stocktake periods and times when key staff are on holiday. A quieter weekday can be preferable, provided the right decision-makers and technical support are available.
On the day, complete a short opening checklist before trading starts. Confirm that tills balance, scanners read labels, printers produce clear receipts, payment terminals accept transactions, customer displays work, user logins are correct and the agreed integrations are available. Keep the old system accessible in read-only form for a defined period where possible, so staff can answer historic transaction or stock queries.
Expect a bedding-in period. The first week may reveal a missing product group, a report that needs adjusting or a workflow that takes one extra click. Capture these issues in one list, prioritise them by effect on patient service and trading, and review progress daily. This is more productive than allowing several informal workarounds to develop.
Measure whether the change is delivering
The migration is not finished when the final cable is fitted. Review the first 30 days against the outcomes you expected: transaction speed, payment reliability, stock accuracy, ordering time, report usage, pricing confidence and staff feedback. Look at the numbers, but also ask where the counter feels less pressured and where the team still has friction.
A pharmacy-specific provider such as MedEpos can support this process with the right combination of installation expertise, pharmacy workflow knowledge and ongoing technical help. The value comes from treating EPOS as part of the pharmacy operation, rather than as a standalone retail till.
The best migration leaves the team with more than newer equipment. It gives them clearer information at the moment they need it, more control over the business and more time for the patient standing at the counter.