Sidekick finds areas to improve, drafts the changes, and compares them against your current storefront using AI-simulated shoppers. It doesn't test with real shoppers. The merchant reviews the recommendation and decides whether to apply it.
Sidekick identifies areas of your storefront that could be improved.
Creates the changes as a draft. Nothing goes live right away.
Compares the draft against your current storefront using AI-simulated shoppers.
Sidekick simulates changes that meet the following 2 conditions.
Applies to improvements that can be expressed as theme changes.
Changes expected to affect add-to-cart are selected.
| Item | Sidekick's AI simulation | Real A/B testing (for reference) |
|---|---|---|
| Who it's tested on | AI AI-simulated shoppers | Real visitors |
| Exposure to the live store | None Not tested on real shoppers | Shown live to a subset of visitors |
| Positioning | Not a live A/B test (stated explicitly) | Live A/B test |
| Creating proposed changes | Automatic Sidekick creates the drafts | Prepare it yourself |
| Decision to apply | The merchant decides after reviewing | Review the results and decide yourself |
| Additional cost | Not specified | — |
Provided as a Sidekick feature.
Not specified.
You get improvement ideas compared against your current setup through AI simulation.
Review the draft's contents yourself.
Apply it once you're satisfied. Nothing goes live automatically.
Simulations are limited to changes that can be tested as storefront theme changes. Whether changes outside the theme (apps, checkout, etc.) are covered isn't specified.
Changes are chosen based on their expected impact on add-to-cart. Keep in mind this doesn't indicate impact on purchase completion rate or revenue.
The article states clearly that it doesn't test with real shoppers and isn't a live A/B test. Treat the results as an early signal of what might work.
Sidekick creates a draft, which is applied only after the merchant reviews it. How the draft is stored in theme management (e.g., as an unpublished theme) isn't specified.
The article doesn't cover API access, conflicts with Git-connected themes, or behavior with custom themes.For projects that manage themes as code, a process for reviewing the diff before applying a Sidekick-created draftshould be agreed on in advance.