← Back to Platform
Partially built — MyTime-integrated today, own-stack build in progress

Booking Engine

The client-facing front door

The moment a phone call or a walk-in question turns into a scheduled, paying appointment — and the point where the client record, the pet record, and the service record all get created for the first time.

Add-on — not part of the core four engines. An add-on for shops that don’t already have a booking system they’re happy with. Bark & Purr itself runs on a third-party booking tool (MyTime) alongside the core platform — proof the platform plays fine without owning booking.

Why the front door matters

A clunky or rented front door costs more than a bad first impression.

Booking is the first transaction — the moment a prospective customer commits. It's also the point where the client record, the pet record, and the service record all get created for the first time. A booking flow that's off-brand, clunky, or owned entirely by a third-party vendor means the business is renting its own most important moment: the one where a stranger becomes a paying customer.

Honestly, today

Brand-owned experience today. A fully owned stack, in progress.

Where it stands

For the reference tenant, Bark & Purr, the live booking page is backed by MyTime, an outside vendor system. The booking flow's client-facing experience is Bark & Purr's own brand — the look, the voice, the steps a customer sees — but the underlying scheduling, pricing, and client-record engine on the other side is MyTime's.

The platform's design intent, and the direction this module is actively moving, is to own the full stack: a self-contained booking engine, already partially built, that replaces the vendor dependency entirely — so the business controls its own pricing rules, its own client data, and its own economics instead of renting them.

That transition is in progress, not finished. The replacement engine can already create a client, a pet, and an appointment, and send a confirmation email. Payment processing, automated reminders, and cancellation handling in the new stack are still being built out.

How it fits the platform

Configurable by design — not a shipped plug-and-play framework yet.

The platform is designed so Booking can run either way by configuration: integrated with an existing vendor or PMS system a tenant already uses, or fully self-contained on Valet's own stack. That flexibility is the platform's design intent, not a shipped, generic integration framework today. We won't market it as plug-and-play with any PMS — the honest description is: a brand-owned booking experience today, moving toward a fully owned stack, tenant-configurable by design.

Step one

The client books

Direct, or through an integrated vendor system — the client's first contact with the brand, on the brand's own booking page.

Step two

Three records, created once

The client record, the pet record, and the service record all get created here, for the first time — the foundation everything downstream depends on.

Step three

It feeds Compass

That appointment lands in Compass as the day's work — staffing, workload, and the schedule as it's actually unfolding.

What's live vs. what's still being built

The own-stack engine, piece by piece.

Create client, pet & appointment recordsWorking today
Confirmation email on bookingWorking today
Payment processing (own-stack)Still being built
Automated reminders (own-stack)Still being built
Cancellation handling (own-stack)Still being built
Generic multi-vendor plug-in frameworkDesign intent, not shipped
See it on your shop

Ask us how the Booking Engine fits your setup.

Whether you're already on a vendor system or starting from scratch, we'll walk you through exactly what's live, what's in progress, and what that means for your numbers.

Book an Executive Briefing → Back to Platform →