You probably already have somewhere to type a date
The short version
- A vaccine field stores what a person typed; that is a different claim from what the document says.
- Blocking a booking on an empty field catches omissions, not mistakes.
- The expensive failure is a false pass: a pet marked current that is not.
- Ask what your current tool does when it is unsure, since a tool that is never unsure is never checking.
Most pet-business platforms include a vaccine field or two: somewhere to record a vaccine name and a date. A staff member reads a certificate, types what they see, and the platform stores it. Some will flag or block a booking when the field is empty or the date has passed.
That is genuinely useful and worth saying plainly, because the usual version of this argument pretends otherwise. A structured place to keep the value beats a note in a margin, and a hard block on an empty field catches the pet nobody got around to.
What it does not do is look at the document. The field holds whatever was typed, whether that matches the certificate, matches an expired copy, or matches nothing at all.
The failure mode that costs you
Compliance tools can fail in two directions, and they are not equally expensive.
A false fail holds out a pet that was actually fine. It is annoying, it generates a phone call, and it gets corrected within the hour because the owner is standing there objecting.
A false pass marks a pet as current when it is not. Nobody objects. It stays wrong until an inspection or an incident, and at that point the fact that a staff member typed it in good faith is not much of a position to argue from.
A field cannot distinguish between a carefully confirmed date and a rushed guess at a busy counter. On screen they are identical. That is the whole gap, and it is why the interesting question is not whether your tool stores a date but whether anything ever checked it.
Four questions worth asking your current setup
This is a capability question rather than a brand question, and you can answer it about whatever you are already using in about ten minutes.
- Is the certificate itself stored, or only the values transcribed from it? An inspector asks for the document.
- Where does the expiry date come from: the certificate, or a term someone assumed?
- What happens when the evidence is unclear? A system that cannot report uncertainty is not checking, it is accepting.
- Who does the chasing when a record approaches its date, and is that a person remembering or the system acting?
If the answers are comfortable, you have what you need and this page is not for you. Most operators find question two or four is where it gets thin.
What verification changes, and what it does not
PawPermit starts from the document rather than a text box. The owner uploads a photo or PDF, the system reads it, pulls the vaccine details and dates off it, and marks the record current when it is confident. When a scan is unclear it flags that record for a person instead of guessing, so somebody confirms the handful that need it rather than the whole pile.
It also does the part a stored field cannot: as a record approaches the expiry date found on its own certificate, the owner is emailed for a fresh one. Worth stating the boundary honestly, since it is the question an evaluator should ask of anyone including us: that follow-up covers pets with a verified record and a date to run against. A pet whose owner has never uploaded anything stays on your worklist until you request it again.
None of this replaces a booking system, and it is not trying to. The question is narrower: when someone asks you to prove a pet was current, does your answer rest on a document or on a keystroke?