Offers and Bundles — The Promotion Engine That Lifts Restaurant AOV

Discounting trains your guests to wait. Bundling teaches them to add. Offers, used carefully, do both — but only if you treat them as a pricing primitive instead of a marketing add-on.

Most restaurant operators build their promotion strategy backwards: they see a slow Tuesday, spin up a 20% discount, and wonder why it still feels slow by the following Tuesday — now with worse margins. The problem isn't promotion. The problem is treating promotion as a reaction rather than a structure.

This is the playbook for designing offers and bundles that grow average order value instead of eroding it. We'll go through the three offer types that actually move the needle, what "good" looks like when it's built into your ordering software, the bundles most full-service restaurants leave on the table, and the reporting question every owner should be asking every week.

The three offer types and when to use each

Time-bound offers (happy hour, late-night, lunch specials)

Use when you have a known soft spot in the schedule. The job of a time-bound offer is to fill seats during hours that would otherwise be empty. Done poorly, this becomes a race to the bottom — permanently thin margins on your most reliable revenue stream. Done well, it uses a thin discount (10–15%) to bring guests in, then bundles in something high-margin (a starter, a cocktail, a side) to keep AOV intact.

The operational requirement is that time-bound rules run automatically. If your team has to remember to apply a happy hour discount manually, half your tables won't get it, and the guests who don't will feel cheated when they see the bill. The discount should activate the moment the table's order is in the applicable window — and stop applying the moment that window closes.

Bundles (the date night, the family share, the chef's tasting)

Use to push the upper bound of AOV. A two-mains-plus-dessert bundle costs the guest less than ordering each item separately, but the per-cover spend is higher than a typical two-main order without dessert. That's the arithmetic that matters: you're trading a small margin reduction for a bill total that would otherwise never have been reached.

Bundles are the highest-leverage offer type. They grow your top line without conditioning guests to expect a discount on à la carte. A guest who orders the Date Night bundle didn't necessarily get a deal — they got a curated experience at a price that felt fair. That framing is worth protecting. Never call a bundle a "discount." Call it what it is: a configuration of the meal.

Targeted offers (loyalty, returning guests, VIP)

Use to recover specific guests. A returning-after-30-days offer to a guest who hasn't been in. A birthday gift. A VIP tasting invite for your top ten covers of the quarter. These are CRM-driven, not menu-wide, and the math is about lifetime value, not single-visit margin.

The operational risk with targeted offers is leakage: the birthday code applied to three different tables because it was forwarded in a group chat, or the VIP invite handed to a walk-in who guessed it. If your platform doesn't validate at the order level — checking that the guest is actually the guest the offer was issued to — you'll see margin bleed without a clear audit trail.

For more on the CRM mechanics that make targeted offers work, see our restaurant CRM guide.

What "good" looks like in your ordering software

The difference between a promotion that works and one that disappears into the noise is almost always in the implementation, not the concept. Here's what the right promotion engine does:

• Visible in the QR menu at the top — not buried under categories. If a guest has to scroll to find the Date Night bundle, most won't find it. The bundle has to be the first thing they see.

• Eligible items are tagged automatically — no "but this dish isn't included" surprises at checkout. The rule engine should know which items participate in which offer without a staff member needing to remember.

• Pricing applies in real time as items are added — guests see the bundle savings as they build their order. The savings feel earned, not applied after the fact.

• Stackable rules are explicit — happy hour and the date night bundle should not both apply simultaneously without an intentional decision to allow it. Set the stacking logic before you go live, or you'll find out what went wrong on a busy Friday.

• Reporting separates organic AOV from offer AOV so you know what's actually working. If you can't attribute the lift to a specific offer, you can't improve it.

The Payverge promotion engine is wired into the order and bill flows, so a bundle priced correctly in the menu is a bundle priced correctly in the kitchen and on the bill. The offers and bundles module handles the rule logic — time windows, eligible items, stacking constraints, and attribution — without needing manual intervention during service.

Five bundles every full-service restaurant should consider

You don't need a long list. You need two or three that run reliably. These are the five that appear most often in successful Payverge deployments:

• Date Night — 2 mains + dessert at a 10–15% discount. Default Tuesday–Thursday, evening slots. This is the entry-level bundle: low complexity, immediately understandable, and reliably lifts the dessert attach rate which otherwise drops when a table has already committed to two mains.

• Family Share — Large-format dish + 2 sides + 4 drinks. Weekend lunch. The target is the group that arrives uncertain about whether to order individual mains or "just share something." The bundle removes that friction and usually lands the table at a higher total than the uncertain path would have.

• Chef's Tasting — 4–5 courses fixed-price. Limited availability per service. This is your high-margin prestige bundle. The key constraint is "limited availability" — scarcity is part of the value. Configure the bundle to close once a cap is reached, so the kitchen isn't overwhelmed and the exclusivity holds.

• Wine Pairing Add-on — Pre-priced wine flight that activates only when 2+ mains are in the cart. This is the pairing bundle mentioned above. It shows up as an optional add-on at exactly the right moment in the ordering flow. Most guests who see it at that moment say yes.

• Loyalty Renewal — Free starter for any returning guest within 30 days of their last visit. This is a CRM trigger, not a menu offer. It runs automatically, requires the guest to be logged in or identified, and pays back in lifetime value multiples.

You don't need all five. Pick two and run them for a quarter before adding more. Complexity in the offer catalog creates confusion for staff and guests alike — more offers do not mean more revenue.

Bundles live or die by visibility. On a physical menu, a bundle is one section among many, and guests only see it once. On a QR menu, the bundle sits at the top of the screen every time the guest opens it — including when they're adding their third round. That visibility multiplier is why QR ordering and bundles compound each other so cleanly. For the full QR mechanics, see our QR ordering playbook. And when a guest asks the AI waiter what to order, the AI can reference active bundles and suggest the Date Night if the table already has two mains in the cart — a contextual upsell no physical menu can replicate. See our AI waiter guide for how this integrates.

Bundles and bill splitting — handle with care

If a four-top hits a Date Night bundle and then wants to split by item, the bundle math has to allocate correctly. If the bundle discount was applied to two items collectively, the split logic needs to know how to distribute that discount across individual guest shares — not just divide the total by four.

This is a sharp edge of most promotion engines. Test it specifically before relying on it for a Saturday rollout. The right behavior: the bundle discount is allocated proportionally to the items that triggered it, and each guest's share reflects their actual items plus their allocated portion of the discount. The wrong behavior: the discount disappears, or gets applied entirely to one guest's share, or the bill total changes on split.

See our bill splitting guide for the broader splitting playbook, including how splitting interacts with service charges, tips, and rounding.

The reporting question every owner should ask weekly

What's the incremental AOV from each active offer?

"Incremental" being the key word — the right denominator is "what would these guests have spent without the offer," not "all sales during the offer window." A time-bound offer that runs during lunch will show high volume simply because lunch is your busiest period. That's not the offer working. The offer is working when the guests who used it spent measurably more than the guests who didn't, in the same period.

If the AOV lift is positive and material — say, 8% or more — keep running the offer. If it's flat or negative, you're discounting for no reason. Kill it, or restructure it so the bundle component brings the total up to a point where the discount cost is covered.

One more cut worth running: check the repeat rate of guests who used a targeted offer. If the loyalty renewal offer is pulling guests back and those guests are spending at full price on their second visit, the offer economics look very different than if they're coming back only when the offer is active. That second pattern is the trap. The first is the business.

Bad offer patterns to avoid

Permanent 20% off everything

This is a price cut. It's not a promotion. It trains guests to believe your regular price is inflated, and it gives them no reason to explore the menu or try something new. If you want to adjust your pricing, adjust your pricing — don't disguise it as a "discount."

Stackable everything

Happy hour + bundle + loyalty + birthday will eventually reach a point where you're paying the guest to eat. Set explicit stacking rules before you launch any offer. The default should be: only one offer applies per order, with a defined priority order if multiple are eligible. Override with intentional exceptions, not as the default.

Print-only flash sales

If the offer isn't in your QR menu and your AI waiter isn't aware of it, it doesn't exist for a large share of your guests. Any promotion that only lives on a printed card or a chalkboard is invisible to anyone who ordered digitally. Build it into the platform first; print it second.

Offers with no sunset date

An offer without an end date is a permanent discount. Set a sunset date for every offer when you create it — even if you plan to renew it. Forced reviews at renewal time are the only reliable way to check whether the offer is still earning its keep.

Offers and bundles are pricing primitives. Treat them like product, not marketing. The good ones lift AOV without training your guests to expect discounts. The bad ones do the opposite — and they do it slowly enough that you don't notice until the margin damage is already done.

The structural advantage of a native promotion engine is that it closes the loop: the offer is created in the same system that takes the order, prices the bill, splits the check, and reports the attribution. There's no gap between the promotion as conceived and the promotion as executed, and there's no manual reconciliation at month-end.

Explore the offers and bundles module — the 15-minute setup is the right place to start.