The industry’s first instinct was to add protein options. That was the right answer to the wrong question.
Somewhere around the middle of last year, something started happening at the modifier line. Not dramatically. Just steadily. The “add chicken” rate crept up. More bowls came out with double protein. Guests who used to order as configured started asking for changes at the counter that all pointed in the same direction.
The menu teams noticed first. They are supposed to. New high-protein builds. Better callouts. Customization options where there used to be none. That response was correct.
But it left a different problem untouched. The one the kitchen wakes up to every morning.
Why Protein Misses Hit Differently
When a kitchen misses prep by twenty portions, the outcome depends entirely on what it missed.
If that miss was rice, someone puts on another hotel pan. Ten minutes later the problem is solved and nobody remembers it happened.
If that miss was grilled chicken, the sequence looks different. The kitchen is managing thaw time mid-service. Ticket times slow. Servers start steering guests toward substitutions. A manager is on the phone with a neighboring location or calling a distributor for an emergency delivery at whatever price they want to charge that afternoon.
And if the team over-prepped those same twenty portions instead? They are throwing away the most expensive ingredient in the building at close.
Protein is not just a higher-cost prep item. It is a higher-consequence one. Under-prep and over-prep are both expensive in ways that simply do not apply to the same degree with anything else on the list. That asymmetry has always existed. What protein maxxing did is increase how many shifts, at how many locations, depend on getting it right.
The stakes did not change. The frequency did.
Sales Didn’t Change. Protein Demand Did.
Here is the part that makes protein maxxing operationally different from most other trends: it is not primarily showing up in menu item sales. It is showing up in modifier behavior.
Look at the POS.
A bowl still counts as one bowl. A plate still counts as one plate. Entree counts can look completely stable week over week. But the amount of protein inside each of those orders has been quietly increasing for months. The guest who used to order the standard build now checks “add chicken.” The guest who skipped the protein add-on now doubles it.
Your menu sales never changed. Your protein demand did.
That distinction is exactly where most prep forecasting falls behind. Forecasting systems are built around item sales. They track what sold. Not how each item was configured when it sold. If modifier attach rates are shifting, that movement is largely invisible to a model watching entree counts, and only visible when the kitchen runs short or the food cost line moves.
The attach rate is the story. Not the sales volume.
If “add chicken” selections climbed from 18 percent to 30 percent at a bowl concept over six months, protein demand on those orders grew by roughly 67 percent, even if total bowl counts held flat. That does not create a 12-point problem. It creates a compounding one, because every additional modifier stacks on top of the base demand the kitchen was already prepping for. Most prep models would never catch it. They are watching the bowl. Not what is inside it.
The Forecast That Keeps Averaging Yesterday Into Tomorrow
Rolling sales history is the foundation most prep models run on. What sold last month. What sold last quarter. Averaged into a prep figure for tomorrow.
That works when ordering patterns are stable. When modifier behavior is shifting mid-trend, the model starts describing a restaurant that no longer exists.
Six months of data that spans both the pre-maxxing period and the post-maxxing period produces a blended number calibrated to a guest who does not really exist anymore. Not the old ordering pattern. Not the current one. An average of both, producing a protein prep figure that will be wrong with uncomfortable regularity.
The forecast is not behind because it is slow. It is behind because it keeps averaging yesterday into tomorrow.
And when the kitchen comes up short on protein and the team gets debriefed on what went wrong, the actual answer is often: the model was built on behavior from before the trend settled in. The team prepped to the right number. It was just the wrong number.
The Metric That Should Be in Every Ops Review
There is one number that makes this visible before the variance report does.
Modifier attach rate. Tracked at the item level, week over week, by location.
Not entree counts. Not total revenue. The rate at which guests are adding protein to orders that did not originally include it, or upgrading the protein in orders that did. That rate is already in the POS. The operators who stay ahead of a shift like this are the ones watching it change in real time rather than finding out through the food cost line three weeks later.
When attach rates climb across multiple locations in the same direction, that is a prep model update. Not an investigation.
At ClearCOGS, modifier-level mix shifts are exactly what we track when building prep recommendations: not just what sold yesterday, but how the composition of what sold is changing, and what that means for tomorrow morning’s prep sheet.
Protein maxxing did not rewrite the menu.
It quietly rewrote the prep sheet. Most forecasting systems just have not read it yet.
Sources
- Restaurant Business. Protein Maxxing Continues to Shape Menus. restaurantbusinessonline.com
