AI-Powered Restaurant POS Software

What the insights use

The current insights code summarizes paid orders, item quantities and revenue, daily sales, configured stock par levels and item pairings in order history. The assistant formats answers from those calculated summaries; it is not a general-purpose AI model.

This distinction matters: reliable insights depend on complete order and inventory records, and suggestions should be checked against actual supplier lead times and stock counts.

Questions the current dashboard can answer

The dashboard can show which items have the highest recorded unit sales, summarize recorded sales and compare today's sales with the average of available sales days. It can identify stock groups below a configured par threshold and display an estimated suggested quantity.

Order history can also surface items that have appeared together in recorded checks. The built-in forecast is a simple heuristic based on recorded daily sales, not a trained demand-planning model.

What it does not currently claim

The available insight code does not calculate actual margin or food cost, infer declining sales trends by comparing defined periods, report a busiest hour, or connect to external market data. Do not use it as a substitute for accounting or inventory verification.

Read how Petu reports recorded sales and the inventory setup guide.

Use insights as a prompt to investigate

Check the underlying period, menu configuration and stock count before acting on a summary. Start with a question that maps to available records, such as “Which items sold the most?” or “Which configured stock groups are below par?” Then validate the answer in the report and on the floor.