Point of sale for hotel restaurants

Your restaurant. Inn your hotel.

“Put it on my room.” Five words your POS was never built to understand.

Inn Restaurant was born inside a hotel. The check lands on the guest folio, follows the corporate agreement and balances the restaurant drawer without anyone reconciling anything.

No hardware. No installer. Runs on the tablet you already own.
Floor · Inn Restaurant
Table 442 min$1,240
Table 718 min$610
Pool 29 min$380
Terrace 1openOpen
Settle Table 4Total $1,240
Cash
Card
Transfer
Charge to room
Only rooms with a guest checked in
Room 204 · Lucía Ortega
Room 118 · Andina Group
Room 305 · Tomás Reyes
Posted to the folioRoom 204 · agreement applied
The drawer never noticesIt is not cash received
Tax splitCompany and guest, each their own
12countries in operation
34reports under the USALI standard
1system, not two integrated ones
0hardware to buy
Figures as of September 2026.
Credibility

Recognized worldwide, proven in operation

First place worldwide in the UN Tourism rural tourism program. Case study at IE University, Madrid. Real operation in twelve countries, from London to Patagonia.

UN Tourism

First place worldwide in the rural tourism program.

IE University, Madrid

Business school case study.

Twelve countries

Real operation, from London to Patagonia.

The problem

Two systems mean two versions of the truth

The POS closes its day. The hotel closes its own. Between them there is a file, a reconciliation and an argument. Every month.

Is the room charge written down on paper?

Then someone keys it in at eleven at night. Sometimes wrong. Sometimes never.

Does the company get its statement with the bar included?

They dispute it, the whole group payment stops, and collections slip for weeks over one beer.

Do the front desk and the restaurant share a drawer?

The close does not balance and nobody knows whose difference it is.

Does credit consumption never reach receivables?

The company piles up debt that never touches its credit line.

Can a check be closed without being paid?

The sale vanishes from the close and the shortage has no explanation.

Are comps approved by word of mouth?

Nobody knows how much was given away last month or who approved it.

The solution

The solution in four moves

From the order to collections, without keying anything twice.

1

The order goes in

The server takes the order on any device and the kitchen sees it instantly.

2

Someone decides who pays

The guest pays there or charges it to the room. If charged, the system verifies the stay and the corporate agreement decides what it covers.

3

The drawer balances

The payment enters the drawer of its revenue center, with its method and the name of who collected it.

4

It gets collected

Whatever stayed on credit is already in receivables, aging and consuming the company credit line.

The platform

Not a POS with integrations. A full hotel system that happens to have a POS.

Front desk, folios, master accounts, collections, booking engine, channel connector, website, CRM, loyalty, reviews, business intelligence and accounting reports. All in the same database as your restaurant.

And if you only want the restaurant, it also works on its own.
The details

The details you notice mid-service

Specificity is the proof: nobody makes up twenty-five details this fine.

Checked-in guest verificationAgreement by categoryTax split per folioDrawer per revenue centerSeveral drawers at onceTips that do not inflate salesSplit check with kitchen status intactTransfer items between tablesAtomic pay-and-closeVoids that never duplicateChange calculatedPayouts that open a shiftReceivables that separate consumed from committedAdjustments with mandatory reason74 granular permissionsAudit trail with author and reasonLock against double table openingFolio with running balancePrices computed on the serverMulti-currencyThree languagesMulti-propertyFour service modes on one screenModifiers per dishReceipt printable on any printer
Reporting

Your controller does not want another dashboard. They want USALI.

Food and beverage per occupied room, revenue center performance, profit per available room and trial balance. The language hotels around the world compare in.

F&B per occupied room
$412
USALI, schedule 2 · illustrative example
Restaurant
Bar
Pool
Room service
Front desk
Frequently asked questions

What people ask before the demo

Why choose Inn Restaurant over another POS?

Because if your restaurant is inside a hotel, half of your operation is not the restaurant. It is the folio, the corporate agreement, the drawer separated from the front desk and collections. No generic POS does that without integrating with another system, and that integration is a contract, a fee and a point of failure.

Does it work if my restaurant is not in a hotel?

Yes. Taking orders, sending to the kitchen, splitting, settling and balancing work the same. You simply do not use the hotel side. And if you ever open rooms, it is already there.

Do I need to buy hardware?

No. It runs in the browser of any tablet, computer or phone. If you already have terminals, use them.

Am I forced to use your payment processor?

No. We do not take a percentage of your sales and we do not tie you to a processor.

How long does implementation take?

Days. Five calendar days in most cases, without closing the restaurant.

Do you charge per user?

No. Add all your staff, each with their own permissions. A system that charges per user is a system where people share passwords.

Does it work without internet?

Today it requires a connection. Offline operation is on the roadmap. We would rather say it here than on installation day.

Is my data mine?

Yes. Exportable whenever you want, in an open format, with no penalty.

Your restaurant already sells. Your system just does not know it.

Fifteen minutes, with your menu and your tables. Nothing to install.

See a 15-minute demo
We use the minimum to make the site work and to know which pages are useful. You can reject the rest.