Selling a dish you just ran out of

The kitchen just called out that the sea bass is gone. Ten seconds later, a ticket prints for two orders of sea bass.

The gap between running out of an ingredient and updating the system is where mistakes happen. A server took an order at table four while the chef was scraping the bottom of the prep pan. Or someone sitting on their couch just paid for a dish through your website. Now you have to walk over to the table, apologize, and ask them to choose something else. If it was an online order, you have to call them, explain the situation, and figure out how to refund a partial payment.

Managing a restaurant inventory during a busy service is not about counting boxes in the walk-in fridge. It is about knowing exactly what you can sell right now. When a key ingredient runs out, the 86 list needs to be immediate.

The cost of a slow update

If your front of house and your kitchen are not in sync, the friction falls on the staff. Servers have to remember verbal updates yelled across the pass. When they forget, they ring up a dish that does not exist. The kitchen gets frustrated because they already communicated the shortage. The server gets frustrated because they look foolish in front of the customer.

Dealing with out of stock online ordering creates even more friction. A customer pays by card before the ticket prints in your kitchen. If your website does not know you are out of stock, it keeps taking their money. Fixing this requires a manager to void the transaction or process a refund, which takes time away from the floor.

Tying the systems together

The traditional fix is to physically cross items off a whiteboard or tape a note to the register. This works if you only have one register and no online orders. But if you have QR code ordering at the tables, a website taking orders, and a server with a handheld tablet, a piece of tape does nothing.

To maintain a stock count restaurant staff can trust, the inventory must be connected directly to the menu. If you know you only have twelve portions of the special, the system should stop selling it after the twelfth order. It should not matter if the orders came from a waiter, a QR code, or someone ordering from home. The count needs to decrease across every channel at the same time.

Once the count hits zero, the item should disappear from the digital menus and gray out on the register. No one has to yell across the kitchen. No one has to memorize a changing list of unavailable items. The system simply prevents the transaction.

One source of truth

Keeping the menu accurate requires a single system. If your website is run by one software provider and your point of sale is run by another, they do not talk to each other fast enough. You end up having to log into two different dashboards to mark an item out of stock. During a Friday night rush, no manager has time to do that.

This is why lokal runs your register, your QR code table ordering, and your website from one database. If you mark a dish out of stock on the POS, it immediately disappears from your online ordering page. If you set a limited quantity for a special, every order from any channel reduces that count. You manage the business in one place, and the menu stays accurate everywhere. lokal costs $1 for the first month, then $99.99 per month, plus tax. There is no contract, and you can cancel any time.