Fast for the server. Exact for the controller.
Taking an order should take seconds. Balancing the cash should take none.
A point of sale is judged in the two most stressful minutes of the day: when six tables walk in at once and when it is time for the shift close. Most systems are built for the first. Inn is built for both.
What it does on the floor and at the shift close
Everything open on one screen
Tables, takeout and delivery, with what each check holds and how long it has been open. No switching modules, no digging through a menu. The floor manager sees the whole room and knows, without asking, which table has been waiting forty minutes for the check.
- Tables, takeout and delivery in the same view
- What each check holds and how long it has been open
- No switching modules, no digging through a menu
Charge without mistakes
Cash with change calculated on screen, card and bank transfer. The system does not accept a payment that does not cover the check, and it tells you exactly how much is missing. With a card it requires the exact amount, because a terminal gives no change. And if the guest pays half in cash and half by card, both methods are recorded, not one with a note.
- Cash with change calculated on screen
- Rejects a payment that does not cover the check and says how much is missing
- Card requires the exact amount
- Mixed payment: both methods recorded, not one with a note
The tip goes to whoever earned it
Shortcuts for ten and fifteen percent, or any amount, always on top of the total. The tip is attributed to the server who waited the table, not split by eye at the end of the shift. And it does not count as hotel revenue, so it does not inflate your average check or your tax. But it is expected in the drawer when it was paid in cash, so the cashier does not end up with a surplus nobody can explain.
- Shortcuts for ten and fifteen percent, or any amount
- Attributed to the server who waited the table
- Not hotel revenue: no inflated average check, no inflated tax
- Cash tips are expected in the drawer
Split without drama
Four friends paying separately, or a dish that moves to the next table because the group joined up. Both totals are recalculated with their taxes, and whatever is already on the grill keeps its status: it is not cancelled and not re-entered.
- Four friends paying separately
- A dish moves to the next table
- Totals recalculated with their taxes
- Whatever is already on the grill keeps its status
Room charge
One more payment method on the charge screen, with all the hotel intelligence behind it. See the full room charge page.
Charging and closing is one single operation
There is never an in-between state where the money is already recorded and the check is still open. That in-between state is where double charges are born, and it is the reason a guest walks out angry. And if the server taps the button twice because the network was slow, the second tap does not charge again.
- No in-between state between charging and closing
- That is where double charges are born
- Two taps on a slow network do not charge twice
Every charge has a name
Not the name of whoever opened the drawer: the name of whoever charged. When the shift close does not balance, that difference has an owner.
Discounts and comps with a trail
A discount is a permission, not a favor. Whoever does not have it does not see the button, and the server side verifies it even if someone tries to bypass the screen. Every discount is stored with its author, its amount and its reason, and shows up in the daily report.
- A discount is a permission, not a favor
- No permission, no button; the server side verifies it
- Author, amount and reason in the daily report
Frequently asked questions
How long does it take a server to learn it?
Ten minutes to take an order and charge it.
Can I run several terminals at the same time?
Yes, with no per-device fee.
Can a paid check be reopened?
No. You void it with a reason, and the void is recorded. Reopening paid checks is how money gets lost.
Can I print the receipt?
Yes, with any network or receipt printer.
Try it with your own menu. Fifteen minutes.
Your restaurant already sells. Your system just does not know it.
Fifteen minutes, with your menu and your tables. Nothing to install.