# Shopify CRO Guide: What to Change and What to Test First

> Shopify CRO guide: the checkout settings your plan lets you change, how Shopify Experiments count visitors, and the traffic a 90-day test needs.

- URL: https://missiongrowth.io/blog/shopify-cro
- Published: 2026-11-12 · Updated: 2026-11-12
- Author: Furkan Aktaş, Co-Founder, Mission Growth
- Publisher: Mission Growth. Company facts: https://missiongrowth.io/llms.txt

Shopify CRO is the work of raising the share of online store sessions that end in an order, and on Shopify its order is set by two limits: what your plan lets you change at checkout and how much traffic a native test needs.

So what is CRO in Shopify beyond a list of tactics? Shopify conversion rate optimization is an order of work, because you probably know the tactics already and the open questions are which ones Shopify lets you touch and which ones your traffic can prove. This guide answers both. For worked examples from real stores, our conversion rate optimization case studies cover them.

In this guide:

- **Rates:** which of Shopify's conversion rates a given change should be judged on.
- **Limits:** the checkout fields your plan lets you edit and how Shopify's native Experiment counts visitors.
- **Sequence:** how many monthly sessions a 90-day test needs and what to do first at your traffic.

## Shopify CRO runs on four conversion rates, and a test shows only some

Shopify's conversion rate is the percentage of online store sessions that lead to an order, and its analytics page defines three more rates, add to cart, reached checkout and checkout conversion, each tied to a different part of the store.

Here are the definitions as Shopify's analytics page words them, with the kind of change they judge:

| Rate | What Shopify says it measures | Change it judges |
|---|---|---|
| Conversion rate | Percentage of online store sessions that lead to an order | Anything judged on orders overall |
| Add to cart rate | Online store visits with items added to cart relative to total visits | Product page and theme edits |
| Reached checkout rate | Online store visits that reached checkout relative to total visits | Cart and theme edits that move people toward checkout |
| Checkout conversion rate | Online store sessions with completed purchases relative to the visits that reached checkout | Checkout and accounts changes |

Shopify also lists bounce rate, the percentage of online store visits that ended after a single pageview. It is a diagnosis metric for entry pages more than a goal.

What you can read depends on how you roll a change out. Shopify's analytics page lists gross sales, orders and average order value for a theme Launch alongside conversion rate and bounce rate.

A theme Experiment lists conversion rate over time, bounce, reached checkout and add to cart. A checkout and accounts Experiment lists checkout conversion.

::figure{src="/blog/figures/shopify-cro-3.svg" alt="Two columns comparing metrics Shopify lists for a theme Launch (gross sales, orders, average order value, rates) with a theme Experiment (conversion, bounce, reached checkout, add to cart)." caption="A theme Launch lists gross sales, orders and average order value next to conversion rate and bounce rate; a theme Experiment lists four session rates only." width="720" height="271"}

Two more rules from the same page matter. A rollout that contains a discount change reports the same metrics as any other rollout, so the revenue or orders attributed to a discount are unavailable.

And if you run one set of changes as a Launch and then as an Experiment, results for the same metric might differ, because each rollout type uses a slightly different algorithm. A Launch reading and an Experiment reading of one rate are not interchangeable.

That gap shows up the moment an offer change is involved. Say a discount lifts conversion 10 percent and cuts order value 12 percent. Multiply the two and revenue per session falls to 0.968 of its old level, a 3.2 percent drop, even though the number you were watching went up.

Shopify's page lists average order value for a Launch, computed from gross sales and discounts divided by orders. No Experiment metric listed for a theme or checkout change measures revenue per session.

So the rule is short. Judge a theme change on add to cart or reached checkout, a checkout change on checkout conversion, and any offer change on revenue per session through a before-and-after read. If your overall number looks low and you don't yet know why, the diagnosis and benchmark side lives in a separate post on [why is my conversion rate low](https://missiongrowth.io/blog/low-conversion-rate).

## What your Shopify plan lets you change at checkout

Shopify's checkout editor and settings let every plan from Basic up change standard checkout options, while apps in the information, shipping and payments steps need Shopify Plus.

Shopify's checkout extensibility page puts it this way: standard customizations are available on all pages for businesses on the Basic plan or higher, and advanced customization only on Shopify Plus. The plan comparison table lists apps that customize the information, shipping and payments pages for Plus. An Experiment rollout, the native way to test any of this, needs the Grow plan or higher.

::figure{src="/blog/figures/shopify-cro-1.svg" alt="Shopify CRO plan matrix showing standard checkout customizations from Basic, Experiments from Grow and checkout step apps on Plus only." caption="Standard checkout options start on Basic, Experiments on Grow, and apps in the information, shipping and payments steps need Shopify Plus." width="720" height="261"}

What can you actually change on a Basic plan? Less than "simplify your checkout" implies. Shopify's form options page says you can make some fields required, optional or not included, and that not all fields can be edited. The Customer information section edits five, and each has its own set of options:

- **Full name:** a choice between requiring only a last name and requiring first and last name. It can't be optional or removed.
- **Company VAT number:** Don't include or Optional. There is no Required option, so a store that doesn't sell to businesses in the EU or the UK can remove it.
- **Company name:** Don't include, Optional or Required.
- **Address line 2:** Don't include, Optional or Required.
- **Shipping address phone number:** Don't include, Optional or Required. It is Optional by default on new stores, so the field shows but doesn't block checkout.

Every other form option is always required, including the Save this information for next time option. That means a fixed core you can't trim, so don't spend a sprint hunting for a field to delete that isn't in the list.

Two more settings act as levers. You can require customers to sign in before checkout, which is Shopify's version of the guest checkout decision. When you do, customers can only use an email address.

Express wallets are the other lever. Shop Pay is included in Shopify Payments and processed at your Shopify Payments rates. The Marketing opt-in section controls where the marketing consent checkbox shows, so it is a consent display setting and stays off this list of conversion levers.

Three traps sit inside these settings.

**Address line 2 can lock customers out.** Shopify's help page warns that Required or Don't include can stop some shoppers from completing checkout, depending on the kind of home they live in. Leave it Optional unless you have a shipping reason.

**The contact method choice decides who sees the Shop Pay save prompt.** Shop Pay needs an email address to save a customer's payment information. If you set the contact method to phone number or email, customers who enter only a phone number aren't prompted to save their information.

No contact method setting requires both an email address and a phone number. Setting Shipping address phone number to Required collects a phone number as well.

**A Required company name hits wallet users.** Customers who pay with Apple Pay or Google Pay must type one in when their wallet doesn't include it.

So "simplify checkout" on Shopify means five field settings, a contact method choice, a sign-in requirement and the express wallets. Changing the checkout steps themselves is a Plus decision.

## Fix the store-wide basics before you test anything

Page speed, mobile product pages, visible reviews and a clear offer are basics to fix before any test, because an Experiment cannot filter results by device and small effects need more traffic than a store has.

The device limit is the practical one. A phone-only fix gets averaged with desktop sessions in the result, since you can't filter by device. Here are five basics to ship on evidence and the rate to judge each on:

1. **Page speed.** Judge it on bounce rate before and after.
2. **Mobile product pages.** Check text scaling, buttons and checkout on a phone, then read add to cart rate.
3. **Visible reviews and clear return policies.** Put them near the add to cart button and compare add to cart rate across the change.
4. **Product images and descriptions.** Same metric, same before-and-after read.
5. **A clear offer.** Bundles and announcement bars can raise conversion while lowering order value, so judge them on revenue per session.

Before you pick, heatmaps and session recordings show where sessions stall on those pages. They decide what to fix, and a before-and-after read decides whether it worked.

Which tactics have strong evidence behind them is a separate question, ranked by traffic level in our [CRO best practices](https://missiongrowth.io/blog/cro-best-practices) matrix. The short rule here: ship what evidence already settles and test only what your sessions can detect.

If your ad traffic lands on a product or collection page, the [landing page optimization](https://missiongrowth.io/blog/landing-page-optimization) piece covers message match.

Speed needs one correction. Akamai's April 2017 report found that a 100-millisecond delay in load time can hurt conversion rates by 7 percent. Google's AI Overview for this query quotes a one-second delay with the same 7 percent and names no study. Neither figure was measured on Shopify stores, so treat 7 percent as a reason to care and not as a forecast for your theme.

One more date check. Interaction to Next Paint replaced First Input Delay as a Core Web Vital, so any speed audit still built around First Input Delay is out of date, and our guide to [Core Web Vitals](https://missiongrowth.io/blog/core-web-vitals) covers the current fixes.

## How Shopify Rollouts experiments assign and count visitors

A Shopify Rollouts Experiment splits eligible visitors between a control and a treatment by an essential cookie, counts only visitors who consent, and counts a session when the change could apply rather than when a visitor saw it.

A rollout is a scheduled set of changes to your main theme, checkout and accounts pages, discounts or product catalogs. An Experiment compares a treatment against a control before a full Launch. By default a new one uses a 50/50 split and an end date 90 days after it starts, and you can change both.

Each mechanic has a consequence for how you read the result:

- **Cookie assignment:** the group is saved in an essential cookie, so a visitor stays in the same group until the cookie expires or is cleared. A new browser or device gets a new group, which means one shopper on a phone and a laptop can land in both. Your theme and apps can't read a visitor's group either.
- **Consent counting:** visitors get a group even if they don't consent to tracking, but only visitors who consent are counted in results. Your numbers come from a consenting subset.
- **Session counting:** a session counts when the changes could apply. Treatment sessions can therefore include customers who never received the change, which dilutes any real effect.
- **No segments:** you can't filter results by device or country, so a change that helps one market or screen can hide inside the average.
- **Discount leakage:** eligible visitors can share a discount code, so a code in an Experiment can reach visitors outside the group you're testing.

Put together, read a Shopify result as a comparison of everyone the change could apply to, which differs from a comparison of everyone who saw it. That reading is diluted by sessions that never saw the change, blind to device, and open to code sharing. So size the test before launch, keep each test to one change, and keep discount codes out of it.

The native Experiment fits a theme or checkout configuration change. Reach for an app when you need the device or country filters the native tool lacks; our look at [conversion rate optimization tools](https://missiongrowth.io/blog/conversion-rate-optimization-tools) compares the app-based platforms.

## How many sessions a 90-day Shopify experiment needs

A Shopify Experiment on a store at the Shopify median conversion rate of 1.3 percent needs about 83,400 sessions per month to detect a 10 percent lift inside its default 90-day window, and about 38,100 at the 2.8 percent that starts the top fifth of Shopify stores.

Both baselines come from Littledata's November 2026 panel of 450 Shopify stores, which includes only stores with at least 90 purchases in 90 days, so smaller stores sit outside it. The grid applies the standard two-proportion sample-size formula, covered in our [minimum detectable effect](https://missiongrowth.io/blog/minimum-detectable-effect) guide, at 5 percent significance and 80 percent power. It uses Shopify's 90-day, 50/50 default. No store was tested for this.

Here is the derivation. Detecting a 10 percent relative lift at 2.8 percent takes about 114,300 sessions across both groups, and at 1.3 percent about 250,100. Divide by the 3 months in the window and you get the monthly figures. For a 20 percent lift the totals are about 29,900 and 65,500.

| Baseline conversion rate | Sessions per month for a 10% lift | Sessions per month for a 20% lift |
|---|---|---|
| 1.3% (Shopify median) | about 83,400 | about 21,800 |
| 2.8% (top 20% start) | about 38,100 | about 10,000 |

A 20 percent lift at the top-fifth baseline needs about 10,000 sessions a month, and at the median about 21,800. The grid assumes every session is independent and ignores the consent filter, so the real need is higher, never lower.

Turn it around and ask what your traffic can detect:

::figure{src="/blog/figures/shopify-cro-2.svg" alt="Grouped bars of the smallest relative lift a 90-day Shopify Experiment detects at 10,000, 30,000 and 100,000 monthly sessions, for 2.8 and 1.3 percent baselines." caption="At 10,000 monthly sessions a 90-day Experiment can only detect a 20.0 to 30.2 percent lift; at 100,000 it reaches 6.1 to 9.1 percent." width="720" height="288"}

At 10,000 monthly sessions the smallest detectable lift is about 20.0 percent at the 2.8 percent baseline and about 30.2 percent at 1.3. At 30,000 it is about 11.3 and 16.9 percent. At 100,000 it falls to about 6.1 and 9.1 percent.

So a store between 10,000 and 30,000 monthly sessions can only detect lifts between 11.3 and 30.2 percent in 90 days. Read that as a design constraint: it tells you how large a change has to be before a test can see it. Peeking early doesn't change the arithmetic, and the stopping rules are in our [sequential testing](https://missiongrowth.io/blog/sequential-testing) guide.

## A Shopify CRO order of work by monthly sessions

Below about 10,000 monthly sessions, fix known problems and measure before and after; from about 30,000, test only changes large enough to clear the detectable lift; above about 100,000, small tests become possible.

This is conversion rate optimization for ecommerce cut down to what a Shopify store can act on. It is CRO optimization Shopify merchants can check against their own analytics, so priorities stop being an argument. Find your monthly sessions, then read your row:

::dataset{key="monthly-sessions-order-of-work" name="Shopify CRO order of work by monthly sessions"}
| Monthly sessions | Smallest lift a 90-day Experiment detects | What to do |
|---|---|---|
| Under 10,000 | Above 20.0 percent (2.8% baseline) or 30.2 percent (1.3%) | Fix known problems, measure before and after |
| 10,000 to 30,000 | 11.3 to 30.2 percent | Ship the basics, test only a major change |
| 30,000 to 100,000 | 6.1 to 16.9 percent | Test one large change at a time |
| Above 100,000 | 6.1 percent or less at 2.8%, 9.1 percent or less at 1.3% | Small tests become possible |

Use it as an ecommerce CRO checklist in this order:

1. **Settle the checkout fields and wallets.** Set the five Customer information fields your plan allows and decide on the sign-in requirement.
2. **Ship the basics.** Speed, mobile, reviews, product pages and the offer, judged before and after on the rate each one moves.
3. **Pick the metric first.** Add to cart or reached checkout rate for a theme change, checkout conversion rate for checkout, revenue per session for an offer.
4. **Check the traffic.** If your sessions can't detect the lift you hope for, ship the change and read it before and after.
5. **Test one large change per quarter.** The default window is 90 days, so a quarter holds one clean test.

Which funnel stage to work on first is a separate call, and our [conversion funnel optimization](https://missiongrowth.io/blog/conversion-funnel-optimization) guide handles it. Worked examples sit in the [conversion rate optimization case studies](https://missiongrowth.io/blog/cro-case-studies).

Back to the thesis: on Shopify, CRO is an order of work set by what your plan lets you change and what your traffic lets you prove. This week, open your checkout settings and see which Customer information fields you've set to Required, then pull your last 90 days of online store sessions and find your row in the table.

## FAQ

### What is CRO in Shopify?

CRO in Shopify is the process of raising the share of online store sessions that end in an order, measured as the conversion rate in Shopify's admin. It works through checkout settings, store basics and tests sized to your traffic. Our conversion rate optimization case studies show what that looks like on real stores.

### Can I A/B test my Shopify checkout without Shopify Plus?

Yes, in principle. An Experiment can compare two checkout and accounts configurations and needs the Grow plan or higher. A checkout test can only vary what your plan's checkout editor and settings allow, which is the five Customer information fields and the sign-in and contact method options.

### What does a Shopify CRO expert do, and do I need one?

A Shopify CRO expert finds what stops sessions from ordering and designs the changes and tests to fix it. Whether you need a [CRO consultant](https://missiongrowth.io/blog/cro-consultant) depends on your traffic, and a good brief names your plan, the metric to move and your sessions per month, using the bands above.

### Is CRO part of SEO on Shopify?

CRO and SEO work on the same pages but answer different questions. SEO brings sessions to the store, and CRO changes what share of those sessions place an order. Fix both in sequence: [Shopify SEO](https://missiongrowth.io/blog/shopify-seo) growth gives a test more sessions to work with.

### How long does CRO take to show results on Shopify?

A basic fix can be read before and after as soon as enough sessions have passed. An Experiment runs to its default 90-day end date, and at the Shopify median conversion rate of 1.3 percent a 10 percent lift needs about 83,400 sessions a month to finish inside it. Smaller lifts need more.

### Can a small Shopify store benefit from CRO?

Yes, by shipping evidence-backed basics rather than testing. At 10,000 monthly sessions a 90-day Experiment only detects lifts of 20.0 to 30.2 percent, depending on baseline, so small stores gain more from fixing known checkout and product page problems and reading the rates before and after.