Your booking page
Your catering booking page
One link — yours — that you can put in a bio, an email signature, or the bottom of a flyer. Clients see your branding and your menu, tell you what the job is, and watch a live estimate build as they pick. Then it arrives with you as a draft. Nothing books itself, nothing prices itself.
What your client actually sees
Two real captures of the page a client opens — the front of it, and the same page once they have started picking dishes.
How an inquiry becomes your quote
Four steps, and you are the third and fourth of them.
They ask, on your page
Your logo, your color, your published menu, and one form. A client leaves their name and email, and — if they want to be useful — a date, a venue address, a guest count, the occasion, a budget range, and anything else you should know. No account, no download, no back-and-forth to find out the basics.
They see a number, not a checkout
Where a dish carries a price you published, the client can tick it and set a headcount, and a running total builds as they pick. It is labeled an estimate on the page, in those words, because that is what it is: a shared starting point, not a price you are bound to.
It lands with you as a draft
Every request arrives in your inquiries queue as a request — never a booked date, never a sent quote. The queue leads with the shape of the job: the date, the headcount, what they picked. On a paid plan the client’s name, email and phone ride the request from the moment it arrives; on the Free plan they unlock when you accept it. Either way they are stored apart from the request, and only you and your managers ever reach them.
You accept, and price it yourself
Accepting creates the event, brings the client onto it, and — when they picked dishes — builds a draft quote from YOUR current prices, recalculated on the server. Nothing the client’s browser worked out is ever treated as the price. You adjust it, you set the deposit line, you send it. It goes out in your name, on your terms.
What is on which plan
The page, the photos on it, and the inquiries it collects are on every plan, starting with the free one — no card, and it does not expire. That free plan publishes one menu with live estimates on it; unlimited published menus are where the paid tiers come in.
- Booking page + inquiry form — from Free
- Booking page live estimates — from Free
- Booking page photos & customization — from Free
| Booking page | Free | Solo | Pro | Team |
|---|---|---|---|---|
| Booking page + inquiry form | Yes — contact unlocks on accept | Yes — uncapped accepts | Yes | Yes |
| Booking page live estimates | Yes — 1 published menu | Yes — 1 published menu | Yes — unlimited menus | Yes |
| Booking page photos & customization | Yes | Yes | Yes | Yes |
This is the same entitlement table the pricing page renders, read from the same data — so it cannot quietly disagree with what you get.
What it will never do behind your back
Nothing books itself
A request is a request. It does not hold a date, it does not create a confirmed job, and it does not send anything to your client. You accept it, or you dismiss it.
Nothing prices itself
The estimate a client sees is built from prices you published. The quote you send is recalculated from your current numbers on the server — a client’s browser can never set the price of your work.
Your client pays you
Clients pay you directly — your money lands in your own accounts and never sits in a CaterKit balance. This page collects the request, not the payment.
Your contacts stay yours
A client’s name, email and phone are held apart from the request, in a table nothing reads directly — they reach you with the request on a paid plan, or on acceptance on the Free plan, and no one outside you and your managers either way. Your page can be open to the whole internet without your contact list becoming so.
Frequently Asked Questions
Can a client book or pay through my catering booking page?
No, and that is deliberate. Nothing books itself, nothing prices itself. A client can tell you what they want and see a rough estimate, but every request lands as a draft you review, adjust, and send — you approve every quote. This page collects the request, not the payment. When clients pay through the platform, Stripe processes the payment on your own connected account — the money settles to you, never into a CaterKit balance.
Is the estimate the price I have to honor?
No. The number on your page is labeled an estimate, on the page, in those words — it comes from the per-person prices you chose to publish, multiplied by the guest count the client typed. Your quote is priced separately, from your current numbers, and it is the only figure either of you is working from once you send it.
Do I have to publish my prices to use it?
No. A dish with no published price still shows on your page — clients can see what you make and ask about it, they just do not get a running total for it. Publish prices on the dishes where a number helps you and leave the rest as a showcase.
Who can see my client’s contact details?
You and your managers — never a visitor to your page, and never crew signed in for the day. The name, email and phone a client submits are stored apart from the request itself, in a table with no read access of its own; they come back out one controlled way. On a paid plan that happens as soon as the request lands. On the Free plan, accepting the request is what unlocks them. It is enforced in the database, not in the interface.
Where does the money go?
To you. Clients pay you directly — your money lands in your own accounts and never sits in a CaterKit balance. When clients pay through the platform, Stripe processes the payment on your own connected account — the money settles to you, never into a CaterKit balance. The booking page collects the request — it does not collect the payment.
See the other end of it
A request that you accept and price becomes the document your client opens, reads, and accepts on their phone.
See a sample quote · Compare plans · Your booking page and inquiries