To understand what delivery-app compensation does to branch profit, do not start and stop with refunds as a percentage of sales. Start with a real settlement and the orders whose values were deducted. Then identify which costs were already incurred and what the app actually returned under its terms. The answer can differ by channel and by claim.
Short on time
Start with settlement
Use actual settlement deductions before estimating profit impact.
Account for the order
Ingredients and preparation may already have been paid for before the refund.
Separate cases
A remake, partial deduction and rejected claim have different effects.
Tie evidence to the decision
Evidence may support a dispute; it does not calculate margin by itself.
Build a worksheet from your records, not an imaginary order
Ask finance for the original settlement, not only the net amount carried into the monthly report. Choose a completed period and separate recorded sales, compensation or deductions, and any commissions or adjustments associated with those claims. Read the channel's terms to determine whether commission on a refunded order was reversed and whether the restaurant bore any cost of a replacement. Do not assume every app treats a claim the same way.
Use POS to find each disputed order and its items. Use branch cost records for ingredients and packaging where those records are reliable. Separate recoverable amounts from costs already consumed. If an item's cost is unknown, mark it unavailable rather than inserting a general restaurant-industry percentage. Finance then sees both what can be calculated and what data needs improving.
Read the deduction beside the order that came before it
An order prepared and packed before a refund is different from one canceled before preparation began. The first may have consumed ingredients and packaging; the second may carry no production cost. If the branch remade the food, record the replacement's labor and ingredients separately. Linking the charge to the order's state prevents these different events from being averaged into a misleading figure.
Classify the reason too: missing item, wrong item, delay or damage after handoff where known. The aim is to identify which part the branch can change. A packing claim may justify reviewing the packing station. Damage after handoff will not be cured by adding a camera there. Do not evaluate an operational investment against a pile of charges it cannot plausibly affect.
Questions that turn the report into an action
What deductions belong to each delivery app and branch? Can each charge be connected to an order and its actual production costs? Which claims received evidence before their deadlines? None of these questions needs a market-wide percentage. Compare the same branch after a defined process change and keep the indicator's definition stable. If the app changes its terms or the restaurant changes how it classifies claims, record that before attributing a shift to the team's performance.
Keep unmatched deductions in a separate row. They may reveal a reference-number or settlement-download problem rather than a packing problem. Ask the branch to inspect a sample of material cases: what POS recorded, what happened at packing and when the app's notice arrived. That is how a finance report reaches a step someone can change during service.
Where visual evidence helps
Packing evidence linked to an order can add something POS cannot show by itself: what was visible at the station before handoff. In Proof Manager, a team can search by order number and review item details, packing result and a short clip where coverage is suitable. That may support a specific response or help explain a recurring mistake. It does not calculate the restaurant's margin for finance, guarantee that an app accepts a dispute, or establish what happened after the order left the camera's view. Begin with your real settlement and choose evidence for the gap it reveals.
