Restaurant software questions, answered directly.
Clear answers about the Cibus platform, product scope, payments, pricing, onboarding, data controls, commercial markets and support. Exact deployment terms are documented during discovery.
Cibus platform
What is Cibus?
Cibus is a B2B restaurant operating system. It connects configured products for POS, QR ordering, kitchen display, payments, staff, reports, direct online ordering, customer growth and delivery in one platform.
Is Cibus a consumer food delivery app?
No. Cibus sells restaurant software to operators. Storefront is a restaurant's branded direct-ordering channel, and Rider supports restaurant delivery operations; Cibus does not position either product as a multi-restaurant consumer marketplace.
Does Cibus replace every restaurant system?
Not automatically. Fit depends on the selected products, restaurant workflow, market, payment setup, hardware and required integrations. Discovery maps what Cibus can replace, what should connect and what should remain in place.
Products
Are Storefront, Reach, Stories and Rider implemented?
Yes. Storefront, Reach, Stories and Rider are implemented Cibus products. Exact channel, provider, market and deployment availability is confirmed during discovery.
Can I use the POS without QR ordering?
Yes. Cibus can be scoped around the products a restaurant needs. The proposal records selected modules, dependencies, location scope, payment setup, hardware, onboarding and support.
Does Cibus use AI to run the restaurant automatically?
No. AI Insights provides briefings, questions and recommendations for operator review. Stories prepares editable content drafts. Cibus positions AI as decision support and drafting, not silent operational or publishing autopilot.
Payments
Which payment methods does Cibus support?
Payment support depends on market and configuration. In Great Britain, Cibus supports Stripe and cash workflows. In Malaysia, supported categories include cash, cards, direct banking, QR Pay and e-wallets. Exact schemes, providers, hardware and commercial terms are confirmed during discovery.
How does reconciliation work?
Supported payment records link to the relevant order or orders. Shift-close and end-of-day workflows compare recorded tender activity, expected cash and counted cash, while the available records depend on the configured payment paths.
Are payment-processing costs included in Cibus pricing?
Payment-provider costs and any applicable Cibus commercial components are documented in the written proposal and provider terms. Cibus does not publish a universal processing rate or imply that third-party costs are included by default.
Pricing
Why isn't pricing published?
Cibus pricing depends on product mix, location count, payment setup, hardware needs, onboarding and support. Commercial terms are prepared after discovery so the proposal can list the actual scope and assumptions.
Does Cibus guarantee lower costs or better restaurant performance?
No. Cost and operational outcomes depend on the restaurant, current contracts, selected products, payment setup, hardware, staffing and rollout. Cibus does not promise revenue, savings, margin, speed or other performance improvements.
Onboarding
How long does onboarding take?
Timing depends on product scope, menu and data preparation, hardware, payment onboarding, integrations, training and number of locations. Cibus documents a rollout plan after discovery instead of promising one setup time for every restaurant.
Do you help import our menu?
Cibus AI menu import can turn a photo, PDF or screenshot into a draft of items, prices, categories, modifiers and detected allergen or dietary fields. The restaurant must review and correct the draft before publishing; it does not replace allergen or food-safety verification.
Can a multi-location group roll out in phases?
Yes. Locations and products can be sequenced in a rollout plan. Restaurant-level configuration, roles, data migration, training, hardware and operational acceptance should be confirmed for each phase.
Data, access and privacy
How is restaurant data protected?
Cibus uses database row-level security policies to scope restaurant data to authorised restaurant access, while roles and capabilities gate supported actions. The applicable architecture, audit coverage and operational controls can be reviewed during discovery.
Does Cibus make a restaurant GDPR or privacy compliant?
No software establishes legal compliance on its own. Cibus provides access and data-handling controls that can support a restaurant's governance processes, while contracts and privacy terms document roles, authorised use, retention, subprocessors and rights-request routing for the selected workflow and market.
Does Cibus store raw payment-card numbers?
Payment-card entry and processing are handled through configured payment providers such as Stripe. Cibus application records do not store raw card numbers.
Markets and support
Where is Cibus commercially available?
Cibus's initial commercial markets are Great Britain and Malaysia. Product, payment, hardware, language and support scope for a location is confirmed during discovery rather than inferred from website access alone.
What support is included with Cibus?
Implementation, training and ongoing support coverage are defined in the proposal and customer agreement. Existing customers use the support route supplied in the Admin Dashboard or their agreement; the website contact form is not an emergency support channel or product-support SLA.
When does Cibus answer website sales enquiries?
The public response promise is within one business day. Sales enquiries are staffed Monday to Friday, 09:00–17:30 Europe/London for Great Britain (excluding applicable England bank holidays) and 09:00–18:00 Asia/Kuala_Lumpur for Malaysia (excluding applicable federal/Selangor holidays).
Still have a question?
See how Cibus connects service, kitchen operations, payments, reporting, customer engagement and delivery into one restaurant operating system.