Last fact-check: August 9, 2026.

Shepherd is a cloud-based veterinary practice information management system, or PIMS. Its current product combines SOAP-based medical records, scheduling, estimates and invoices, inventory, payments, client communications, a pet portal, reporting, wellness plans, integrations, multi-location administration, and AI-assisted documentation and clinical support.

The feature list is broad, but it does not answer the hardest buying questions. Shepherd does not publish a base dollar price on the product pages reviewed. The public end-user agreement refers to a separate Service Agreement, combines a one-year initial term with a 14-day customer termination provision, and promises CSV data tables at exit without defining the complete export schema. AI tools and third-party integrations also create clinical, privacy, support, and contract questions that should be settled before a practice moves its records.

This independent desk review uses current first-party Shepherd product pages, integration material, support information, privacy policy, published end-user agreement, and dated vendor articles or guides. We did not use a live Shepherd account, interview customers, run a data conversion, or test a clinical workflow. We do not assign a star rating or repeat unverified complaints as fact. Every material workflow should be demonstrated with the exact subscription and integrations in your proposal.

Shepherd Veterinary Software Review: The Short Verdict

Shepherd deserves consideration from independent veterinary practices that want a modern cloud PIMS with a strong SOAP workflow and a substantial amount of functionality in one interface. Its most attractive documented elements are:

  • SOAP-based records tied to treatment plans, invoices, discharge instructions, and tasks;
  • automatic charge capture from clinical activity;
  • scheduling, a digital whiteboard, forms, estimates, reminders, and activity logs;
  • inventory tracking connected to product administration;
  • built-in payments through Shepherd Pay;
  • a messaging center, pet portal, refill requests, appointment requests, and two-way texting;
  • TranscribeAI and DiagnoseAI inside the PIMS workflow;
  • a large and actively updated integration catalog;
  • centralized multi-location settings and reporting;
  • unlimited users, unlimited workstations, training, support, Shepherd Pay, and no implementation fee according to the current features page.

The principal risks are less visible:

  • no public base price or complete public fee schedule;
  • unclear pricing for each location, payment processing, wellness plans, messaging usage, AI, or third-party services;
  • a contract structure that requires both the EULA and separate Service Agreement to understand the real commitment;
  • migration marketing that does not publicly define every converted record type or acceptance standard;
  • a CSV exit promise that may not equal a complete, immediately reusable archive;
  • reliance on internet access and cloud availability;
  • integrations with different directions, scopes, vendors, costs, and support owners;
  • AI output that still requires veterinarian judgment and verification;
  • security and privacy claims that need current audit evidence, scope, subprocessors, retention terms, and incident commitments.

Shepherd is not a product to buy from a polished demo alone. It can be a strong fit when a representative team validates real cases, reports, inventory, payments, integrations, migration, and exit data. The signed order should capture everything the practice relied on.

What Shepherd Veterinary Software Includes

The official features page describes a cloud PIMS rather than a narrow electronic medical record. The current subscription page says unlimited users, unlimited workstations, expert training, veterinary-experienced support, Shepherd Pay, and no implementation fees are included.

Those words are valuable, but “included” should be translated into contractual detail. Ask whether there are limits by legal entity, location, veterinarian, storage, patient volume, transaction volume, messages, AI usage, portal activity, or support contact. Confirm which third-party services require their own agreement and which functions are available in the proposed country and practice type.

SOAP records and connected workflow

Shepherd centers its clinical workflow on SOAP records. The vendor says completing a SOAP can update the medical record and invoice, generate discharge instructions, and initiate linked tasks or reminders. It also lists templates, autosave, vital comparisons, medical and prescription history, patient-status dashboards, customizable forms, and complete activity logs.

The design may reduce duplicate entry, but it can also spread one incorrect selection across the record, invoice, inventory, and client instructions. Test both the normal path and corrections. A veterinarian should change, remove, backdate, and reopen an item while the practice manager verifies every downstream effect and audit entry.

Scheduling, estimates, and patient flow

Documented scheduling features include appointment types tied to provider availability, blocked provider time, new-patient creation from appointment requests, and a digital whiteboard showing current treatments. Estimates can be created inside or outside a patient record and sent for approval.

Run the clinic's actual scheduling edge cases: urgent add-ons, boarding or hospitalized patients, multi-doctor appointments, drop-offs, mobile routes, surgery resources, late clients, no-shows, rescheduling, recurring care, and online requests that should not book automatically. Verify how permissions, status changes, deposits, cancellations, and waitlists work.

Invoicing, inventory, and payments

Shepherd promotes charge capture because treatments recorded in the medical workflow can flow to invoices. The platform also tracks inventory when products are administered and provides end-of-day, commission, treatment, patient, and inactive-client reports. Shepherd Pay supports a USB terminal, stored cards, and online pet-portal payment according to the features page.

These are high-value workflows, but the public page does not disclose payment-processing rates, terminal costs, funding time, chargeback fees, card-vault terms, or reconciliation details. The quote should identify the processor, merchant agreement, PCI responsibilities, supported tender types, refund behavior, and exit process for stored payment credentials.

Test a controlled substance, split package, partial dose, returned item, expired lot, negative inventory, special order, refill, refund, discount, tax, deposit, payment plan, and bad debt. Confirm what happens to inventory and the ledger when a SOAP or invoice is corrected after checkout.

Client communication and pet portal

The client communication page says the messaging center and pet portal are included at no extra charge. It lists unlimited two-way texting, mass SMS and email, message templates, automatic reminders, appointment and refill requests, medical-record access, vaccine certificates, and online balance payments.

“Unlimited” should still be tested against fair-use, carrier, registration, geographic, or message-type restrictions. Ask how opt-in and opt-out status is stored, how shared household numbers work, whether a failed delivery is visible, and which messages enter the legal medical record. The EULA places compliance with the Telephone Consumer Protection Act, CAN-SPAM, and other communication laws on the client.

Shepherd Veterinary Software Pricing in 2026

Shepherd does not publish a base dollar price on the home, features, multi-location, integration, or contact pages reviewed. Buyers must request a personalized demo and proposal.

Current public materials do reveal part of the pricing structure:

  • the features page says the subscription includes unlimited users, unlimited workstations, training, support, Shepherd Pay, and no implementation fees;
  • the client-communication page says the messaging center and pet portal are included at no extra charge and describes two-way texting as unlimited;
  • an older switching guide advertises free data migration;
  • a March 2026 vendor article on wellness-plan rollout says Shepherd's wellness-plan pricing is 3% to 5% of plan revenue and that commission is collected quarterly.

The older migration guide is not a current price sheet, and a vendor blog does not replace the signed order. Confirm every statement in the proposal.

What to request in the quote

Build a three-year total-cost schedule covering:

  • base PIMS subscription and billing frequency;
  • each practice, legal entity, location, mobile unit, or shared group;
  • any limits related to veterinarians, records, storage, documents, images, or transactions;
  • multi-location administration and group reporting;
  • TranscribeAI, DiagnoseAI, future AI features, and usage allowances;
  • Shepherd Pay rates, terminals, ACH, text-to-pay, refunds, disputes, and stored cards;
  • wellness-plan percentage, minimums, refunds, cancellations, and reporting;
  • SMS registration, carrier charges, mass messaging, short codes, or fair-use limits;
  • labs, imaging, pharmacy, communication, financing, accounting, analytics, controlled-drug, and inventory integrations;
  • data conversion by source system, record category, historical depth, attachment type, and image volume;
  • training, go-live coverage, after-hours assistance, and later refresher sessions;
  • custom forms, templates, reports, workflow setup, and professional services;
  • API access, rate limits, sandbox, documentation, and custom-integration support;
  • taxes, travel, devices, scanners, label printers, terminals, and local network work;
  • renewal pricing, price-increase notice, cancellation, export, transition assistance, and deletion.

If the vendor says a cost is included or waived, put that language in the Service Agreement. A salesperson's email or an old PDF is weaker protection than the executed order.

Shepherd Contract Terms to Read Before Signing

The published Shepherd EULA updated May 22, 2024 is an addendum to a separate Service Agreement. The EULA therefore does not establish the complete price, commercial scope, or hierarchy of every negotiated term.

Term and termination need clarification

The EULA says the agreement has an initial one-year term and automatically renews for successive one-year terms. It also says the client may give notice at any time, with termination effective 14 days later provided all payments due through termination are paid. Shepherd may give three months' notice, and it can suspend access for a security risk, contrary use, or payments more than 30 days overdue.

Those clauses raise a practical question: does customer notice during the initial year end future charges after 14 days, or are remaining initial-term amounts still due under the Service Agreement? Ask the vendor to answer in writing and identify which document controls. Also request price-increase notice, renewal reminders, cure rights, data-access rights during a dispute, and transition support after notice.

The exit promise is useful but incomplete

The EULA says that upon termination the client will receive all data as raw tables exported in CSV form and up to two data backups as needed. It also says the client owns customer data, while Shepherd and affiliates may analyze, publish, and use anonymized and deidentified practice data.

CSV tables can be useful for structured fields, but the public language does not explain:

  • export timing and secure delivery;
  • table definitions, keys, relationships, and data dictionary;
  • attached documents, images, signed forms, original files, and message media;
  • audit logs, change history, templates, permissions, and configuration;
  • payment tokens and third-party integration data;
  • whether the two backups are database copies, file archives, or another format;
  • fees for transition help or a different format;
  • post-termination availability and deletion schedule.

Require a sample full export before signing. Give it to the person who would actually archive the records or move them to another system. Put the accepted format, content, timing, encryption, delivery method, fees, and deletion confirmation in the Service Agreement.

Clinical responsibility stays with the practice

The EULA says Shepherd does not promise secure, uninterrupted, or error-free use and that the client must use its own judgment, training, experience, and expertise. It explicitly says the client should not rely on recommended dosages or procedures presented by the PIMS.

That disclaimer is especially important when evaluating automation or DiagnoseAI. Shepherd can support clinical work, but the veterinarian remains responsible for checking the patient context, calculations, contraindications, record, client instruction, and final decision.

AI Features: TranscribeAI and DiagnoseAI

The current features page describes two built-in AI paths:

  • TranscribeAI listens to or processes visit information and generates structured SOAP documentation inside the PIMS;
  • DiagnoseAI uses information from the SOAP subjective to suggest differential diagnoses, treatment options, and certain discharge instructions.

The presence of AI inside the medical record reduces copying between tools, but it increases the need for governance. A demo should use noisy rooms, overlapping speakers, different accents, species, drug names, numbers, negative findings, and complex histories. Require the veterinarian to compare source audio or notes with the generated SOAP and measure correction time, not only generation speed.

Before enabling either tool, request written answers about:

  • the model provider and subprocessors;
  • where audio, transcripts, prompts, outputs, and feedback are processed and stored;
  • retention periods and deletion behavior;
  • whether practice data is used to train a shared model;
  • client-notice or consent needs for recorded conversations in applicable jurisdictions;
  • role permissions and audit logs;
  • version changes, validation, monitoring, and incident response;
  • how references are selected for clinical suggestions;
  • known limitations by species, specialty, language, and case type;
  • the workflow for human review before signing, invoicing, prescribing, or sending instructions.

No AI-generated diagnosis, dosage, treatment, discharge instruction, or medical record should bypass qualified review. Measure error severity as well as time saved.

Integrations: Verify Direction, Scope, and Ownership

The official integrations directory is extensive and current. It covers laboratories, imaging, payments and financing, pharmacy, communication, scheduling, inventory, controlled-drug logs, microchipping, reporting, client education, wellness plans, and other categories.

The directory makes a useful distinction:

  • software integrations provide two-way data sharing;
  • data connections share information with Shepherd but may not be bidirectional;
  • resources are available inside the integrations area without necessarily exchanging practice data.

Do not treat every logo as the same kind of integration. For each required provider, document:

  • exact product, country, account type, and version;
  • one-way or two-way behavior;
  • fields, attachments, images, results, charges, corrections, and statuses exchanged;
  • sync trigger, delay, error queue, retry, and audit history;
  • duplicate detection and patient matching;
  • separate vendor agreement and cost;
  • data-sharing consent and subprocessor role;
  • support owner and escalation path;
  • behavior during an outage or when the partner changes its API;
  • export or deletion of integrated data at termination.

Test the practice's actual lab, imaging, pharmacy, payment, accounting, and communication accounts. A directory entry does not prove that a specific analyzer, modality, workflow, or field is supported.

Multi-Location Capabilities

The multi-location page describes centralized administration for clinics, users, products, settings, forms, reports, reminders, inventory, and bulk edits. It also promotes cross-location reporting, shared records, and group-level access.

Multi-location groups should test more than a consolidated dashboard. Run a patient who visits two locations, a transferred appointment, shared and location-specific inventory, different tax or pricing rules, provider movement, centralized client communication, duplicate clients, permissions, refunds across locations, and financial close by entity.

Ask whether the system supports separate merchant accounts, bank deposits, charts of accounts, legal entities, local formularies, controlled-substance locations, record ownership, and location-specific retention rules. Confirm which changes flow to every clinic and how a mistaken bulk edit is reversed.

Data Migration and Implementation

Shepherd's current features page says there are no implementation fees and expert training is included. The older switching guide says data migration is free and handled by an experienced team. Public marketing does not, however, define a complete conversion matrix or acceptance procedure.

Create a written inventory before signing:

  • clients, patients, species, breeds, alerts, responsible parties, and communication preferences;
  • medical history, SOAPs, diagnoses, problems, prescriptions, vaccinations, reminders, and certificates;
  • appointments, provider schedules, resources, recurring care, and waitlists;
  • estimates, invoices, payments, credits, deposits, refunds, accounts receivable, and taxes;
  • inventory items, units, costs, lots, expirations, vendors, purchase orders, and controlled-drug history;
  • lab requisitions and results, diagnostic images, reports, documents, forms, signatures, and photos;
  • messages, portal activity, referrals, tags, custom fields, templates, and audit history;
  • users, roles, permissions, locations, and configuration.

Require a test conversion and formal acceptance. Compare record counts, financial control totals, inventory valuation, active reminders, open balances, patient timelines, images, attachments, and representative complicated cases. Define the freeze window, late-entry method, rejected-record report, correction process, rollback conditions, and person responsible for every exception.

Training should be role based. Veterinarians, technicians, CSRs, managers, inventory owners, and finance staff need different scripts. Schedule a second training cycle after the team has used real data and accumulated real exceptions.

Security, Privacy, and Availability

Shepherd announced completion of a SOC 2 audit in a September 2024 vendor article. The article says the audit covered areas including security, access, backups, business continuity, and incident response. The current multi-location page also describes Shepherd as SOC 2 compliant.

This is a positive diligence lead, not proof that every current service, integration, or customer configuration is secure. Request the latest SOC 2 report under NDA, confirm Type I or Type II, review the scope and period, obtain a bridge letter if needed, read exceptions and complementary user-entity controls, and verify that the exact PIMS, AI services, payment path, and infrastructure are covered.

The current privacy policy was published in February 2024 and says it was last updated June 9, 2024. It discusses information collection, service providers, affiliates, United States processing, retention based on purpose, security measures, and state privacy rights. The EULA links customer information to this policy and allows sharing with integrated third parties when the client opts in.

Ask for the current PIMS-specific data-processing terms, subprocessor list, hosting regions, encryption details, backup schedule, recovery time and recovery point objectives, restore-test evidence, multifactor authentication, role controls, support access, security logs, vulnerability reporting, incident-notification deadline, cyber insurance, and record deletion procedure.

Availability also needs an operational plan. A cloud PIMS depends on internet and vendor service. Shepherd documented an emergency read-only access feature in a 2024 update, but buyers should demonstrate the current version and learn exactly which schedules, records, invoices, and prices remain available. Run a tabletop exercise for internet loss, vendor outage, lab outage, payment outage, and identity-provider failure. Keep vendor contact details and safe paper or offline procedures accessible.

Shepherd Support and Training

The current Shepherd team page says customer care is available every weekday from 8:00 a.m. to 8:00 p.m. Eastern Time. The product page also describes in-software chat and veterinary-experienced support.

Ask whether those are the contracted hours for your subscription. Request severity definitions, response and restoration targets, holidays, after-hours emergency handling, uptime terms, scheduled maintenance notice, status-page history, escalation contacts, and ownership when a third-party integration fails.

During the demo, open a support ticket from the workflow where a problem occurs. Verify what diagnostic access support receives, how access is approved and logged, whether sensitive records can be masked, and how a case escalates to engineering.

Shepherd Reviews and Complaints: How to Evaluate Them

Public reviews can reveal questions, but they do not establish the performance of the proposed configuration. A review may describe another year, practice type, integration set, payment processor, data source, location count, or support incident. Vendor-selected testimonials are also not an independent sample.

Use repeated themes as hypotheses for a demo and reference call. Ask Shepherd for current references similar to your practice in size, species, care model, country, source PIMS, labs, imaging, payment setup, and locations. Speak with veterinarians, technicians, CSRs, a manager, and the person who reconciles money and inventory.

Ask references:

  • Which functions and integrations are actually live?
  • What did not migrate, and how was it corrected?
  • How long did each role need to become independent?
  • Which workflow still needs a workaround?
  • Do SOAP, invoice, inventory, and discharge changes remain synchronized?
  • How reliable are lab and imaging connections?
  • Which reports reconcile to the bank, processor, inventory, and general ledger?
  • What happened during the most serious outage?
  • How quickly did support resolve a patient-blocking or checkout-blocking issue?
  • What charges were not obvious in the first quote?
  • Has the practice produced a complete usable exit export?
  • Would the team choose Shepherd again under the same terms?

Record the date, product configuration, and practice context for every answer.

Who Is Shepherd Best For?

Shepherd is most plausible for:

  • independent general practices wanting a cloud PIMS centered on SOAP workflow;
  • clinics trying to connect clinical activity, charge capture, inventory, discharge, and client communication;
  • practices that value built-in payments, portal, messaging, forms, and reminders;
  • multi-location groups prepared to validate centralized settings and financial separation;
  • teams willing to run a structured migration, security review, integration test, and pilot;
  • practices that want AI documentation or decision support but will retain qualified human review.

It may be a weaker fit for:

  • buyers requiring a public base price before sales contact;
  • organizations that cannot tolerate reliance on internet and cloud availability without a tested downtime process;
  • practices whose critical analyzer, imaging device, pharmacy, accounting, or specialty workflow is not proven in the demo;
  • teams expecting every historical record and file to migrate or export without a written conversion matrix;
  • buyers who need a fixed contractual service level or support schedule that Shepherd will not include;
  • practices seeking autonomous AI clinical decisions rather than assistive tools subject to veterinarian oversight.

Shepherd Veterinary Software Demo Scorecard

Use real test data and give each item a pass, conditional pass, or fail.

Commercial and contract

  • Produce a line-item three-year total cost.
  • Reconcile the proposal, Service Agreement, EULA, privacy terms, and partner agreements.
  • Explain the one-year term and 14-day termination language in writing.
  • Define renewal increases, suspension, cure, and post-termination access.
  • Confirm what “unlimited,” “included,” “free,” and “no implementation fees” mean.

Clinical and daily operations

  • Complete, correct, sign, reopen, and amend a complicated SOAP.
  • Trace every change into treatment plan, invoice, inventory, discharge, and audit log.
  • Run outpatient, surgery, hospitalized, urgent, mobile, chronic, and refill workflows.
  • Test scheduling, whiteboard, forms, estimates, portal, messages, reminders, and staff tasks.
  • Verify permissions for veterinarians, technicians, CSRs, managers, and temporary staff.

Finance and inventory

  • Reconcile a day from invoice through Shepherd Pay settlement and accounting.
  • Process deposits, split payments, refunds, chargebacks, stored cards, credits, and bad debt.
  • Test lots, expirations, partial units, transfers, returns, recalls, and controlled-drug records.
  • Reproduce five critical financial and operational reports.
  • Verify multi-location and legal-entity separation.

AI and integrations

  • Test TranscribeAI with challenging audio and measure correction time and error severity.
  • Test DiagnoseAI with incomplete, contradictory, and atypical cases.
  • Demonstrate source references, human approval, permissions, retention, and audit history.
  • Run every required lab, imaging, pharmacy, payment, communication, and accounting connection.
  • Create, detect, retry, and audit an integration failure.

Migration, security, and exit

  • Complete a test conversion with counts, control totals, exceptions, and sign-off.
  • Review the latest SOC 2 report, subprocessors, recovery evidence, and incident terms.
  • Demonstrate MFA, roles, activity logs, support access, and emergency read-only access.
  • Deliver a representative full CSV export plus the promised backup format.
  • Prove how attachments, images, messages, financial history, and audit logs leave the system.

Final Recommendation

Shepherd has a credible modern feature set and an unusually coherent connection between the clinical record and practice operations. Its public materials make the strongest case for practices that want SOAP workflow, charge capture, inventory, payments, communication, and integrations without a local server.

The buying decision still depends on evidence that marketing pages cannot provide. Obtain the base price and every variable fee. Resolve the term and termination language. Test the exact integrations and payment reconciliation. Run a sample conversion and exit export. Review current security, privacy, AI, support, and availability terms. Put the accepted workflows and data requirements into the Service Agreement.

If Shepherd passes that process with the practice's real cases and people, it merits a controlled pilot. If the vendor cannot define migration completeness, export usability, costs, or support responsibility, the risk is too high regardless of interface quality.

For the physical layer around rollout—not a substitute for vendor-approved equipment—use our veterinary intake and kennel workflow guide to build a separate checklist for scanners, label printers, privacy accessories, workstation power, and intake organization.

Official Sources Checked

All listed source URLs returned HTTP 200 when checked on August 9, 2026. Dated vendor articles and PDFs are identified as such and are not treated as a current contract or independent performance evidence.