Cibuscibus.
Solutions

Connect the counter, pickup queue and daily menu.

Fast counter POS, modifier-aware menus, mobile staff tools, pickup ordering and customer marketing — all in one connected system.

Book a café demoExplore the Platform
Cibus · Borough & Vine
One operating layer · live
POSQRKDSPaymentsStaffReach
Active orders
Live
all channels
Table status
In service
floor view
Kitchen queue
Connected
by station
Payment status
Recorded
audit trail
Live event stream
all surfaces
  • Order sent to kitchenPOS · table status
  • Online order receivedStorefront · new
  • Payment receivedPayment status · recorded
  • Campaign draft readyReach · review
7connected modules

Recommended Cibus surfaces for this operation, on one platform.

6workflow stages

An illustrative route through this restaurant operation.

1operating layer

Orders, kitchen, payments and staff share connected operating context.

1customer context

Supported ordering and engagement workflows use connected customer records.

The pain

What this restaurant type runs into

Slow counter queues at peak
A crowded item grid and unstructured modifiers add extra steps during the morning rush.
Modifier chaos on hot drinks
Milk, shot, syrup and temperature variants are bolted on, not designed in — so they're missed or wrong.
No view of repeat customers
Regulars are invisible to the till. Loyalty lives in a separate app the team forgets to use.
Online ordering bolted on the side
Third-party pickup orders can arrive on a separate device with different commercial terms and limited customer context.
Marketing disconnected from sales
Email tools don't see what was actually bought — so campaigns talk past real behaviour.
Old way vs. Cibus

From patchwork to one connected layer

Without Cibus
  • Two separate terminals for in-store and pickup
  • Loyalty app + POS that don't talk
  • Modifiers typed as free text
  • No way to message yesterday's regulars
  • End-of-day cash-up done by hand
With Cibus
  • One counter POS for in-store and pickup
  • Identified, supported visit activity can update customer context
  • Modifier sets designed for drinks and pastries
  • Reach can prepare consent-aware audiences from eligible order and visit records
  • End-of-day reconciliation handled in the platform
Workflow

An example service flow

  1. 01Order
    Customer orders at counter or via Storefront pickup
    Connected counter and Storefront workflows use the configured menu and modifiers; identified activity can be associated with the appropriate customer context.
  2. 02Modifiers
    Drink modifiers fire to the bar station
    Milk, shot and temperature land cleanly, not as free-text notes.
  3. 03Bake
    Pastry items print or appear on the bakery KDS
    Behind-counter staff see them in the order they're prepped.
  4. 04Pay
    Customer pays by card, wallet or saved account
    Cash, Stripe Terminal and wallets all routed through one payment flow.
  5. 05Receipt
    Digital receipt issued where opted in
    The receipt stays tied to the order and payment record; printed and digital paths depend on configuration.
  6. 06Loyalty
    Visit count updates the customer profile
    Recorded activity can support consent-aware Reach segments without exporting a separate list.
How Cibus helps

What Cibus does for cafés & bakeries

•
Tap-to-order counter POS
Keep frequently used items visible and apply structured modifiers without free-text workarounds.
•
Modifier sets built for drinks and pastries
Designed around milk, shot, syrup, temperature, allergens — not a free-text afterthought.
•
Customer profile across visits
Where a diner is identified and the restaurant is authorised to use the context, supported counter and Storefront activity can be associated with a customer profile.
•
Owned pickup ordering on your brand
Storefront provides a branded direct-ordering route connected to the same menu and order flow.
•
Customer segments from order history
Reach can prepare consent-aware segments using recorded visit and order activity.
•
Daily-special content drafts
Stories prepares caption and visual drafts for today's bake, ready for owner review before use.
One platform

Not a stack of disconnected tools. One operating layer for cafés & bakeries.

Ordering, kitchen, payments, staff, reporting, customer engagement and delivery share operational context instead of relying on separate hand-offs.

Recommended modules

The Cibus modules that fit best

POSStaff Mobile AppQR Order & PayPayments & ReceiptsStorefrontReachStories
Connected platform

The rest of Cibus is one click away

The modules on this page are designed to share menus, order context, customer records and operational events where their workflows connect.

Storefront for pickup
A branded pickup channel using the same menu and modifiers as the counter POS.
Customer ordering
Reach for regulars
Build consent-aware segments from recorded visit activity inside the connected platform.
Growth
Stories for daily bakes
Draft content for today's specials, with the owner reviewing before it is used or published.
Growth
Benefits

What changes for the operator

•
Counter-first order entry
A counter view designed around frequently used items and structured modifiers.
•
Structured modifier hand-off
Milk, shot, syrup and temperature choices are recorded as defined options for the bar.
•
Connected visit context
Supported visit history can inform the till view and consent-aware Reach segments.
•
Direct pickup route
Storefront gives known diners a branded ordering path alongside third-party channels.
•
Review-first content
Stories prepares editable drafts for the team to review before use.
Example shift

What it looks like in service

  1. 07:42
    Morning rush begins on three counter terminals
    Same menu, same modifiers, no staff switching apps.
  2. 08:10
    Pickup orders land directly on the bakery KDS
    Storefront orders queue alongside walk-ins without a separate device.
  3. 08:35
    An identified returning customer is associated with supported visit context
    Staff can review any configured, eligible offer; consent and promotion eligibility remain separate.
  4. 11:00
    Lull — owner drafts today's croissant post in Stories
    AI suggests three caption variants for review before publishing.
  5. 16:30
    Reach prepares a win-back audience from eligible, identified records
    The operator reviews audience, channel eligibility, consent and message before send.
  6. 18:00
    End-of-day reconciliation is reviewed
    The report compares configured cash, card and Stripe records against orders.
Illustrative workflow · not customer or performance evidence
FAQ

Cafés & Bakeries questions

Is the POS fast enough for a morning rush?

The counter view keeps frequent items visible and uses structured modifier sets. The demo should be tested against your actual menu, hardware and peak workflow before rollout.

Run cafés & bakeries on one operating layer.

Book a demo and see how Cibus connects ordering, kitchen, payments, staff, reports, marketing and delivery for your operation.

Book a café demoTalk to Sales