Management software for compounding pharmacies
The pharmacist stays up front.
VUpharma organizes what sits behind the counter: the pharmaceutical catalog, lot-based inventory with assays and expiration dates, and branches, with a migration that is test-run on a copy and reconciled against record counts.
Illustrative values.
The context
Independent pharmacies work on thin margins.
Stock that expires on the shelf and records no one trusts are costly for anyone working on thin margins and carrying technical responsibility.
78.98%
of the operational losses recorded in pharmacies and drugstores are related to product expiration.
56%
of the independent pharmacies surveyed saw reduced profits between 2020 and 2024.
9,320
active compounding pharmacies in Brazil in 2025; 77.5% of them operate under Simples Nacional, the simplified tax regime.
That is why what sits behind the counter needs to be in order.
Before switching systems
Three fears when switching systems.
The migration going wrong
The import is test-run on a copy and reconciled against record counts before it takes effect, and what it covers in your case is agreed in writing before the proposal.
Support disappearing
Channels, hours and response times are set out in the contract before the migration begins.
The system deciding for you
VUpharma does not assess prescriptions or approve preparations. It records, and it rejects whatever falls outside the rules your pharmacy has defined.
The product
What VUpharma organizes behind the counter.
Pharmaceutical catalog
DCB, CAS, regulatory class, Portaria 344/98 list, dosage forms, capsules, shelf life by dosage form and label name, in a single set of product records.
Lot-based inventory
Lots with pharmaceutical factors, quarantine and release, receiving and adjustments, with the balance computed from a stock ledger that is never erased.
Certificates of analysis and expiration dates
Raw-material lot assays with version history, and a daily expiration alert at each branch.
Migration
Data from your current system goes in under the same rules as data entered by hand. Beforehand, the import is test-run on a copy and checked in a reconciliation report.
Migration
Migration is the project, not a detail.
Anyone switching systems is afraid of losing data. That is why, when the import covers your source system, the data comes in through the same path and under the same rules as someone typing on the screen. Before the proposal, we state in writing what it covers in your case.
01
Measure the current database
We count what exists in today’s system, with read-only access, before importing anything.
02
Confirm with the pharmacist
Codes and factors without a clear meaning in the previous system are only entered after a recorded decision by the responsible pharmacist.
03
Test-run on a copy
The import runs on a copy of the data and ends with a count-based reconciliation report.
04
Publish with approval
The data only takes effect in the live system after the test run, with explicit, recorded approval.
How VUpharma works
Professional responsibility is yours. The system does not take your place.
Assessing the prescription and approving the preparation are acts of the responsible pharmacist. VUpharma organizes, records and rejects whatever does not follow the rules your pharmacy has defined.
01
Nothing is assumed.
A quantity is only converted using the product’s or the lot’s own factor. Without the factor, the conversion is rejected.
02
A correction is recorded on top.
Every inflow, outflow and adjustment becomes a ledger entry that is never erased. An error is corrected by a reversal, and the history stays in place.
03
Rejected before saving.
Inconsistent master data and stock operations outside the category’s rules are rejected before saving, with the message in the user’s language.
Homeopathy
Scales and methods as the pharmacopeia defines them.
CH, DH and LM as scales; FC and K as methods; SD and C flagged as non-pharmacopeial. No equivalence between scales, and the dilution ratio recorded only where the Brazilian Homeopathic Pharmacopeia (FHB) defines it.
Scales
Methods
Non-pharmacopeial
Branches
One pharmacy or a network of branches.
Data separated by branch
Lots, balances, stock ledger, receiving records, adjustments, assays and alerts belong to one branch and are only visible to the people who work there.
Shared master data
Products, dosage forms, capsules and suppliers can apply to the branches you choose.
Sanitary dossier by branch
Each branch’s operating license and the person responsible for SNGPC (ANVISA’s controlled-substance reporting system), with that person’s document stored encrypted.
Questions you will ask.
See VUpharma in action.
We show the catalog, lot-based inventory, homeopathy and the migration method, and we answer your pharmacist’s questions.
