The Bath That Never Happened: Grooming Requests on a Boarding Stay

A Small Failure With a Long Memory

A family books ten nights over the holidays. On the booking form they tick the box for a bath before pickup. They are picturing the drive home with a clean dog.

Ten days later they collect a dog that smells like a kennel.

Nothing dramatic happened. Nobody was negligent. The request was made at booking, it went into a notes field, and by day three it was four screens back. No one saw it again.

That is the whole failure. It costs you thirty dollars of revenue and a piece of trust that is much more expensive to replace.

Why the Notes Field Loses

A grooming request attached to a stay is a piece of work with a deadline, and the deadline is somebody else's checkout date.

A notes field cannot carry a deadline. It cannot sort. It cannot age. It cannot tell you that the dog in run four goes home tomorrow morning and still has no groomer assigned.

So the request survives exactly as long as somebody remembers it. Over a ten day stay, across three shifts and a weekend, that is not a system. It is luck.

Make the Request a Real Thing

The fix is to create an actual appointment the moment the owner ticks the box.

It has no groomer and no time yet. That is fine. It has a status that says requested, it is attached to the stay, and it generates a staff notification. It is now a row that exists, not a sentence in a text box.

Once it is a row, it can be worked. Staff see a requests queue sorted most urgent first. Urgency comes from the stay, not from the request date, because what matters is how soon that dog goes home. A request on a stay ending tomorrow outranks one made yesterday on a stay ending next week.

That ordering is the feature. It puts the right dog at the top of the list without anybody having to think about it.

Attach It to the Stay, Not to the Booking

One design detail is worth explaining, because it decides how much of your business the feature covers.

If the grooming request points at one kind of record, it only works for that kind. A board-and-train dog going home after four weeks is left out, and that is arguably the one that matters most. That family has spent thousands of dollars and is about to see their dog for the first time in a month.

Attaching the request to the stay in a general way covers both. In Pet Ops a request can hang off a boarding stay or a training enrollment, so an overnight boarder and a four week board-and-train dog work the same way. Day boarding is a boarding stay priced by the day, so a dog in for the day and going home clean is the same path again.

The Warning at Checkout

Everything above still fails if nobody looks at the queue on the right day.

So the last piece is a warning at boarding checkout. If a dog is going home and it has a grooming request that is still unassigned, the person doing the checkout is told before the dog walks out.

That is the point of the entire feature. The queue is useful. The warning is what makes the failure impossible rather than unlikely.

It is worth being careful about how a warning like that is built. Boarding checkout is the most load bearing screen in a kennel. A warning must be strictly additive and it must never block. A checkout with no grooming attached has to behave exactly as it did before, byte for byte. Getting this wrong to fix a thirty dollar bath would be a bad trade.

One Invoice or Two

A practical question follows: does the groom go on the boarding invoice.

In Pet Ops it does not. Grooming writes its own invoice.

That is not an accounting preference. Boarding invoices get recomputed when a stay changes, and a recompute that regenerates boarding lines can drop lines it does not know how to rebuild. A grooming charge sitting on a boarding invoice is a charge waiting to disappear during a correction. Keeping grooming on its own invoice means the groom cannot be silently erased by an unrelated boarding edit.

What This Is Really About

Boarding software and grooming software usually live in different products, or in different corners of the same product that do not talk. The bath before pickup is the exact place that gap becomes visible to a customer.

Closing it is not a big feature. It is a request that is a real row, a queue that ages, and a warning at the door.

Pet Ops handles it in boarding and grooming software that runs on one pet record, alongside the wider dog grooming software.