Cibuscibus.
Real-time

Live state across connected service surfaces.

Orders, tickets, tables, payments, staff and delivery updates move across connected POS, QR, KDS, Storefront, Admin and Rider workflows through shared live state.

Book a DemoHow Cibus works
All surfaces · in sync
Illustrative
POSOrder sent
Table T12 · 6 items
KDSSent
Pass queue · 2 lines
QRLive cart
Round of House Natural Red, 175ml
PayAuthorised
Visa · £86.00
RiderEn route
Delivery task · 2.4 km
AdminLive
3 sites · staff on shift
Illustrative state · connected update received
6live surfaces

Supported updates across configured POS, QR, KDS, Storefront, Admin and Rider workflows.

1event stream

Supported order, ticket and payment events on a connected stream.

1shared record

Shared table state available to authorised connected staff devices.

Liveconnected state

Supported updates arrive through subscriptions while the device is online.

The pain

What 'check the other screen' actually costs

Refresh-driven workflows
Staff hit reload to see whether an order, payment or ticket actually went through.
Out-of-sync devices
Two servers see different versions of the same table and add the same drink twice.
Kitchen surprises
Tickets appear that the floor doesn't remember sending; nobody knows the source.
Customer status guesswork
Guests ask 'is it ready?' because the customer view never updates by itself.
Delivery in the dark
Couriers go quiet between pickup and dropoff; the kitchen has no idea.
Old way vs. Cibus

From refresh-driven to live by default

Refresh-driven
  • Staff refreshing screens to see state
  • Servers add the same item twice
  • Tickets arrive in the kitchen with no source
  • Customers ask staff for status
  • Delivery is a phone call away
With Cibus
  • Connected surfaces receive the same supported live state
  • Shared table state reduces duplicate entry
  • Tickets trace to the order that produced them
  • Configured QR, Storefront and Rider views receive supported status updates while online
  • Configured courier status can flow across pickup, transit and drop-off
Live state

A typical moment in service

19:42
Table opened on POS
T12 · 4 guests
19:43
QR cart appears live
Shared state reduces duplicate entry
20:05
KDS receives ticket
Grill + cold stations
21:13
Payment authorised
Stripe Terminal · split
21:15
Customer view ticks
Digital receipt issued
Live surfaces

What updates in real time

•
Live order feed
Supported order updates appear across POS, KDS and Admin.
•
Live floor and table view
Occupancy, status and progress visible at a glance.
•
KDS ticket updates
Station claims, prep, bumps and serves propagate in real time.
•
POS ↔ Staff Mobile sync
Connected staff devices receive the shared table state.
•
Customer-facing status
Diners see live order status from QR, Storefront or delivery tracking.
•
Rider delivery updates
Pickup, in-transit and dropoff statuses flow back to the order view.
•
Manager dashboards
Sales activity, orders, tickets and shift state at a glance.
•
Payment confirmations
Card, terminal and wallet payments confirm against the order in real time.
•
Shift state
Open, active and close shift state visible across the team.
Example shift

One table across connected surfaces

  1. 19:42
    QR scan opens the table on the live record
    The server POS can receive that shared state while connected.
  2. 20:00
    Server adds a side from Staff Mobile
    Connected QR, KDS and POS views receive the order update.
  3. 20:30
    KDS bumps a ticket; customer view ticks to 'Ready'
    No separate status re-entry is required while the workflow remains connected.
  4. 21:00
    Rider courier picks up an online order
    Storefront customer view ticks to 'On the way'.
  5. 21:25
    Card authorised on Terminal
    The POS payment drawer receives the authorised state against the order.
Live by default

Shared state instead of separate refresh loops. Connected surfaces follow the same shift.

Supported order, ticket, table, payment, staff and delivery events move across the products participating in that workflow while they are online.

Connected platform

Where real-time shows up

How Cibus works
The event flow that connects supported product surfaces.
Platform
Kitchen Display System
Where real-time ticket flow is most visible in service.
Service ops
Rider
Where real-time delivery status reaches the customer.
Delivery
FAQ

Real-time questions

Do staff need to refresh anything?

Connected clients subscribe to supported live state and do not normally require a manual refresh. A working network connection is required, and the application shows reconnect or retry state when it cannot confirm an update.

See real-time service in action.

See how Cibus connects service, kitchen operations, payments, reporting, customer engagement and delivery into one restaurant operating system.

Book a DemoExplore the platform