Skip to main content
The Hemsy Shopify app includes a theme app extension, so everything on the other embed pages (the script tag, launcher attributes, checkout vs cart) is configured from the Shopify theme editor instead of your theme code. Your theme files are never edited, and uninstalling the app removes everything. The extension has two parts:
Your Hemsy dashboard’s Embed page has one-click deep links that open the theme editor with each part pre-selected, plus your store slug ready to copy.

​
1. Enable the app embed

  1. In the Shopify admin, go to Online Store → Themes → Customize, then open App embeds (the puzzle-piece icon).
  2. Toggle on Hemsy Embed.
  3. Paste your Hemsy store slug (copy it from the dashboard’s Embed page).
  4. Choose what happens when shoppers finish:
    • Open Hemsy checkout (default): Hemsy opens Shopify checkout directly.
    • Add items to the store cart: Hemsy adds the shopper’s items straight into your store’s cart using the native cart strategy. No callback code is involved.
  5. Save.
The embed alone doesn’t render anything. It binds any element matching [data-hemsy-trigger] as a launcher, which is exactly what the trigger block emits.

​
2. Add trigger blocks

Add the Hemsy Trigger block to any section from the theme editor (product templates are the usual spot). Each block is its own launcher with its own settings: Because instant mode and the finish action are per-launcher, you can freely mix triggers on one page: an instant “See it on a model” button next to a shared-look button next to a plain designer link.

​
Custom placements

If you want to launch Hemsy from an element the trigger block can’t reach (a nav link, a custom section), give that element the data-hemsy-trigger attribute plus any launcher attributes:
The app embed’s script binds it automatically, including elements re-rendered by the theme editor, which the script rebinds on shopify:section:load.

​
Headless or custom storefront?

The theme extension requires an Online Store theme. If your storefront is headless (Hydrogen or a custom frontend), use the script install instead — same script, same attributes, and your code owns the cart handoff via event callbacks. Everything else in these docs applies equally to both install paths.