Restaurant Operations Platform

Waitlist, tips, and payroll — one system.

CoTable started as the system we used in our own restaurants. Guests get a text when their table is ready. Servers close out their tips on the phone instead of a spreadsheet, and owners can check every location's numbers from theirs.

Made for small and mid-sized restaurants. CoTable sticks to what a working restaurant actually needs, and keeps track of the things an owner would otherwise have to chase down.

Products

Three products that share the same data.

Each one covers a different part of the day, so nobody enters the same thing twice.

For Guests

Regulars Hub

The waitlist and reservations, run from a screen at the door and a pad at the host stand.

At the door

  • Wait status stays on the kiosk screen all day, in large type — how many teams are waiting and the current wait
  • Guests check themselves in: party size, phone number, name, on a big number pad
  • A quick check of the phone number before joining, so a typo doesn't lose the text alerts
  • Request chips instead of typing — baby chair, wheelchair access, quiet seat
  • Other guests' names never appear on the kiosk screen
  • The screen clears itself after 60 seconds, ready for the next party

At the host stand

  • One live list of waiting parties, grouped by party size, with the wait for each
  • One tap to text "almost ready," call the party, or seat them
  • Every party's history on one sheet, from joining the list to sitting down
  • Phone parties sit in their own "not arrived yet" section until they check in
  • Arriving guests check in with the last 4 digits of their phone number
  • No answer when called? The party goes back to the end of the list — staff decide no-shows, not the system
  • Undo for a few seconds instead of confirmation pop-ups
  • Seated, cancelled, and no-show history, with restore to the original spot in line

Text messages

  • A text when the party joins the list, one when the table is almost ready, one when it's ready
  • Every text starts with the restaurant's name
  • Texts go out in the guest's own language
  • Guests agree to texts with a checkbox at the kiosk — and replying STOP ends them

Reservations & regulars

  • Reservations arrive by KakaoTalk channel, by phone, from the waitlist, and from the web — and land on one list that every server can see on the staff pad
  • Phone reservations are taken right on the pad: number first, then name, time, and party size
  • Enter the number and the guest's record comes up with it — past visits, average spend, no-show count — so you can take the booking while you look at it
  • A guest book that remembers regulars, their visits, and their preferences
  • Guests can also join the waitlist from their own phone

Your guests, your list

  • The phone numbers and guest history collected here belong to your restaurant — not to us
  • CoTable is the tool that keeps the list in order; your guest list is never held hostage by the platform
  • For guests who separately agree to marketing texts, send an offer by text now and then — and give regulars a reason to come back
For the Team

Server Hub

Tips and schedules, on each server's own phone. When the tips are in, they carry straight into payroll — and every server can see the same numbers.

Entering tips

  • Sign in by tapping your name and a 4-digit PIN — no password to type
  • Today only, split into lunch and dinner, with the scheduled roster already on screen
  • Pick who worked from the roster; hours go in with preset buttons, not typing
  • Card tips are collected from the POS for you — you add cash tips and hours
  • The split is calculated at the bottom of the form while you enter
  • A confirmation sheet shows the full split before anything is sent
  • Sent the wrong thing? Re-open the service, fix it, send again

Splitting the pool

  • The kitchen share comes off the pool first, at the rate set for your store
  • The rest is split by hours worked — twice the hours, twice the share
  • Tip levels per person: a fixed amount, a percentage, or an hourly tip rate
  • Totals always show before the kitchen deduction; the deduction is its own line
  • Rounding cents land on the kitchen amount, so the split always adds up exactly

Closing the service

  • One tap starts the close, and collection of that service's card tips and cash starts at that moment
  • The closing amount is the real POS total at the time of the close — no estimates, no provisional numbers
  • The closing screen shows the cash that goes in the drawer and the float to leave behind
  • Tables still open at lunch carry to dinner, with each table's tip entered there

Shared, and into payroll

  • Tips flow straight into payroll. Nobody sits down after a shift to add them up by hand
  • Every server sees the same tip numbers, updated as they come in — the split is out in the open
  • Tip history on a calendar, with totals for each pay period (1st–15th, 16th–end of month)
  • Voids listed with the time, the reason, and who approved them

Schedule

  • Your week, or the full schedule for the whole team
  • A week shows up only when a manager publishes it
  • A push when the schedule is published, and a reminder one hour before your shift
  • The roster on the schedule is the same roster the tip form uses that day

Running the store

  • Managers keep the staff list in one place: names, POS names, PINs, roles, tip levels
  • Lunch and dinner services, kitchen percentage, and the closing cash float are store settings — set once
  • The same app at every store; stores differ in their settings and data, never in the software
For Owners

Owner Hub

Every location's day on one phone screen — pick all stores, or just one.

Home

  • Store cards sorted by today's sales, biggest first
  • On each card: today's sales, today's reservations, and how many parties are waiting right now
  • Today's voids, as an amount and a count
  • An expected total for the day that includes tables still open
  • Each card shows when its numbers were last updated
  • A badge on the card when one of the store's devices needs attention

Store detail

  • Sales split by card and cash, and by lunch and dinner
  • The day's tips — card and cash — and whether each service has been closed
  • Voids broken down by reason
  • The waiting list in detail: who is waiting, how long, and today's seated, no-show, and cancelled counts
  • The last 7 days of sales, a line per day
  • Labor starts as a daily estimate and is replaced by the confirmed figure after each payroll run; monthly profit builds up from confirmed days

Reservations & guests

  • Today's reservations in time order — add, change, or cancel them right in the app
  • A warning when the same phone number already holds a reservation that day
  • Cancelled reservations stay on record, counted at the bottom of the list
  • Look up a caller to see their reservations, their no-shows, and the notes your team left on them

Purchasing

  • This month's purchases — the total, and the total by vendor
  • Last month next to it, for the same period
  • Recent invoices with the vendor, the date, and the amount
  • Search any product: its latest price, the price before it, and who sold it

Payroll & records

  • Payroll runs in the same app — the hours and tip totals are already there
  • Tip records, break records, and payroll runs are stored in one place, and they add up over time
  • When a question comes up months later, the record is there to pull up

In-store devices

  • Every kiosk and staff pad reports in: network, battery, memory, and whether its screen is on
  • Devices are graded normal, caution, or offline — with the reason in plain words
  • App updates go out in batches, installed now or scheduled after closing
  • Each device's screen is captured every 10 minutes and kept for a week, so a problem can be looked at afterwards
  • Reboot a device, or restart its app, from the device screen
Platform

Why it works the way it does

Restaurants are busy and the staff changes every shift. So CoTable asks for as little typing as possible, every screen stays current on its own, and the system runs the same at one location or at ten.

Runs on your own phone

Each person uses CoTable on their own phone — Android or iOS. It installs straight from the browser, no app store in between, and push notifications cover the things that need you: a published schedule, a shift reminder, a device that's gone quiet.

Korean, English, Spanish

Staff screens come in Korean, English, and Spanish, and the language switch sits in the same place on every screen — staff change, the button doesn't. Guest screens add Chinese.

No end-of-night uploads

When a party joins the waitlist or a check closes, every screen sees it right away.

Connects to your POS

CoTable reads sales and labor data straight from the POS systems your restaurants already run.

Records that stay

Tip records, break records, and payroll runs live on the server, not on paper or on one person's phone. Your store's history builds up in one place, ready to look up when you need it.

Big buttons, plain words

Most screens are taps, not typing, with large type for busy floors. If a screen needs an explanation, we fix the screen.

Restaurants

Built in these five restaurants.

CoTable wasn't drawn up in an office. It was built around how these five restaurants in Buena Park and Costa Mesa actually work.

Venice Beach storefront at The Source Mall, Buena Park

Venice Beach

The Source Mall · Buena Park

Korean seafood and sashimi.

Tami Sushi at The Source Mall, Buena Park

Tami Sushi

The Source Mall · Buena Park

All-you-can-eat sushi.

K Soul Food logo

K Soul Food

The Source Mall · Buena Park

Korean kitchen.

Mochinut

Mochinut

South Coast Plaza · Costa Mesa

Mochi donuts.

K Soul Food logo

K Soul Food

South Coast Plaza · Costa Mesa

Korean kitchen, next to Mochinut.

Talk to us

Pick the kind of question you have, and send it through the form. We read everything that comes in.

CORNERSTONE INC 7002 Moody St, Ste 207
La Palma, CA 90623
United States