Creating a Price Test
After your theme has been configured with data attributes, you're ready to create your first price test.
Step 1: Create a test
Log into Shoplift
Click Create Test to create a new test draft
Select Price Test from the test type options
Confirm you've read both Overview and Theme Setup documentation
Step 2: Select products
After selecting Price Test, a product drawer opens and displays your entire product catalog.
Finding your products
You can quickly search for the specific products by entering:
Product names
Product IDs
Product handles
Adding products to your test
As you browse through the product drawer, click on any product to select it for testing. Selected products appear in the confirmation panel on the right side of your screen, giving you a clear view of what you've chosen.
Review and confirm
Once you've made your selections:
Review all chosen products in the right panel
Click Confirm to add these products to your test
The drawer will close and your selections will populate the main test configuration table
Managing product selections
If you need to adjust your product selection at any point:
Click Manage Products to reopen the selection drawer
Your previous selections remain intact
Add forgotten items or remove reconsidered products
Products and their prices are only loaded upon opening the product drawer. After the drawer closes, we maintain the selected products and prices throughout test setup and launch. Therefore, if you add/delete products or change product prices, you will need to re-select products via the product drawer.
Step 3: Configure test prices
With your products selected, your test draft now displays a table with all chosen products and variants. This is where you'll define the price changes for your experiment.
Setting your test prices
For each product or variant in the table, you can configure two price points:
Price: The actual price your test group visitors will see and pay. This is the core of your experiment and should reflect your hypothesis about optimal pricing.
Compare-at Price (optional): An optional strikethrough price indicating the "original" or "regular" price. This can create a sense of value or urgency, though it's not required for every test.
Testing compare-at prices
Compare-at price elements are typically implemented with conditional logic that determines whether the element renders on the page. This logic executes based on the backend Shopify price, not the DOM-manipulated price applied by Shoplift.
This creates two common edge cases:
Scenario 1: Removing a compare at price: If your A side has a compare-at price and your B side sets it to $0 (no compare-at price), the backend will still render the compare-at element. Shoplift will then overlay $0 on top, but the element itself remains visible.
Scenario 2: Adding a compare-at price: If your A side has no compare-at price and your B side adds one, the compare-at element won't render at all when the page loads, and there will be nothing for Shoplift to manipulate.
To work around these issues, consider editing the conditional logic for price tests using our exposed test configs.
Step 4: Configure test details
With products and prices set, it's time to define the broader parameters of your test. These settings control how your test runs and help you track its performance.
Test name
Choose a descriptive name that clearly identifies your test's purpose. Good test names help you quickly understand what you tested when reviewing results months later:
"Premium Collection 15% Increase"
"Bestsellers Price Optimization Q1"
"Free Shipping Threshold Test - February"
Document your hypothesis
Recording your hypothesis serves multiple purposes:
Aligns your team on what you're testing and why
Provides context when analyzing results
Builds institutional knowledge for future tests
A strong hypothesis includes your expected outcome and the reasoning behind it.
Traffic allocation
Decide what percentage of visitors will see each variant:
50/50 split: Provides the fastest path to statistical significance
80/20 split: More conservative, limits exposure to price changes
Custom splits: Tailor to your specific risk tolerance
Consider your risk tolerance and the magnitude of price changes when setting these percentages.
Step 5: Review and finalize
Before moving forward, conduct a final review of your test configuration. This final check ensures everything is properly configured before you proceed to testing.
Verify that:
All selected products have at least one price change
Test name clearly identifies the experiment
Hypothesis is thoroughly documented
What's next
With your test created and configured, you're ready to preview and QA your test to ensure everything is working perfectly before going live:
Preview your test to see exactly how prices will appear to visitors
Run comprehensive QA checks across devices and user journeys
Launch your test with confidence to start collecting data
Last updated
Was this helpful?