The floor is a working view.
Keep the table and the service state in the same picture.
- Table map and covers
- Waiter assignment
- Reservations and roster context
POS · Food service
Flocci Restaurant POS
Floor, waiter, guest QR, kitchen stations and settlement working from the same service. Fire the right ticket, see what is ready and split the bill the way the table actually wants to pay.
Live demo · Organisation onboarding · Rollout consultation
Use floor, waiter or guest QR entry.
Route KOTs by station and track ready/bump status.
Allocate the check and settle each share on its tender.
Explore the tools, records and controls that make the workflow possible.
Keep the table and the service state in the same picture.
A mixed order should not become a vague ticket for everyone.
Bring QR orders into the existing service record.
Make settlement match the table.
Review the menu from actual operating data.
Keep routine operations in one product.
Run a multi-station kitchen with a live floor-to-KDS flow.
Let guests order from the QR while staff retain the same service record.
Handle a table that needs several differently paid check shares.
Shared Flocci identity and credits support the operator workspace. Roster staff and QR guests are not automatically paid sign-in seats; restaurant Graph events carry bounded operating metadata.
Organisation seats cover signed-in operators under the current plan. Routine orders, KOTs, splitting and settlement are unmetered; the optional menu-intelligence report consumes published AI credits.
Connect the floor, waiter view and guest QR to station-specific kitchen tickets and a live KDS. Split checks by guest, item or amount, settle each share and keep reservations, roster and service records together.
Organisation seats cover signed-in operators under the current plan. Routine orders, KOTs, splitting and settlement are unmetered; the optional menu-intelligence report consumes published AI credits.
No. Aggregator intake and partner status are distinct from automatic third-party integration. Confirm the actual configured intake path.
By guest, item or amount. Tax and service charge are apportioned and each share can be settled separately.
Shared Flocci identity and credits support the operator workspace. Roster staff and QR guests are not automatically paid sign-in seats; restaurant Graph events carry bounded operating metadata.
FLOCCI ENGINEERING · STORIES
Explore the architecture and product decisions behind this part of Flocci.

October 7, 2026 · On Crashtech
How Flocci connects specialized business products through reusable identity, spending, delivery and intelligence while preserving distinct workflows.
Read the story
October 7, 2026 · On Crashtech
How Flocci Account and shared payment capabilities connect personal credits, organization funding, allocations and accountable spending across products.
Read the storyRun every service from first seating to final settlement.