help1
shopify sidekickshopifyshopify aisidekick

Shopify Sidekick: What It Handles, and What We Reach Past It

A task-by-task look at where Shopify Sidekick reliably delivers, where its ceilings bite, and what we reach for when it hits a wall in 2026.

help1 Team
Shopify Sidekick: What It Handles, and What We Reach Past It

Quick answer. Shopify Sidekick is genuinely useful for one-shot Liquid snippets, small admin lookups, and narrow admin apps on the plans that still allow them. For bulk catalog work, real-time reporting, multi-step automation, or anything that runs longer than a few messages, we default to external AI or the native admin and treat Sidekick as a search box.

Two numbers keep coming up in the r/shopify threads we watch. One is 500, the rough cap on how many records of any type Sidekick will load in one query. The other is three to four, the number of back-and-forth messages we've seen before context begins to slip. Those two ceilings do most of the work of deciding whether we reach for Sidekick or something else, and the shape of the answer has been stable across the February through July 2026 threads.

This is a scorecard, not a manifesto. Sidekick is not a toy in the ways some threads say. But it is not the "AI that runs your store" that the launch messaging suggested either. Below is what we've settled into for a real workday.

The scorecard, up front

The table lists the six tasks we throw at any AI tool inside a Shopify workflow, what happens when we ask Shopify Sidekick to do them, and what we reach for instead when Sidekick stalls. "External AI" means Claude or ChatGPT run outside the admin, with product exports pasted in as context.

TaskSidekick verdictWhat we reach past to
Bulk catalog audit or SEO cleanup at >500 recordsSilently truncatesExport CSV, then Claude or ChatGPT
One-shot Liquid or JavaScript snippetFast, usually rightSidekick, verified in a preview theme
Real-time report retrieval (abandoned checkouts, orders in the last N hours)Inconsistent since mid-July 2026Native Analytics, or the Orders search
Multi-step admin automation across 5+ messagesContext slips, session slowsShopify Flow, or write the workflow yourself
Narrow custom admin app (report joiner, metafield migrator)Excellent on Grow, Advanced, PlusSidekick if you're on those plans
Third-party app recommendationBiased toward paid apps, misses nativer/shopify, help1 chat, or a colleague

The rest of the piece walks each row and explains what backs it.

Bulk catalog work and SEO cleanup

If you have more than roughly 500 products, or you want to audit metafields across a full catalog, Sidekick will finish the task and hand you back a partial result. It does not surface a warning at the start of the query that the record cap will bite. You only notice when the count in the answer looks wrong.

Two documented failure modes matter here. First, one merchant asked Sidekick to review their catalog for SEO gaps and later found the tool had invented alphanumeric product codes that did not exist in their store. They spent time reviewing more than 80 products by hand to undo the damage. When they escalated to Shopify support, the response they got back was that there is "no setting to prevent the AI from hallucinating data or ignoring negative SEO constraints" and that Sidekick "works for prose not exact data." That is not a bug you can configure your way out of.

Second, a UK jewelry merchant used Sidekick to recommend collection filters and got 14 suggestions back. When they cross-checked search demand, 13 of the 14 had zero UK volume. Worse, the store used "9K gold" in product titles; UK customers search "9ct gold," so the store was invisible for its own core term. Sidekick can see what is in your catalog. It has no visibility into what your customers type.

Our default now is to export the products to CSV and hand the file to Claude or ChatGPT with a prompt that names what we want back: banned keywords, character limits, spelling variants, whatever the constraint is. External AI has a bigger context window than Sidekick's session and no Shopify-side record cap to trip. For anything at scale, that difference is decisive.

One-shot Liquid and JavaScript snippets

This is where Shopify Sidekick actually earns its keep. Asking Sidekick "write a Liquid snippet that shows a trust badge when the cart total exceeds fifty dollars" produces fast, usable code more often than not. The framing matters. Merchants on r/shopify have noticed that phrasing the ask as an action ("do this: ...") beats phrasing it as a question ("how do I ...?"), which tends to return a rewritten help article.

The important caveat is verification. One long-time community poster called out that "AI is for drafts summarization etc that THEN is 100% incumbent upon you to put in the actual effort and verify what such tools randomly generate." We have watched enough Sidekick-generated code fail on edge cases to agree. The pattern we settled on: never paste Sidekick's Liquid into a live theme without duplicating the theme first, running the change on the duplicate, and checking mobile in DevTools. That takes a few minutes and catches most regressions before they touch a customer.

Where we still reach past Sidekick on code: anything that spans more than one file, anything that touches app blocks or the section schema in a non-trivial way, and anything you need to iterate on for more than three or four rounds. Sidekick's context starts thinning fast around the fourth exchange; the browser can freeze on a maxed-out laptop after several prompts in a heavy session. External AI handles the longer session more gracefully.

Real-time reports and store ops

Through the spring, Sidekick was decent at pulling one-off reports. Ask for the last four hours of abandoned checkouts, get a summary. That is what one merchant reported having done "at least 100 times" before mid-July 2026, when Sidekick started answering the same request with a version of "I'm sorry, I don't have access to that info." The community thread documenting the change had zero comments when we first read it and 17 by early August. Something changed. No public changelog, no staff reply.

We do not know whether the abandoned-checkout regression is a plan gate, a permission scope tweak, or a temporary bug. We admit that openly. What we do know is that we can no longer count on Sidekick for time-boxed report queries in the way we could two months ago. For anything time-sensitive we go straight to the native Analytics section or the Orders search, both of which are unchanged and cost nothing.

There is a second real-time gap worth naming. Sidekick has no awareness of Shopify's own status page. If Shopify is having an incident, Sidekick will happily try to diagnose the resulting data discrepancy as a configuration problem. One merchant spent time troubleshooting a nineteen-versus-seventy-six order-count mismatch before discovering the platform was in an incident. When Sidekick's numbers do not match what you see in the admin, our reflex is to open shopifystatus.com in another tab before assuming a config error.

If you find yourself in that spot and cannot tell whether it's an outage, a plan change, or something you did last week, the first 15 minutes with a help1 expert is free and that is usually enough to name what changed and what to do next.

Multi-step automation across a longer session

Anything that requires Sidekick to hold state across more than a few messages runs into predictable trouble. The complaint we hear most is that Sidekick "forgets context after 3 messages." Merchants working on iterative catalog edits, chained flow logic, or multi-part SEO rewrites report the tool losing the thread mid-session, forcing them to re-explain the task and re-confirm decisions from scratch. Long sessions also compound performance issues: response times stretch from seconds to minutes, the browser can crash, and starting a new session means re-training Sidekick on the same context all over again.

For automation that has real branching (customer segment enters state A, wait for order, tag if condition, notify if not), Shopify Flow is still the answer. Flow gives you a visible graph and durable state; it does not forget your last message. For anything more ambitious than Flow, we write the workflow ourselves in a small Node script or an admin app and treat Sidekick as an occasional autocomplete rather than the runtime.

One workaround that surfaces in the threads: batching. A merchant who needed to query 3,000 gift card codes broke the job into groups of 100 and processed them manually. That works, and it also tells you something about the shape of the tool. If you are batching in groups of 100 to work around a 500 cap, you're managing Sidekick rather than being helped by it.

Custom admin apps for narrow jobs

This is the strongest practical Shopify Sidekick capability we have documented. Sidekick can generate small admin apps that fill specific reporting gaps: a production list that pulls unfulfilled orders through a print-and-pack workflow, a report that combines tax and sales data the native reporting refuses to join, or a metafield migrator. One merchant successfully used Sidekick to migrate 950 product descriptions into a metafield, a job that would otherwise have required a paid app or a developer.

The important asterisk: as of end of April 2026, generated app creation is no longer available on Basic plans. It remains on Grow, Advanced, and Shopify Plus. If you are on Basic and you were counting on Sidekick's app generation as a way to avoid installing a paid tool, that door has closed. That change also drives the "endgame is a paywall" concern that keeps surfacing in the community threads.

Generated apps are also scoped to the Shopify Admin API. They cannot host external databases or call arbitrary third-party services. For anything more than admin-scope work, we build the app in the ordinary way and treat Sidekick as an assistant on individual functions rather than the whole app.

Where the app recommendations come from

We saved this row for last because it changes how you should read every "have you tried this app" suggestion Sidekick offers you. In a well-documented case, a merchant asked Sidekick if they should use FlowMail (a paid third-party email app) for transactional emails. Sidekick said no. Three days later, in a related conversation about email timing, Sidekick came back to suggesting FlowMail. Native Shopify email handles that use case out of the box.

We are not accusing Shopify of a design decision here. The community reads it two ways: either Sidekick's training data underweights Shopify's own native tools, or the recommendation surface is biased by the app marketplace. Either way, the practical result is that when Sidekick fails a task and suggests an app to fix it, the recommendation is not vetted. Before installing anything based on a Sidekick suggestion, we do three cheap checks:

  1. Is there a Shopify-native feature on your plan that handles this? The plan features list is the fastest place to look.
  2. Search r/shopify for the app name and "issues" or "problems." Ten minutes of reading tells you what you are signing up for.
  3. If the task looks like it needs custom code rather than an app, run a well-structured prompt through Claude or ChatGPT with the exported context. We covered this pattern for AI-generated storefronts in where Shopify AI storefronts break, and the same principle applies to admin work.

What we would actually pick in 2026

Our stack, honestly:

  1. Shopify Sidekick for admin navigation ("where did the shipping profile move to"), for single-file Liquid snippets, and for narrow admin apps on plans where that is still available.
  2. Claude or ChatGPT, run outside Shopify with pasted CSV context, for anything at catalog scale, anything with strict output constraints, and anything requiring more than a few conversational turns.
  3. Native Shopify Analytics and Flow for real-time reporting and durable automation.
  4. A paid app only after checking the two lines above, and only after reading the community on it.

The one place we are least certain: whether the July 2026 report-access changes are permanent, a plan-gate rollout, or a temporary regression. We have not seen a Shopify staff reply on any of the affected threads. If your ops depends on Sidekick pulling live reports, we would build the same workflow off the native Analytics section in parallel now, so you are not the merchant scrambling in September.

Try this today

Pick the two tasks you delegated to Shopify Sidekick most often over the last month. Write them down. For each one, note which row of the scorecard above it lives in, and whether the tool we reach past to (native admin, external AI, or Flow) is one you already have set up. If it isn't, spend fifteen minutes wiring it up before you need it. That is the single change that shifts you from "Sidekick failed, now I'm stuck" to "Sidekick failed, I have somewhere else to go." If you'd rather have a second pair of eyes on that shortlist before you commit to changes, our expert chat is exactly the seat for it.

Still stuck? Talk to an expert.

Our vetted Shopify experts can fix this issue for you in a live session. $39 per session. Your first 15 minutes are free.