Menu Engineering for Small Restaurants: Keep, Fix, Feature, or Remove
A simple decision framework for menu profitability using margin and popularity.
Menu engineering sounds corporate, but the small-business version is simple: understand which products are popular, which products contribute profit, and which ones deserve attention.
Two axes are enough to start
Look at margin and popularity. High margin plus high popularity means protect and feature. High popularity with weak margin means fix cost, portion, supplier, or price.
Low popularity with high margin may need better placement or sales support. Low popularity with weak margin may deserve removal.
Cost accuracy comes first
Menu engineering based on bad costs is theater. If supplier prices are stale or sub-recipes are missing, the matrix will lie.
Karu should build the data foundation first, then make the decision layer easy.
Small changes can be enough
Not every issue requires a price increase. Sometimes the answer is supplier comparison, portion adjustment, packaging review, or removing a low-value garnish.
The system should suggest actions, not only report problems.
Operator checklist
Combine margin with sales volume.
Review high-volume weak-margin products first.
Try supplier and recipe fixes before price changes.
Feature products with strong margin and demand.