Cibuscibus.
How it works

From order entry to shift review on one operating layer.

Follow a Cibus order from the table scan, server POS or Storefront, through kitchen prep, payment, receipt, reporting and customer re-engagement.

Book a workflow demoReal-time operations
Event stream · live
Illustrative
  1. QR
    QR Order & Pay
    Table T12 · 4 guests
    Open
  2. POS
    POS
    Server SM · 6 items
    Sent
  3. KDS
    Kitchen Display
    Grill · Cold
    Cooking
  4. PAY
    Payments
    2× card · split
    Authorised
  5. REC
    Receipts
    Digital · order linked
    Issued
  6. RCH
    Reach
    Ready for review
    Drafted
  7. INS
    AI Insights
    Tonight's briefing
    Updated
One order · seven surfaces · one record
1operating layer

Ordering, kitchen, payments, staff and growth on one platform.

1event stream

Supported order actions contribute to connected operational events.

1menu source

Connected channels use the configured menu and price records.

1customer profile

Supported visit, order and consent context can be associated with a customer profile.

The pain

What patchwork stacks cost a restaurant

Patchwork stacks
POS, online ordering, customer engagement and delivery tools can hold separate menu, order and customer records.
Manual hand-offs
Staff retype information between tools because the systems don't talk to each other.
Reports that don't agree
Different tools can use different definitions and cut-off times, leaving the team to reconcile the shift.
Customer disappears in between
QR, marketplace, phone and walk-in customers all look different to the team.
Old way vs. Cibus

From four vendors to one operating layer

Patchwork stack
  • POS, QR, KDS, payments, marketing and delivery on separate vendors
  • Staff retype data between tools
  • Receipts and orders live in different systems
  • Customer follow-up disconnected from real orders
With Cibus
  • One operating layer carrying supported orders from entry to shift review
  • Supported events connecting configured POS, KDS, payment, Storefront, Reach, Rider and Insights workflows
  • Receipts, refunds and tips tied to the order line item
  • Supported customer and consent context available to Reach workflows
The full flow

What happens between scan and insight

  1. 01Entry
    Order enters from QR, POS, Storefront or Staff Mobile
    Connected ordering surfaces use the configured menu and modifier records.
  2. 02Build
    Connected order surfaces use shared order and calculation rules
    Pricing, tax and discount rules are validated through the configured workflow, reducing per-channel drift.
  3. 03Route
    Kitchen tickets route by station
    Priority, special instructions and prep timers per station.
  4. 04Pay
    Payment captured: card, terminal, wallet, cash, voucher or split
    Tied directly to the order line items.
  5. 05Receipt
    Digital and printed receipts issued automatically
    The order and payment record supports receipt, refund and end-of-day workflows.
  6. 06Engage
    Customer context supports Reach, Stories and AI Insights
    Access and consent scope still apply; recommendations and drafts remain subject to operator review.
  7. 07Deliver
    Delivery orders dispatch to Rider
    Live tracking and proof of delivery flow back to the order.
  8. 08Report
    Owners review sales activity, shift status and recommendations
    Connected records provide a consistent starting point across configured sites and shifts.
The layers

What connects underneath

•
Menu & modifiers
One menu drives POS, QR, Storefront and reporting — with per-location overrides.
•
Order record
A connected order record is updated by the product surfaces participating in that workflow.
•
Kitchen routing
Tickets route by station with priority, prep timers and expediter view.
•
Payment & receipts
Card, terminal, wallet, cash, vouchers and splits — connected to the order.
•
Customer profile
Supported order history, consent and preference records can inform Reach and AI Insights.
•
Event stream
Supported operational events provide shared state for reporting and configured activity records.
Example shift

One order, end to end

  1. 19:42
    Guest scans the QR menu at the table
    Same live menu as the POS the server is holding.
  2. 19:48
    Server adds wine pairing from Staff Mobile
    The connected QR view receives the updated order state.
  3. 20:05
    Kitchen tickets route to grill and cold stations
    Expediter sees the full pass; each station sees its own work.
  4. 21:15
    Bill split across two cards through Stripe Terminal
    Payment allocations remain tied to the order; supported refund workflows retain payment and order context.
  5. 21:22
    Digital receipts issued from the payment record
    Where appropriate, separately recorded marketing preferences can support a later Reach workflow.
  6. Tomorrow
    AI Insights briefing raises a menu question
    The owner reviews the supporting records and decides whether any action is appropriate.
One layer

Not four vendors stitched together. One operating layer for the whole shift.

Supported scan-to-insight events connect configured menu, order, payment and customer-context workflows, reducing manual reconciliation.

Connected platform

Explore each layer

Real-time, payment and control layers share supported operational context across the workflows configured for the restaurant.

Real-time operations
How POS, KDS, payments and Rider share state across connected workflows.
Platform
Payments & money
Splits, tips, service charges, receipts and reconciliation in the order flow.
Platform
Security & compliance
Role and capability checks, tenant isolation and supported activity records.
Platform
FAQ

How Cibus actually runs

Do all surfaces share the same menu?

Configured POS, QR, Storefront and reporting workflows use connected menu records. Restaurant, channel and location differences depend on the approved setup.

Walk through a live Cibus order.

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

Book a DemoExplore the platform