Default Options

Default options are the preselected choices on your site — shipping speed, subscription cadence, product variant — that quietly steer the majority of buyers. Set them well and you lift revenue without adding friction.
Default Options
Preselected choices on a page or form that most users accept without changing, exploiting default bias to steer behaviour.
Default options are the values, variants, or settings already selected when a shopper lands on a step in your funnel — the shipping method that's checked, the subscription frequency the slider opens on, the product size that's highlighted, the checkbox for marketing emails. Because changing a default takes effort and implicit endorsement, most people accept it.
Defaults are one of the highest-leverage tools in choice architecture: a single line of config can shift double-digit percentages of revenue. They're also ethically loaded. The same mechanism that helps a buyer pick the right size by default can also trap them in a pre-ticked add-on they didn't want, so the right defaults align user interest with business goal — not just business goal.
The mechanism behind default options is default bias: a well-documented tendency to stick with the pre-set choice rather than evaluate alternatives. Effort, loss aversion, and an implicit signal that the default is recommended all reinforce it.
Defaults sit inside the broader discipline of choice architecture — the deliberate design of how options are presented. Where a sort order or a comparison table nudges, a default actively assigns. That makes defaults the most powerful lever in the toolkit, and the one that demands the most care.
Revenue Impact = Visitors × Default Adoption Rate × (AOV_default − AOV_baseline)
Visitors
Funnel visitors
Shoppers who reach the step where the default is set.
Default Adoption Rate
Adoption rate
Share of visitors who accept the default without changing it.
AOV_default
AOV with new default
Average order value when the new default is in place.
AOV_baseline
AOV with old default
Average order value under the previous default.
An apparel Shopify store changes its default product size from S to M after data shows M is the most-purchased size. The checkout-flow step sees 40,000 monthly visitors. Adoption of the default size sits at 62%. Average order value rises from €58 to €64 because fewer shoppers abandon after a size swap.
Visitors: 40000
Default Adoption Rate: 62%
AOV_default: €64
AOV_baseline: €58
→ €148,800 incremental monthly revenue
A configuration change with no development cost outperforms most paid-acquisition tests at this revenue band — which is why defaults are the first lever experienced teams pull.
Adoption rates depend heavily on the decision type. Low-stakes, high-friction choices (cookie consent, marketing opt-in) see near-total default acceptance. High-stakes, identity-laden choices (product size, subscription cadence) see lower adoption but bigger revenue swings per shopper who accepts.
Typical default-adoption rates by decision type on DTC checkout flows
| Decision type | Default adoption rate | Revenue sensitivity |
|---|---|---|
| Marketing email opt-in (pre-ticked) | 85–95% | Low — list quality drops |
| Shipping speed (standard preselected) | 70–85% | Medium |
| Product variant / size | 55–70% | High |
| Subscription frequency (e.g. 30 days) | 60–75% | Very high — drives LTV |
| Gift-wrap / add-on (pre-ticked) | 25–40% | Medium — refund risk |
| Currency / region (geo-detected) | 90–98% | Low — UX-driven |
Treat every default as a hypothesis. The right default for a beauty SKU isn't the right default for an electronics store, and the right shipping default in Q1 isn't the right one in Q4. Test the candidate against the incumbent, watch refund and unsubscribe rates alongside conversion, and revisit the winner every quarter as catalogue and traffic mix shift.
Default options FAQ
A recommendation is a visual highlight on an option the shopper still has to click. A default is already selected — the shopper has to actively choose something else to override it. Defaults convert far better because they shift the work onto the dissenter.
Under GDPR and most EU consumer law, no — explicit opt-in is required for marketing communications, so the box must start unchecked. Pre-ticked is still legal for purely operational defaults like shipping speed or product variant. When in doubt, default the experience, not the consent.
Choice architecture is the parent discipline — the deliberate design of how options are framed, ordered, and presented. Default options are one tool within it, alongside anchoring, decoy pricing, and progressive disclosure. Defaults are the most powerful because they assign rather than suggest.
Default to the frequency that matches actual consumption, not the shortest interval. Beauty consumables typically default to 30 or 60 days; coffee to 14 or 28; pet food to a frequency matched to bag size. Defaulting too short drives churn after the second order.
Default to the most popular variant that aligns with your margin goals. The cheapest variant often anchors expectations low and reduces AOV. The bestseller typically converts better because it carries social-proof signal and matches what most shoppers want anyway.
Run a controlled A/B test where one variant keeps the existing default and the other applies the candidate. Hold the test long enough to capture a full purchase cycle — including returns and refunds, since a bad default often shows up as elevated returns rather than reduced checkout conversion.
They can be. A default that aligns user intent with business outcome (defaulting to the right size, the most-loved variant, a reasonable shipping speed) is good design. A default that traps users into add-ons or extends a subscription past their need is a dark pattern — and increasingly regulated.
Yes, but adoption is usually 10–20% lower than for first-time visitors because returning customers have prior preferences. The highest-leverage personalisation is to default each returning shopper to their own last-purchased variant or frequency.
On choices with high consequence asymmetry — anything where accepting the default could cost the user materially more than declining it. Insurance add-ons, expedited shipping fees, and recurring billing frequencies all warrant explicit selection rather than a preselected nudge.
Every quarter, and whenever the catalogue or traffic mix changes materially. The default size that worked when your mix was 70% women's apparel won't hold once men's launches. Treat defaults as a living config, not a launch decision.
Test ideas before you ship them
Run unlimited A/B tests, attach hypotheses to outcomes, and build a searchable archive of what works — and what doesn't.