Run your first checkout test
A step by step plan for testing a checkout change without risking revenue.

Why checkout
Checkout is where traffic turns into revenue, so small gains are worth the most and mistakes cost the most. It is also the best place to learn the discipline of guardrails.
Step 1: pick one friction point
Look at your funnel and find the step with the biggest drop. Watch ten replays of users abandoning that step. Write one sentence naming what they struggled with.
Step 2: write the hypothesis
Use this form: because we saw X, we believe changing Y will improve Z for audience A. Keep it to one change. If you change the shipping step and the payment step together, you will not know which one worked.
Step 3: set metrics
- Primary: completed orders per visitor.
- Secondary: average order value, so a win does not come from discounting.
- Guardrails: payment success rate, page load p95, refund requests.
Step 4: size the test
Use the Kerf sample size estimator with your baseline conversion rate and the smallest lift you would act on. For most stores this means two to four weeks, covering at least two full weekly cycles.
Step 5: launch carefully
Ship behind a flag. Start at 5% of eligible traffic for a day while you check the sample ratio and the guardrails. Then raise to the planned split.
Step 6: read it
Wait for the planned end date, unless you are using sequential testing. Check the sample ratio again before looking at the result. Ship, stop or extend, and write down why.
More playbooks

Test your pricing page
How to test plan layout, anchoring and copy on a pricing page without changing what anyone pays.

Improve onboarding activation
A playbook for finding your activation event and running a steady series of onboarding tests.

Run a painted door test
Measure demand for a feature before you build it, using a fake entry point and an honest follow up.