Revenue Leakage

Overview

• Revenue Leakage summarises recorded Discounts, Refunds, and current snapshots of Voided/Cancelled/Failed orders.
• Discount rows distinguish Order-level and Item-level usage.
• A split-payment period can contain a proportional discount amount without counting the same discount use again.
• Unsuccessful-order reasons are never inferred. If no reliable reason was stored, the report explicitly says it is unrecorded.
• Unsuccessful orders are current-status snapshots of orders created in the selected range because a reliable status-transition timestamp is not stored for that analysis.

When to use this

• Use this to find unusually high discounts/refunds/unsuccessful orders that deserve review—not to assign blame automatically.

Step-by-step

1. Review total Discounts and Refunds.
2. Compare Order-level and Item-level discount use.
3. Review unsuccessful order counts by status/Store/staff context.
4. Open the underlying orders/refunds before deciding the cause.
5. Improve staff reason capture/process where 'unrecorded' is too common.

Common mistakes

• Do not label every Discount/Refund as preventable loss.
• Do not invent a cancellation reason from order data when the report says unrecorded.
• Do not count proportional split-payment discount allocation as another separate discount use.

Troubleshooting

• If a refund appears in a historical period, check refund attribution to the originating Payment.
• If unsuccessful orders are unexpectedly high, inspect actual order records/status rather than report aggregates alone.