Weekly AOV Review Template for Shopify DTC Operators

Why Weekly AOV Review Matters

AOV is the second input to unit economics (the first being conversion rate). A 5% AOV drop with flat traffic is equivalent to a 5% revenue drop. Unlike traffic, which moves slowly, AOV can degrade in days - through discount creep, bot traffic, or accidental pricing changes.

Weekly review catches these shifts before they compound into monthly damage. The goal is not to obsess over daily noise, but to flag directional breaks that require investigation.

Core Metrics to Track

Pull these numbers every Monday morning for the prior week (Sunday - Saturday):

AOV (total revenue / order count)
AOV by traffic source (organic, paid, email, direct)
AOV by product category or collection
Median order value (catches outlier sensitivity)
% of orders with discounts applied
% of orders with upsells / bundles
Cart abandonment rate (proxy for pricing friction)

Threshold Framework

Set thresholds relative to your 4-week rolling average, not absolute targets. Thresholds vary by vertical and seasonality, but these guardrails apply to most DTC:

Green: Within 2% of 4-week average
Yellow: 2-5% below 4-week average - investigate but do not act
Red: 5%+ below 4-week average - root cause analysis required same day
Spike: 5%+ above 4-week average - document what changed (traffic quality, product mix, discount pause)

Diagnostic Checklist for Red Flags

When AOV drops into red, work through this checklist in order:

Traffic source mix - did paid traffic increase relative to organic? Paid often has lower AOV.
Discount application rate - did discount % jump? Check if a campaign auto-applied a code.
Product mix - did bestsellers shift to lower-priced SKUs? Pull top 10 by volume week-over-week.
Median vs. mean - if median is flat but mean dropped, a few large orders were replaced by smaller ones. Check for bot traffic or refunds.
Upsell / bundle attach - did post-purchase upsell rate drop? Check email or app performance.
Pricing changes - confirm no accidental price reductions in Shopify admin or third-party apps.
Refund rate - spike in refunds can artificially lower AOV if counted as negative revenue.

Common Failure Modes

Operators often miss AOV degradation because they conflate it with revenue. Revenue can stay flat while AOV drops if traffic increases. Conversely, AOV can rise while revenue falls if traffic collapses. Track both independently.

Discount creep - small incremental discounts (5% → 10% → 15%) erode AOV gradually. Weekly review catches the trend before it becomes structural.
Paid traffic quality decline - new ad accounts or audiences often have lower AOV. Spot this by segmenting AOV by source.
Bot traffic - fake orders inflate order count and lower AOV. Check for orders with $0 or unusually low values.
Seasonal product mix - Q4 gift sets have higher AOV than Q1 basics. Compare year-over-year, not week-to-week in isolation.
Email list fatigue - if email AOV drops while volume holds, list quality is declining. Segment by subscriber cohort age.

Weekly Review Template (Spreadsheet Format)

Use this structure in a Google Sheet or CSV updated every Monday:

Column A: Week ending date
Column B: Total revenue
Column C: Order count
Column D: AOV (B/C)
Column E: 4-week rolling average AOV
Column F: % change from rolling average
Column G: Status (Green/Yellow/Red)
Column H: Top traffic source AOV
Column I: Discount % of orders
Column J: Notes (e.g., 'Paid traffic spike', 'New bundle launched')

Action Rules

Assign actions based on status:

Green - document and move on. No action required.
Yellow - add to backlog. Schedule a deep dive if yellow persists 2+ weeks.
Red - stop. Run diagnostic checklist same day. If root cause is discount-related, pause or adjust. If traffic-related, audit ad account settings. If product mix, consider merchandising changes.
Spike - celebrate, but reverse-engineer it. Document what changed so it can be repeated or scaled.

Questions

FAQ

Should we review AOV daily or weekly?

Daily review introduces noise and false signals. Weekly is the minimum cadence for DTC. If you're running a major promotion, daily checks are warranted during that week only. Otherwise, weekly on Monday morning is the standard.

How do we handle AOV spikes from high-ticket orders?

Track both mean (AOV) and median order value. If a single large order skews the mean, median will stay flat. Use median as a secondary check. If spikes are recurring (e.g., B2B wholesale orders), segment them separately or exclude them from the DTC AOV calculation.

What if AOV is stable but revenue is declining?

AOV stability with revenue decline means traffic or conversion rate is falling. This is a separate problem. Check traffic sources, conversion rate by device, and email list health. AOV is not the lever here - acquisition and conversion are.

How do we account for returns and refunds in AOV?

AOV should be calculated on completed orders (post-refund). If your system records refunds as negative revenue, subtract them from total revenue before dividing by order count. Alternatively, calculate AOV on orders placed, then track refund rate separately. Consistency matters more than the method - pick one and stick with it.

Want this on your account?

Thirty minutes. Bring the number that keeps you up.

Book a demo