The honest answer is: far more often than you reprint, and far less often than the inputs change. Most restaurants treat pricing as an annual event — a once-a-year sit-down, a new print run, and another twelve months of drift. That interval made sense when the data took weeks to gather. It doesn’t now. Here is how to think about the two different clocks running on your menu.
Reviewing is not reprinting
The confusion at the centre of this question is between two separate things:
- Reviewing prices — looking at what each dish costs, contributes, and sells, and deciding whether anything should change.
- Reprinting the menu — physically changing what the guest sees.
These do not happen on the same clock. Reviewing should be frequent, because the inputs move constantly. Reprinting should be deliberate, because the menu is something the guest perceives as stable and trustworthy. Reprice the decisions weekly; change the artifact when the accumulated decisions justify it. Conflating the two is why operators either reprice far too rarely (because reprinting is a project) or fear that “frequent pricing” means a new menu every week. It doesn’t.
What’s actually changing under the menu
Three clocks run faster than an annual review:
Ingredient costs. Produce, protein, and dairy move with seasons and supply. A dish that costed cleanly in January can quietly slip below its target contribution by spring while its menu price sits frozen.
Your comp set. Comparable restaurants nearby adjust prices, rotate dishes, and respond to the same cost pressures you feel. If they have moved and you haven’t, you are either leaving money on the table or standing out as the expensive option for no reason. (More on this in what your comp set is actually doing.)
Demand. A dish’s popularity shifts with the season, the weather, and what’s trending locally. Popularity is one axis of the menu engineering matrix, and it doesn’t hold still for a year.
A practical cadence
A workable rhythm for most properties:
- Weekly: review the numbers. Contribution margin, sales mix, and any cost drift, read off your POS and current recipe costs. Flag what’s moved. Decide — don’t necessarily act.
- As justified: make price changes. When a dish has clearly drifted, reprice it. Small, frequent corrections beat one big annual jump that shocks regulars.
- Batched: reprint. Hold the visible changes and roll them into a menu update when enough have accumulated — or use formats (inserts, daily sheets, digital boards) that let you change a price without reprinting everything.
The goal is not velocity for its own sake. It is the elimination of drift — catching a Plowhorse before it has leaked margin for six months, and adjusting to the market while the adjustment still fits. This is the same case we make for the whole discipline in why menu engineering belongs in a weekly cadence, and the underlying method is on the methodology page.
What not to do
A few guardrails:
- Don’t surprise loyal guests. Frequent, small, defensible moves on the right dishes — not sudden, across-the-board jumps.
- Don’t reprice everything at once. Target the dishes the numbers point to. A blanket increase teaches you nothing and risks the dishes that were fine.
- Don’t let the print run set the strategy. The cost of reprinting should govern when you reprint, never when you think about price.
Review weekly, decide as the numbers warrant, reprint when it adds up. The menu stays stable to the guest while the economics underneath it stay current.