Verticals · 9 min read

AI for restaurants and hospitality groups: where it works and where it does not

A 20-restaurant Italian hospitality group I worked with through BistroTools saved more than 100,000 euros in their first year on procurement and operations. Not on labor. Not on fancy customer-facing AI. On boring back-office work that humans were doing 50 hours a week and that AI now does in three. This is where AI actually pays for itself in restaurants and hospitality groups, and where the hype does not.

The four workflows that pay back this quarter

1. Supplier price intelligence

Most restaurant groups buy from 20 to 80 suppliers across produce, meat, fish, dry goods, beverages, and consumables. Prices change weekly. Most groups do not have visibility into which supplier is cheapest for which item this week, because the comparison work is too time-consuming.

An AI system that ingests price sheets, normalizes units, and flags weekly arbitrage opportunities cuts cost of goods sold by 2 to 6 percent in the first six months. For a 20-restaurant group with 6 to 10 million in food spend, that is a 120,000 to 600,000 euro line item recovered. The implementation is six to ten weeks. The ongoing cost is small.

The catch is that supplier price sheets are inconsistent. PDFs, Excel files, scanned faxes, email bodies. The work to normalize them is not glamorous and not the model's job. Plan for serious data plumbing.

2. Demand forecasting and waste reduction

Restaurants throw away 4 to 10 percent of food cost as waste. AI demand forecasting tied to historical sales, weather, local events, and reservations can pull 30 to 50 percent of that waste back. The math is straightforward. A million-euro restaurant cuts 15,000 to 40,000 euros of waste annually.

This is not a generative AI use case. It is classical forecasting, which has been mature for years. The new opportunity is that the cost to deploy a forecasting model in 2026 is a fraction of what it was three years ago. Mid-sized restaurant groups can now afford it. The implementation is real engineering work, not a no-code tool, and it requires reasonable POS data hygiene.

3. Reservation and front-of-house assistance

Phones, emails, WhatsApp messages, walk-ins. Front-of-house staff spend half their day on coordination work that an AI assistant can handle. Reservation confirmations, special request capture, dietary restriction logging, table change negotiations, no-show follow-ups.

The win is not replacing the host. The win is freeing up the host to do the human work, the in-person greeting, the recommendation, the recognition of regulars. The AI handles the structured coordination. A 100-cover restaurant recovers 20 to 30 hours of staff time a week, which is one full employee in payroll terms.

4. Menu engineering and pricing

Menu engineering used to be a quarterly project. With modern tools it is a continuous one. AI systems that analyze sales mix, contribution margins, and customer behavior can recommend price changes, item placements, and combo bundlings in real time.

The realistic uplift is 3 to 8 percent in margin in the first 12 months for a group that did not previously do active menu engineering. Implementation is straightforward if the POS data is reasonable and the operator is willing to act on the recommendations. The hardest part is operator buy-in. The AI will recommend things that feel counterintuitive. Operators who trust the data win.

The three pitches that waste money

1. The voice ordering bot

This pitch comes around every six months. A voice AI that takes orders by phone. It looks great in a demo. In practice, the failure modes around accents, ambient noise, complex modifications, and customer impatience produce a lower conversion than an answering machine. The few groups that have made this work are at scale, with deep integration into POS and a long tuning runway. For most restaurant groups, this is not the project that pays back this quarter.

2. The customer-facing chatbot

Most restaurant customer questions are can I book, what time do you close, do you have outdoor seating, do you have a vegetarian option. A FAQ page and a structured booking flow handle 90 percent of these at zero cost. A chatbot adds maintenance burden and a new failure surface. The handful of restaurants that benefit are at the high-volume and high-personalization end. Most do not.

3. The kitchen automation pitch

Robotic kitchens, AI-driven cooking. Real, but not yet at the price point that makes sense for the typical hospitality group. The teams chasing this in 2026 are large quick-service operators with capital. Mid-sized restaurant groups should focus on procurement, forecasting, and front-of-house wins where the technology is mature and the ROI is measurable.

The actual stack that works

For a 5 to 30 restaurant group, the realistic AI stack in 2026 has four pieces. A procurement and supplier intelligence layer. A demand forecasting and ordering layer. A front-of-house coordination layer. A menu and pricing analytics layer. The four can be built or bought. They share the same POS, supplier, and reservation data, so they integrate cleanly.

The total investment for a 20-restaurant group ranges from 80,000 to 200,000 euros across the four pieces. The total annual return ranges from 200,000 to 800,000 euros depending on starting baseline. The payback period is typically six to twelve months.

What slowed BistroTools clients down

The number one blocker on every BistroTools deployment was POS data quality. Restaurants run on POS systems that were not designed to feed downstream analytics. Data is missing, mislabeled, or fragmented across locations. The first eight to twelve weeks of every engagement were data work. Operators who skipped that work and tried to deploy AI on top of dirty POS data got AI that produced confident, fluent, and wrong recommendations.

The lesson is not glamorous. Clean the data first. The AI is the easy part.

Where to start if you are a hospitality operator

Pick one of the four workflows. Procurement is usually the highest-ROI starting point. Run a six to ten week pilot in one or two locations. Measure against a clear baseline. If the math works, expand. The mistake is trying to deploy all four at once across all locations. The right shape is one workflow, two locations, ten weeks, then scale.

If you operate a hospitality group and you want a second opinion on where AI fits in your operation, write to me. I respond within 48 hours.

Working on something like this?

I respond to every email within 48 hours. If you want a second opinion before you commit budget, get in touch.

More on verticals