Reservations and floor
See arrivals, seat a party, track table status, and give the team the context they need before the first order.
Restaurant websites and service systems
Welcome guests online. Keep the evening moving inside.
Worklane can connect a restaurant website with the operating details behind service: reservations, floor status, server orders, kitchen tickets, and the close.
Try Cedar & Salt ↗One connected service flow
The goal is not a prettier spreadsheet. It is a clear handoff between the host stand, the floor, the kitchen, and the guest.
Server order entry
Choose the table, seat, course, modifiers, and notes. Send the order when it is ready for the kitchen or bar.
Kitchen tickets
Route items by station and move tickets from new to ready to served, keeping guest notes with the order.
What the Cedar & Salt demo lets you try
01
Open the floor
Start with the seating chart and see which tables are free, reserved, seated, or waiting to be cleared.
02
Seat a party
Move a reservation onto a table and assign a server so the check has an owner.
03
Send a ticket
Add menu items with courses and notes, then send them into the kitchen and bar queue.
04
Close the check
Advance the ticket, record a simulated payment, and leave the table ready for the next party.
Questions about a restaurant system
Does the demo process real payments?
No. It is a browser-based sample with invented data. No card details are collected and no money moves.
Could this use our menu and stations?
Yes. A real project would be shaped around your menu, prep stations, roles, service style, and the tools you already rely on.
Can the public website and service system share reservations?
That is the intended connection: a booking request can become a reservation record, then a table, then an evening of service.
See the service flow, then make it yours.
Choose Cedar & Salt as the starting point in your project inquiry.