The certificate that reads itself

Every groomer has asked for the rabies certificate and been handed last year’s photocopy. The date on the paper is the only part that matters, and nobody in the driveway is reading it carefully. Slickerbook has kept vaccination records on the pet for a while: the vaccine name, the date given, the expiry date, and a daily check over the ones coming due. What it never had was cheap entry. Typing a certificate in by hand, mid appointment, does not happen. Two things changed that.

The certificate reads itself

Upload a certificate for a pet, from the pet dialog, the customer’s own page, or the customer’s portal, and it goes to a local AI. Everything after that is code. The accuracy is measured, not assumed. On a clean printed certificate the model read 15 of 15 fields, twice. On the same certificate rotated a few degrees, blurred, grained and re-compressed as a phone photo, it read 10 of 15: every date right, the pet and owner names right, and all three lot numbers wrong. A warm read takes about 13 seconds; a cold model load about 38. The vision model this replaced scored 1 of 15 on the photo, and it is not the fallback.

A person still confirms

The reply is proposed rows, not records. Dates the code can parse and vaccine names it recognises are marked high and arrive pre-filled. A lot number is marked low every single time, because the trial above is exactly where a lot number gets invented and a wrong one looks identical to a right one at a glance. A date the code cannot parse is low. So is the clinic phone number, for the same reason as the lot number. One check stands on its own. The name on the certificate is compared with the name on the pet, and when they differ a red banner says so. The wrong animal’s paperwork is the mistake that costs the most, and it is the easiest one to miss.

Whoever has the phone can file it

The reader is on the staff side and in the customer portal. At intake it takes the paperwork a new customer hands over. At the front desk it takes one filed against an existing pet. A customer can photograph the certificate and upload it themselves, and the shop ends up with records nobody typed. Nothing reaches the pet’s record until a person saves the rows. The certificate is stored either way, under the pet and behind a signed link, so the copy the owner handed over does not get lost while the details are being checked.

The reminder runs on its own

Once the expiry date is on the record, the nightly check does the rest. The expiring list includes records that have already lapsed, so the ones nobody caught stay in front of you. The reminder goes out on the customer’s preferred contact, clamped server-side to the channels the shop actually sends on, so an email-first customer gets an email instead of silence. The message can name the pet, the vaccine and the days left, and sign with the business name. The record is marked when a reminder goes out, so each vaccination is reminded once rather than once a night, and a provider failure leaves it unmarked for tomorrow’s run to retry. That is the shape of it. A certificate enters the record with a person behind it, and the expiry date keeps counting after everyone has driven away.