POS Analytics separates menu, employee, tip, channel, daypart, and kitchen evidence so managers can answer an operational question without treating every filter as global.
Analyze menu and sales timing
Open Admin → POS → POS Analytics → Sales. Under Breakdown & comparison options, set Menu mix — group by to Category, Product, or Hour of day.
Use Menu mix to compare item quantity and sales at the selected grouping. Use Sales by time of day for breakfast, lunch, dinner, and late-night totals. Use Channels to compare POS, Kiosk, Web, Display, or Unknown order sources.
The Channel selector in Report scope applies to Channel sales, not every report section. Product and category results still follow their own section query and the selected location and period.
Review employee performance
Open the Staff tab for Employee sales, Employee sales by time, Employee sales by channel, and Employee sales by channel and time. The report attributes available ledger activity to the recorded server or actor; it does not measure service quality by itself.
Use Department, Job title, and Employee carefully. Department and job title apply to Tips and Staff and payments. The Employee selector limits Staff and payments. Confirm the table heading and active filters before comparing two employees.
Staff and payments includes sales, captured and refunded amounts, counts, and refund rate where available. Investigate role, shift, table assignment, and manager actions before interpreting a high refund rate.
Review tips and the sharing preview
On Payments, use Tips to review assigned tips, auto gratuity, and unassigned amounts for the selected report scope. An unassigned amount needs operational review; it should not be silently attributed to an employee.
Tip sharing is a planning preview. Its pool total follows the same report scope as Tip Summary, while clocked hours can include all locations in the account for the period. The screen explicitly identifies it as not payroll advice, and the handoff CSV continues to use assigned tips unless the business adopts and executes a separate pool policy.
Viewing the preview does not post payroll, redistribute tips, or change employee balances.
Review kitchen speed separately
Open Operations → Kitchen speed when the question is about ticket throughput rather than sales. KDS SLA reporting uses location when a ticket's order is linked to a store. Export station, hour, cause, or cause-detail CSV evidence when deeper analysis is required.
Missing kitchen rows can mean no linked ticket evidence matched the period and location. Do not infer kitchen performance from sales totals alone.
Build a repeatable review
- Choose one business question and report period.
- Confirm location and the section-specific filters.
- Compare the relevant table with its previous period when useful.
- Export only the evidence needed for the authorized audience.
- Record filters with any conclusion so another manager can reproduce it.
Refreshing, filtering, saving a browser range, or exporting a report does not change menu items, employee assignments, tips, payroll, or KDS tickets.