Run your bar or restaurant on one system.
Your servers fire the order from their phone; the kitchen and bar see it on screen. Close the check and the sale comes out invoiced — the order is the invoice. Your website — QR menu and online reservations — is built in. One system to run your floor on a Friday night.
Software the way it should be: built around how you work, not one more tool that does everything halfway.
Floor · Orders · Kitchen · Inventory · Billing
A different system for everything, or a messy one you fight every night: the order, the kitchen, the check, the inventory, the invoices.
Three WhatsApp groups to run the place
One for the floor, one for buying, one for the kitchen. Someone asks for something, it gets forgotten, it never shows up. And no one knows who was supposed to do what.
The paper ticket that never made it to the kitchen
The server dropped it off, the cook never saw it. The dish comes out late, or it does not come out at all. The guest waits.
Invoiced later, by hand.
The invoice as a separate chore
Invoices at the end of the night, by hand, disconnected from the sale. The inventory, in a spreadsheet nobody opens anymore.
Built from inside service, not from an office.
It isn't a billing tool with a POS bolted on top. It's a modular, intelligent system: eleven areas that talk to each other. Sell a dish or a drink and stock drops on its own; close the table and the invoice comes out.
Know what's happening at every table without getting up.
A live map of the floor: open, seated, reserved. How many guests and for how long, at a glance. Did it start raining? Disable the terrace by zone in one tap. Drag one table onto another to join them and they share a single check. Your host sees table status from any device, read only.
- Live states
- Guests per table
- Zones in one tap
- Join tables → one check
- Host view
From the server's phone to the kitchen and bar screens.
The server fires the order from their phone and it lands straight on the kitchen and bar screens — no shouting, no ticket lost on the floor. Screens, printers, or both together: each station takes its tickets however it works best, and every order routes to where it belongs. Mark dishes by course so the ticket reads in sequence, or fire a tasting menu course by course — plate to the kitchen, pour to the bar. Change the order and the kitchen sees it instantly.
- Order from the phone
- Screens, printers, or both
- Routes per station
- Courses & tasting menus
- Changes in real time
Open the register, take payment, reconcile. No surprises at closeout.
Every shift opens with its float and closes with the count and the variance in plain sight. Payments by method, tips, petty-cash expenses, and bank drops. Split the check by item, evenly, or across methods and people. The expected cash always matches what's in the register.
- Open and close per shift
- Payments by method
- Split the check
- Tips, expenses and drops
- Variance in plain sight
Stock drops on its own when you sell the dish or the drink.
Stock by storeroom: bar, kitchen, back room. Every recipe, dish or drink, is tied to its menu item, so inventory is deducted with the sale. Cost and margin per item, updated in real time. Import the supplier's invoice and Mantel reads each line, works out the cost per unit, and matches it to your inventory — costs current without retyping. Even your smallware (glassware, plates, pans) keeps its own counts, breakage included.
- Storeroom, kitchen and bar
- Recipes tied to the item
- Live cost and margin
- Import the supplier invoice
- Smallware counts & breakage
The guest-chef dinner, without a separate spreadsheet.
Create the event — guest chef, date, hours — and its menu shows on your public carta that night only. Each dish carries limited servings that sell out on their own, and the pairing pours from your own cellar: every glass sold deducts its bottle. If the chef takes over the kitchen, your dishes step aside and the bar keeps selling. At the end, sales per dish and clean numbers to settle with the chef.
- A menu per event
- Limited servings
- Pairings from your cellar
- The chef's kitchen, your bar
- Clean numbers to settle
From the online booking to the table, with nothing lost in between.
Bookings from your website land in the system with their status: confirmed, with a deposit, pending. Log walk-ins and assign a table. When someone arrives, the host checks them in and the table shows up on the floor instantly.
- Bookings and walk-ins
- Deposits and holds
- Host view
- Live arrivals on the floor
Who clocks in, who clocks out, how many hours.
Your team clocks in and out from their own device. Build the week with assignments by person and by day, and everyone gets their shift instantly. A report of hours worked by person and by role.
- Clock in and out
- Weekly schedule
- Hours per person
- Live shift alerts
Everyone sees only what they need to see.
Admin, manager, floor lead, server, bartender, kitchen, chef, cashier, storekeeper, host. Each role with its own view. And it's all a PWA: it installs like an app on any phone or tablet, no App Store, no heavy downloads, and it holds up if the wifi blinks for a moment.
- Ten defined roles
- A view for each role
- Phone, tablet or display
- Installs like an app · PWA
Installs like an app · PWA · no App Store
What happened today, in numbers that add up.
Sales by method, hours worked, cost and margin per dish, and your website's visits in the same place. A layer that reads the operation: which dishes are stars and which are dead weight, your bar variance in dollars, the busiest days and hours, and what data needs fixing. And your accountant gets a workspace of their own: sales and purchase ledgers, withholdings, the 104 worksheet, a P&L, and the monthly ATS export — with read-only access.
- Sales by method
- Cost and margin per dish
- Menu engineering
- Bar variance in $
- Your website analytics
- Ledgers, 104 & ATS
- Read-only accountant access
And in the end, the invoice isn't a separate chore. It's the sale.
Everything above ends here: electronic invoicing built in, not bolted on. Taxes and service charge worked out on their own. The order becomes the invoice: you close the table and the invoice is already done — RIDE as PDF, email, or thermal print. Regulars autofill by ID, and a client directory builds itself from every invoice. A refund? The credit note issues from the same place.
- Native electronic invoicing
- VAT 15% + service 10%
- The order is the invoice
- RIDE: PDF, email or thermal
- Credit notes
- Client registry + autofill
- Adapted to Ecuador's SRI
Floor, kitchen, inventory and your public menu read and write the same data.
Floor changes show up instantly, on every screen.
Late-night service rolls up to the right day.
On any phone or tablet, no App Store.
From the door to the storeroom.
Your website comes built in, too.
It is not just the back-of-house system. It includes your public site (landing page, QR menu, and online reservations) with your brand and your domain. The QR on the table opens your live menu. Guests book on their own, and capacity, deposits, and tables are all handled by the same system.
Every visit (where it came from, whether it booked, how long your team took to reply) lands in your reports.
Your brand and your story: your spaces, tastings and events, location and hours.
The table QR opens here. Live from the system; whatever gets 86'd disappears on its own.
Online reservations. Up to 4 people straight through; 5+ takes a deposit and you call them.
One system. Your brand.
You don't share an account with a hundred other venues. We deploy your own instance, with your color, your logo, and your domain, and the same operation takes on your brand. Pick one and watch it change.
Same system, same screens. Only the brand changes.
It isn't a plan you subscribe to. It's a system that supports you.
We deploy your own instance, tailored to how you work, ready in three steps.
We talk.
We get to know your venue: your zones, your roles, your menu, how your team works on a packed Saturday. No generic forms, just a conversation about how you run service.
- Your zones
- Your roles
- Your menu
- Your service flow
We configure and deploy.
Your brand, your data, your domain. We set up your own instance, tailored to your venue. You don't share an account or a database with anyone else.
- Your brand
- Your domain
- Your data
- Your own instance
You run it.
Your team logs in on day one and everything works. No endless migrations, no 80-page manuals. The server opens their phone and starts taking orders.
- No endless migration
- No 80-page manual
- Ready on day one
Mantel is ready for any bar or restaurant. In Ecuador, the SRI module already comes adapted.
The platform isn't married to one country. But if you operate in Ecuador, the SRI electronic invoicing is already built and tested (access key, signature, transmission, RIDE) and running in production. You don't wait months for someone to integrate it.
A wine garden in Quito. Customer zero. What you see on this page is the same system running there every night.
“I didn't want one more piece of software that promises and never delivers. I wanted to see my tables, send the order, and have the invoice come out on its own. That's what it does.”
Wine garden · proof of concept in production
Ecuador's electronic invoicing is built and tested against the SRI, in production. It isn't an imported module or an add-on you pay for separately.
The platform runs for any restaurant or bar. The tax module adapts to each country; the SRI one is already done.
If something breaks mid-service, you don't open a ticket: you reach the person who built the system and runs it every night.
Want to see how it would run
at your place?
No forms, no 40-minute demos. Drop us a line and we'll show you the system with your tables, your zones, your menu.
Quito, Ecuador