Conversion only
Scenario conversion × current basket
——
Retail planning / visitors to sales
Model daily sales from visitors, conversion and average order value. Compare conversion and basket changes separately, then together.
Keep the visitor definition and sales-reporting basis consistent. The defaults are examples, not industry benchmarks.
Both scenarios use the same daily traffic. Changing conversion or basket value here does not establish that either change will happen.
03 / Change one assumption at a time
The two single-change cases hold the other input at its current value. The combined case changes both; the same visitor count runs through every row.
Scenario conversion × current basket
——Current conversion × scenario basket
——Scenario conversion × scenario basket
——When both inputs change, the changed transaction count also receives the changed basket value. This interaction completes the arithmetic; it does not identify a real-world cause.
Effects use unrounded values, then display in cents. Conversion differences are percentage points; they are not the relative percent change.
Revenue growth can come from more traffic, a higher conversion rate or a larger basket. This tool isolates conversion and basket size so store teams can see whether a small operational improvement would matter more than simply chasing more visitors.
Transactions = visitors × conversion rate. Revenue = transactions × average order value. Scenario revenue uses the same visitor count with the scenario conversion rate and scenario AOV. Lift = scenario revenue − current revenue.
Three hundred daily visitors at a 72% conversion rate produce 216 transactions. At a $62 average order, that is $13,392 in daily sales. Raising conversion to 76% and AOV to $65 would produce $14,820, a $1,428 daily lift at the same traffic.
Check the cost side with Break-Even. Keep assumptions consistent with Product Pricing and Inventory Turnover.
Use consistent transaction records from Dispensary POS systems. For store planning, see Setting up a dispensary.
In this model it is completed purchase transactions divided by store visitors. Your POS or door counter may define visits differently.
AOV is revenue per transaction. One customer can create more than one transaction over time.
Yes, if you are modeling e-commerce and use online orders as the converted outcome.
Put the scenario to work
Check the cost, service and operating-day assumptions behind the daily sales model.