Your Menu Changed in Your POS Last Night — Did Your Training?

Every operator I know has a version of this story. The menu changes in the POS and the training doesn't. Not because anyone is lazy or careless. Because there's no system connecting the two things. Your Toast or Square rep does exactly what they're supposed to do. The item updates, the price updates, the modifier fires correctly at the register. The POS side is clean. The problem is everything downstream of that update. The floor staff still has the old version in their heads.

Think about what the floor actually knows. They know what they learned during onboarding, what they picked up shadowing someone, and whatever got said at the last pre-shift meeting they were awake for. That's it. When the kitchen switches the burger from a brioche bun to a pretzel bun because of a supply issue, nobody sends a memo. When you 86 the fish tacos and replace them with shrimp tacos for the weekend, somebody tells the first two tables and then it gets lost in the noise. When you bump the happy hour draft price by 75 cents because your cost on the keg went up, the server who opens on Thursday doesn't know until a customer corrects them.

The cost isn't always a walkout or a bad review. Sometimes it's subtler. A server confidently describes a dish the kitchen hasn't been making that way for a week. A customer orders something that's 86'd and the server has to go back, apologize, and re-take the order. Another customer hears a price at the table, sees a different one on the receipt, and says nothing but doesn't come back. These things happen every service, at every restaurant, because the menu in the POS and the menu in the staff's head are two different documents with no connection between them.

Here's what I'd want operators to sit with. How many days, on average, does it take for a menu change in your POS to reach every person on your floor? Not just the ones who worked the day you announced it. Not just the ones in the group chat who saw the message. Every server, every bartender, every new hire who's two weeks in and terrified to ask questions. In most restaurants, the honest answer is you don't know. The change trickles out, some people catch it, some don't, and you find out someone missed it when a customer makes a face.

There's also an allergen problem buried in here that I don't think gets enough attention. You swap out an ingredient. The POS reflects it. But a server who trained on the old version of the dish is still telling a customer with a tree nut allergy that it's safe, because that's what they learned. That's not a bad review. That's a liability. Menus change constantly in real kitchens, especially right now when supply chains are still weird and commodity prices are all over the place. Every change to an ingredient is a potential allergen gap if your training doesn't move with it.

Now let me tell you what it looks like when the menu and the training are actually the same system.

You change a price or update an item and the quiz regenerates. The staff takes it before their next shift. Not because a manager printed something out and left it in the break room. Because it's on their phone, they get a notification, and they've already learned to take two minutes before they clock in because that's what this team does. By Saturday night, every person on the floor knows the pretzel bun. They know the shrimp tacos. They know the draft price. They know because they were tested on it, not just told.

That's the gap I built ShiftTrained to close. The POS does its job. But nothing downstream of the POS was ever designed to update automatically when the menu changes. Training was always a separate process, a separate tool, usually a separate person whose job it was to chase people down. When those two things are connected, the lag goes from days to hours. The floor knows what the kitchen is actually serving.

I want to be clear that this isn't a knock on any POS company. Toast, Square, Lightspeed, all of them do exactly what they're supposed to do. The gap was never their problem to solve. It's a training problem, and for thirty years the restaurant industry handled it the same way: write it on a whiteboard, say it at pre-shift, hope it sticks. That process doesn't scale and it doesn't update fast enough for how quickly real menus actually change.

The operators I know who have this dialed in share one thing. They treat training as a live document, not a one-time event. The menu changes, the training changes. Same day. That's the standard worth building toward, whether you've got five seats at a counter or a hundred-seat dining room. Because the server confidently describing a dish that doesn't exist anymore isn't trying to mess up. They just don't know. And that's on the system, not on them.

Have a great day! — Terry Psaltakis
Your AI Restaurant Guy

For more on putting this into practice, see how ShiftTrained approaches a restaurant training program.