Restaurant POS Sales Analysis: Seven Metrics to Review Every Week

Seven starting metrics

Track sales, guests, average order value, item quantity, sales by time, additional-order rate, and table turnover. Add gross profit when cost data is reliable.

Keep the review small enough for a manager to complete in about thirty minutes each week.

Compare time and day

Place guests, average order value, staffing, and service time beside sales. High sales can still hide overstaffing or delays.

Record weather, events, reservations, and promotions so week-over-week comparisons have context.

Review product performance

Combine quantity, revenue, margin, and kitchen workload. Separate popular low-margin items from profitable items that are hard to discover.

Change menu position, imagery, description, or bundles and review results over a defined period.

Additional orders and recommendations

Partner materials describe prompts and recommendations based on commonly combined orders. Results depend on relevance, frequency, and timing rather than feature availability alone.

Use natural combinations such as drinks, sides, and desserts, and avoid excessive prompts.

Turn analysis into experiments

Change one or two variables at a time. Large simultaneous changes make attribution impossible.

Record the baseline period, target item, expected effect, and result.

Protect data quality

Classify voids, discounts, staff meals, test orders, and refunds consistently across locations.

Confirm exports, date filtering, cross-store reporting, permissions, and accounting integration before purchase.

Turn each metric into a controlled operating action

A dashboard does not improve performance unless each metric has an owner, a review interval, and a permitted action. For example, low sales in one period may lead to staffing, opening-hour, menu, or promotion changes, but those actions should not be made simultaneously. Record the hypothesis, change date, affected items or hours, and the expected result so that the next review can distinguish improvement from normal variation.

Check data quality before drawing conclusions. Voids, staff meals, discounts, refunds, split payments, table transfers, missing covers, and inconsistent item names can distort average order value and product rankings. Compare POS figures with settlement data and accounting totals, and keep a stable product hierarchy for reporting. Weekly analysis should produce a small number of testable actions; it should not become a list of every number that moved.

Use a consistent review calendar. Daily checks should focus on exceptions and cash control, weekly reviews on menu and staffing tests, and monthly reviews on pricing, supplier cost, channel mix, and system configuration. This keeps urgent anomalies separate from strategic decisions.

Archive the reviewed export so later decisions can be traced to the data available at that time.

Frequently asked questions

Official sources

• Wiz — Kantan Chumon official page
• funfo official site
• EMEAO! — POS register and POS system differences