CaterRailBook a demo

Every feature

What’s in the box

The storefront the customer uses, the HQ the operator runs it from, and the plumbing between them. Nothing on this page is a roadmap item; everything here is in the demo.

01

The storefront

What the customer sees

  • Your own domain

    catering.yourbrand.com, or a path on your site. The address bar never says anyone else's name.

  • Locations first

    Every shop with its photograph, minimum, order-by time and delivery radius, before the customer sees a menu.

  • A real catering menu

    Packages priced per person or per tray, with photography, required choices, optional add-ons and a minimum headcount that the checkout enforces.

  • Delivery or pickup

    Each location sets its own radius and fee. An address outside it is told so before it builds an order.

  • Order windows with capacity

    A customer picks a day and a half-hour window. A window that is full is not offered.

  • Card held, not charged

    The card is authorised at checkout and captured only when the kitchen accepts. A declined order costs the customer nothing.

  • No account to create

    Name, phone, email, done. The confirmation goes by text and email.

  • Your brand, all the way down

    Colour, type, logo, case and corner radius come from the brand's own tokens. Two groups on CaterRail look nothing alike.

02

HQ

What the operator sees

  • Today, across every location

    Orders, money booked, what is waiting on acceptance and which windows are full, on one screen.

  • Accept, propose a change, or decline

    A new order waits on a person. Accepting captures the card. Declining with a reason releases it.

  • A board per kitchen

    Each location's minimum, lead time, catering hours, delivery radius, orders per window and alert list, changeable by that location's manager.

  • Pause a location

    One switch closes new orders at that kitchen, and only that kitchen, until the pass clears. Orders already accepted still print.

  • Prep sheet by window

    Accepted orders roll up into what actually has to be made — sixty-two rounds, two half pans, four bowls — printed before service.

  • Order history

    Every order with its trail, searchable by customer, location and day.

03

Alerts

How the kitchen finds out

  • Text and email, to a list

    Every phone and inbox on that location's list is told the moment an order lands.

  • Retry, then escalate

    No response inside the window and it goes again, then to a backup contact.

  • A trail on every order

    Who was told, when, by what channel, and who opened it. "Nobody told us" stops being an argument.

04

Menu library

One menu, however many shops

  • Write it once

    Items, prices, photography and option groups live in one place and push to the locations that serve them.

  • Per-shop overrides

    A location can hold its own minimum, its own lead time, or leave an item off, without forking the menu.

  • Change a price once

    Every shop that serves the item updates on the next order.

05

Money

Where it goes

  • Your Stripe account

    Payouts land in your bank on your schedule. CaterRail never holds your money.

  • Separate payouts per entity

    A group that is legally more than one company keeps one storefront at the front and separate Stripe accounts at the back. Nothing commingles.

  • Flat monthly, nothing per order

    Card processing goes to Stripe at their published rate, the same as today. No line grows with the size of an order.