Cibuscibus.
For independent operators

Run your restaurant without stitching five systems together.

Cibus gives independent restaurants one connected platform for POS, QR ordering, kitchen tickets, payments, staff, reporting, online ordering and customer growth — so every shift runs from the same menu, order and payment record.

Built for cafés, takeaways, casual dining, ghost kitchens and single-site hospitality businesses.

Book a DemoExplore Products
CafésTakeawaysCasual diningGhost kitchensSingle-site operators
Owner dashboard
Today · Daily briefing
Live
Active orders
Service running
Kitchen queue
Tickets routed
Payment status
Captured & receipted
Staff on shift
Floor + kitchen
Table status
Occupied / open
Online order
Storefront live
Ready for review
AI Insights
  • Menu update awaiting publish
  • End-of-day reconciliation ready
  • Campaign draft prepared in Reach
The patchwork problem

Independent restaurants are running modern service on disconnected tools.

An independent restaurant can rely on several tools that do not share an order or customer context. The seams appear in reconciliation, customer records and reporting.

POS in one place
QR ordering somewhere else
Kitchen tickets on paper or another app
Payments and receipts disconnected
Staff operations handled manually
Reports exported to spreadsheets
Marketing tools disconnected from order history
Delivery and online ordering governed by third-party terms
Before / after

From patchwork to one operating layer.

Same shift. Same orders. Same payments. A different shape underneath.

Before Cibus
Patchwork
  • Separate POS
  • Separate ordering app
  • Separate payment terminal
  • Manual kitchen handoff
  • Manual staff follow-up
  • Disconnected customer list
  • Spreadsheet reporting
With Cibus
One operating layer
  • One menu
  • One order flow
  • One kitchen queue
  • One payment record
  • One receipt trail
  • One customer view
  • One dashboard
A day in service

A full shift, connected from first order to close.

This illustrative shift shows one order moving through connected Cibus products, with the next team receiving the relevant status and context.

  1. 01
    Manager checks the dashboard
    Daily briefing surfaces what needs attention before doors open.
  2. 02
    Staff open shift & pair terminal
    Shift open, cash float set, terminal paired and ready.
  3. 03
    Orders are taken
    Customers order by QR or staff enter orders at POS.
  4. 04
    Kitchen receives routed tickets
    Tickets land on the right station as soon as they're sent.
  5. 05
    Staff track order & table status
    Floor sees order progress and table state in real time.
  6. 06
    Payments captured & receipts issued
    Card, wallet, cash or split — every receipt tied to the order.
  7. 07
    End-of-day reconciliation
    Daily close ties payments to orders and float. Reports ready.
  8. 08
    AI Insights highlights attention items
    Review what needs action before the next shift opens.
POS tablet
Service open
T1
T2
T3
T4
T5
T6
Table status · Order open
QR ordering · phone
Web
Starteradded
Mainadded
Sideadded
Drinkadded
Sent to kitchen
Kitchen tickets
In prep
Ticket ARouted
Ticket BClaimed
Ticket CReady
Payment & receipt
Captured
  • MethodStripe Terminal
  • TipApplied
  • SplitBalanced
  • ReceiptIssued
Staff mobile
Shift open
  • Order taken at table
  • Ticket fired to kitchen
  • Payment confirmed
  • Cash float updated
Storefront order
Online order
Direct online channel · Pickup or delivery · Tied to the same menu and customer record.
What Cibus replaces

Replace the patchwork. Keep the control.

Every product runs on the same menu, order, payment and customer record — so you can collapse tools without losing visibility.

Owner outcomes

Built around the realities of independent operators.

What changes when service, payments, staff and growth use connected records, shared identifiers and supported events.

Connected service hand-offs
Floor, kitchen and till use the same order context.
Order-linked payment records
Supported receipts and payment records remain tied to the relevant order.
Connected reconciliation
End-of-day reporting uses payment, order, refund and float records from the same platform.
Shared service visibility
Owners can review active orders, kitchen queue and supported payment state together.
Governed customer context
Order history, consent and segment access follow the applicable restaurant role, contract and privacy responsibilities.
Connected menu and staff management
Supported product surfaces use the configured menu, staff and role context.
Growth tools connected to real order history
Storefront, Reach and Stories run from operational data.
Direct customer relationship

Add a direct channel alongside third-party routes.

Storefront, Reach and Stories connect direct ordering, campaign preparation and content drafts to the restaurant's menu and supported customer context. Access to order history, consent and segments follows the restaurant's contract, role scope and data-protection responsibilities.

Cibus is a B2B restaurant operating system — not a consumer marketplace.

StorefrontReachStoriesCustomer viewConsent
Reach & Stories
Campaign draft
  • Segment built from order history
  • Story draft from menu
  • Ready for review
Money & payments

Every payment tied back to the order.

Stripe, Stripe Terminal, wallets, cash and manual card recording all settle against the same order line — with balanced receipts and exact-cent math.

Stripe & Stripe Terminal
Card-not-present and card-present captured against the same order.
Wallets, cash & manual card
Every method recorded with attribution to staff and shift.
Splits, tips & service charges
Applied consistently with balanced totals on one order.
Digital & thermal receipts
Supported receipt paths stay linked to the relevant order and payment record.
EOD reconciliation
Daily close balances payments, refunds, float and tips.
Exact-cent calculations
Tax, discount and service-charge math done in integer cents.
Payment & receipt
Captured
  • MethodStripe Terminal
  • TipApplied
  • SplitBalanced
  • ReceiptIssued
End-of-day reconciliation
Balanced
  • Payments tied to orders
  • Tips and service charges applied
  • Cash float closed
  • Receipts issued
  • Refunds and adjustments audited
Staff & kitchen

Front-of-house and kitchen stay in sync.

Floor and kitchen see the same live state — order, table, ticket and payment — without phoning back and forth.

Staff mobile
Floor tool for tables, orders, payments and shifts.
POS
Tablet service flow for tables, counters and splits.
KDS
Routed kitchen tickets with claim, prep and ready states.
Table & order status
Floor and kitchen see the same live state of every order.
Shift open/close & cash float
Open, close and balance shifts with cash float tracking.
Error & retry messaging
Clear messaging when something needs attention or a retry.
Staff mobile
Shift open
  • Order taken at table
  • Ticket fired to kitchen
  • Payment confirmed
  • Cash float updated
POS tablet
Service open
T1
T2
T3
T4
T5
T6
Table status · Order open
Kitchen tickets
In prep
Ticket ARouted
Ticket BClaimed
Ticket CReady
Setup & growth path

Start with service. Add growth when you are ready.

Cibus is modular. Most independents start with the core service layer and add direct ordering, growth and delivery later.

  1. Core service
    Step 01
    Run the floor
    POS, QR ordering, KDS and payments.
  2. Operations
    Step 02
    Run the business
    Staff, admin dashboard and reports.
  3. Direct ordering
    Step 03
    Add a branded channel
    Storefront for direct online ordering.
  4. Customer growth
    Step 04
    Plan customer engagement
    Reach for campaigns and Stories for review-first content.
  5. Delivery control
    Step 05
    Run restaurant-managed delivery
    Rider for dispatch, tracking and proof of delivery.
  6. Intelligence
    Step 06
    Decide with data
    AI Insights for daily briefings and analysis.
Commercial model is shaped around your operation and rollout — not a fixed package.
See Pricing
FAQ

Independent restaurants — common questions.

Is Cibus only for large restaurant groups?

No. Cibus is designed for single-location independents—cafés, takeaways, casual dining and ghost kitchens—as well as growing operators.

One connected operating system for your restaurant.

See how Cibus connects service, kitchen, payments, staff, reporting and growth through configured workflows and shared operating context.

Book a DemoExplore Platform