Cibuscibus.
Guide · Growth

How to own your online ordering channel.

A direct channel gives your restaurant more control over the ordering journey while marketplaces can remain part of the acquisition and delivery mix.

Answer first

The short answer

By Abbas8 min read

Do not treat direct ordering as a website project. Treat it as an operating channel: one controlled menu, an accessible mobile checkout, clear allergen information, secure payments, consent-aware customer communication and a fulfilment route that reaches the same kitchen workflow as every other order.

  • Run direct ordering alongside marketplaces instead of assuming an immediate replacement.
  • Model the economics and service workload for collection, owned delivery and third-party delivery separately.
  • Separate transactional messages from marketing consent and document data responsibilities.

Marketplaces can provide discovery, ordering and delivery infrastructure. Relying on one as the only digital route, however, leaves channel rules, customer access and commercial terms largely defined by its contract. A direct channel creates an additional route for diners who already know the restaurant; whether it improves economics depends on payment, fulfilment, support and acquisition costs.

Why this matters

Trade-offs in a marketplace-only model.

Limited first-party relationship
Access to contact details, order history and communications depends on the marketplace agreement and applicable privacy rules.
Channel-specific fees
Marketplace charges vary by contract and service. Compare the full fee schedule with payment, delivery, support and acquisition costs on a direct order.
Rules sit outside your control
Ranking, promotions, listing requirements and fees are governed by the marketplace's current terms.
Limited brand presentation
A shared marketplace interface limits control over navigation, presentation and the path back to your restaurant.
Shared support ownership
Support, refund and dispute responsibilities may be divided between the restaurant and marketplace. Make the hand-off explicit.
The reorder path stays in-platform
Without a direct option, repeat orders continue through the marketplace experience and its discovery rules.
Framework

A seven-step path to an operational direct channel.

  1. 01Step 01
    Decide what 'direct' means for you
    Click-and-collect from your site, scheduled pre-order, delivery via your riders, delivery via a marketplace's fleet — pick the mix that suits your operation.
  2. 02Step 02
    Get the menu, modifiers and routes right
    Reuse the same menu as your POS and KDS. Don't run a parallel online menu that drifts out of sync.
  3. 03Step 03
    Build the channel on your domain
    Use a clearly branded route that diners can verify and return to. If a service uses another domain, make the relationship and destination unambiguous.
  4. 04Step 04
    Wire orders into the same KDS
    Online orders should land on the same kitchen screen as in-store, with a clear channel tag and the same priority logic.
  5. 05Step 05
    Solve delivery operationally
    Either run your own riders with proper dispatch or use a delivery-as-a-service network while keeping the customer-facing hand-off clear.
  6. 06Step 06
    Drive the channel
    Use owned surfaces such as receipts, table materials and social profiles. Obtain and record the appropriate choice before sending electronic marketing.
  7. 07Step 07
    Keep marketplaces — on your terms
    Keep marketplace channels where they serve the operation, and make the direct route clear for diners who choose it.
Before / after

What changes when you own the channel.

Marketplace-only
  • All orders flow through a third-party app
  • Economics defined by the marketplace contract
  • Customer access follows the marketplace agreement
  • Marketing options depend on the marketplace relationship
  • Brand and presentation controlled by someone else
Direct + marketplace
  • Direct channel running alongside marketplaces
  • Direct-channel economics measured separately
  • Data roles, access and retention documented
  • Marketing uses a recorded, compliant contact basis
  • Branded route with measured acquisition sources
Channel design

Six things to get right.

•
One menu, many channels
In-store, QR, Storefront and any delivery integration all read from the same menu, modifiers and routing rules.
•
Phone-first checkout
Design the complete cart, modifier, allergen and payment path for small screens and keyboard or assistive-technology access. Do not require an account unless it is necessary.
•
Smart pickup windows
Use capacity-aware time slots and a clear process for pausing or adjusting availability when the kitchen cannot accept more work.
•
Customer-facing tracking
Show states such as accepted, preparing, ready or dispatched, and explain where a diner should go when the status needs attention.
•
Payments that match the venue
Wallets, cards, vouchers, promo codes — at checkout, at the door, in the till. Reconciliation rolls into the same EOD.
•
Receipts as a comms surface
Keep transactional receipts clear. A reorder link can be useful, but promotional messaging must follow the consent and opt-out rules that apply in the market.
Delivery options

You don't have to run your own fleet on day one.

•
Your riders, your dispatch
This gives the restaurant more operational control but also adds staffing, dispatch, safety, insurance and support responsibilities.
•
Delivery-as-a-service
A third-party fleet completes the last mile for an order initiated through the direct channel. Document who receives customer data and handles delivery support.
•
Marketplace fleet for spillover
A mixed model can add capacity, provided order ownership, hand-off, status updates and support responsibilities are explicit.
Pitfalls

Mistakes that quietly sink direct channels.

✓
Don't build it in isolation
A separate menu, stock view or kitchen queue creates a risk of inconsistent availability and duplicate staff work.
✓
Don't undersell direct
Set prices and promotions only after reviewing channel economics and marketplace terms. Do not assume price parity or undercutting rules are the same across providers.
✓
Don't ignore the funnel
Building it is not the same as giving diners a reason to find it. Plan the QR-to-direct, in-store-to-direct and marketplace-to-direct paths before launch.
Where Cibus fits

How this looks on Cibus.

•
Storefront, native
Cibus Storefront is a direct ordering channel built into the platform — same menu, same modifiers, same kitchen routes as your POS.
•
Live on the same KDS
Online orders land on the kitchen screen with a clear channel tag. Pacing and station routing apply the same way.
•
Rider for owned delivery
Cibus Rider provides the dispatch, tasking and proof-of-delivery layer if you want to run your own delivery — without spreadsheets.
•
Reach for the funnel
Segments, drafts and review-first campaigns draw from platform records, subject to the consent and entity scope configured for the campaign.
•
Customer data, governed by Cibus
Cibus records customer, consent and order data with scoped access. The restaurant and Cibus still need documented controller and processor responsibilities for each use.
Connected platform

The products that build the channel.

Storefront
Your direct ordering channel on the same menu.
Product
Rider
Dispatch, tasking and proof-of-delivery for your own riders.
Product
Reach
Segmented re-engagement built on the same customer data.
Product
FAQ

Common questions from operators.

Should we drop marketplaces entirely?

Not by default. Marketplaces can contribute discovery, ordering or delivery capacity. Compare each channel's contract, operating workload, customer access and economics before changing the mix.

Sources

Primary guidance used in this review

Food Standards Agency — allergen guidance for food businesses

UK guidance says distance sellers must provide allergen information before purchase and again when food is delivered.

UK Information Commissioner's Office — electronic mail marketing

Primary guidance on consent, the customer soft opt-in and offering a clear way to object.

PCI Security Standards Council — merchant payment responsibilities

Explains the payment-security responsibilities that remain when processing is outsourced.

Requirements vary by market and contract. This guide is operational guidance, not legal, tax, employment or payment-compliance advice.

Back to all guides

Designing your direct channel?

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

Book a DemoExplore Storefront