Managers can stop comparing unlike sales figures by agreeing on a metric dictionary before they compare reports. For each number, record the calculation, source, time period and person responsible for its definition. Then use the same version across locations.
Start with gross sales, discounts, refunds, net sales, tax and tips. The names alone are not enough: one report may subtract refunds on the day they happen, while another adjusts the original sale date. Both can be useful, but they answer different questions.
Agree on what each sales number includes
A metric dictionary is a shared operating document, not a list of labels copied from a dashboard. Each entry should say what goes into the number, what stays out and when activity is counted. Give each definition an owner who can settle questions and approve changes.
Use these starting definitions as a team decision, then check them against the reports you actually use:
- Gross sales: The menu price of items sold before discounts and refunds. Decide whether voided items or canceled orders ever enter this figure.
- Discounts: Reductions applied to item prices. Define how a discount covering several items is allocated if item-level comparisons matter.
- Refunds: Amounts returned against a sale. Record item refunds separately from returned tax and tips so the team knows what each total represents.
- Net sales: Gross sales minus discounts and item refunds under the selected timing rule. State explicitly whether tax and tips are excluded.
- Tax and tips: Track these separately from sales. A tip is not an item sale, and tax collected is not the same measure as menu revenue.
Also decide how to handle service charges, gift card sales and redemption, deposits, delivery charges and partial refunds. A deposit received today is not automatically the same measure as a completed sale today. If the business uses an accounting definition for any of these items, ask its qualified adviser how that definition should relate to the operating report.
Write down the decision even when every manager thinks the answer is obvious. A definition such as “net sales after adjustments” still leaves too much room for disagreement. Name the adjustments.
Map definitions to reports and periods
For every metric, list the report or transaction record it comes from, the field or fields used, the calculation and the reporting period. Include the time zone and the start and end of the business day. A location that closes after midnight may need a business-day cutoff that differs from a calendar day.
Next, identify the date used for each event. An order can have an order date, completion date, payment date and refund date. A report filtered by one is not interchangeable with a report filtered by another. If managers compare weekly performance, they should know whether a late refund changes the original week or appears in the week it was issued.
Use two named views when both questions matter:
- Activity-date view: Count a sale and a refund in the periods when each occurs. This helps managers see activity during a shift or week.
- Original-sale-date view: Assign the refund back to the original sale period. This helps compare the eventual value of orders from that period, but earlier totals can change after the period closes.
Neither label guarantees how a particular system calculates its reports. Ask a vendor to show how its date filters and adjustments work, including whether an earlier period is restated. If the available view does not match the dictionary, label the difference rather than silently treating the numbers as equal.
Keep dimensions separate too. Order source describes where an order came from; dining option describes how it was fulfilled, such as dine-in or pickup. An online order can be for pickup. Comparing “online” at one location with “pickup” at another mixes two different questions.
Fleksa's management software includes dashboard and order views, with sales and order summaries for a selected period. Ask which views and settings are available for your setup, and check their definitions against the team's dictionary. If payroll, inventory or accounting figures are part of the comparison, establish their sources separately rather than assuming one dashboard supplies them.
Use a sale and refund to test the dictionary
The following is a hypothetical worksheet, not a result from any restaurant or software product. Assume one order has $80 in item prices, a $10 discount, $7 in tax and a $12 tip. The guest pays $89. On a later day, the restaurant refunds $20 of item value and $2 of tax; the tip stays unchanged. The net payment retained after the refund is $67.
The table applies the definitions above using activity dates. It separates item sales from tax, tips and payment. These are sales and payment measures, not operating profit: fixed costs, variable operating costs and exception costs are all excluded.
| Dictionary entry | Calculation or treatment | Sale day | Refund day |
|---|---|---|---|
| Gross item sales | Item prices before discount and refund | $80 | $0 |
| Discounts | Item price reductions | $10 | $0 |
| Item refunds | Returned item value, excluding tax | $0 | $20 |
| Net item sales | Gross less discounts and item refunds | $70 | −$20 |
| Tax | Tax collected less tax returned | $7 | −$2 |
| Tips | Tips collected less tips returned | $12 | $0 |
| Payment movement | Payment collected less total refund | $89 | −$22 |
Across both days, net item sales are $50, net tax is $5 and tips are $12. Together they equal the $67 retained payment. That check works because this example has no other charges or payment adjustments. It does not mean sales and payment are the same metric.
Now change only the timing rule. In an original-sale-date view, the eventual net item sales for the sale date would be $50 rather than $70. The activity-date view still shows $70 on the sale day and negative $20 on the refund day. A manager comparing those sale-day figures without the timing labels could mistake a definition difference for a performance difference.
Decision boundary: Compare locations directly when they use the same item inclusions, adjustment rules and date basis. If one location cannot produce that basis, either convert both reports using reliable underlying records or show them separately with the mismatch labeled. Do not rank the locations on those figures until the comparison is like for like.
Run an acceptance check before rollout
Use the worksheet as a simulated check with sample records or a vendor demonstration. No real card payment, guest message or courier dispatch is needed. Ask each manager to calculate the expected numbers first, then compare them with the proposed report output.
- Show the original order, discount, tax and tip as separate fields. Can the team identify the source for each?
- Apply the partial item and tax refund on a later date. Does the activity-date report show the refund in the later period?
- Change to an original-sale-date view if one is offered. Does the earlier period update as expected, and can users tell that it changed?
- Filter the same order by source and dining option. Are the two dimensions labeled separately?
- Check the period cutoff and time zone. Would the same late-night order fall into the same business day at each location?
Accept a metric for shared reporting only when the team can reproduce its definition and explain any differences in output. If a report cannot show the required detail, document the gap and decide whether another source or a separate view is needed. Do not rename a field to make it appear equivalent.
After the simulated check, a live service pilot can use normal, authorized transactions and the restaurant's ordinary operating process. Review actual reports afterward; do not create a real guest order or payment merely to practice. The restaurant POS is one place to discuss how orders and adjustments are recorded before they reach a management report.
Keep the dictionary current across locations
Assign one person to own the dictionary and name a contact at each location. The owner does not need to make every decision alone, but someone must maintain the approved wording and tell managers which version to use.
For each entry, keep the metric name, business purpose, formula, included and excluded items, source, date basis, cutoff, owner, effective date and version. Store the document where managers can reach it beside their regular reporting instructions.
When a menu, ordering channel or report changes, propose the definition change before using it in a comparison. Record why it is needed, which locations and historical periods it affects, and whether older reports can be converted. Have the relevant managers check a small example, approve the new version and announce its effective date.
Do not overwrite the old definition without a record. If last month's report used a different rule, either recalculate it on the new basis or label the break in the comparison. For related performance decisions, apply the same period discipline when you compare labor hours with sales by shift.
Next step: Bring your current sales reports and a draft dictionary to discuss requirements with Fleksa. Ask the team to walk through the sale-and-refund check and compare the workflow with your reporting needs.
Frequently asked questions
What is the difference between gross and net sales?
In the example above, gross sales are item prices before discounts and refunds. Net sales subtract those adjustments. Your dictionary should state the exact inclusions and timing used by your reports.
Should refunds change the original sales day?
That depends on the question. An original-sale-date view assigns refunds back to the sale period; an activity-date view shows them when issued. Label the view and use the same basis when comparing locations.
Who should approve metric definitions?
Give one person responsibility for the shared dictionary, with input from location managers and anyone responsible for the source reports. Consult a qualified adviser when an operating definition needs to align with accounting or tax treatment.
