A veterinary practice is not an ordinary ERPNext customer. The person who pays the bill is the owner, but the thing being treated is the animal — and the clinical history, the vaccination due dates, the weight curve, the allergy notes and the microchip number all belong to the animal, not to the Customer record. ERPNext core gives you Customer, Item, Sales Invoice, Stock Entry, Batch and Serial No, and those are genuinely the right foundations for billing, retail and pharmacy stock. What it does not give you is a patient. There is no DocType that says "this Labrador belongs to this owner, was born on this date, is due for a booster in 41 days, sits in a 12 kg dosing band, and reacted badly to the last NSAID". Practices end up encoding that in customer names (Ahmed Khan - Bella), in free-text notes, or in a parallel spreadsheet nobody reconciles — and the first casualty is the vaccination recall, which is the most reliable source of repeat revenue a clinic has.

We build a proper Frappe app for this — its own repository and module, installed onto your bench with bench get-app and bench --site <site> install-app — rather than a pile of Custom Fields bolted onto Customer. The core is an Animal Patient DocType linked to the owner's Customer, carrying species, breed, sex, date of birth, neuter status, colour and markings, microchip and tag numbers, insurance reference, current weight, and child tables for allergies and chronic conditions. A Patient Visit DocType captures the consult: presenting complaint, vitals, examination findings, diagnosis, treatment plan, and child tables for procedures performed and medicines dispensed. Vaccinations get their own record — Vaccination Record stores the product given, the batch, site of administration, administering vet and a computed next-due date driven by a Vaccination Protocol you configure per species, so a puppy course and an annual feline booster follow different rules. Boarding is a Boarding Booking against a kennel or run resource, with check-in/check-out timestamps, feeding and medication instructions, and daily-rate lines that flow through to the invoice.

Technically it is all standard Frappe, which is the point — nothing here is a black box your next developer cannot read. Business rules live in server-side controller methods and hooks.py doc events: on submit of a Patient Visit we validate that dispensed quantities exist in the dispensing warehouse, create the Stock Entry or Delivery Note against the correct Batch (respecting expiry, FEFO first), and optionally raise the Sales Invoice against the owner with consultation, procedure and medicine lines already populated. Dose calculators and species-conditional field visibility run as Client Scripts on the visit form, so a vet entering a weight sees the mg/kg figure immediately with no round trip. Recalls run from a daily scheduler_events hook that queries due and overdue vaccinations and queues email, SMS or WhatsApp notifications through your configured provider, honouring per-owner consent and a suppression flag so a deceased or transferred animal is never messaged. Everything is exposed over the standard Frappe REST API (/api/resource/Animal Patient) plus a small set of @frappe.whitelist() methods for the operations that need transactional integrity — check-in, dispense, close-visit — giving a reception tablet or future mobile app a clean contract. Permissions are real Frappe permissions: Role Profiles for Veterinarian, Vet Technician, Receptionist and Practice Manager, permlevel-protected clinical fields hidden from front desk, and User Permissions to scope records when you run more than one branch. Print Formats cover the vaccination certificate, discharge summary and boarding agreement. We target Frappe/ERPNext v15 and v16 and build against the exact version your bench runs.

This is build-to-order, not a marketplace download — there is no instant zip file, and nothing is installed until you have accepted a written scope. We start with a short scoping call: species mix, the vaccination protocols used in your country, whether you dispense from one pharmacy or several, how boarding is priced, and what your existing ERPNext already contains. That becomes a fixed specification with DocType-level detail. Typical delivery is 2 to 4 weeks from confirmed scope, depending on how much of the protocol and pricing logic is bespoke. You get a staging install first for UAT against your own data with a documented rollback, then the production install, a training session for vets and reception, and a post-go-live support window while the practice settles in. The source lives in a git repository we hand over to you, so you are never locked to us.