Most café owners have more data than they ever look at. The till records every sale, every refund and every busy hour, but the reports sit behind a dashboard that takes time to open and interpret. At ten at night, after cash-up, few people want to filter a sales report by date range and export it to a spreadsheet.
AI assistants are starting to change that. Some EPOS systems now let you connect an assistant such as Claude, so you can ask questions in plain English: "How did we do yesterday?" or "What sold worst this month?" This article explains how that works, which questions are worth asking, and where the limits and privacy questions lie.
How it works
A general AI assistant does not know anything about your café. It cannot guess your takings. To answer questions about your business, it needs a connection to the system that holds the data, usually your EPOS or till.
That connection is often called a connector. Many are built on the Model Context Protocol (MCP), an open standard that lets an assistant call a set of defined tools, such as "get sales summary" or "list top items", provided by another service. When you ask a question, the assistant decides which tool to use, the EPOS returns the figures, and the assistant writes them up in plain language.
Three points matter here:
- The numbers come from your till, not from the AI. The assistant fetches and summarises. It should not be making figures up, and a well-designed connector shows which lookup produced each answer.
- You sign in and approve access. You connect with your own EPOS login and can remove the connection at any time.
- Access is limited to what the tools allow. If the connector has no tool for issuing refunds, the assistant cannot issue refunds.
Questions worth asking
The value is in quick answers to questions you would otherwise not get round to. Some practical examples:
Daily check-ins
- "How did we do yesterday compared with the same day last week?"
- "What are today's takings so far, and how many orders are still open?"
- "Give me a short morning briefing: yesterday's sales, best sellers and any new feedback."
Menu decisions
- "What were our five best sellers this month, and what barely sold?"
- "Which items have we sold fewer than ten of in the last four weeks?"
- "Search the menu for anything containing nuts and list the prices."
Staffing and opening hours
- "When are we busiest on Saturdays?"
- "Which hour on weekdays has the lowest sales?"
- "Is Monday afternoon worth staying open for, based on the last two months?"
Guest feedback
- "Summarise this week's guest feedback. Are there any recurring complaints?"
- "Show me any ratings below three stars from the past month."
Quick actions
- "Mark the banana bread as sold out."
- "Add these dishes to the menu" (with a photo of a printed menu).
Follow-up questions are where this becomes useful. Ask for the busiest hours, then ask whether that pattern differs between weekdays and weekends, without building a new report each time.
An example: Claude and Café QR
Café QR, a cloud EPOS for independent cafés, restaurants and takeaways, offers a Claude connector that is listed in Claude's connector directory. According to the company, it is free on every Café QR plan, though you need your own Claude account.
Owners and managers can ask about sales and takings for a given day, week or month, best and slowest sellers, individual orders, live status (open orders and takings so far), busy times by day and hour, guest feedback and ratings, and the menu with prices and allergens. The company says sales figures exclude cancelled orders, take off refunds and match the till's takings and cash-up reports.
The connector can make a small number of changes. It can mark an item sold out or back on, and the setup guide says it can also add dishes to the menu, including from a photo of a printed menu. It asks before changing anything, and changes appear in the dashboard's audit log. It cannot take payments, issue refunds, cancel orders, delete anything, or change staff or pay, and it cannot see guests' phone numbers or email addresses.
Setting it up means opening Settings, then Connectors in Claude, finding Café QR, signing in with your Café QR login and allowing access. Only owners and managers can connect. Kitchen and floor staff cannot, and a manager limited to one branch only sees that branch.
The limits
AI assistants are useful, but they are not accountants or analysts, and they can be wrong.
- Check important figures. For VAT returns, payroll or anything you will sign, use the cash-up and reports in your EPOS, or your accountant, as the source of truth. Treat the assistant as a quick way to look, not a replacement for proper records.
- Interpretation is not fact. If you ask "why were sales down on Tuesday?", the assistant can only see what the till recorded. It does not know it rained, that a road was closed or that a member of staff called in sick. Its explanation is a guess unless you supply the context.
- Be specific about dates and sites. "Last week" can mean different things. Give date ranges, and name the branch if you have more than one.
- Small numbers mislead. A dish that sold four times this month and two times last month has not "dropped by half" in any meaningful sense. Ask for the raw counts.
- Confirm before changes. Read the confirmation carefully before you approve anything that changes your menu.
Privacy and data
Before connecting any assistant to your business data, ask these questions:
- What can it see? Ideally only business figures. Guest contact details should stay in your dashboard.
- What can it change? Fewer write permissions is safer.
- Who can connect? Limit it to owners and managers.
- Is your data used to train AI models? Check both the EPOS provider's policy and the assistant provider's. Café QR, for example, says it does not use café data to train AI, and that chat history is governed by your Claude account.
- How do you disconnect? It should be immediate and easy.
Read the security and data page of whichever provider you use, and the AI provider's own privacy settings, especially if staff share an account. Do not paste customer personal data into a chat yourself.
Conclusion
Connecting an AI assistant to your EPOS will not change how you run your café, but it can make the figures you already have easier to use. A two-minute morning question about yesterday's sales, a weekly check on what is not selling and a look at busy hours before you do the rota are all realistic uses.
Start with read-only questions, check the answers against your reports for the first few weeks, and keep important financial decisions grounded in proper records. Used that way, it is a practical way to get more out of data you are already collecting.