If menu prices changed during a campaign, do not treat the increase in reported revenue as campaign growth. Recalculate the later orders using the earlier prices, then compare order counts and item mix. That gives you a clearer view of what changed, although it still cannot prove the campaign caused the change.
The buying question is whether your reporting tools can supply the order-level evidence for that calculation. A useful report should let you identify the campaign period, see when prices changed, and compare the same items consistently.
Build a campaign period around the price change
Start with the date and time the new prices took effect. Divide the campaign into a before period and an after period. Record the number of service days, hours, ordering channels and locations in each period. A seven-day stretch with a holiday is not automatically comparable to an ordinary seven-day stretch.
The following example is hypothetical. A restaurant runs one campaign for two weeks and changes two menu prices at the start of the second week. Each period has seven service days, and the figures cover the same location and ordering channel. Every order contains exactly one of the two items.
| Measure | Before price change | After price change |
|---|---|---|
| Orders | 100 | 110 |
| Bowls sold | 60 at $10 | 50 at $12 |
| Sandwiches sold | 40 at $8 | 60 at $9 |
| Reported item revenue | $920 | $1,140 |
| Revenue at earlier prices | $920 | $980 |
The table separates reported revenue from a price-adjusted comparison. Before the change, bowls brought in $600 and sandwiches $320, for $920. Afterward, they brought in $600 and $540, for $1,140. The reported increase is $220.
At the earlier prices, the later period's 50 bowls and 60 sandwiches would have generated $500 plus $480, or $980. On the later period's item quantities, the price increases therefore account for $160 of the reported increase. The remaining $60 reflects the change in quantities and mix at earlier prices.
These are item sales amounts, not profit or cash deposited. The example assumes no discounts, refunds, tax, tips or delivery charges. It excludes fixed costs, variable costs and exception costs, including campaign fees, food, labor, processing, refunds and delivery. It is not an example of Fleksa pricing or a claim about Fleksa reporting.
Separate order count, item mix and revenue
The later period has 10 more orders, but it also has a different mix: fewer bowls and more sandwiches. Both facts matter. At earlier prices, a bowl is worth $2 more than a sandwich, so replacing a bowl with a sandwich reduces comparison revenue even when the order count stays the same.
One way to explain the $60 quantity-and-mix difference is to hold the earlier average order value constant first. The earlier $920 divided by 100 orders is $9.20. Ten extra orders at that average would add $92. The later mix then reduces the comparison by $32: 110 orders at $9.20 would be $1,012, while the actual later mix at earlier prices is $980. That leaves $60 of additional revenue at earlier prices.
This breakdown describes the sales pattern. It does not establish why the pattern occurred. More orders could reflect the campaign, a busy weekend, a competing restaurant closing, or another change. The price increase itself may also have influenced what guests ordered.
Check average order value alongside order count, not instead of it. Here, reported average item revenue rises from $9.20 to about $10.36. At earlier prices, the later average is about $8.91. The higher reported average is therefore consistent with higher prices masking a shift toward the lower-priced item.
Real orders may contain several items, modifiers or partial refunds. For those, count orders separately from item quantities. Ask whether the report shows each line item and its actual selling price, rather than only an order total or today's menu price.
Make a like-for-like item comparison
Map each later item to the earlier version before recalculating revenue. A stable item identifier helps, but the identifier alone is not enough if the portion, ingredients or included sides changed. Record those changes so you do not call two different offers identical.
For a comparable item, multiply the later quantity by its earlier price. Add those amounts across matched items. Compare that total with the earlier period's item revenue, while keeping unmatched items visible in a separate line. A new item has no earlier price; a discontinued item has no later sales. Do not silently assign either one a price or remove it without showing the effect.
Modifiers need the same care. If a bowl's base price changed but an added protein also changed price, compare the base and modifier separately where the data allows. If a meal bundle replaced individual items, note that the bundle may change both the price and what a guest receives. A forced comparison could be more misleading than leaving the bundle unmatched.
Decide whether to use prices before or after discounts. Either can answer a useful question, but mixing them cannot. A pre-discount comparison isolates menu prices more directly. A net item-sales comparison can show what guests actually paid after promotions, provided discounts, returns and their timing are treated consistently in both periods. Show both if campaign discounts are material.
Your restaurant POS system may be one place to request item-level sales records. For online sales, ask how the restaurant management software identifies the order channel and connects it to the transaction. Confirm the specific fields and export workflow with the vendor rather than assuming that a dashboard total contains the detail.
Use a decision worksheet with your vendor
Before buying or renewing a campaign tool, write down the evidence you need and what would make it usable. The following worksheet is a starting point; adjust the thresholds to the size of your menu and the decision at stake.
- Period and scope: Request order timestamps, location, channel and campaign identifiers where available. Accept the report only if you can define the price-change boundary and apply the same scope to both periods.
- Item history: Request item and modifier identifiers, quantities, transaction prices and the effective dates of price changes. Accept it if you can reconstruct earlier-price revenue for matched items without substituting current prices.
- Adjustments: Request discounts, refunds and cancellations with dates and amounts. Accept it if you can state whether each figure is gross or net and apply the same treatment across periods.
- Coverage: Request an export of matched and unmatched items. Accept the comparison if unmatched sales are shown separately and are small enough for your decision; set that limit before reviewing the result.
- Campaign measurement: Ask how the tool associates orders with a campaign and whether it distinguishes a sent message, a redeemed offer and a completed sale. Accept the report only if those labels and their limits are clear.
- Usability: Ask for a sample export and a walkthrough using simulated data. Accept it if your team can reproduce the comparison and reconcile its totals to the underlying sales records.
Fleksa's restaurant marketing automation page describes email and SMS campaigns, segmentation, promo codes and loyalty tools. Ask how the campaign and sales data needed for your worksheet can be accessed, combined and exported for your setup. Access to contact data is separate from permission to send marketing; ask how your team will manage both.
For costs, use a written quote for the workflow you need and check Fleksa's plans, reviewed in November 2026. Separate the software quote from processing, delivery and other operating costs that may apply. A campaign revenue comparison alone cannot tell you whether the campaign paid for itself.
Make a decision without overstating the result
Once the worksheet is complete, write a short finding in three parts: what happened to reported sales, what happened at earlier prices, and what remains uncertain. For the example above, the finding would be that reported item revenue rose by $220; $160 of that difference is explained by applying the higher prices to later quantities; and revenue at earlier prices rose by $60. The figures do not show how many sales the campaign caused.
Look for other changes before acting: service hours, stockouts, menu availability, channel mix, promotion terms and local events. If an item sold out after the price change, its lower quantity is not a clean measure of guest demand. If the campaign reached different guests in each period, the periods do not isolate price or campaign effects.
A stronger future comparison might use a suitable comparison group or a planned period with stable prices and similar operating conditions. Even then, document meaningful differences instead of promising a causal answer from a dashboard. If you cannot match a substantial part of the menu or reconcile adjustments, treat the result as descriptive and avoid a confident campaign return calculation.
Next step: Use the worksheet to compare your requirements with Fleksa. Ask for a walkthrough of the relevant campaign, sales and export workflow using simulated data, and confirm it meets your acceptance criteria before buying.
Frequently asked questions
Can I compare campaign revenue if prices changed halfway through?
Yes. Split the period at the effective price-change time and recalculate later matched-item quantities at earlier prices. Keep unmatched items and discounts visible, and do not present the adjusted difference as campaign impact.
Does a higher average order value mean the campaign worked?
No. Higher menu prices can raise the average even when guests buy a lower-priced mix. Compare order count, item quantities and average value at consistent prices before interpreting the change.
What if the vendor only provides campaign revenue totals?
Ask for transaction-level item quantities, selling prices, timestamps and adjustments, plus campaign identifiers where available. If you cannot reconstruct a consistent comparison, use the total as a sales description rather than proof of campaign performance.
