Shopify Canvas: Review Sidekick Theme Changes on Tracing Paper First

This article teaches the tracing paper walk: choose the editor, list missing app blocks and Markets gaps, preview on an unpublished theme, and name who can lift the sheet off before anyone publishes. How Sidekick learns from admin GraphQL traffic belongs in Shopify Sidekick's Continual Learning Flywheel: What Merchants Should Know.

Whether the current theme has already left the supportable Online Store 2.0 path belongs in Shopify Theme Customisation Limits: When Your Store Leaves the Supportable Path. This piece stays on the 1 October launch. Canvas is a new workspace next to the editor, and the review has to happen before Sidekick writes production section JSON.

Merchant and developer threads this week keep returning to the same launch facts Shopify staff posted. Canvas can describe a page and build it, while theme app extensions, Markets, translations, and Rollouts are still missing. The community signal is a missing review owner, so treat the prompt as the easy part of the job.

Illustrators sketch changes on a sheet of tracing paper laid over the finished drawing. If the new line is wrong, they lift the sheet away and the original is untouched.

I call this the tracing paper rule. Every Canvas or Sidekick edit happens on a sheet you can lift off, which means an unpublished theme copy, and it only gets pressed into the live drawing once someone has checked what the sheet hides.

The rule matters because of what Canvas is. Shopify introduced it on 1 October 2026 as a visual workspace that lays out every page of a store in one place. A merchant can click into a section and edit it, or describe the layout and have Sidekick assemble the page, and Shopify said the workspace launches alongside the online store editor and would roll out over the following days.

Canvas sits on the same Online Store 2.0 model of JSON templates, sections, and merchant-editable settings that Online Store 2.0: What Changed and Why It Matters already covered. The new risk is speed. A prompt can restack a homepage faster than a developer can map which section file now owns the hero, and faster than an app can find the theme in the Admin API.

The same staff posts listed what Canvas cannot do at launch. Theme app extensions are unsupported, so a theme created or duplicated in Canvas will not show app blocks or embeds. Themes edited in Canvas also do not appear when an app lists the store's themes.

Rollouts, Markets, and translations are out of scope for now as well. Shopify framed those gaps as early-product limits and said it expects theme app extension support within a few weeks, before Canvas becomes the default editor.

The Theme Store post added one more boundary, because Canvas does not yet have full backwards compatibility with third-party themes. Until that lands, a premium theme your agency already forked remains an editor-and-code surface, even with Canvas visible in admin.

Shopify also told developers that existing themes keep working in the online store editor and that apps can stay on their current code for day one. You still have two editors and one published theme, so keep selling on the current theme while Canvas is early.

Review a Canvas change before it goes live

Write the change in one sentence before anyone opens Sidekick, whether that is a new homepage stack, a collection banner, a product-page trust row, or a whole theme duplicate. Then pick the surface that can still see the apps and markets that change depends on.

Use the online store editor when the page already mounts theme app extensions, when the copy must follow a Markets catalogue, or when the file lives on a GitHub branch your team deploys. Use Canvas when you want a visual map of every page, or a Sidekick layout proposal you will later rebuild as named sections.

Keep each change in one surface on the live theme, because running it in both within the same hour loses the trail of which tool wrote the JSON.

If the sentence reads "make the homepage feel more premium" with no section list, stay in the editor or write the section list first. Canvas will happily invent modules, and after the prompt finishes you should still be able to point at the sections, assets, and settings it touched. The Anatomy of a High-Performance Shopify Theme is the map you should still be able to read after Sidekick leaves the chat.

Sidekick is louder in admin than it was a year ago, and some teams are already hunting for a way to shrink its chrome so the rest of admin fits on a small laptop. That is an admin preference, and the storefront decision still belongs on the page you are about to publish.

Established DTC brands feel this first when marketing already uses Sidekick in admin and now sees a storefront workspace that can write pages. App-heavy catalogues stay on the editor until Shopify ships theme app extension support. Multi-market brands keep Markets and translation checks outside Canvas. Agency-owned GitHub themes need a human commit after any prompt, because Canvas-edited themes may never appear in the app listing your partner uses to inspect files.

Open the unpublished theme and list every storefront app the live page shows today: reviews, loyalty, subscriptions, size guides, scripts, and any block a merchant added from the theme editor. Walk the same page in Canvas or on the Canvas-created duplicate and mark each block present, missing, or unknown.

Reviews, analytics tags, and other embeds look "part of the theme" to a merchandiser, yet they are app-owned. They drop off the page without a Liquid error.

Do the same pass for Markets, translations, and Rollouts, because a UK default homepage can look finished while the German market still serves the previous hero, the wrong currency presentation, or a missing language string. Add a Canvas column to the market sheet you already keep for peak traffic in Shopify Markets Black Friday Traps: Duties, Currency, and Catalog Gaps.

Write the gaps in the same note as the editor choice. "Homepage restack, Canvas, reviews missing, EU market not previewed" is enough for a second pair of eyes, whereas "looks good" records nothing anyone can check.

Duplicate the live theme, or create the Canvas experiment as an unpublished copy, before Sidekick writes anything you cannot discard. Shopify's own theme-customisation guidance still starts with a backup copy, and Canvas makes that step easy to skip because the workspace feels like a sketch while publish stays one click away.

Preview on a phone and a desktop. Confirm price, variant picker, and add-to-cart still sit where the live PDP puts them, and that the header and footer still come from the section groups your theme already uses. A second announcement bar or a new header row is an early sign of duplicate chrome.

If the store connects the theme to GitHub, fetch the branch after the save and confirm the files you expected actually landed. Theme-editor asset uploads have recently failed to commit while new snippets succeeded, and Shopify staff treated that as a defect.

A Canvas save that never appears in git log belongs to the same class of problem, because admin looks updated while the rollback copy your developers trust is stale. Keep the unpublished theme itself as the revert target until the commit exists.

Publish once the unpublished theme has passed the app-block list, the Markets list, and a second person who was outside the Sidekick chat, however close the laptop preview looks to the campaign Figma.

Write one name next to the unpublished theme: the person who can publish the previous copy, revert the GitHub commit, and tell paid media to pause if the live page loses reviews or a market hero. A workspace that generates a page in a minute can leave three teams each assuming someone else can undo it.

That owner needs access to Online Store, Themes, and the GitHub repo if you use one. They also need the name of the last known-good unpublished copy, written down instead of remembered as "the version from Tuesday."

If your apps cannot see Canvas-edited themes, the owner needs a browser session on the theme editor too, since the partner dashboard may not list the file they have to restore.

Put a time box on the first live week. Shopify said Canvas would evolve daily and that app support would follow in weeks rather than as a same-day toggle.

A homepage experiment you publish on 6 October may need a different review by 20 October, once theme app extensions land. Keep the rollback name in the note you update whenever Shopify documents those surfaces.

If nobody on staff can read section JSON or restore a theme, stop at the unpublished preview. Prompt-led layout is still theme architecture, and the hire path for this job is Shopify theme development, because the artifact is a storefront your marketing team can keep editing after Sidekick leaves the chat.

Canvas leaves the online store editor in place, and a store that never opens Canvas still sells. If the live theme already mixes leftover static header tags, Custom CSS dumps, and undocumented Liquid, Sidekick will write into that mess, so recover the section groups first and let Canvas propose layouts on a clean duplicate.

This review covers only the storefront files Sidekick can now reach through a visual workspace. Admin AI, connector permissions, and checkout Functions are separate jobs, and buying a new premium theme to "be ready for Canvas" is a later architecture project for after launch week.

Shopify said the Theme Store remains a destination for a polished starting theme while it rethinks that role. A storefront that already sells on a forked premium theme should stay on the editor-and-code path until backwards compatibility is documented.

You can now walk a Shopify Canvas or Sidekick storefront edit through a written editor choice, a list of missing app blocks and Markets surfaces, an unpublished-theme preview, and a named person who can lift the sheet off. That is the whole launch-week job. The prompt is the easy part.

When the unpublished copy already drifts from the section groups your team can name, or when Canvas hides the apps your product pages depend on, Shopify theme development puts an owner back on the files. Book a discovery call if you want that review before marketing treats Canvas as the default editor.