Ecommerce Revenue Audit Template: Find Leaks in Orders, Refunds, AOV, Retention, and Product Mix

What is an ecommerce revenue audit template?

An ecommerce revenue audit template is a repeatable operating document that helps you diagnose why revenue, profit, cash, or customer quality changed. It turns scattered reports into a single investigation path.

The goal is not to admire metrics. The goal is to answer practical questions:

• Did revenue actually decline, or did one report change because of timing, refunds, taxes, shipping, or attribution rules?
• Are orders down, or are orders stable while AOV dropped?
• Are gross sales healthy while refunds, discounts, or shipping costs are eroding net revenue?
• Are you acquiring customers who place a first order but do not return?
• Did a product launch grow sales but increase refunds, support tickets, exchanges, or low-margin orders?
• Are paid channels reporting performance that does not match order-level customer quality?

The template should help operators move from “sales are down” to a specific finding such as “first-time orders from Campaign B increased, but those customers used deeper discounts, refunded more often, and had weaker second-order behavior.”

Key revenue audit terms

When should ecommerce operators run a revenue audit?

Run a revenue audit whenever the top-line story and the operating reality do not match. If the dashboard says sales are fine but cash is tight, refunds are rising, or repeat purchase is soft, you need an audit rather than another generic report.

You should run the audit when:

• Revenue is down despite stable traffic.
• Traffic is up but orders are flat or declining.
• Orders are stable but AOV dropped.
• Gross sales look healthy but net revenue or cash is weak.
• Refunds, returns, exchanges, cancellations, or support issues increased.
• Discount usage rose faster than order volume.
• Repeat purchase, second-order rate, or retained revenue declined.
• Paid channel reports disagree with ecommerce platform revenue.
• A new product launch created sales but unclear profitability.
• A subscription, bundle, marketplace, wholesale, or POS channel started mixing into ecommerce reporting.
• Inventory constraints changed what customers could buy.
• Finance, marketing, and merchandising teams are using different definitions of revenue.

What kind of problem are you diagnosing?

The revenue audit inputs and template tabs

A good ecommerce revenue audit template should be simple enough to run monthly and detailed enough to expose the leak. You do not need every tool in your stack to agree before starting. You need clean exports, consistent date ranges, and a clear place to log findings.

Required data inputs

• Ecommerce platform order export: order ID, order date, customer ID or email, revenue, line items, SKU, quantity, discount, taxes, shipping, refunds, tags, channel, fulfillment status, cancellation status.
• Payment processor export: deposits, fees, chargebacks, refunds, payout dates, transaction IDs.
• Refund and return export: refund date, refund amount, refunded item, reason, restock status, exchange status.
• Ad platform spend: spend, campaign, ad set, creative, reported conversions, reported revenue, click date, conversion window.
• Email and SMS performance: campaign sends, flow sends, attributed orders, revenue, unsubscribe rate, click activity.
• Product catalog: SKU, category, price, cost, bundle status, inventory status, margin notes.
• Discount code export: code, promotion type, usage count, order value, customer type, stacking behavior, expiration date.
• Fulfillment notes: delays, stockouts, backorders, damaged shipments, carrier issues, warehouse notes.
• Customer/order history: first order date, purchase count, first product, first channel, last purchase date, total revenue, refunds.

Recommended template tabs

Step 1: Reconcile revenue, orders, and reporting mismatches

Start the audit by proving which numbers are real. If finance, marketing, and ecommerce operations are using different revenue definitions, every later conclusion will be shaky.

Create a reconciliation table for the audit period and the comparison period. For example, compare this month to last month, this month to the same month last year, or the last 28 days to the previous 28 days. Use the same timezone and the same order inclusion rules across every export.

Revenue reconciliation workflow

1. Set the audit period. Choose exact start and end dates. Avoid mixing calendar months, rolling windows, and platform-specific attribution windows in the same comparison.
2. Export all orders. Include order ID, created date, paid date, fulfillment status, cancellation status, channel, customer ID, line items, discounts, refunds, taxes, and shipping.
3. Separate order date from refund date. Refunds can distort period reporting when the sale happened in one period and the refund happened later.
4. Compare gross sales to net sales. Identify how much of the gap comes from discounts, returns, cancellations, taxes, shipping treatment, or manual adjustments.
5. Compare ecommerce revenue to payment deposits. Payment processor deposits may differ because of fees, payout timing, chargebacks, reserves, or multi-day settlement windows.
6. Check channel inclusion. Confirm whether marketplace, POS, wholesale, subscription, draft, manual, or exchange orders are included.
7. Check attribution windows. Ad platforms and analytics tools may assign credit based on different click, view, and conversion windows.
8. Document the trusted revenue definition. For the audit, define the number you will use as the operating source of truth.

Common causes of ecommerce reporting mismatch

Step 2: Find leaks in refunds, discounts, and AOV

Once the revenue number is reconciled, look for immediate monetary leaks. These are the issues that can make sales look healthy while the business keeps less money than expected.

Audit refunds by product, customer, source, and time

Do not only look at total refund amount. A blended refund number can hide the actual problem. Break refunds into operational segments.

• By product or SKU: Which products have high refund volume or high refund value?
• By category: Is the issue concentrated in a product type, size range, material, flavor, variant, or bundle?
• By first order source: Are certain campaigns or channels bringing customers who refund more often?
• By discount code: Are heavily discounted orders more likely to refund?
• By customer type: Are first-time customers refunding more than returning customers?
• By cohort: Did customers acquired in a specific month, launch, or promotion behave differently?
• By reason: Are refunds caused by sizing, quality, shipping delay, damaged items, wrong expectations, duplicate orders, or buyer remorse?
• By timing: How many days after purchase do refunds typically happen?

Refund diagnosis table

Audit AOV without fooling yourself

AOV can rise or fall for healthy and unhealthy reasons. A higher AOV is not automatically better if it comes from deeper discounts, low-margin bundles, or fewer entry-level orders that normally create repeat customers. A lower AOV is not automatically bad if it comes from a profitable acquisition product that leads to strong second purchases.

Audit AOV by decomposing it into the behaviors that create it:

• Units per order: Did customers buy fewer items per checkout?
• Average item price: Did the store shift toward lower-priced SKUs?
• Bundle attach rate: Did bundles, kits, or multipacks decline?
• Cross-sell attach rate: Did add-ons, accessories, refills, or warranties decline?
• Free-shipping threshold behavior: Are customers adding items to reach the threshold, or stopping below it?
• Discount depth: Did the pre-discount basket stay stable while post-discount revenue fell?
• New vs returning mix: Did more first-time customers buy entry-level products?
• Inventory availability: Were high-AOV items out of stock?

Compare gross, net, and contribution-aware revenue

Discount leakage checks

Discounts can create useful demand, but they can also train customers to wait, reduce margin, and make channel performance look better than it is. Include these checks in the audit:

• Which codes drove the most orders?
• Which codes drove the most net revenue?
• Which codes had the deepest average discount?
• Which codes were used by new customers versus returning customers?
• Which codes stacked with other promotions?
• Which discounts were used on already low-margin products?
• Which codes produced high refund rates?
• Which codes produced weak second-order behavior?

Step 3: Diagnose retention, cohorts, and product mix

Revenue leaks often show up after the first order. A campaign can bring in customers. A product can sell out. A launch can spike revenue. But if those customers do not return, refund more often, or buy products with poor margin, the initial revenue story is incomplete.

Build retention cohorts around the first purchase

Group customers by the moment or behavior that started the relationship. Then compare what happened after purchase.

Useful cohort groupings include:

• First purchase month: Customers whose first order happened in the same month.
• First product purchased: Customers grouped by the SKU, bundle, or category that acquired them.
• Acquisition channel: Customers first attributed to paid search, paid social, organic, email, affiliate, marketplace, or direct.
• Campaign or promotion: Customers acquired from a launch, sale, influencer, giveaway, or seasonal offer.
• Discount used: Customers who used no discount, a welcome code, a seasonal code, or a deep promotion.
• Customer type: First-time, returning, subscription, wholesale, marketplace, or POS customers.

Retention metrics to compare

Audit the role of each product

Not every product has the same job. Some products acquire new customers. Some products create repeat purchase. Some lift AOV. Some are profitable but slow-moving. Some create support and refund problems. Product-level revenue audits should separate these roles.

Step 4: Turn audit findings into operator actions

The audit is only useful if it changes what the team does next. Every finding should become an action with an owner, a due date, and a review metric.

Map findings to next steps

Build action logs, not just dashboards

Dashboards show what happened. Attribution tools help assign credit. A revenue audit should connect orders, refunds, customers, products, and lifecycle actions so the team can decide what to fix next.

Your action log should include:

• The finding in plain language.
• The metric or export that supports it.
• The suspected cause.
• The business impact.
• The owner.
• The next action.
• The due date.
• The review date.
• The metric that will prove whether the action worked.

Monthly ecommerce revenue audit checklist

Use this checklist as a recurring operating rhythm. The best revenue audits are not one-time investigations. They become a monthly habit that helps the team catch leaks before they become expensive.

Monthly checklist

Simple monthly audit sequence

1. Set the date range and comparison period.
2. Export orders, refunds, discounts, products, customers, and payment data.
3. Reconcile gross sales, net sales, orders, refunds, and deposits.
4. Identify the metric that moved most: orders, AOV, refunds, discounts, repeat purchase, or product mix.
5. Segment the movement by product, channel, customer type, discount, and cohort.
6. Write the finding in plain language.
7. Assign an owner and action.
8. Review the metric again at the next operating meeting.