Cibuscibus.
Rider

Own the delivery layer.

Coordinate Storefront delivery orders through a connected rider workflow. Review assignments, pickup and drop-off status, available delivery evidence and customer updates while keeping the task linked to its Cibus order.

Discuss Delivery OperationsExplore Storefront
Rider · Dispatch · Service in progress
MapBoardRiders
Dispatch board
Pickup task
Ready for pickup
Assigned task
Assigned
Active task
In transit
Completed task
Delivered
Delivery route · selected task
Restaurant
Rider · On route
Dropoff
Route status
Rider app · Active
Pickup
Borough & Vine
Dropoff
Customer address
ArrivedPickupNavigateDropoff
Delivery confirmation · configured evidence
Storefront orderKDS ready stateRider dispatchCustomer status viewDelivery record linked to order
Illustrative delivery operations
Dispatchdispatch view

Review assignments and delivery status in one workspace.

Statustask checkpoints

Pickup and drop-off context stays with the delivery task.

Evidencedelivery confirmation

Configured evidence can be linked to the order record.

Orderorder record

Delivery tasks remain connected to the Cibus order workflow.

The problem

Delivery breaks when it lives outside the restaurant system.

Most own-delivery operations are stitched together with phone calls, WhatsApp groups, printed receipts, manual driver assignment and separate tracking. That makes it hard to know what is ready, who has the order, whether it was delivered and which task records are available for review. Rider keeps delivery connected to Storefront, KDS, Admin, payments and the customer order record.

Without a connected delivery layer
  • Delivery order arrives on a separate tablet
  • Kitchen prints a ticket disconnected from dispatch
  • Manager messages a driver on WhatsApp
  • Customer calls the restaurant for status
  • Proof of delivery is missing or inconsistent
  • Earnings are reconciled manually in spreadsheets
With Cibus Rider
  • Storefront order creates the delivery workflow
  • Kitchen status feeds dispatch readiness in KDS
  • Rider accepts or receives an assigned task
  • Customer tracking updates from the same order
  • Configured handover evidence stays with the delivery task
  • Admin provides an operational delivery view
End to end

From direct order to delivery confirmation.

  1. 01
    Storefront order
  2. 02
    Kitchen preparation
  3. 03
    Ready for dispatch
  4. 04
    Rider assigned
  5. 05
    Pickup confirmed
  6. 06
    Dropoff confirmed
  7. 07
    Delivery record updated
Dispatch

A dispatch board for real service pressure.

Rider gives operators a dispatch view of delivery tasks by status: unassigned, offered, accepted, at pickup, in transit, delivered or issue flagged. Managers can review what needs attention from the task board.

Dispatch board · operational view
Neutral status labels
New
New delivery
Storefront · Delivery
Unassigned
Ready for pickup
Pickup task
Storefront · Delivery
Offered
Assigned
Assigned task
Storefront · Delivery
Accepted
In transit
Active task
Storefront · Delivery
On route
Delivered
Completed task
Storefront · Delivery
Confirmed
Issue flagged
Flagged task
Storefront · Delivery
Issue note
Rider app

A simple mobile workflow for riders.

Riders need a focused mobile workflow, not a full restaurant admin system. Rider presents task offers or assignments, active delivery details, navigation handoff and pickup and drop-off status. Earnings, payout and support views depend on the configured market deployment.

Rider · Offers
Incoming delivery
New offer
Pickup
Borough & Vine
Dropoff
Customer address
Payout
Payout shown
DeclineAccept
Rider · Active delivery
In progress
Delivery task
Pickup confirmed
On route
Dropoff confirmed
NavigateConfirm dropoff
Rider · Confirmation
Delivery confirmation
Delivery task
Handover
Issue note
Evidence
Configured evidence preview
Confirmation recorded
Proof of delivery

Keep handover context with the delivery task.

Rider can keep pickup, drop-off and configured delivery evidence linked to the Cibus order. Available evidence types, access and retention are documented for the deployment.

Order record
Online order · delivery record
Confirmation recorded
  • PickupConfirmed
  • DropoffConfirmed
  • Delivery evidenceConfigured
  • Review statusAvailable
  • Issue noteNone recorded
Pickup, drop-off and available delivery evidence remain linked to the Cibus order.
Pickup checkpoint
Pickup status remains linked to the delivery task.
Drop-off checkpoint
Drop-off status remains linked to the delivery task.
Delivery evidence
Available evidence depends on the configured workflow.
Handover context
Record the configured handover status and notes.
Delivery note
Capture contextual information for the task.
Time context
Show available timing context for recorded checkpoints.
Issue notes
Rider can flag and describe an issue.
Admin visibility
Configured delivery records are available for operations review.
Customer tracking

Give customers a connected delivery-status view.

Configured Rider status can be exposed through the customer order experience, including accepted, prepared, picked-up and on-the-way states. Available detail and update frequency depend on the deployment.

Rider · Customer tracking
Borough & Vine
Your order is on the way
Delivery status
Order received
In kitchen
Ready for pickup
Rider assigned
Picked up
On the way
Delivered
Same order record
Tracking states map to the same Cibus order the kitchen worked on.
Status context
Customer-facing states can reflect configured delivery events.
Self-service view
Customers can review available progress in the order experience.
Branded experience
Status remains inside the restaurant's Storefront journey.
Delivery zones

Define delivery scope for each location.

During setup, review the service areas, order rules, delivery fees, service windows and assignment policy available for the restaurant's market and commercial scope.

Delivery zone
Zone · Central
Active
  • Service areaPolygon defined
  • Minimum orderConfigured
  • Delivery feeConfigured
  • AvailabilityService hours
  • RidersEligible riders
Delivery scope
Review available service-area options per location.
Service-area rules
Confirm available zone behaviour for the market.
Order rules
Document supported minimums and eligibility rules.
Delivery fees
Define applicable fee handling in the commercial scope.
Service timing
Review available service windows and lead-time settings.
Rider availability
Configure supported assignment and availability rules.
Operator review
Review tasks that need manual intervention.
Issue handling
Keep delivery exceptions visible for follow-up.
Earnings & reporting

Review rider and delivery records in context.

Rider keeps delivery work visible for riders and operators. Available views can include task status, earnings or payout records, issues and delivery confirmation; exact fields depend on the configured market and workflow.

Rider earnings · summary
Earnings records
Per-rider, per-period
Neutral preview
Completed delivery tasks—
Earnings record where configured—
Tip record where configured—
Payout status where configured—
Earnings and payout views depend on the configured market and commercial workflow.
Admin · delivery operations
Delivery operations
Available scope varies by deployment
Neutral preview
Tasks by status—
Order linkage—
Rider assignment—
Issue records—
Confirmation status—
Delivery scope—
Inside Rider

Configured tools for restaurant-run delivery.

01
Rider
  • Rider app
    Native mobile workflow for riders on the road.
  • Accept / decline
    Riders accept or decline offered jobs.
  • Earnings records
    Configured deployments can provide a per-rider delivery summary.
02
Dispatch
  • Dispatch board
    Assign, queue and reroute deliveries by status.
  • Status and route context
    Review the delivery status and available route context.
  • Delivery scope
    Review available service-area, order-rule and fee settings.
03
Operations
  • Delivery confirmation
    Keep configured handover evidence with the delivery task.
  • Issue handling
    Flag, note and resolve delivery exceptions.
  • Admin reporting
    Delivery operations visible across Admin.
Own the last mile

Not a separate delivery app. Dispatch connected to the order record.

Review assignments, pickup and drop-off status, available delivery evidence and rider activity in the context of the original Storefront order.

Connected platform

Delivery connected to the rest of service.

Rider connects the delivery task to Storefront orders and the relevant Cibus operational context. The exact KDS, payment, customer-status, Admin and Reach data available depends on the configured deployment.

Storefront
Delivery orders start from the restaurant's branded direct ordering channel.
Kitchen Display System
KDS readiness helps delivery teams know when an order can be picked up.
Payments & Receipts
Available payment and receipt context can remain linked to the delivery order.
Admin Dashboard
Configured delivery status, confirmation and rider activity can feed into the Admin operational view.
Reach
Eligible delivery customers can be considered for consent-aware follow-up when the required data scope is configured.
Staff Mobile App
Floor and counter teams stay aware of active orders and fulfilment status.
In service

A takeaway delivery, end to end.

A customer places a delivery order through Storefront. The kitchen prepares the order in KDS. Once it is ready, the delivery task is assigned through Rider. The rider updates pickup and drop-off status, available customer status is shown in the ordering experience, and configured delivery confirmation can appear in the Admin operational record.

Illustrative scenario
FAQ

Rider questions, answered.

Is Rider a third-party delivery marketplace?

No. Rider is a restaurant delivery-operations product connected to Cibus Storefront, order and kitchen workflows. It does not list multiple restaurants for consumer marketplace discovery.

Connect delivery to the rest of your restaurant.

Review how dispatch, delivery status, configured evidence and rider workflows can connect Storefront orders with the relevant Cibus operational context.

Discuss Delivery OperationsExplore Storefront