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.

Example · lot recordRaw material
LotMP-2026-0412
StatusReleased
Density0.62 g/mL
Correction factor1.05
Content assayversion 2 · supersedes version 1
Expiration date01/14/2027
Balance482.50 g · computed from the stock ledger
AlertExpires in 87 days

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.

Source: Abrappe, Pesquisa de Perdas no Varejo 2025, as reported by Guia da Farmácia

56%

of the independent pharmacies surveyed saw reduced profits between 2020 and 2024.

Source: IFEPEC/Febrafar, Visão 360º, 2025 · 2,200 owners

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.

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

CHDHLM

Methods

FCK

Non-pharmacopeial

SDC

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.

No. Assessing the prescription and approving the preparation are acts of the responsible pharmacist. The system organizes the master data, records every stock movement and rejects, before saving, whatever does not follow the rules the pharmacy has defined.
The import saves each record through the same entry point and under the same rules as someone using the screen, keeping the identity it had in the previous system. It is first test-run on a copy and ends with a count report: a rejected row is counted, and whatever was inconsistent at the source comes in flagged, in plain view. Before the proposal, we state in writing what the import covers in your case.
We assess your source system before the proposal and state in writing what the import covers, without accessing the pharmacy’s data.
Yes. The master data includes seven dynamization abbreviations: the CH, DH and LM scales and the FC and K methods follow the Brazilian Homeopathic Pharmacopeia (FHB); SD and C are flagged as non-pharmacopeial. The lot records the dynamization method and the potency.
Yes. Each branch has its own lots, balances, movements and alerts, and each user signs in to their default branch. Products, dosage forms, capsules and suppliers can be shared among the branches you choose. Stock transfers between branches and a consolidated network report are not part of VUpharma.
No. VUpharma runs in the cloud and is used in the browser, with no server at the pharmacy.
No. VUpharma organizes what sits behind the counter: catalog, lot-based inventory, assays and expiration dates. Counter sales, tax invoicing, submission to SNGPC, formula calculation and label printing are not part of it.
The VUpharma team. Channels, hours and response times are set out in the contract before the migration begins.
We do not give a timeline before measuring your database. Implementation requires the responsible pharmacist to confirm codes and factors, and the pharmacy to confirm the meaning of the lot statuses.
The price is presented in the demo, with a written proposal, based on your operation.

See VUpharma in action.

We show the catalog, lot-based inventory, homeopathy and the migration method, and we answer your pharmacist’s questions.