This is a bizarre take. I dine/eat out fairly often to a point I know the staff names in quite a few places (it's Europe, no tipping culture, either). I don't quite see how I could customize any order with a web interface, realistically (food intolerances).
>when they're printing hundreds of fresh menus a day
They change the menu every day? Around here the menus are commonly placed in a book alike folder or the least they will have a plastic slip. As for waste the online part (with datacenters and all) would be more wasteful/less green.
>Plus the bonus of never having to experience "oh sorry we're out of that" if they update the menus dynamically is fantastic.
So they need to link the kitchen to the menu system in real time. That feels unliklely - most of the menus would mostly static web (or worse pdf) interfaces, and an order button.
> That feels unliklely - most of the menus would mostly static web (or worse pdf) interfaces, and an order button.
You say that like it's a given, but why? Products that can dynamically update the menu when something is out of stock with a couple of touches from FOH staff already exist. It's not exactly complex.
> I don't quite see how I could customize any order with a web interface, realistically (food intolerances).
This is harder, but that's why I don't think you can replace all your staff with a web interface - you still need a human in the loop to ask about important things like this.
>when they're printing hundreds of fresh menus a day
They change the menu every day? Around here the menus are commonly placed in a book alike folder or the least they will have a plastic slip. As for waste the online part (with datacenters and all) would be more wasteful/less green.
>Plus the bonus of never having to experience "oh sorry we're out of that" if they update the menus dynamically is fantastic.
So they need to link the kitchen to the menu system in real time. That feels unliklely - most of the menus would mostly static web (or worse pdf) interfaces, and an order button.