Session brief: Shopify theme embed for the assistant

WardrobeIt publishes this as an on-demand written session about theme embed. There is no Zoom ID and no speaker bio invented for this page. The topic is why embed placement is part of the shopping journey, not a developer-only afterthought.

Fashion themes already compete for edges of the screen. A shopping assistant that exists only in an app admin toggle is not installed. A shopping assistant that exists only on the homepage is not installed for apparel decisions.

Learning objectives

• Separate catalog connection from theme embed as two jobs.
• Name the templates where fashion shoppers actually decide.
• Verify desktop and mobile on the theme you publish.
• Know where to stop if a step is not in Help Center.

What the session covers

• Connecting a Shopify store with the access catalog sync needs.
• Placing the storefront widget on the theme you actually publish.
• Verifying collection and product templates used by fashion themes, desktop and mobile.
• Paid landing templates and other page-builder templates that often miss the embed.
• Accessibility and overlap with size charts, sticky carts, and consent banners.

Sequence (do not reverse it)

1. Catalog trust: you would defend five SKUs in conversation.
2. Connect a Shopify Store so the assistant has inventory to speak about.
3. Install the Storefront Widget on the live theme.
4. Verify collection, PDP, and any campaign landing templates.
5. Only then talk about merchandising rules and knowledge polish.

Product context for the embed model is Shopify Theme Embed. Shopify Catalog Sync does not place a launcher; it feeds the catalog. Mixing those jobs produces “we installed it” reports that shoppers never see.

Workshop exercise

Open your live theme preview. Navigate to one collection and one PDP that uses a different template. Confirm the assistant is reachable without covering size charts or cookie banners. Repeat at a phone width. If it only appears on the homepage, the session is not complete.

A second pass for paid landings

If you run ads to page-builder URLs, open those URLs in a private window. Many fashion campaigns fail this pass. Treat that as an embed gap, not as proof that “AI does not work on paid traffic.”

Discussion prompts

• Which product templates does our theme actually use (bundles, preorder, default)?
• Who can publish the theme that currently has the embed?
• Where does the sticky add-to-cart bar sit relative to the launcher on a phone?
• Do translation or wishlist apps alter the product template we tested?

Fashion-theme conflicts to workshop

Sticky add-to-cart, size-chart modals, announcement bars, wishlist drawers, and cookie consent all compete for the same viewport edges. The assistant should not trap keyboard focus or hide a chart the shopper opened in good faith. If your theme uses alternate product templates for bundles, preorder, or gifts, those files need their own pass. Translation apps should still resolve to the same SKUs.

Cache and app managers can make a preview lie. Hard-refresh a real URL. Confirm you are on the published theme, not a development copy. The operator guide on fashion templates in Guides is the companion reading.

Failure modes this session is meant to prevent

• Embed enabled only on an unpublished theme.
• Homepage launcher treated as “installed.”
• Paid landing templates left out of scope.
• Unsupported snippets pasted from a freelancer memory.

After the session

Record the templates you verified and the ones you skipped. Skipped templates are known risk. Continue with recommendation rules and knowledge only after a merchandiser can complete a real question on a live PDP. Related: AI Shopping Assistant, Getting Started, and the guides hub article on fashion-template install.

This brief will not add a seating capacity or a start time. When a live workshop exists, it will publish as a dated event, not as a retrofit on this page.

Bring these URLs to the workshop

A collection that uses your default grid. A PDP with a size chart. An alternate product template if you have one. One paid landing URL if you run ads. Open all four in a private window on a phone-width viewport with production apps enabled. If any launcher is missing, record it as incomplete install, not as a model failure.

Connection remains a separate job. An attractive launcher with a stale catalog still fails shoppers. Connect a Shopify Store and Shopify Catalog Sync.

Accessibility and legal overlap

• Keyboard open, move, close.
• Size-chart modal still usable.
• Cookie consent not permanently covered.
• Checkout-adjacent placement does not hide required notices.

If a step is undocumented, stop. Troubleshooting and Contact. Operator guide: Guides.

Sign-off artifact

Write the theme name, the four URLs you tested, desktop and mobile results, and who can publish the theme. That page is the session output. A verbal “it is on” is not. If a paid landing fails, media should not scale that URL until embed exists. Install the Storefront Widget.

Accessibility failures are install failures. Keyboard traps and covered size charts are not polish tickets for later. Stop and fix before merchandising spends time on rules.

Homepage-only placement is not a completed session. Fashion decisions happen on collection and product templates, including alternate PDPs and paid landings. Desktop and mobile both count. If a step is not in Help Center, stop rather than pasting a snippet. Shopify Theme Embed.

Confirm the embed is on the theme you actually publish, not only on a development theme that never goes live.