> For the complete documentation index, see [llms.txt](https://docs.elevateab.com/elevate-helpcenter/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elevateab.com/elevate-helpcenter/price-testing/preview-and-qa-a-price-experiment.md). # Preview and QA a Price Experiment A pass or fail checklist for verifying a price experiment in Elevate A/B Testing before it goes live, and what to do when a check fails. *** Price experiments change what customers are charged. A layout bug is embarrassing; a pricing bug costs money and trust. Work through every check below before you submit. ### How to preview Use the **Preview** button next to any product while setting prices, or at step 7. In the preview dialog: * **Select Variation to Preview** chooses which version you see. Every variation is available, including the control. * **Select Market to Preview** chooses the market, if you sell in more than one. * **Preview** opens it on desktop. * The **QR code** opens the same variation on your phone. Check every variation, on desktop and mobile, in every market you are pricing for. **Preview in an incognito window.** The preview pins you to the chosen variation for a year. Without incognito you will keep seeing that variation as you browse your own store. ### Core checks | Check | What you should see | If it fails | | ---------------------------- | ------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- | | Control is unchanged | Exactly your current live price | Confirm you have not edited the control column. Only variation columns are editable. | | Variation prices are correct | The price you entered, to the cent | Return to step 3. If you used Autofill, check the rounding option produced what you expected. | | Every variant is priced | Products with multiple variants show a test price on each, not just the default | Expand the product in step 3 and check each variant row | | No zero or blank | No variation shows zero or an empty price | Re-enter it. A blank field does not fall back to the control. | | Compare at price makes sense | Higher than the selling price | A compare at price below the selling price displays as a negative saving. Correct it in step 3. | | Page is otherwise unchanged | Nothing shifted, broke, or disappeared around the price | See [Troubleshooting Price Experiments](https://claude.ai/chat/troubleshooting.md) | | Mobile is correct | The price displays correctly on a phone | Scan the QR code. Long prices can wrap or overflow in tight layouts. | ### Check every place a price appears Open the variation and confirm the test price shows consistently on: * The product page * Collection and category pages * Search results * Recommendation and related product blocks * The cart * Checkout A visitor who sees one price on a collection page and another on the product page will not buy, and may not come back. ### Confirm the charged price You can add a previewed product to the cart and complete checkout to confirm what a customer is actually charged. **A test order placed from a preview counts in your experiment results.** Cancel or refund it, and remember it when you read the numbers. Keep test orders to a minimum on low traffic experiments, where one order can visibly move a metric. ### If you sell in more than one currency | Check | What you should see | | ----------------------- | ---------------------------------------------------------------------------------------------- | | Each currency is priced | Every currency you selected has a price for every product | | Prices suit each market | Deliberate for that market, not a rounding artefact from a conversion | | Targeting matches | If prices are market specific, your audience targeting restricts the experiment to that market | | Formatting is right | Correct symbol and decimal convention | Use **Select Market to Preview** to check each one rather than assuming one currency proves the rest. ### If you are testing subscription pricing | Check | What you should see | | --------------------------- | ------------------------------------------------------------- | | One time price is right | Matches what you intended | | Subscription price is right | Matches what you intended | | The gap is deliberate | The difference is the discount you meant to offer | | Selector works | Switching between one time and subscription updates the price | Requires Recharge. See [Price Testing with Subscriptions](https://docs.elevateab.com/elevate-helpcenter/price-testing/price-testing-with-subscriptions). ### If you added content or code changes * Content changes appear on the correct variation, and only that variation * Custom code runs without console errors * Tracked click elements are present and clickable * One variation changes the price only, so you can separate price from presentation ### Before you submit * \[ ] Every core check passes * \[ ] The price is consistent everywhere it appears * \[ ] Currency and subscription checks pass, where they apply * \[ ] Goal metric is Revenue per visitor or Profit per visitor, not conversion rate * \[ ] Product Costs are added, if the goal metric is Profit per visitor * \[ ] The hypothesis field records what you expect * \[ ] Traffic allocation is what you intended * \[ ] Audience targeting is what you intended, and no narrower * \[ ] No sale is planned during the run that would change catalogue prices ### What review covers, and what it does not Elevate's technical support team reviews your first price experiment and confirms prices update consistently across your store. If something is inconsistent, they correct it. Review does not check that your prices are the right prices. Nobody but you knows whether 49.99 is a sensible test against 54.99, whether your compare at price is defensible, or whether you selected the products you meant to select. Do the checks above regardless.