Talk to us

Tell us about the job.

Two steps, one real job. We will help you decide whether Phoros fits and show what it can do inside your tools and boundaries.

  1. The job
  2. Your details
What should we start with?
Optional. Say where it gets stuck and which decisions must stay with you.

Please do not include passwords, account numbers or sensitive customer data.

Restaurant OS

Every table, every ticket, one service.

Point of sale with tabs and a floor plan, kitchen orders, bar and kitchen stock, bookings, accounting and payroll, on one set of records. Phoros watches the pass and asks before the menu changes.

Illustrative screen · Restaurant OS

The service handoff

Every order should reach the kitchen once.

A dinner rush touches the floor, the kitchen, the bar, the bill and the books. When they live apart, the gaps show up on the plate and in the till.

  • The till remembers what already fired
  • Stock is counted by what was sold
  • The day closes with the books already posted
Illustrative diagram · Restaurant OS

What a restaurant gets

The till was built for a service floor.

Thirty-one areas sit behind that sentence. These are the ones a room full of guests actually needs, starting with the floor.

  • Every table with its server, covers, spend and time
  • Timers that warn at the minutes you choose
  • A bill split item by item, into new tabs
Illustrative screen · Restaurant OS
  • On the floor

    Tabs per cashier, named for a table or a guest. A floor plan with rooms and tables showing server, covers, spend and time, timers with your own warning and critical minutes, and a tab split item by item into new tabs or into another open tab.

    See point of sale
  • To the kitchen

    Orders reach the kitchen once, on a bump bar or printed by category and location, and the till remembers what already fired.

  • The bill

    Eight ways to pay and one bill split across them, a service charge for the house and a rate per cashier, three suggested gratuities on the receipt, happy-hour discounts by category on chosen days, and ten currencies at a live rate.

  • At close

    The drawer counted by denomination and by currency, the variance against thresholds you set, a safe drop, and gross profit per service.

  • Behind the bar

    Bar stock, dry goods and fresh ingredients on one ledger: received by the case, sold by the glass, watched for expiry, and reconciled against what should have been used.

    See inventory
  • The guest

    One guest record at every location, holding what they ordered, what they owe and what they said.

  • Reservations

    Booking forms with available days, a limit per session and a cut-off time, deposits collected when the guest books, landing in the planner and on the guest record.

  • The people

    Shift staff from the clock-in at the door to the payslip, with tips carried through and the statutory tables built in.

    See payroll

And the honest line. Reservations arrive through a booking form and land in the planner and on the guest record. There is no table-map reservation engine.

Virtual staff for restaurants

Your virtual staff know the service routine.

Add help with guest messages, stock watch, supplier follow-up, the daily close, cost checks and the weekly review, inside the same restaurant system. Refunds, allergies, safety and special requests come back to your team.

  • Every close built from the night's own records
  • Voids and shortages flagged, never quietly fixed
  • Orders wait for your yes
Illustrative screen · Restaurant OS
  • Guest follow-up

    Sends routine booking confirmations and answers in your voice, and returns complaints and special requests to your team.

  • Daily close

    Gathers sales and payments and surfaces refunds, voids and gaps before the books close.

  • Stock watch

    Tracks bar and kitchen stock against what was sold and surfaces exceptions. You approve every reorder.

  • Supplier follow-up

    Chases invoices and delivery windows, and keeps each answer on the record it belongs to.

  • Cost watch

    Keeps food and drink costs beside menu prices and surfaces exceptions before they spread.

  • Weekly review

    Reviews sales, stock, guest threads and supplier gaps, and leaves one page for the owner.

Connections

Run it all on Phoros Cloud, or connect what you already use.

Run the whole restaurant on Phoros Cloud: tabs and the floor plan, kitchen orders, stock, books, payroll and bookings. Already using tools you like? Phoros Cloud connects to them.

Built in today

Moving from QuickBooks? Connect it while you switch.

  • AccountingQuickBooks
  • PaymentsStripeDIME
  • Bookings and eventsEvent Temple
  • Messages and marketingWhatsAppMeta
  • WorkspaceGoogle WorkspaceMicrosoft 365

Can be connected

Tools with an MCP server connect through open connectors, and Software OS can build a connection to anything with an API.

  • AccountingXeroSageZoho Books
  • PaymentsPayPalSquare
  • BookingsOpenTableResy
  • Messages and marketingMailchimpCanva
  • WorkspaceSlackMicrosoft Teams
  • Staff scheduling7shifts

How we test

Tested on real days, not demo scripts.

In the summer of 2026, Phoros Pilots ran for eight weeks with agents carrying real business jobs under daily human review. Stakeholder acceptance was the test. We publish evidence as the work supports it, so ask us what the current results show.

How we test

Your restaurant, online on day one

A web presence for the restaurant, ready before the first booking.

Three finished sites for places that feed and host people. Start from one, and the cards, flyers and social content follow to match.

18 finished sites 8 categories Browse the gallery

Every site is a complete page, and the same desk makes the business cards, flyers and social content to match. See brand development and management

Restaurant OS

Bring one service workflow.

The pass, the bar count, the daily close or bookings: we will show you how it connects to the rest of the restaurant and which recurring steps virtual staff can take on.

See plans and pricing

Questions

Before your first restaurant job.

Something else on your mind? Our team will talk it through with you.

What does Phoros connect for a restaurant?

The floor and the tabs, the kitchen, the bill, bar and kitchen stock, suppliers, bookings, the people and the daily close, in one Business Operating System. Virtual staff can help with recurring follow-up inside it.

Is Phoros the point of sale?

Yes. Tabs per cashier, the floor plan, the kitchen board and the bill are built in, on the same record as the stock and the books.

Can virtual staff help with guests?

Yes. Virtual staff can send routine booking confirmations and answers in your voice. Complaints, refunds, allergies, safety and special requests come back to your team.

Can virtual staff order or refund on their own?

Not by default. Virtual staff prepare the work against rules you set. Purchases, refunds and price changes stay with your team.

Can it work with the tools we already use?

Yes. Some tools are built in, tools with an MCP server connect through open connectors, and Software OS can build a connection to anything with an API. The list above shows which is which.

What happens to my data if I leave?

It is yours. Your records, files and history belong to your organization, and leaving with your work is a right, not a negotiation.