Analytics and Reports

Overview#

Analytics is spread across Finance, Statistics, dish statistics and the optional Dashboard. Data refresh and exports depend on the report; there is no universal real-time Excel export.

For a specific management question, start with the report guide.

Finance has eight tabs: Overview, Sales, Purchases, Cash shifts, Delivery channels, Order sources, Staff and Expenses & P&L. Kitchen, risky operations and cash shifts are supported in both clouds. Google Analytics traffic collection is not connected on cenaly.ru yet; CLV cohorts in Order sources are not available on cenaly.ru yet either.

Dashboard#

Open Finance → Overview. Choose Today, Yesterday, 7 days, 30 days, 90 days or 12 months. The day presets compare with the same weekday last week; 7/30/90 days compare with the preceding equal-length window. The 12-month preset has no previous-year comparison. The overview shows:

• Revenue — total amount for the period (day/week/month)
• Number of orders — total count and trend
• Average check — average order amount
• Revenue minus purchases and Purchases / revenue — based on purchases in the period, not the cost of items sold
• Location comparison — available with all locations selected and data for at least two locations, including CSV export

Menu visits belong in Statistics → Traffic, not the financial overview.

Sales Reports#

General report#

Open Finance → Sales for channels, payment methods, Tips by waiter, the revenue heatmap and top dishes by quantity and revenue. Revenue trends and location comparison are in Overview.

Menu ABC analysis#

ABC classifies dishes by cumulative revenue share, not by popularity and margin together:

Profitability report (COGS)#

Dish statistics can calculate recipe cost from inventory purchase prices and show margin per item. A manual item cost takes precedence. Incomplete recipes or missing prices must be resolved before relying on margin. Menu engineering considers popularity and margin together.

Staff KPIs#

Waiter metrics#

• Tips by waiter — Finance → Sales.
• Planned versus actual staff shifts and hours — Finance → Staff.

These do not constitute a revenue-by-employee report.

Kitchen metrics#

Open Statistics → Kitchen for acceptance, cooking and full-ticket times, late percentage, the heatmap, Slowest dishes to cook and Wasted prep. The late percentage uses a common threshold, not each dish’s standard. See Statistics for Promised vs actual.

Channel Report#

Open Finance → Delivery channels for channel status, revenue, estimated revenue lost during downtime, paused/offline hours and cancellations.

Compare dine-in, delivery, takeaway and aggregator revenue under Sales, including net revenue after aggregator commissions. Order sources covers attribution by source, medium and campaign, with attribution models and CLV cohorts where available.

Menu Analytics#

Item popularity#

Dish statistics shows quantities, revenue, ABC, margin, trend against the previous period and time since the last sale. Expand a dish for its daily trend, view-to-cart-to-purchase funnel and frequently bought together items. Review the funnel before assuming why an item is not selling.

Heatmap#

Finance → Sales has a revenue heatmap by weekday and hour. Statistics → Traffic has a website-session heatmap. Neither is a historical dining-room occupancy report.

Menu engineering#

A dedicated tab in menu statistics lays dishes out on the Kasavana & Smith matrix (stars, plowhorses, puzzles, dogs) and gives a recommendation for each: keep it featured, raise the price, move it up the menu, or take it off. The same tab shows margin by channel with aggregator commissions taken into account.

Details — Menu engineering.

Report groups#

The menu your guests see and the breakdown you need in a report often differ: the menu has "Breakfast", "Seasonal", "Combos", while the report needs "food / drinks / alcohol". Categories and items therefore have a report group: Food, Drinks, Alcohol or Other. The group is set for the whole account (all locations at once) and does not change the guest menu.

1. Open Dish statistics → the "🗂 Categories" view → switch "Group by: Report groups".
2. Click "⚙ Report groups" and pick a group for each category.
3. If a single item belongs to another group (say, mulled wine in "Drinks" belongs to "Alcohol"), click "Items" under the category and pick the item's group — it overrides the category. "As category" removes the override.

The table shows revenue, share, portions and average price of each group with the same "Dayparts" or "Channels" split as categories. Items without a group are a "No report group" row, so the total equals dish revenue. The same breakdown is in Finance → Sales — the "Sales by report group" block under the top dishes; its total equals the dish total of the period.

Merged duplicates in reports#

If the same item was created twice ("Cappuccino 0.3" and "Cappuccino 300"), merging duplicates (voice assistant → "find duplicates") keeps the primary item and deletes the others. The primary item remembers which items were merged into it, and every report — top dishes in Finance and Statistics, Dish statistics, menu engineering, the category and report-group breakdowns — shows the sales history of both items as one row under the primary item's name. Refunds of the old item are subtracted from the primary one. If the primary item is later merged into another one, the history follows the chain to the last.

Merges made before this feature existed are not linked: the primary item does not know about them.

Financial Reports#

P&L (Profit and Loss)#

Open Finance → Expenses & P&L to review:

• Revenue
• Cost of goods sold (COGS)
• Gross profit
• Operating expenses
• Net profit

Cash Flow#

Open Finance → Cash shifts for closed shifts: cashier, opening float, cash and card sales, expected and counted cash, shortages and surpluses. Payment-method breakdowns are under Sales.

Data Export#

CSV is available for Location comparison, menu engineering, Network stock and storefront search terms. There is no universal XLSX or PDF export for all reports, and no separate kitchen CSV button.

The account archive is a separate export under Settings: see Data export.

Accounting Integration#

Accounting and catalog integrations are enabled through location cards in Extensions. Available examples include 1C, Evotor and WooCommerce, subject to the location’s country and plan. These are specific integrations, not a universal automatic transfer of all analytics reports. Personal MCP API keys are managed under Settings → Access.

Tips for Working with Analytics#

1. Check the dashboard daily — spot trends and anomalies
2. Use ABC analysis once a month — update the menu based on data
3. Compare periods — to see growth or decline
4. Use available CSV exports — for further analysis
5. Review risky operations — discuss specific events with staff

8. Inventory Management and Cost of Goods#

Ingredient tracking#

1. Inventory → Stock → add all products with purchase price
2. Link ingredients to menu items (recipe cards)
3. The system will automatically calculate the cost of each dish

Recipe card (recipe)#

For each dish, specify:

• List of ingredients with exact weight (grams / ml) There are no separate processing-loss percentage or finished-yield fields in the recipe card described here. Include expected losses in component quantities.

Food cost calculation#

Stock control#

• Auto write-off: when an order is closed, ingredients are written off automatically
• Low stock: push notification when the minimum is reached
• Stocktaking: reconcile actual stock with system stock
• Discrepancy report: actual/system deviations to control theft

Purchasing#

• The system suggests a purchase list based on the sales forecast
• Supplier orders are reviewed and sent through the procurement workflow; a low balance alone does not automatically place an order
• Purchase history with prices to track inflation

9. Demand forecast#

The forecast lives in Inventory, on the "Forecast" tab, and is computed from sales history with no AI at all — from two explainable statistics: the median sales of a dish on this weekday over 8 weeks, and how that demand is spread across dayparts.

What comes out of it:

• a prep plan for the shift — with recipes exploded (including nested semi-finished items) and a "be ready by" hour;
• a supplier order draft for a chosen coverage horizon;
• a "runs out around 19:00" risk corrected for today's pace.

Details, including the limits, — Demand forecast.

10. Automated Reports#

Mailing setup#

There is no general scheduled revenue-and-top-items report with a recipient list. Loss-control rules can notify the owner by email; the work-chat attention view collects issues that need action.

Auto-report contents#

Automatic notices are specific to their workflow, such as low-stock alerts or loss-control rule matches. For a repeatable view of your own metrics, enable Dashboard in Extensions and configure a chart. It supports date windows, Bucket, a Location dimension and Compare with previous period. See Dashboard.