Appearance
Pets
Book visits for your clients' pets: each pet's card with its breed, size, what to watch for and the groomer's notes, a booking that says whose it is, services offered only to the species and sizes they fit, vaccine records with a reminder before they run out, and a report of each groom sent to the owner.
kitloom/ · admins: kitloom/, kitloom/
Video lessons
Recorded in the Filament admin; the Nova admin works the same way.
Pets for a groomer, a vet's front desk or a trainer. Each client's card holds their pets, and a visit is booked for one of them: Full groom — Rex. The groomer finds the pet's breed, size and what to watch for before the dog is on the table, and the notes of the last groom.
The admin is kitloom/booking-pets-filament or kitloom/booking-pets-nova.
A pet's card
A pet belongs to one client's card. It has:
- its name and species (a dog, a cat: the species are yours to set, see Settings);
- breed, sex, neutered, coat and colour;
- its birthday. A guess will do: the age is shown round, "3 years", "7 months";
- its weight in kilograms, and its size. With a weight, the size follows from it. Without one, you choose the size;
- about: what the client says of it, in their own words;
- health: allergies, conditions, medication, and the vet (a name and a phone);
- plays with others: yes, no or not known yet;
- what the staff must watch for: short lines, such as Muzzle for nails or Not with other dogs. The staff see them first, wherever the visit is shown. The client never does;
- the salon's note, which the client never sees either;
- a photo.
All of it is plain text. Formatting typed or pasted into it is dropped.
The groomer's notes are kept with the pet, newest first: what was done (#4 blade, teddy face) and what to remember (nervous at the dryer). Each is signed, dated and may name the visit it is about. A note is added, never changed. The next groomer starts from the last one.
A pet's visits are the bookings made for it, newest first, with their photos.
A pet is never deleted
- Inactive: the pet no longer comes. It leaves the booking form.
- Passed away, with the day. It leaves the booking form, and "time to book again" never names it again. The client may mark it themselves.
Either way its visits and notes stay. A pet is removed only when its client asks to be forgotten (see Personal data).
Services by species and size
Full groom, small and Full groom, large are two services, each with its own minutes and price. For each service you may say which pets it is for:
- species: dogs only, cats only, or any;
- sizes: small and medium only, or any.
A service you say nothing about is for every pet. A pet is offered, and booked, only the services that fit it. A pet whose size is not known yet is not turned away by size: you see it at the door.
Booking for a pet
- On the site and in the app, a client who is signed in picks one of their pets, or adds a new one with its name, species, breed, size, birthday and a few words about it.
- A guest (not signed in) names their pet. It goes on the client card their email or phone matched. If that card already has a pet of the same name, the booking is for that pet: what the guest typed fills only what the card lacks and changes nothing the salon wrote. The guest is never shown what the card holds.
- The salon books for any pet of the client's card, and may correct afterwards whose visit it was.
- A visit that does not fit is refused, in the client's words: Full groom, large is not offered for Pip.
- A series of visits is for the same pet as its first.
- "Time to book again" is about the pet whose visit it was. Bella is reminded about even when Rex has a visit ahead. A pet that passed away or no longer comes is never reminded about.
Vaccines
The salon keeps a record of each pet's vaccines: which vaccine, the day it is valid until, and a copy of the paper (a photo or a PDF).
- Which vaccines are yours to set (see Settings). To start: Rabies, required for dogs and cats; DHPP, Bordetella and FVRCP, required for none — they are on the list so a record of them can be filed.
- A record is told by the client (on the booking form, later from their account or the app) or filed by the salon. The client's word is To verify until the salon looks at the paper: Verify it, or Reject it with a reason. A record the client gave counts for booking until the salon rejects it, so a new client can book online the same evening.
- The record that counts for a vaccine is the one valid the longest, of those not rejected. Older records stay on the pet's page.
- A client cannot send a record that has run out already. The salon may file one, for the history.
- No record is valid for more than 3 years from today, for anyone: no vaccine is given for longer, and a date further ahead is a typo or worse. A developer changes it with
kitloom-.booking- pets. vaccines. max_ years - The paper is a JPEG, PNG or WebP picture or a PDF, judged by what the file holds, not by its name, up to 8 MB. It is kept as it was sent, on the same private disk as the visits' photos, and opened only through an address that lives a quarter of an hour, given to whoever may see the pet.
Asking for vaccines at booking
Vaccines asked at booking has three settings:
- Warn (to start): a booking goes through. The staff see what is missing or to verify, in red, as the last line of what to watch for: Vaccines: Rabies — none on file. On the booking form, a new pet has a date for each required vaccine; the client may leave it empty.
- Require: a booking from the site or the app is refused until every vaccine asked of the pet's species is valid on the day of the visit. A new pet's dates must be given; a client's own pet with a record run out is refused with Please contact the salon about a new record. Your own bookings (the front desk, the admin, a walk-in) are never refused. A guest is judged by what they type alone: they are never told what the salon has on file for a pet of the same name.
- Off: nothing is asked, drawn or warned about, anywhere.
The dates a client types on the booking form are kept as records To verify. On a pet the salon already knows:
- a client signed in to their own account replaces the record that counts only with a later date;
- a guest (not signed in, matched by email or phone) never replaces a record that is still valid on the day of the visit, verified or not: their date is kept only for a vaccine with no record, or one that has run out by then. Someone who knows a client's email cannot push your verified paper aside, silence its reminder or vouch for the pet's next visits.
A visit the client moves themselves is asked about again: under Require, a move to a day a required vaccine no longer covers is refused (Rex's vaccines are valid for the day booked but not for the new one: Rabies. Please contact the salon about a new record.), and the visit stays where it was. Your own moves are never refused; when you move a visit past a record's end, the staff's alert on it says so — Rabies — runs out on …, before the visit.
Asking the client for a record
When a client books a visit for a pet themselves — on the site or in the app — and the salon has no record of a vaccine it asks of that pet's species valid on the day of the visit, the client gets an email asking for it (under Warn and Require; never under Off). It names the pet, the vaccines and the day, and:
- where your theme has My pets in the account, a Send a record button leading there — a photo of the paper will do;
- otherwise, asks them to bring the paper to the visit or to send a photo of it in reply (replies go to the bookings' notification address when one is set).
One email per pet in 7 days, however many visits are booked. Never for your own bookings (the front desk, the admin, a walk-in, a series), a pet that passed away or no longer comes, or a client without an email. It is written in the language the client booked in. The email is checked again when it goes out: nothing goes once the record has come in, or once the visit is cancelled, declined or moved to another day. A developer turns it off with kitloom- or changes the days with vaccines. (0 — never).
Before a record runs out
Every day at nine in the morning, in the salon's timezone (Settings → General; the server's when it cannot be read), the client is sent one email per pet naming each required vaccine that runs out within the days you set (14 to start; 0 — never), once per record. No email about a pet that passed away or no longer comes, nor to a client who switched reminders off or has no email. The email is checked again when it goes out: a record replaced or rejected meanwhile is left out, and nothing goes once the vaccines are off, the client switched reminders off, or the pet passed away.
With kitloom/notifications, you are told in your chat when a client sends a record, or types its date on a booking: Vaccine record to check.
The visit's report
At the end of a visit you write the client a short report of it — what MoeGo and Gingr call a report card:
- What was done, in the groomer's own words: Bath, blow-dry, #5 on the body, teddy face, nails, ears.
- How it went: Loved it, Calm and easy, A little nervous or A hard day, and a line about it if you like (the dryer scared him).
- What we noticed (optional): a mat behind the ears, a red patch, long quicks.
- Come back in (optional) 1 to 26 weeks: We suggest the next groom in about 6 weeks.
- The visit's photos: those already kept with the booking (the ones you or the client added to the visit). They are not copied: the report shows them.
One report a visit, for a visit of a pet that took place — begun, or marked done; never one cancelled, declined, missed, still waiting for its deposit, or still ahead. It is a draft until you send it: the client sees nothing of it before. Sent, it goes to the client by email and shows on the pet in their account (where your theme has My pets), with New until they open it. A report can be corrected at any time, and the client is not emailed again for a correction — only when you send it again. Two people pressing Send at once mail the client once. A report is never deleted.
A report follows its visit: when you correct which pet a visit was for (another pet of the same client), the report moves to that pet. When the visit is left for no pet, or given to another client, the report stays where it was and becomes a draft again, and cannot be sent until the visit is that pet's again (This visit is no longer this pet's: correct the report before it is sent.). An email already waiting to go out is not sent then either.
Write it for the client. The groom notes, what the staff watch for and the salon's note are yours and never go into a report unless you type them there. What you type is kept as typed — plain text, nothing of a web page.
The email, in the language the client booked in, to the address on their card: Rex's groom today, what was done, how it went, what was noticed, when to come back and who groomed, and a link to book the next visit. No photo is attached or linked in it — a visit's photos are private and an email lives for years: where your theme has My pets, the email says how many photos there are and links to the account, where the client sees them after signing in; otherwise it says nothing about them. A client without an email address is not a refusal: the report is marked sent and shows in their account. The email is checked again when it goes out: nothing goes for a report taken back to a draft or for a pet that passed away since. A mail that fails never undoes the sending.
Who writes and sends a report: the bookings managers, and a staff member for the clients who booked with them — the same people who verify a vaccine record. A client never writes one. The vaccines' mode (Off, Warn, Require) changes nothing about reports.
Settings
Bookings managers change them.
- Species: the animals you take, each with a key that never changes (
dog) and a name clients read (Dog). Dogs and cats to start. To rename a species, change its name, not its key: the pets keep the key. - Sizes: from the smallest up, each to a weight in kilograms. To start: Small to 10 kg, Medium to 25, Large to 40, Extra large above. The last has no upper weight.
- Vaccines: each with a key that never changes (
rabies), a name clients read (Rabies) and the species it is required for. A key that records on file use cannot be removed or renamed: change its name instead, and untick its species to stop asking for it. - Vaccines asked at booking: Off, Warn (to start) or Require (see Asking for vaccines at booking).
- Days before a vaccine runs out that the client is told: 14 to start; 0 sends no reminder.
- The booking form asks for a pet: off to start. On, a visit booked on the site or in the app must name a pet. Your own bookings (the front desk, the admin) never must. Switch it on only after your mobile app is updated: switching it on turns away the bookings made from builds of the app that do not ask for a pet yet. The settings page says so under the switch.
In the admin
The section Pets sits next to Bookings, in both admins (kitloom/booking-pets-filament, kitloom/booking-pets-nova).
- All Pets: every pet with its photo, client, species, breed, size and age. What the staff must watch for shows in red; a pet that passed away or is inactive is marked. Filter by client, species, size or status; search by the pet's name or the client's. A staff member sees only the pets of the clients who booked with them.
- A pet's form: the client (chosen once: a pet stays on its client's card), name, species, breed, sex, neutered, birthday, weight, size, coat, colour, plays with others, vet, about, health, Watch for (one line each), the salon's note and a photo. Give a weight and the size follows from it; choose a size only for a pet without one. What cannot be saved is said on its field.
- A pet's page: Watch for on top, then what it is, its photo, Groom notes newest first with Add a note, and its Visits newest first with their photos, each opening its booking. Mark as passed away (with the day) and back, Deactivate and Activate. There is no delete.
- Pet card on a booking (Filament: the bookings list, a booking's page and the calendar's visit): the pet's Watch for, its details and last notes in a panel at the side, and a note about this visit. Shown only on a booking for a pet. In Nova, open the pet from All Pets (filter by the client).
- Services by pet (managers): which species and sizes each service is for. Filament lists every service and changes it in place; Nova lists the services that are not for every pet, a new line adds one, and For every pet takes it off the list.
- Settings (managers): the species, the sizes, and whether the booking form asks for a pet (see Settings above).
- How it works: this page.
Who may do what
The module has no permission of its own.
- Bookings managers (
manage_) see and change every pet, the services' rules and the settings.bookings - A staff member (
manage_, linked to a staff member) sees and changes the pets of the clients who booked with them, and writes notes about them.own_ bookings - A client sees and changes their own pets, and may mark one as passed away. They never see or change what the staff watch for, the salon's note, plays with others, whether the pet is active, or the groomer's notes. They read the reports sent to them, never a draft, and never write one.
Moving in
With kitloom/spreadsheets, Pets comes in from a spreadsheet and goes out to one. Bring the clients in first (Booking clients). Each row finds its client by the owner's email, else their phone, and the pet on that card by its name. A row whose client is not found is refused, never a client made up from it. Species and sizes may be written by their key or their name. A weight sets the size. The lines to watch for are apart by |.
Personal data
With kitloom/privacy, a client's pets are in WordPress's Export Personal Data: everything on each pet, its health and the staff's lines included, its vaccine records, the visits' reports sent to the client (not your drafts — a draft is your working text, said to nobody yet), and the groomer's notes. Erase Personal Data removes them all, their notes, records, reports (drafts too), photos and papers, with the client — as does Forget client on the client's card. The visits themselves stay in the salon's books, without the client's details, as kitloom/bookings keeps them.
For the developer
- Data (the site's table prefix in front; no foreign keys, as in the bookings):
booking_(pets Models\, registry keyPet booking_):pet client_(a bookings card),id speciesandsizeas keys of the settings,weightin kg,alertsa JSON list,passed_a date,on active;photoa path on the bookings' private photo disk (Visit, folderPhotos:: disk() pets/), served signed bykitloom..booking- pets. photo booking_(pet_ visits Models\,Pet Visit booking_):pet_ visit booking_+id pet_, unique together. One a booking now; the table allows several.id booking_(pet_ notes Models\,Pet Note booking_):pet_ note pet_,id booking_,id author_,id body,created_.at booking_(pet_ services Models\,Pet Service booking_):pet_ service service_(unique),id speciesandsizes(JSON lists, null for any).booking_(pet_ vaccines Models\,Pet Vaccine booking_):pet_ vaccine pet_,id kind(a key of the setting),expires_,on file(a path on the bookings' photo disk underpets/, served signed byvaccines/ kitloom.withbooking- pets. vaccine- file Content-),Security- Policy: sandbox status(reported,verified,rejected),verified_,by verified_,at note,reminded_. Never deleted but with its pet.at booking_(pet_ reports Models\,Pet Report booking_):pet_ report pet_,id booking_(unique: one a visit),id author_(who wrote it first),id done(text, at most 2,000 characters),mood(one ofPet:Report:: MOODS great,good,nervous,hard;Petgives their labels),Report:: moods() mood_(300),note noticed(1,000),next_(1–26),weeks sent_(null — a draft),at seen_(the client opened it). Never deleted but with its pet. The photos are the bookings'at booking_of the visit, never copied.photos
- Settings (
Booking, read throughPets Options Pet):Settings booking_andpets_ species booking_(JSON lists ofpets_ sizes {key, label}, the sizes withmaxin kg, null for the last),booking_(bool),pets_ required booking_(a JSON list ofpets_ vaccines {key, name, required},requiredthe species' keys),booking_(pets_ vaccine_ mode off,warn,require),booking_(int). Written bypets_ vaccine_ days Setting,Writer manage_. The paper's size limit isbookings kitloom-(8192); the furthest valid-until date,booking- pets. vaccines. max_ kb vaccines.(3) from today. A save ofmax_ years booking_that drops a key the records use is refused.pets_ vaccines - Writers and readers:
Petis the only writer of pets, notes, vaccine records, the visits' reports, the services' rules and a booking's pet, with the actor:Writer save(),passed,On() set,Active() set,Photo() remove,Photo() note(),vaccine(),verify,Vaccine() reject,Vaccine() report(),send,Report() report,Seen() set,Rule() attach(),set.Visit() forget()is for a forgotten client alone. A record landing asreportedsendsEvents\(Vaccine Reported vaccine,Id pet,Id actor) once committed.- A report:
report(Booking, $input, $actor)writes or corrects it —doneandmoodrequired on a new one, a key left out of a correction keeps its value, null clears it — on the booking's row lock;sendsetsReport($report, $actor, again: false) sent_, sendsat Events\(Report Sent report,Id pet,Id booking,Id actor) once committed and queuesNotifications\after the commit in the booking's language (a failure is reported, never thrown); a sent one goes again only withVisit Report again. The first send is claimed in one statement (sent_), so two at once mail once. It refuses (at IS NULL ValidationonException report) a report whose visit is no longer its pet's (Reports::);belongs To Pet() Visitasks the same when the queue sends it, and its "today" is the day it was sent.Report:: should Send() setcarries the visit's report to the new pet of the same card; to no pet or another card's, the report stays and becomes a draft (Visit() sent_,at seen_cleared).at reportsetsSeen() seen_once, as the system.at filemarks one sent without the email or the event — a demo's or an import's history, as the system, never from a screen;Report($report, $at, $seen) $seennot before$at.report()judges the booking as its locked row says now, not as the caller holds it. Who:Peton the pet's card, or the system. The texts lose what looks like a tag and control characters, and keep the rest as typed (Access:: as Salon() <3stays). Reports(bound per request):ofnewest visit first,Pet($pet, $drafts = false, $limit = 20) of(one query for a page, drafts included),Bookings() of,Booking() takes(which visits take a report — done, or pending/confirmed once begun — asking no query; the writer's own rule,Report($booking, $now = null) Reports::andANYTIME ONCE_),BEGUN reportable($pet, $limit = 50)(the pet's visits that take one and have none yet, newest first),present($report, $viewer, $salon— the client's view throws on a draft; the photos areSide) Visitfor thosePhotos:: present() Visitlets the viewer see (the system on the salon's side, all). For the client's side, every read through one rule,Photos:: sees() for(sent, the visit still the pet's inClient() booking_and on the pet's card — the site's API's client view too):pet_ visits with,Sent Count() latest(each pet's newest sent ones in one query),Of() page(),older(after a report held),Than() sent.Of() Vaccines(bound per request):of(),current(),current(one query for a page of pets),Of() missing(),unverified(),state()(none,ok,check,due),line()(the staff's),file,Url() to.Check() Pets(bound per request):of,Client() of(one query for a list),Bookings() history()(visits with photos and notes),fits(),unfit(),services,For() age(),line(),photo,Url() subject().Petsays who sees and writes which pets, from the bookings'Access Booking.Access
- The bookings ask through their
Contracts\, which this module binds (Visit Subject Visits\; off withPet Subject kitloom-). Inputsbooking- pets. subject. register subject(a pet's id) andsubject_(new name,species,breed,size,birthday,about, andvaccine_— a<kind> Y-— for each vaccine required of some species; each such field carries them- d speciesit is asked of). The staff'salertsof a subject end withVaccines::for the booking's day.line() vaccines_onasked_ at booking_: when the client was last asked for a record after a booking (pets Visits\, on the bookings'Ask For Vaccines Booking, after the commit;Requested Notifications\, queued, checked again at send time). Claimed byVaccine Asked Petin one statement before the email is queued (two bookings at once ask once), given back byWriter:: claim Vaccines Ask() releasewhen it cannot be sent. A failure anywhere in the listener is reported, never thrown at the booking.Vaccines Ask() booking-runs daily from the scheduler at 09:00 in the salon's timezone, read when the schedule is built (the application's if it cannot be read);pets: remind --lists without sending.dry- run Notifications\, queued, checks again at send time.Vaccine Expiring - A client's move (
Booking) asksWriter:: reschedule() Pet: underSubject:: moving() require,Vaccines::on the new day refuses it withmissing() Booking; the salon'sRefused:: subject() update()is not asked. - Around, each tagged only while its module is installed (switches in
config/):kitloom- booking- pets. php - AI agents:
booking_,pets_ list booking_(withpets_ get vaccinesandreports, the salon's view, drafts included),booking_,pets_ save booking_,pets_ note booking_(add, verify, reject; no file),pets_ vaccine booking_(a visit's report by booking code or id, written or corrected;pets_ report send:sends a draft and mails nothing for one already sent, so a call tried again is safe;true send_mails a sent one once more), and theagain: true booking_block ofpets describe_(the vaccines asked and the mode,site report_);moods /(kitloom/rest-api): the salon sees the pets of the clients it sees, a client their own without the salon's fields; a read-onlyapi/ v1/ booking- pets vaccines(state and the records that count, without the salon's note) andreports(at most 20, newest visit first: the client's view — sent ones — for a client's token, the salon's with drafts for whoever writes the pet's as the salon); never deleted;- the
booking-sheet (kitloom/spreadsheets);pets: pet - the personal data exporter and eraser,
kitloom-;booking- pets - the owner's notice
pet.(kitloom/notifications;vaccine_ reported kitloom-).booking- pets. notifications. register
- AI agents:
- Backups: the vaccines' papers sit in the bookings' photo folder, which kitloom/bookings already hands to kitloom/backup (
Backed); the module adds no folder of its own.Up Photos - Two cards merged into one (
Clients) take their pets along.Merged - A client forgotten (bookings'
Client, heard byForgotten Pet) takes their pets, notes, reports, visit rows and photos with the card, whichever eraser or provider comes first.Writer:: follow Forget() - A report stays on its pet: when the salon gives the visit to another client, the first client no longer reaches it (their side reads only reports of visits still on the pet's card); writing it again moves it to the visit's pet of the moment.
For a theme
What a theme draws for the client's own pets. A theme that draws none of it loses nothing: nothing below is shown anywhere until a theme uses it.
The routes, / (the session's user, the web group as the bookings' own client routes; a guest gets 401, another card's pet 404 on every route; errors are WordPress's JSON, a form's by field in data.):
| Route | Does |
|---|---|
GET pets | {pets: — every pet of the card: those still coming first, then those the salon made inactive, the ones passed away last |
POST pets | adds one: name, species (required), breed, sex, neutered, birthday, weight, size, coat, colour, about, medical, vet, and vaccine_ dates (kept as records To verify); 201 {pet}. A user who never booked gets a card of their own with it |
POST pets/ | changes the same fields; {pet} |
POST pets/ | multipart photo; {pet} |
DELETE pets/ | {pet} |
POST pets/ | passed: true marks it (today), false takes it back; {pet} |
POST pets/ | multipart kind, expires_ (Y-), file (optional: a picture or a PDF), note (optional); lands To verify; 201 {pet}. With the vaccines Off the route is not there (404 rest_) |
GET pets/ | the pet's further sent reports, 10 a page: with before (the id of the last report the page holds), those older than it — stable when a report is sent meanwhile; without it, after the 5 the Pet carries, counted from the newest. page from 1 (400 otherwise); before a report's id (400 otherwise), one the client reaches (404 rest_ otherwise): {reports: |
POST pets/ | the client opened it: seen_ set once; {report}. A draft, another pet's report, or one of a visit no longer on the card is 404 rest_ |
The salon's fields (Watch for, its note, plays with others, active) are never written through them: sent, they are left out. Through these routes everyone is a client, a manager or a groomer with a pet of their own too: the client's checks (no record run out already), and every record lands To verify.
Limits the salon keeps, each 422 with a code and a message to show:
booking_: a card keeps at mostpets_ too_ many kitloom-(20) pets that still come — one more added, or taken back from passed away — and at mostbooking- pets. account. max_ pets account.(60) pets in all, whatever became of them: passed away is the client's own switch, and would otherwise make room for the next. Counted under the card's row lock.max_ pets_ ever booking_: a pet that passed away, or that the salon made inactive, takes no vaccine record. Its photo and the client's own fields can still be changed — a photo to remember it by, a name spelled right — and passed away can be said and taken back (the module cannot tell whether the salon or the client marked it).pets_ pet_ not_ coming booking_: a pet keeps at mostpets_ too_ many_ records account.(30) vaccine rows in all.max_ records
A record of a kind that still waits to be checked is replaced by a new one of the same kind: the one waiting is rejected by the system with Replaced by a newer record from the client. and keeps its paper, so a client has at most one record waiting a pet a kind, and corrects a wrong date without waiting for the salon. The owner's notices about one pet's one vaccine share a key (pet-), so repeats are told as one.
Throttles: booking- (120 a minute, the reports' pages too), booking- (30, seen too), booking- (20). kitloom- takes the routes away, and so does subject. off: without the visits being for pets there is no My pets either.
Pet, the client's view (never the alerts, the salon's note, plays with others, who verified a record, nor anything of another card):
json
{
"id": 12, "name": "Rex",
"species": "dog", "species_label": "Dog",
"breed": "Golden retriever", "sex": "male", "neutered": true,
"birthday": "2021-05-01", "age": "5 years",
"weight": 31, "size": "large", "size_label": "Large",
"coat": null, "colour": null, "about": null, "medical": null, "vet": null,
"line": "Golden retriever · Large",
"photo": "https://…/booking-pets/photo/12.jpg?expires=…&signature=…",
"active": true, "passed_on": null,
"services": [3, 4],
"vaccines": {
"state": "due",
"items": [
{"kind": "rabies", "name": "Rabies", "required": true, "status": "none",
"expires_on": null, "file": null,
"rejected": {"why": "The date on the paper does not match."}}
]
},
"reports": [Report…],
"reports_more": false
}weight: kilograms, a number or null.photo: a signed address living an hour, or null.services: the ids of the active services the pet may be booked for, or null — every one.vaccines.:state none(nothing is asked of it, or the vaccines are off),ok,check(all there, something still to verify),due(something missing or run out).vaccines.: one per kind asked of its species, then each other kind it has a record of.items statusis the record that counts:none,reported,verified, orexpired(run out before today);expires_andon file(a signed address living a quarter of an hour, or null) are that record's.rejectedis{why}(whymay be null) when the newest record of the kind was rejected after the one that counts, else null. With the vaccines off: only the kinds on file, nonerequired.reports: the pet's newest reports sent to the client, at most 5, the newest visit first;reports_— there are older ones (more GET pets/). A draft is never there. A page of pets asks the database the same whatever the number of pets and reports.{id}/ reports?before=<the last one's id>
Report, the client's view:
json
{
"id": 7,
"booking": {"code": "K7Q2XW", "date": "2026-11-02", "service": "Full groom", "groomer": "Mira"},
"done": "Bath, blow-dry, #5 on the body, teddy face, nails, ears",
"mood": "nervous", "mood_label": "A little nervous", "mood_note": "The dryer",
"noticed": "A mat behind the left ear", "next_weeks": 6,
"sent_at": "2026-11-02T22:10:00Z", "seen": false,
"photos": [{"id": 3, "url": "…signed…", "thumb": "…signed…", "width": 1600, "height": 1200, "caption": null, "side": "staff", "date": "2 Nov 2026", "removable": false, "booking": null}]
}booking.: the visit's day in the salon's timezone (date Y-);m- d service: its services, as the bookings name them;groomer: its staff member.mood:great,good,nervous,hard, andmood_in the visitor's language. Texts are plain: draw them as text, keep the line breaks.label photos: the visit's photos as the bookings hand them to this client (Visit, addresses that live an hour) — those of a visit booked under their account; none otherwise.Photos:: present() seen: false untilPOST …/— draw it New and mark it when it is opened.seen
Rules, what a form needs:
json
{
"label": "Pet",
"species": {"dog": "Dog", "cat": "Cat"},
"sizes": {"small": "Small", "medium": "Medium", "large": "Large", "extra-large": "Extra large"},
"fields": [{"key": "name", "label": "Name", "type": "text", "required": true}, "…",
{"key": "vaccine_rabies", "label": "Rabies valid until", "type": "date", "required": false, "species": ["dog", "cat"]}],
"vaccines": {"mode": "warn", "kinds": [{"key": "rabies", "name": "Rabies", "required": ["dog", "cat"]}, "…"],
"max_years": 3, "max_kb": 8192, "types": ["image/jpeg", "image/png", "image/webp", "application/pdf"]},
"max_pets": 20
}fields are those of a new pet on the booking form: a vaccine_ field is shown only for the species it lists, and is there only while the vaccines are not off. vaccines. are every kind the salon keeps, each with the species it is asked of (empty: asked of none).
My pets in the account (Site\, ?section=pets) is not switched on by the module: every theme lists each section tagged, and a theme that cannot draw it would show an entry leading nowhere. A theme that draws it switches it on in its boot:
php
$this->app->tag([\Kitloom\BookingPets\Site\Account\PetsSection::class], \Kitloom\Site\Contracts\AccountSection::TAG);Its data: {pets: — the routes above as full addresses, {id} standing for a pet's id (…/) and {report} for a report's (…/), and book the bookings' page. It is there for every signed-in user while the bookings' visits are for pets, one who never booked included. Once a theme switches it on, the email asking for a vaccine record and the report's email link to it (Pets).
Tests
tests/ runs inside a kitloom application: Pet, Pets, Pet (the bookings' contract method by method), Booking (through Booking and Series), Settings, Agent, Api, Privacy, Vaccines (the writer, the files, the reader), Vaccine (the three modes through Booking), Vaccine (the command and the notice), Vaccines (privacy, agents, API), Client (booking- over HTTP), Pets (My pets, off until a theme tags it), Vaccine (the email asking for a record), Report, Reports, Visit, Client (the client's side over HTTP), Reports (privacy, agents, API), Report (a visit corrected or handed on, two sends at once, the stable page, the subject's day), French.