Cibuscibus.
Storefront

Your ordering channel, not a marketplace.

Give customers a branded online ordering experience for pickup and delivery — connected to the same menu, kitchen, payments, customer records and marketing tools as the rest of Cibus.

Book a DemoExplore Reach
borough-and-vine.cibus.food
Borough & Vine
Ordering open · Pickup and delivery
PopularPastaPizzaDessertsDrinks
Truffle Tagliatelle
£18.00
Allergens: gluten · dairy
Mains
Heritage Tomato & Burrata
£11.50
Allergens: dairy
Starters
30-day Ribeye, Bone Marrow Butter
£32.00
Allergens: dairy
Mains
Online order · status
Ordered·Kitchen·Ready·Handover
Menu synced from AdminOrders connect to KDSDelivery connects to RiderConsented order context supports Reach
Illustrative ordering UI
1branded channel

Your ordering site under your name, not a marketplace listing.

2fulfilment modes

Pickup and delivery, handled in the same flow.

1shared menu

Same menu and modifiers as POS and QR Order & Pay.

1customer record

Authorised order context can support Reach audience review.

Direct-ordering option

Add a branded ordering path alongside your channel mix.

Marketplace and direct channels serve different roles. Storefront provides a restaurant-branded ordering path connected to the Cibus menu, kitchen, payment and order workflows. Commercial terms and customer-data responsibilities remain defined by the channels and agreements a restaurant selects.

Third-party marketplace
  • Generic listing beside competitors
  • Commercial terms set by the marketplace
  • Customer access depends on marketplace terms
  • Separate menu maintenance
  • Manual reconciliation against the POS
  • Harder to run win-back campaigns
Cibus Storefront
  • Branded ordering site under your name
  • Restaurant-branded customer journey
  • Same menu and modifiers as POS and QR
  • Orders enter the configured Cibus workflow
  • Pickup and delivery flows together
  • Authorised order context can support Reach
Customer journey

Browse, customise, checkout and track.

01
Discover
Opens the restaurant's branded link.
02
Browse
Published menu with photos, allergens and tags.
03
Customise
Modifiers, extras, removals, notes.
04
Fulfilment
Pickup time or delivery address.
05
Checkout
Available card or wallet options for the configured payment setup.
06
Track
Accepted → kitchen → ready → handover.
07
Return
Order history and account context where configured.
One menu

One menu across configured ordering channels.

Storefront uses the same Cibus menu foundation as POS and QR ordering. Restaurants do not rebuild items, prices, modifiers, photos or allergens in another system — when the menu changes, the online ordering experience stays aligned with operations.

Admin · menu item
Truffle Tagliatelle
£18.00
section · Mainsmodifier group · configuredallergens · gluten · dairychannels · POS · QR · Storefront
Modifier group · available
Channel status · published
One menu record for the channels where the item is published.
Storefront · customer card
Truffle Tagliatelle
£18.00
Published menu description and item details.
MainsContains gluten and dairy
Fulfilment

One Storefront. Two fulfilment paths.

Pickup

Order ahead, collect when ready.

Customers choose a pickup time and place the order. The kitchen sees it inside the same KDS flow as table and counter orders — not a separate tablet.

Order placed→KDS ticket→Preparing→Ready for pickup→Collected
Delivery

Delivery connected to Rider.

Delivery orders flow from Storefront into Rider dispatch with delivery status and tracking linked to the same order record.

Order placed→KDS ticket→Rider assigned→Picked up→Delivered
Accounts

Keep order context available after checkout.

Storefront can connect account, order-history and preference experiences to the customer journey. Saved details and payment options depend on the configured market and Storefront scope and are confirmed during discovery.

Customer · signed in
Guest
Customer preferences
Delivery address
Customer-provided delivery address
Payment
Managed by the configured payment provider
Recent orders
  • RecentDelivery · completedOrder record
  • PreviousPickup · collectedOrder record
  • HistoryOrder recordOrder record
Preferences
  • Marketing emailYes
  • Marketing SMSNo
  • LanguageEnglish
  • DietaryVegetarian
Configured consent and preference fields can inform Reach audience review.
Operations

Online orders should not create another operations silo.

One operating system
Storefront order→Menu / modifiers→Checkout / payment→KDS→Rider or pickup→Receipt→Reach segment

Storefront orders enter the connected Cibus workflow rather than a separate marketplace tablet. Configured KDS, Admin, payment, Rider and Reach context can remain linked to the order record.

Repeat business

Use consented order context to plan follow-up.

Where the required consent and data scope are in place, Storefront order history and preferences can support Reach audience selection for return offers, launch announcements and seasonal campaigns. Audience and channel choices remain subject to review.

Reach · segment builder
Recent Storefront customers
ChannelStorefront
Order recencyRecent-order window
ConsentEmail · yes
Menu categorySelected category
Campaign idea
"Return-visit campaign draft"

Prepare an offer for eligible Storefront customers using configured order context and channel-consent status. Audience, offer and timing remain subject to review.

Schedule · Review
Channel · Select
Offer · Review
Supports Reach audience review where consent and data scope are configured.
In service

Friday dinner, ordered direct.

A customer opens the restaurant's Storefront, chooses delivery, customises a pizza, adds dessert, pays online and tracks the order. The kitchen receives the ticket in KDS, Rider handles delivery, the receipt is issued, and consented order context can be reviewed for a future Reach audience.

Illustrative service flow
  1. Order placed
    Customer completes an order on Borough & Vine's Storefront.
  2. Payment
    Configured online payment is confirmed against the order.
  3. Kitchen
    The order enters the configured KDS workflow.
  4. Ready
    The fulfilment status is updated for handover.
  5. Delivery
    The delivery task connects to Rider where configured.
  6. Complete
    The receipt and order status remain linked to the order record.
  7. Follow-up
    Consented order context can be reviewed for a Reach audience.
Illustrative scenario
A branded front door

Not another marketplace listing. A direct channel connected to operations.

Branded ordering for pickup and delivery, on the same menu, kitchen, payments and customer record as the rest of Cibus.

Connected platform

Storefront is the front door to the Cibus operating system.

Kitchen Display System
Configured online orders can enter the connected kitchen ticket flow alongside POS and QR orders.
Payments & Receipts
Available online payment and receipt context can remain tied to the order record.
Rider
Configured delivery orders can move into Rider dispatch, status and delivery-confirmation workflows.
Reach
Authorised order and consent context can support Reach audience review.
Admin Dashboard
Configured Storefront order records can appear with other operational reporting context.
QR Order & Pay
Storefront and in-venue QR share the same menu foundation and modifiers.
FAQ

Storefront questions, answered.

Is Storefront a marketplace?

No. Storefront is a branded ordering channel for the restaurant. Customers use the restaurant's ordering link rather than browsing a multi-restaurant marketplace listing.

Add a branded online ordering channel.

Bring menu, checkout, kitchen, delivery, receipt and consent-aware follow-up context into one connected restaurant ordering workflow.

Book a DemoExplore Reach