Type shopify.com/magic into a browser today and you land on the Sidekick page. As of 2026-07-26, the old Magic product URL redirects to shopify.com/sidekick. That redirect is the first useful fact in this comparison, because it shows how Shopify now frames the two names. The second useful fact: Magic is not discontinued. Shopify still documents Shopify Magic features and still uses the name on feature surfaces. What changed is the packaging: one assistant at the front door, the generation features behind it.
The short answer
Shopify Magic is the generation layer. Shopify's documentation presents it as a family of AI features embedded across the platform rather than an assistant you talk to: product and marketing text generation and rewriting, Shopify Email copy and subject-line suggestions, Shopify Inbox suggested replies, and product-media work like background removal, replacement, and generated scenes.
Sidekick is the store-aware assistant. Shopify's Sidekick page calls it an "AI Shopify expert" with direct access to store data, an understanding of commerce workflows, and the ability to take action in the admin. It requires no separate purchase. Shopify's exact FAQ wording: "No. Sidekick is included with your Shopify plan. Features and usage limits vary by plan."
So the decision is not "which AI is better." It is which job you are delegating. Blank page or product photo: Magic. A job that starts from store data or ends in an admin change: Sidekick. Either way, the merchant still defines the goal, supplies source facts, approves customer-visible or financial changes, and verifies results. Neither product replaces operations staff.
Compare by five dimensions, not a feature checklist
Feature lists go stale within a quarter. These five dimensions hold up better:
- Context: Magic works on the content field in front of it. Sidekick reads store data, within the staff member's permissions.
- Output: Magic produces drafts and generated media. Sidekick produces answers, analysis, configured objects, and supported actions.
- Permission and approval: both operate inside your admin session and staff rights; writes wait for confirmation.
- Verification: drafts get read, media gets compared against the physical product, actions get confirmed and checked.
- Reach: Magic lives on native Shopify surfaces. Sidekick works in the admin, in the Shopify mobile app, and, since Spring '26, in a selected set of partner apps.
| Shopify Magic | Shopify Sidekick | Your part | |
|---|---|---|---|
| What it is | Generation features embedded in Shopify surfaces | Store-aware assistant in the admin | Decide which job to delegate |
| Typical output | Text drafts, email copy, inbox replies, edited media | Answers, analysis, configured objects, supported actions | Review before anything goes live |
| Data context | The content field in front of it | Store data, within your staff permissions | Supply the facts AI cannot know |
| Reach | Native Shopify surfaces | Admin, mobile app, selected partner apps | Everything outside that reach |
What Spring '26 changed
Per Shopify's Spring '26 Editions page, Sidekick now works with partner apps (starting with Judge.me, Klaviyo, Loop, Smile, and others), opens admin sessions with "Actionable guidance from Sidekick" covering acquisition, conversion, and repeat sales, asks multiple-choice clarifying questions, keeps working in the background across chats and closed windows, runs across the Shopify mobile app by typing or voice, creates customer records from plain-language descriptions, generates test events for Shopify Flow automations, and gains a generated-app editor with code editing, previews, and version history.
The operational consequence matters more than the feature count. Sidekick is moving from answering questions toward taking action, background work, app reach, and lightweight software creation. Every one of those moves increases what a wrong or premature action can touch. Permissions, confirmation, testing, and post-action verification matter more after this release, not less.
Six scenarios, and who does what
A product description. Magic's home ground: first drafts and tone variants in the product editor. Thin product facts produce fluent, generic copy. No generation feature recovers missing specs, verified claims, or brand policy. You supply substance and edit for truth.
A product photo background. Magic can remove or replace backgrounds and generate scenes. Treat output as a candidate: compare edges, proportions, textures, labels, shadows, and reflections against the physical product.
"What was my best product last month?" A Sidekick question with a trap inside. "Best" can mean gross sales, net sales, units, margin, conversion, repeat purchase, a channel, or a time window. Sidekick queries store data; you own the definition. For high-stakes reporting, deterministic reports and exports remain the safer path.
Creating a discount or a customer record. Sidekick can do both. Discounts touch money and are customer-visible: review the exact configuration before confirming, then check the storefront after.
Testing a Flow automation. Sidekick can generate test events to verify workflow logic before it touches real orders. An untested automation is an assumption, and a failed trigger is silent until someone looks.
Acting in a third-party app. Spring '26 names an initial partner set, which proves selective expansion, not universal compatibility. Confirm your specific app and action are supported before designing a process around them.
Permissions, approval, and what still requires a merchant
Sidekick inherits staff permissions. Shopify's exact FAQ wording: "Every staff member can use Sidekick based on their admin permissions. It respects access controls, so team members only interact with data and features they're authorized to use." Your permission hygiene now doubles as AI risk management.
Approval requirements protect the merchant and define the product's ceiling: a tool that waits for confirmation before a write is not unattended store operations. Five things stay human regardless: defining success (including metric definitions), supplying reliable source facts, approving customer-visible or financial changes, verifying outcomes after actions, and owning the systems Sidekick cannot reach, which still includes most external and legacy tooling.
Methodology and limitations
Research cutoff was 2026-07-26. I directly verified the /magic to /sidekick redirect and fetched the current Sidekick product page and Spring '26 Editions page. Capability examples cited are Shopify's own, labeled as such, not independent validation. No hands-on testing was performed for this article, and no claims are made about sales lift or output accuracy, because no broad independent dataset exists for the current Spring '26 Sidekick. Shopify's Help Center blocked automated fetching (HTTP 403), so Magic feature categories come from stable documented categories rather than a fresh fetch. Partner app support is selective and evolving.
The longer version of this analysis, with a FAQ and per-audience recommendations, lives on the ClawMama blog.
Top comments (0)