Restaurant POS software that already knows the room.
Restaurant POS for table tabs, orders, kitchen sends, staff controls, tender records, and offline-first service, with native Maitredi Flow context.
Tap pricing and rollout are confirmed directly. Reservations is available separately.
A separate restaurant point-of-sale product
Maitredi Tap models table tabs, menu items and modifier notes, kitchen sends, staff PINs and permissions, discounts, cash or card-on-terminal tender records, receipts, and end-of-night totals. Current rollout requirements must be confirmed before deployment.
Native Flow and Tap workflow
- A Maitredi reservation can own the assigned table and become that table’s Tap tab.
- Close-time guest spend can return to the reservation guest record.
- Sold menu-item quantities feed Maitredi’s POS-sales input for inventory calculations.
Offline behavior belongs to a configured native Main
On a configured native Maitredi Tap Main, supported service operations can be accepted into an encrypted local database and queued for synchronization. Staff can see synchronization and conflict states, while device recovery and authority changes remain manager-controlled. Venue devices, networking, peripherals, and recovery are confirmed during rollout.
Explicit payment and rollout boundaries
Current Tap workflows record cash or an externally approved card-on-terminal payment. Maitredi does not claim integrated card acquiring. Hardware, peripherals, geography, tax, migration, support, pricing, and current availability are confirmed for each rollout.