Restaurant intelligence that understands the shift.
Ask operational questions and review daily briefings across sales, menu, kitchen, staff, permitted customer context and financial-health signals — with recommendations kept under operator control.
A morning read on the shift ahead, in plain language.
Sales, menu, kitchen, staff, customers and financial health.
Operational questions assessed against permitted Cibus records.
Recommendations for operator review — no silent action.
Restaurant data is everywhere. Decisions still happen by gut feel.
Owners may review sales, kitchen tickets, staff hours, menu records and customer context in separate reports. AI Insights brings supported signals into defined analysis contexts so authorised managers can investigate operational questions in Cibus.
- Sales exports
- Kitchen ticket history
- Staff hours
- Menu reports
- Payment records
- Customer order history
- Gut-feel decisions
- Daily briefing
- Analysis contexts
- Restaurant-aware questions
- Menu recommendations
- Kitchen bottleneck review
- Staff & labour signals
- Financial health prompts
- Action cards for review
Start the day with the questions that matter.
The daily briefing presents sales patterns, menu signals, kitchen flow, shift activity, anomalies and recommended checks for an authorised owner or manager to review.
Ten lenses for running the restaurant.
Ask the question you would normally ask a consultant.
Owners don't always need another report. Sometimes they need to ask: 'Why was dinner slower?', 'Which category is underperforming?', 'Where is labour pressure building?' or 'What should I change before Friday?' AI Insights is designed for those restaurant-specific questions.
Turn menu data into menu decisions.
AI Insights surfaces item, category, modifier, dietary and pricing patterns for review. The restaurant remains responsible for interpreting the context and deciding whether to act.
See where the shift slowed down.
Because Cibus connects POS, QR, KDS, staff and Admin, AI Insights can help managers review kitchen flow and staff patterns together. Ticket age, station load, prep-time outliers and staffing questions become part of the same conversation.
Review unusual operating patterns in context.
AI Insights can surface financial-health signals and anomalies across supported sales, labour, menu, payment, discount, refund, void, cash-variance and demand records. A signal is a prompt to investigate, not proof of a cause.
Build the menu from what you already have.
Upload a menu photo, PDF or screenshot and Cibus creates an editable draft of items, descriptions, categories, modifiers, allergen fields and dietary tags. The restaurant must verify every field before publishing, especially prices, allergens and dietary information.
- 01Upload
- 02Extract
- 03Review
- 04Approve
- 05Publish
Recommendations, not autopilot.
AI Insights presents analysis and recommendations for review. It does not silently change menus, prices, staff schedules or financial settings; an authorised user decides whether to act.
- Owner reviewRecommendations require human approval.
- Permission-gated accessRoles control who sees and acts on insights.
- Data scope selectionChoose timeframe, location and channel.
- Clear source contextSupported insights identify the input context available for review.
- No silent changesMenus, prices and schedules require an authorised user action.
- Admin-linked workflowActions open inside Admin for review.
Not autopilot. Recommendations you stay in charge of.
Daily briefings, patterns and answers drawn from permitted Cibus records — surfaced for operator review and never acted on silently.
AI Insights works because Cibus is connected.
AI Insights can use supported records already held in the Cibus operating system, including POS orders, QR activity, KDS ticket flow, Storefront orders, shifts, payments, receipts, menu data and permitted customer context.
Before Friday service.
The owner opens AI Insights and asks what to review before Friday dinner. Cibus analyses recent order, menu, kitchen, staff and payment patterns, then returns a briefing with areas to check, questions to ask the manager and actions to review before service.
AI Insights questions, answered.
Is AI Insights a generic chatbot?
No. AI Insights works with Cibus restaurant operations data and defined analysis contexts; it is not a general-purpose assistant.
What can AI Insights analyse?
Supported contexts include daily briefings, sales, menu, kitchen, staff, financial-health signals, anomalies, demand forecasts and free-form operational questions.
Which restaurant records can it use?
Depending on the modules enabled and the user's permissions, it can use relevant order, menu, kitchen, shift, payment and permitted customer-context records held in Cibus.
Can I ask my own questions?
Yes. Owners and authorised managers can ask restaurant-specific operational questions in plain English within the available data scope.
Does AI Insights change settings automatically?
No. It presents briefings, analysis and recommendations for review. Menus, prices, schedules and financial settings require an authorised user action.
Can AI Insights support a menu review?
Yes. It can surface item, category, modifier, dietary and pricing patterns for an authorised operator to assess.
Can it review kitchen and staff patterns?
Yes. Available contexts include ticket age, station load, prep-time outliers, shift activity and labour-related signals.
Does Cibus support AI menu import?
Yes. A menu photo, PDF or screenshot can be converted into an editable draft. The restaurant must verify every field, especially prices, allergens and dietary information, before publishing.
Who can access AI Insights?
Access is permission-gated through roles configured in Admin, so each restaurant controls which authorised users can review insights and recommendations.
Put restaurant signals into an operator review.
Use AI Insights to review a shift, ask operational questions and prepare menu-import drafts across supported sales, menu, kitchen, staff, customer-context and financial-health records.