Combo Meals and Bundles: How to Structure Them Without Hiding Value

What a combo is actually for

A combo does three jobs, and it is worth being clear about which one you want.

It can speed up decisions. A guest who does not want to assemble a meal from four sections will take a well-named bundle and move on. It can raise the average check by attaching a drink, a side or a dessert that the guest would not have ordered alone. And it can move a component that has capacity to spare — a fryer, a drinks machine, a dessert case.

What it should not do is disguise a price increase or push a large portion on guests who do not want one. If the bundle only works because the guest cannot see the individual prices, it is not a bundle; it is a pricing trick, and guests eventually notice.

Choose the anchor and the add-ons

Start with the anchor: the item guests already order by name, with steady volume and a known cost. A burger, a bowl, a sandwich, a curry, a coffee. The anchor carries the bundle's identity.

Then choose add-ons using four filters:

Two or three components is usually enough. A bundle with five choices creates more decisions than it removes, and every option multiplies the ways a kitchen can make a mistake.

• **Fast to assemble.** If the add-on needs a station that is already the bottleneck at peak, it is the wrong component.
• **Stable cost.** A component whose price swings weekly makes the bundle margin unpredictable.
• **High perceived fit.** A drink and a side fit a burger. A dessert and a coffee fit a lunch. Random pairings feel like inventory clearing.
• **Capacity to spare.** The bundle should use equipment and prep you already have, not create a new bottleneck.

Price the bundle against the contribution floor

Write down the à la carte price of each component, then the contribution each one keeps after its own cost. The bundle price should sit below the sum of the parts — that is the guest's reason to choose it — and above the total contribution you would lose by selling the components at the bundle price instead of separately.

There are two ways to protect the margin. The first is to keep the discount modest and rely on the attachment: the guest buys a drink they would not have bought, so the total contribution rises even though the burger's contribution falls slightly. The second is to use components with high contribution and low cost — a fountain drink, a simple side, a dessert made in batches.

What you should not do is guess. If you cannot state the contribution of the bundle and of its components, you are not ready to price it.

Show what is included

The display decision is as important as the price. Guests compare a bundle with ordering separately in a few seconds, and they need three things: the components named, the bundle price, and the individual prices visible nearby.

Put the bundle at the top of its section, not hidden at the bottom. Name it in plain words — "Burger, fries and a drink" tells the guest more than an invented brand name. If substitutions are allowed, state which ones; if they are not, say so where the guest reads the offer, not at the till.

On a QR menu, keep the bundle as a single item with the components in the description and a clear price. On a printed menu, give it a box or a band so it reads as one offer. On a delivery listing, check that the platform shows the components in the item description, because a guest ordering from a list view sees less context than a guest reading a full menu.

Channel differences matter more than they look

The same bundle behaves differently in each channel.

• **Printed menu:** guests can compare prices across the whole page, so the value has to hold up against the full list, not just against the components inside the bundle.
• **QR menu:** the guest sees a narrow column and may not scroll back, so the bundle has to stand alone with its components visible.
• **Delivery listing:** the guest often sees only the item name and price, and the platform's commission changes the arithmetic entirely — recalculate the contribution with the platform's cut included before you publish, because a bundle that works in the dining room can lose money in delivery.

Worked example: a lunch bundle

The numbers below are illustrative, not a recommendation.

A café sells a sandwich at $11 with a contribution of $6, a side salad at $4 with a contribution of $3, and a fountain drink at $3 with a contribution of $2.60. Ordered separately, the guest pays $18 and the café keeps $11.60.

The bundle is priced at $15. The café keeps $11.60 minus the discount of $3 — that is, $8.60 — if the guest would have bought all three anyway. But the bundle is designed for the guest who would have bought only the sandwich: that guest now pays $15 instead of $11, and the café keeps $8.60 instead of $6. The bundle only loses money on guests who were already buying all three components, and those guests are the minority in most lunch counters.

The operational check comes next: can the line assemble the salad and pour the drink in under a minute at the lunch peak? If not, the bundle is priced correctly and still the wrong idea.

Watch the bundle after launch

Review the bundle the same way you review any item. Look at the units sold, the components it displaced, and the average check in the daypart where it runs. If the bundle lifts units but lowers total contribution in that daypart, either the discount is too deep or the wrong components are inside it. If the kitchen slows down at peak, the bundle is too complex for the moment it is sold.

Change one variable at a time: the price, the components, or the placement. Two changes at once make the result unreadable.

When the offer is settled, the MenuCrafters AI menu builder keeps the menu you edit as the source for the hosted QR page and the print-ready PDF, so the bundle appears consistently wherever guests order.

Limitations and assumptions

This approach assumes you know, or can estimate, the contribution of each component. Where costs are unknown, the arithmetic becomes an assumption and should be labelled as one. It assumes your POS can distinguish bundle sales from individual sales; if a bundle posts as its own item, you will need a manual check to see which components it displaced. It cannot predict demand for the bundle, how much it will cannibalise full-price orders, or how a delivery platform will present it. Platform commission rules, substitution policies and allergen labelling requirements vary and should be checked before the bundle goes live.