Marketing opens Shopify Canvas, asks Sidekick to restack the homepage for a drop, and the unpublished preview looks tidy on a laptop. The live theme still carries review stars, a Markets hero for the EU catalogue, and a GitHub branch that last synced a snippet, not the asset Sidekick just wrote.
That session is the job: walk the edit through editor choice, the launch gaps Shopify named on 1 October 2026, an unpublished-theme preview, and a person who can revert before anyone presses publish.
Introduction
This article teaches you to walk a Shopify Canvas or Sidekick storefront edit through editor choice, missing app-block and Markets checks, unpublished-theme preview, and a named rollback owner before it ships live. 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, and theme app extensions, Markets, translations, and Rollouts are still missing. The community signal is a missing review owner, not a missing design prompt.
What changed
On 1 October 2026 Shopify introduced Canvas, 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. Shopify said Canvas launches alongside the online store editor and would roll out over the following days.
The same staff posts listed what Canvas cannot do at launch. Theme app extensions are unsupported. A theme created or duplicated in Canvas will not show app blocks or embeds. Themes edited in Canvas do not appear when an app lists the store's themes. Rollouts, Markets, and translations are also out of scope for now. 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 a second boundary: Canvas does not yet have full backwards compatibility with third-party themes. Shopify said the Theme Store still matters for merchants who want a polished starting theme, and that theme developers will have a role in the later state. Until that compatibility lands, a premium theme your agency already forked is still an editor-and-code surface, even if Canvas is visible in admin.
Canvas sits on top of the same Online Store 2.0 idea Online Store 2.0: What Changed and Why It Matters already covered: JSON templates, sections, and merchant-editable settings. 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.
Review a Canvas change before it goes live
Who is affected
| Storefront shape | What Canvas can do this week | What to keep on the theme editor |
|---|---|---|
| Existing live theme with app blocks (reviews, wishlists, subscriptions) | Experiment on a duplicate if you accept missing blocks | Any change that must keep those blocks visible |
| Theme created or duplicated inside Canvas | Prompt-led layout on Shopify-native sections | App embeds, Markets, translations, Rollouts |
| GitHub-connected or CLI-owned theme | Visual sketch you then port as a reviewed pull request | The commit that production will actually ship |
| Third-party or heavily forked premium theme | Limited, until Shopify documents backwards compatibility | Section groups, custom Liquid, and Support-facing files |
| Hydrogen or headless storefront | Nothing on the headless surface | Your existing storefront pipeline |
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 (reviews, loyalty, subscriptions, scripts) 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.
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. The merchant still has two editors and one published theme, so the review below assumes you will keep selling on the current theme while Canvas is early.
Choose Canvas or the theme editor for this edit
Write the change in one sentence before anyone opens Sidekick: new homepage stack, collection banner, 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 when you want Sidekick to propose a layout you will later rebuild as named sections. Do not run the same change in both surfaces on the live theme in the same hour, because you will lose the trail of which tool wrote the JSON.
Sidekick is louder in admin than it was a year ago, and some teams are already hunting for a way to shrink the Sidekick chrome so the rest of admin fits on a small laptop. Treat that chrome as an admin preference, and keep the storefront decision on the page you are about to publish.
If the sentence you wrote is "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. The Anatomy of a High-Performance Shopify Theme is the map of sections, assets, and settings you should be able to point at after the prompt finishes.
Check app blocks, Markets, translations, and Rollouts
Before you preview, open the unpublished theme and list every storefront app the live page currently shows: reviews, loyalty, subscriptions, size guides, scripts, and any block a merchant added from the theme editor. Then walk the same page in Canvas or on the Canvas-created duplicate and mark each block present, missing, or unknown.
Shopify's launch note is blunt on this point. Theme app extensions are unsupported. A Canvas-created or Canvas-duplicated theme will not offer those blocks. Apps that list themes for install or audit will not see Canvas-edited themes. Reviews, analytics tags, and other embeds that look "part of the theme" to a merchandiser are still app-owned, and they drop off the page without a Liquid error.
Do the same pass for Markets, translations, and Rollouts. Canvas does not support them at launch. 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. Shopify Markets Black Friday Traps: Duties, Currency, and Catalog Gaps is the market-by-market record you already keep for peak traffic; reuse that sheet and add a Canvas column that says supported or not for this edit.
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. "Looks good" is not a check.
Preview on an unpublished theme
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. Canvas makes that step easier to skip because the workspace feels like a sketch, and the publish control is still one click.
Preview on a phone and a desktop. Confirm price, variant picker, and add-to-cart still sit where the live PDP puts them. Confirm the header and footer still come from the section groups your theme already uses. If Canvas added a second announcement bar or a new header row, you are already close to the duplicate-chrome problem the customisation-limits article walks through.
If the store connects the theme to GitHub, fetch the branch after the save and confirm the files you expected actually landed. Theme-editor uploads of assets 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 is the same class of problem: the admin looks updated, and the rollback copy your developers trust is stale. Keep the unpublished theme itself as the revert target until the commit exists.
Do not publish from Canvas because the laptop preview looks closer to the campaign Figma. Publish when the unpublished theme has passed the app-block list, the Markets list, and a second person who was not in the Sidekick chat.
Name a rollback owner
Write one name next to the unpublished theme: who can publish the previous copy, who can revert the GitHub commit, and who tells paid media to pause if the live page loses reviews or a market hero. Canvas and Sidekick do not create that owner. The workspace can generate a page in a minute and leave three teams assuming someone else can undo it.
The owner needs access to Online Store, Themes, and the GitHub repo if you use one. They need the theme name of the last known-good unpublished copy, not a Slack memory of "the version from Tuesday." If your apps cannot see Canvas-edited themes, the owner also needs a browser session on the theme editor, because 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, not as a same-day toggle. A homepage experiment you publish on 6 October may need a different review on 20 October once theme app extensions land. Keep the rollback name in the same note you update when Shopify documents those surfaces.
If nobody on staff can read section JSON or restore a theme, stop at unpublished preview and hire the theme work. Prompt-led layout is still theme architecture. 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.
What this does not change
Canvas does not retire the online store editor this week. Shopify launched the two surfaces together and told developers that existing themes and app installs keep working in the editor. A store that never opens Canvas still sells.
Canvas does not replace a supportable section model. If the live theme already mixes leftover static header tags, Custom CSS dumps, and undocumented Liquid, Sidekick will write into that mess. Recover the section groups first, then let Canvas propose layouts on a clean duplicate.
Canvas does not replace the Sidekick admin flywheel work, the Claude connector permission model, or checkout Functions. Those are different jobs. This review is only for storefront files Sidekick can now reach through a visual workspace.
Canvas also does not make the Theme Store obsolete on day one. Shopify said the store remains a destination for a polished starting theme, even while it rethinks that role. Buying a new premium theme to "be ready for Canvas" is a later architecture project, not a launch-week task.
Conclusion
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 revert the live theme. 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 is the path that puts an owner back on the files. Book a discovery call if you want that review before marketing treats Canvas as the default editor.
