How Do You Increase Average Order Value in a Restaurant?

What is Average Order Value in a restaurant?

Average Order Value, or AOV, is total revenue divided by total transactions, and it tells an owner whether the business is getting better or worse at capturing spend from each guest who already walked in.

Most restaurant owners track daily revenue closely but have never calculated AOV by shift. Without that number, there is no way to know if the team is improving at maximizing each guest's check or simply riding whatever traffic shows up.

AOV = Total Revenue / Total Transactions. That is the whole formula. The hard part is not the math, it is building the habit of pulling it from the POS every week and acting on what it shows.

Why does raising Average Order Value matter more than getting new customers?

AOV matters because it captures more revenue from guests already sitting in the restaurant, while acquiring a new customer costs money through marketing, promotions, or delivery commissions.

Getting an existing guest to spend a few dollars more costs almost nothing. It requires a suggestion from a server or a small tweak to how the menu is presented. A team processes hundreds of transactions a week, and each one is a chance to add a side, a drink, a dessert, or an upgrade. Right now, in most restaurants, those chances are missed because nobody is tracking them and nobody is rewarded for capturing them.

The scale of the opportunity is real. A 10% increase in AOV across 1,000 guests per week at a $50 AOV adds $260,000 in annual revenue, with no new customers, no additional marketing spend, and no extra seats. It comes from $5 more per transaction, from guests who were already going to walk through the door.

What are the four levers that increase Average Order Value?

The four levers, in order from easiest to hardest, are add-ons and modifiers, bundle engineering, premium positioning, and occasion expansion.

Each lever works differently and takes a different amount of effort to put in place.

• Add-ons and modifiers: sides, drinks, desserts, protein upgrades. Asking "Would you like to add avocado for $2?" needs no new menu item, only a prompt.
• Bundle engineering: combo meals and "for the table" options that raise per-check spend. A $14 sandwich becomes a $19 combo with a side and a drink, the guest perceives value, and the restaurant captures incremental revenue.
• Premium positioning: Good, Better, Best tiers on key items, such as a regular burger at $14, a signature burger at $18, and a wagyu burger at $26. The top tier exists partly to sell, and partly to make the middle option feel reasonable.
• Occasion expansion: turning a lunch guest into a dinner guest, a dine-in customer into a catering lead, or a one-time visitor into a gift card buyer. This stretches the relationship past the current transaction.

Swipe sideways for all 4 columns →

Add-ons come first because they need no menu changes and can start through server training the same week. Bundles and premium tiers take more setup. Occasion expansion takes the longest because it depends on building a relationship beyond a single visit.

Results are not typical and will vary with your business, your market, your team and how much of the work you actually do. Client figures on this site come from recorded interviews and are dated. Nothing here is a guarantee of revenue, profit or growth.

Is raising menu prices the same thing as increasing AOV?

No. Raising a price is margin management, while AOV growth comes from getting guests to add more items to the same transaction.

Moving a burger from $14 to $15 changes margin, and it can also reduce traffic if guests notice and push back. AOV strategy works on the same price and asks for one more item per check: a side, a drink, an upgrade. That distinction matters because the two levers carry different risks, and mixing them up leads owners to think they are building AOV discipline when they are only adjusting the price list. Read more on how to raise restaurant menu prices if pricing itself is the goal.

A second common mistake is tracking AOV as one overall number instead of by shift. Lunch and dinner behave differently. Lunch might carry a lower AOV with a lot of room for add-ons, while dinner might already run high with limited room to grow. Blending the two into a single average hides where the actual opportunity sits. A third mistake is expecting staff to suggest add-ons with no incentive at all. Even a simple daily contest or a weekly shout-out for top sellers gives the team a reason to change behavior.

Does transaction count matter more than AOV?

For many concepts, average check is fairly fixed and hard to move dramatically, which means daily transaction count often carries more room to grow than AOV alone.

One Founders Board member runs a cloud kitchen business, delivery and pickup only, out of shared kitchen spaces. When he opened a new location, it came in at 43.5 orders per day at a $25.50 AOV, more than double his projection of 20 orders. His projected monthly burn of $9,360 dropped to $2,249 as a result.

The coaching lesson pulled from that number was about AOV itself: average check tends to be relatively fixed for a given concept, and it is very hard to move it dramatically. Going around the group, every member confirmed their own AOV was stable within a narrow range, at $25, $31, $39, and $40. The number with the most room to move was daily transactions.

This member's break-even analysis showed he needed 88 orders per day at $25.50 to cover all costs. His first location was already averaging 429 orders per day across all brands, with a goal of 500. At 500 orders and a $25.50 AOV, that location would generate roughly $4.6 million annually. A modest AOV, driven by high volume, built a multi-million dollar business from cloud kitchens. The lesson: AOV and transaction count work together, and the job is to know which one has more room to move in a given concept.

How does a restaurant build an AOV improvement plan?

A restaurant builds an AOV plan by calculating current AOV by shift, setting an 8-12% target for 30 days, choosing one lever to start with, and tracking the number weekly.

1. Pull revenue and transaction counts by shift, lunch, dinner, weekend, and takeout or delivery, for the last four weeks, and calculate AOV for each.
2. Set a target AOV at current AOV multiplied by an 8-12% increase, and calculate the revenue impact as (target minus current) times weekly transactions times 52.
3. Choose a lever to start with. Add-ons and modifiers is the recommended first move because it requires zero menu changes and can start through server training right away.
4. Write down three specific add-on items staff will be trained to suggest starting this week.
5. Track AOV weekly against the baseline and the target, noting variance and what changed.

This is the same scorecard used inside the coaching system that Founders Board members get a licence to as part of the Scaling Engine OS™. Restaurants that have gone through structured operating work like this show up across the case studies, including one that installed KPIs on every P&L line and later sold for over a million dollars.