Why a pharmacy needs more than its counter system
The counter system does its job very well: dispensing, e-prescriptions, till and sales stock. What it doesn't do is the back-office management behind it. Purchasing from wholesalers and laboratories, the shift rota, holidays and absences, standard operating procedures, staff training and appointments for care services end up scattered across spreadsheets, email and paper. Each piece works on its own, and nobody has the full picture.
That is where Odoo comes in. We don't position it as a replacement for the counter —changing it is expensive, risky and usually unnecessary— but as the back-office management system, connected to the counter so data is never typed twice.
Odoo does not replace the pharmacy's counter system: it complements it and runs the whole back office in a single tool.
What Odoo runs in a pharmacy back office
Purchasing and orders
With the purchase module, every supplier order is recorded with its price and terms history. When the counter is connected, restocking needs reach Odoo and the order is built from real data, not memory. Matching is done by the product's national code, the same identifier the pharmacy already uses.
Staff, shifts and absences
Each team member's record, holidays, leave and sick days live in Odoo, with their approval flow. The shift rota, on-call duty included, can be kept in the same system, and working hours are recorded and searchable.
Documentation and SOPs
Standard operating procedures, protocols and health documentation need a single home, with versions and owners. Odoo can organise them as a document repository where everyone finds the current version.
Internal training
Internal courses, mandatory reading of a new SOP and check quizzes can be set up as training inside Odoo, so there is a record of who did what and when.
Care appointments
Professional services —blood pressure checks, medication reviews, personalised dosage systems— need a diary. Odoo provides one with a shared calendar and, where useful, online booking.
Need → Odoo module
| Pharmacy need | Odoo module (technical name) | Edition |
|---|---|---|
| Orders to wholesalers and laboratories | purchase | Community |
| Back-office stock and receipts | stock | Community |
| Staff records | hr | Community |
| Holidays, leave and sick days | hr_holidays | Community |
| Time tracking | hr_attendance | Community |
| Skills and qualifications | hr_skills | Community |
| Internal training and courses | website_slides + survey | Community |
| Shared calendar | calendar | Community |
| Tasks and internal follow-up | project | Community |
| Document repository | documents | Enterprise / Community Plus |
| Shift rota and on-call duty | planning | Enterprise / Community Plus |
| Online booking | appointment | Enterprise / Community Plus |
Where Community falls short, Community Plus —our edition— brings the Enterprise modules with no licence fees. It can also be solved with custom development, as we did in the real case below.
Real case: two pharmacies in the Maresme
Two community pharmacies in the Maresme ran their counter on Farmatic and their back office on spreadsheets and email: purchasing, shifts, training and health documentation didn't talk to each other. We solved it with Odoo 19 Community.
- A Farmatic ↔ Odoo connector that reads the counter without stopping it and matches by national code.
- Purchase control with an order composer.
- A document repository for SOPs and internal training.
- Shift rota, absences and care appointments with online booking.
- Data isolation between the two pharmacies.
The result: one tool for both pharmacies' back office, with the counter untouched. Live since October 2026. The full anonymised case is on our case studies page.
What changes day to day
The pharmacist in charge stops chasing spreadsheets: orders, the rota, pending training and the week's appointments are on one screen. Staff see their own shifts and request leave from the same place. When an inspection asks for a procedure or a training record, it is found in seconds, with its version and its date. And because everything shares the same data, a change in one place —a new hire, a revised SOP, a supplier with new terms— reaches everything that depends on it without anyone having to remember to update it by hand.
How we work with a pharmacy
- Analysis: we look at how the back office works today and what can be read from the counter.
- Configuration: we set up the modules you need, and no more.
- Counter connection: reading without stopping dispensing, matching by national code.
- Staff training and support during go-live.
We implement Odoo only for companies in Catalonia, with more than 900 implementations behind us. Implementation starts from 4,500 € with Community; the configurator on our site gives you the figure for your case.