How to Measure Restaurant Delivery Price Markups

To measure a restaurant channel markup, compare the same item at the same restaurant and time, under the same customer conditions. Use the dine-in or pickup price as the stated reference, then calculate the percentage difference in the listed item price. Keep delivery fees, service fees, promotions and membership benefits separate. Otherwise, the result mixes menu strategy with checkout cost and cannot be reproduced.

Four rules for a reliable channel-price comparison

Match the exact product and minimum valid configuration.
Match the restaurant, observation time and customer state.
Name the reference channel and price component.
Preserve every unmatched or unavailable observation instead of forcing it into an average.

These rules matter more than the size of the final percentage.

What is a restaurant channel markup?

A restaurant channel markup is the percentage by which a listed item price in one sales channel is above or below a stated reference channel.

If pickup is the reference, the delivery item-price markup is:

(delivery item price minus pickup item price) divided by pickup item price, multiplied by 100

For example, if the same item is £8.00 for pickup and £9.20 for delivery, the listed item-price markup is 15%. This example illustrates the calculation only. It is not a Getplace market finding.

Always state the reference. “Delivery is 15% higher” is incomplete unless the reader knows whether the comparison is against dine-in, pickup, direct ordering or another platform.

Item-price markup is not checkout premium

Customers may pay more than the listed menu price because of delivery, service or small-order fees. They may also pay less because of a promotion or membership benefit.

Keep at least three measures separate:

Listed item-price markup: the difference between matched base menu prices.
Effective item-price markup: the difference after item-level discounts and required modifiers.
Checkout premium: the difference in the comparable basket total after visible fees, discounts and taxes.

Each measure answers a different business question. Combining them into one “delivery markup” makes the result difficult to interpret.

Match the product before calculating the markup

Use the exact product, size, quantity and meal composition. Check required modifiers and default choices. A meal with a larger drink or an included side is not the same product as a standalone item, even if the names look similar.

For every match, keep:

the original listing name;
stable product and restaurant identifiers;
size and quantity;
required choices and minimum valid configuration;
match status and review note.

Do not assign a percentage to an ambiguous pair. Mark it for review or leave it unmatched.

Match restaurant, platform and time

Store-level variation can be lost when teams compare city or brand averages. A valid channel comparison should normally refer to the same restaurant or to a clearly defined matched store group.

Record:

restaurant identifier and address;
sales channel and platform;
collection timestamp and time zone;
customer or delivery location where relevant;
account and membership state;
availability and promotion status.

If observations were collected at different times, state the gap. A later menu update may otherwise look like a channel difference.

Treat each channel as a separate observation

Do not assume that dine-in, direct pickup, marketplace pickup and marketplace delivery show the same base price or conditions. Capture each one separately.

The same restaurant may use:

one price for dine-in;
another for direct pickup;
a marketplace pickup price;
separate delivery prices by platform.

This structure lets the team compare only the channel pairs relevant to its decision.

Keep promotions, membership and taxes visible

A promotional price is not the regular menu price. Record both when they are shown. Also record who can access the offer, the required basket value and whether the customer must have a membership or subscription.

Taxes should be treated consistently. If one channel displays tax within the price and another adds it later, the values are not yet comparable. State whether the analysis uses tax-inclusive or tax-exclusive prices.

How to handle missing and channel-exclusive items

An item that appears in one channel but not another has no valid markup percentage. It may be exclusive, unavailable, renamed, delisted or missed during collection.

Keep these outcomes distinct:

matched and comparable;
present in one channel only;
temporarily unavailable;
collection failed;
ambiguous match;
channel-exclusive by confirmed rule.

Coverage and assortment differences can be important, but they should not be hidden inside the price calculation.

Build the benchmark from matched observations

Calculate each valid restaurant-item pair first. Then summarise the distribution across the defined panel.

Useful outputs include:

median markup;
lower and upper quartiles;
minimum and maximum, with outlier review;
share of matched pairs above a stated threshold;
result by restaurant, item, platform and market;
matched, unmatched and missing denominators.

Avoid calculating one average from all raw prices. A change in the mix of products or restaurants can move that average even when no matched item changed.

What QSR teams can decide from channel-markup data

A reliable comparison can support several decisions:

reviewing whether channel rules are applied consistently;
identifying products or restaurants outside the intended range;
comparing competitor channel structures;
estimating how menu prices and fees contribute to the customer total;
selecting cases for a pricing or catalogue review.

The data does not by itself explain why a competitor chose a price. It also does not prove demand, profitability or customer response. Those questions require first-party commercial data and, where appropriate, a controlled test.

Channel markups and menu consistency answer different questions

This guide measures the size and distribution of valid cross-channel differences. The separate menu-consistency process checks those differences against an approved pricing rule to decide whether they are explained strategy, unresolved drift or a confirmed correction.

For the broader collection and matching workflow, read Getplace's guide to menu and price comparison at scale. Teams that need store-level channel observations can review Getplace's restaurant pricing intelligence capabilities.

Frequently asked questions

What is the difference between delivery price parity and checkout parity?

Delivery price parity compares listed menu prices. Checkout parity compares the final customer total after fees, discounts, required choices and taxes. They are not interchangeable.

Should delivery fees be included in a restaurant price markup?

Not in the listed item-price markup. Include them only in a separately labelled checkout-premium calculation.

Should pickup or dine-in be the reference price?

Use the channel that matches the business question and state it clearly. There is no universal reference for every analysis.

How should a missing item be handled?

Do not calculate a markup. Record the missing, unavailable, failed or exclusive state and include it in the coverage denominator.

How often should channel prices be compared?

Choose a cadence that matches the event and response window. Promotions may need more frequent observation than a strategic quarterly benchmark.

The useful markup is the one the team can reproduce

A channel-price percentage is only as reliable as the match beneath it. Preserve the product, restaurant, time, customer conditions, reference channel and price components. Then the result can support a real decision instead of becoming another unexplained average.

About the evidence

This is a method-led article. Relevant Denis posts were reviewed as editorial leads, but their figures were excluded because their underlying observations were unavailable. The numerical example above is illustrative and is not a market finding.

Dine-In vs Pickup vs Delivery Prices: How to Measure Channel Markups