Veterinary · head to head
RxWorks vs VisionVPM
RxWorks
Veterinary
Server-based practice management with a corporate group heritage in Australia, New Zealand and the United Kingdom
- From
- On request
- Rated
- -

VisionVPM
Veterinary
On-premise practice management for veterinary groups in Australia, New Zealand, the UK and Ireland
- From
- On request
- Rated
- -
The short version
- Each has a real cost: RxWorks it is a legacy line inside Covetrus, which promotes Pulse as its strategic cloud product, so the practical question is not capability but how long the system will be supported and on what notice.; VisionVPM it needs a Windows server, a backup regime and someone responsible for both, so the true cost includes IT support that cloud competitors absorb into their subscription.
- They diverge on capability: RxWorks covers Multi-site group operation, VisionVPM covers Local database.
- Prices and features above were last checked on 1 September 2026.
Where they differ
Only the attributes on which RxWorks and VisionVPM actually diverge.
Identical on both: starting price (On request), pricing model (quote), free tier (No), platforms (Windows), user rating (Not yet rated), category (Veterinary).
What each one covers
Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in RxWorks
- Multi-site group operation
- Dispensing and stock control
- Client accounts
- On-premise database
- Regional configuration
- Laboratory integration
Only in VisionVPM
- Local database
- Large and mixed animal modules
- Stock and wholesale ordering
- Debtor and account management
- Multi-site consolidation
- Clinical reminders
What people use each for
The jobs each tool is most often brought in to do.
RxWorks
- A practice joining an Australian, New Zealand or United Kingdom group that already standardises on RxWorksnot VisionVPM
- A group that needs consolidated reporting and centrally controlled price lists across many sitesnot VisionVPM
- A mixed or large animal practice that runs account customers on credit terms rather than payment at the time of servicenot VisionVPM
- A site that cannot rely on its internet connection and needs the clinical record held locallynot VisionVPM
VisionVPM
- A rural mixed practice where internet connectivity is too unreliable to depend on a browser-only systemnot RxWorks
- A corporate group that requires clinical and financial data to remain on infrastructure it controlsnot RxWorks
- A farm-heavy practice needing herd recording and monthly account billing that companion-animal cloud systems handle poorlynot RxWorks
- An established VisionVPM site weighing an upgrade against the cost and disruption of migrating to a cloud systemnot RxWorks
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
RxWorks
- It is a legacy line inside Covetrus, which promotes Pulse as its strategic cloud product, so the practical question is not capability but how long the system will be supported and on what notice.
- It is a Windows server product, so the group carries hardware, database, patching and backup costs that never appear in the software quotation.
- Its relevance is regional: outside Australia, New Zealand and the United Kingdom the installed base and the support and consultant network are thin, which matters for a group expanding into new markets.
- Remote and mobile working is poor compared with cloud systems, which is a growing problem as groups centralise administration and clinicians expect record access away from the practice.
- The eventual migration off it will be a full data conversion with retraining across every site, and at group scale that project cost should be modelled now rather than treated as a future problem.
VisionVPM
- It needs a Windows server, a backup regime and someone responsible for both, so the true cost includes IT support that cloud competitors absorb into their subscription.
- Upgrades are scheduled events with downtime rather than transparent releases, which means version drift across a multi-site group and a coordination burden at each release.
- Covetrus is steering customers towards its cloud product, so development effort is unlikely to favour VisionVPM long term and buyers should assume a migration eventually.
- Remote and out-of-hours access requires a remote desktop or Citrix layer, which adds licensing, latency and another system to secure.
- Ordering and prescription workflows are built around Covetrus as the supplier, so a practice buying from other wholesalers loses the automated parts and reverts to manual entry.
Pricing, plan by plan
RxWorks
On request- RxWorks$undefined/year
- Quoted per site, normally under a group agreement
- Annual support and maintenance charged separately
- Server infrastructure is the responsibility of the practice or group
VisionVPM
On request- VisionVPM$undefined/year
- Licence and annual support quoted per practice
- Server hardware and Windows licences bought separately
- Data migration quoted per site
Which should you pick?
Choose RxWorks if
- You need multi-site group operation.
- You work on Windows.
- You also want dispensing and stock control.
Choose VisionVPM if
- You need local database.
- You work on Windows.
- You also want large and mixed animal modules.
Questions people ask
- Is RxWorks or VisionVPM better?
- Neither clearly leads. RxWorks starts at On request and VisionVPM at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, RxWorks or VisionVPM?
- RxWorks starts at On request and VisionVPM at On request.
- Does RxWorks or VisionVPM run on more platforms?
- Both run on Windows, so platform support will not decide this one for you.
- What is RxWorks best used for?
- RxWorks is most often used for a practice joining an australian, new zealand or united kingdom group that already standardises on rxworks, a group that needs consolidated reporting and centrally controlled price lists across many sites, a mixed or large animal practice that runs account customers on credit terms rather than payment at the time of service, a site that cannot rely on its internet connection and needs the clinical record held locally. Of those, a practice joining an australian, new zealand or united kingdom group that already standardises on rxworks and a group that needs consolidated reporting and centrally controlled price lists across many sites are not what VisionVPM is typically brought in for.
- What can RxWorks do that VisionVPM cannot?
- RxWorks covers Multi-site group operation, Dispensing and stock control, Client accounts, On-premise database. VisionVPM covers Local database, Large and mixed animal modules, Stock and wholesale ordering, Debtor and account management.
Answered from the vendors’ own pages
RxWorks: Should a new practice adopt RxWorks today?
Generally no, unless you are joining a group that already runs it. A new independent practice should be evaluating cloud systems instead.
VisionVPM: Can VisionVPM run in the cloud?
Only by hosting the Windows server yourself or through a partner and connecting over remote desktop. It is not a browser application and hosting it does not make it one.
RxWorks: Is it still supported?
Covetrus supports it, but Pulse is the stated strategic product. Ask for the support commitment and the end-of-life notice period as written contract terms.
VisionVPM: Is VisionVPM still being developed?
It receives maintenance and compliance updates, but its owner sells a separate cloud product and directs new development there. Plan on a migration within the life of your next server.
RxWorks: Where is it actually used?
Mostly Australia, New Zealand and the United Kingdom, heavily within corporate practice groups. It has very little presence in the United States.
VisionVPM: Does it work outside Australasia and the UK?
It is sold and supported in Australia, New Zealand, the UK and Ireland. Tax handling and supplier integrations are built for those markets.
RxWorks: What does migration off it involve?
A full clinical and financial data conversion per site plus retraining. At group scale that is a programme of work, not a weekend.
Related pages
Other head to heads
- RxWorks vs ezyVet
- RxWorks vs Provet Cloud
- RxWorks vs IDEXX Neo
- RxWorks vs VIA Veterinary
- RxWorks vs Animana
- RxWorks vs Onward Vet
- RxWorks vs Vetstoria
- RxWorks vs PetDesk
- RxWorks vs Talkatoo
- RxWorks vs Shepherd
- RxWorks vs Digitail
- RxWorks vs VetBadger
- RxWorks vs IDEXX Cornerstone
- RxWorks vs Vet Radar
- VisionVPM vs ezyVet
- VisionVPM vs Provet Cloud
- VisionVPM vs IDEXX Neo
- VisionVPM vs VIA Veterinary
- VisionVPM vs Animana
- VisionVPM vs Onward Vet
- VisionVPM vs Vetstoria
- VisionVPM vs PetDesk
- VisionVPM vs Talkatoo
- VisionVPM vs Shepherd
- VisionVPM vs Digitail
- VisionVPM vs VetBadger
- VisionVPM vs IDEXX Cornerstone
- VisionVPM vs Vet Radar
