Hey Sage · Free ecommerce scenario planner · AUD
AOV & CVR
scenarios
Enter your current AOV, purchase conversion rate, cost per landing page view and planned spend. Set your revenue and ROAS goals, then adjust AOV and CVR to compare the result.
Start with your current cost per landing page view, AOV, purchase conversion rate and planned spend. Add your revenue and ROAS goals, then adjust scenario AOV and CVR. The planner updates projected orders, revenue and ROAS as you move either input.
The chart plots current performance, your selected scenario and the combinations that meet both goals. Use it to compare changes to basket size, conversion rate or both.
Use AOV, purchase conversion rate and cost per landing page view from the same reporting period.
Add planned spend, revenue goal and target ROAS on one consistent attribution basis.
Change either scenario input to see the effect on projected orders, revenue and ROAS.
Review the chart and reference scenarios to see which combination reaches both goals.
Planned spend divided by cost per landing page view gives the traffic available to both the current and scenario projections.
Orders equal landing page views multiplied by purchase conversion rate. Revenue equals orders multiplied by AOV. ROAS equals revenue divided by planned spend.
We compare your revenue goal with the revenue implied by planned spend and target ROAS. The chart shows the AOV and CVR combinations that reach the higher requirement.
Use the same date range, attribution basis and treatment of GST, shipping, discounts, cancellations and returns across every input.
Use your current AOV, purchase conversion rate, cost per landing page view and planned spend. Add a revenue goal and target ROAS using the same reporting period and attribution basis.
The current projection uses your current AOV and purchase conversion rate. The scenario projection holds spend and cost per landing page view constant while you adjust AOV and CVR.
Planned spend divided by cost per landing page view gives projected landing page views. Multiply those views by purchase conversion rate and AOV to calculate projected revenue.
At the same planned spend, a revenue goal and target ROAS can imply different revenue requirements. We use the higher requirement so a scenario must meet both goals.
Yes. Hold one scenario input at its current value and change the other, or adjust both to compare a shared path to the goal.
Use purchases divided by landing page views because the traffic input is cost per landing page view. A session-based conversion rate uses a different denominator and should not be mixed into the same scenario.
No. It is a planning model based on the inputs you provide. It does not account for contribution margin, repeat purchases, traffic quality or changes in acquisition cost.
We can connect the scenario to contribution margin, allowable acquisition cost, channel mix and a practical test plan.
















