StoreBuilt reviewed Shopify’s theme-extension documentation alongside our app-audit and release guidance for this article. The central implementation distinction is that installing an app and displaying its storefront feature are separate steps. A working app dashboard does not establish that the correct theme, template and customer context are serving the widget.
A Shopify app embed not showing is especially confusing after a theme launch: the subscription is active, the app still contains its settings and the public feature has disappeared. This guide gives UK ecommerce teams a way to isolate the missing layer before reinstalling software or adding another script. The worked example is illustrative, rather than a claim about a particular app or client.
In this guide
- Describe the feature and its expected location
- Distinguish a block from an embed
- Confirm which theme customers actually see
- Check placement on the actual product template
- Inspect market and app-level eligibility
- Reproduce the public journey without preview assumptions
- Work through an illustrative theme launch
- Make one change at a time
- Verify behaviour as well as visibility
- Leave a maintainable handover
- StoreBuilt point of view
Describe the feature and its expected location
Record what should appear, on which page and under what conditions. A floating chat bubble, an inline review block and an invisible analytics integration are different features. “The app is missing” is not precise enough for a useful investigation. Identify the customer-visible outcome or, for a background feature, the evidence that would demonstrate it is running correctly.
Capture the page URL, theme name, template, market, device and relevant customer state. Note whether the problem began after a theme publication, app update or configuration change. Preserve a working example if one exists. These facts let the team compare two contexts without repeatedly toggling settings and losing track of which action changed the result.
Distinguish a block from an embed
Shopify’s theme app guidance separates app blocks, app embeds and custom code integrations. Blocks occupy a position in a compatible section or template. Embeds can provide floating elements or background functionality. The same app may expose more than one feature, so read its current installation instructions before choosing the integration point.
This distinction changes the test. A review block may need placement on the intended product template; a chat embed may need activation in the theme’s embed controls. Adding an arbitrary Apps section is not a universal remedy. If the app uses an older custom-code approach, record that fact and ask its developer how the integration should be maintained in the current theme.
| Integration style | Where to investigate | Useful acceptance evidence |
|---|---|---|
| App block | Compatible section and template | Feature appears in intended position |
| App embed | Theme embed controls | Intended overlay or behaviour works |
| Background integration | Documented runtime and provider status | Relevant event or function verified |
| Custom theme code | App installation guidance and theme changes | Single supported integration path |
| Checkout extension | Checkout configuration | Feature works in the checkout context |
Confirm which theme customers actually see
Identify the published theme and the theme being edited. An app working in a draft preview is useful evidence, but it does not establish the public result. Conversely, changing the published theme while looking at a different preview can make a valid correction appear ineffective. Keep the theme name and identifier in the investigation record.
Shopify states that apps need reactivation when the published theme changes; do not assume a new theme inherits every integration state. Review the relevant app setup in the intended launch theme before publication. Include this in the release checklist alongside product templates and purchase controls. An attractive new homepage is not sufficient evidence that all the functions supporting it are ready.
Check placement on the actual product template
For an inline feature, identify the template assigned to the affected resource and inspect the section that should contain the block. A widget appearing on one product but not another may reflect different templates or app eligibility. Choose a control product that should qualify, then compare the configuration without changing both products at once.
Theme sections vary in their support for app blocks. If the intended placement is unavailable, consult the theme and app documentation before adding a custom workaround. The correct outcome may be a supported section, a template adjustment or a developer change. It should not be a duplicate widget pasted into product descriptions, where future maintenance becomes difficult and the app’s intended lifecycle is bypassed.
Contact StoreBuilt with the app name, affected URL and recent theme change for a focused integration review.
Inspect market and app-level eligibility
Shopify supports market-specific app embed configuration. Record the market selected in the editor and the context used on the public storefront. A feature enabled for one market can therefore require a different investigation from a feature missing everywhere. Compare the actual settings rather than assuming a UK tester and a UK-targeted page necessarily share the same context.
Then inspect the app’s own documented rules. Depending on the feature, those may involve product eligibility, publishing status, schedules or account state. Treat these as app-specific questions, not universal Shopify behaviour. If the provider offers diagnostics, save the relevant result. A theme toggle cannot override an app-side decision to withhold a feature, and a successful app-side check cannot prove the theme has rendered it.
Reproduce the public journey without preview assumptions
Open the public URL in a fresh session and repeat the customer’s actions. Compare desktop and mobile, and test the page transition that precedes the failure. Some issues appear only after navigating from a collection or changing a variant. A direct page load can look healthy while the real customer sequence remains broken.
Where consent or browser protections legitimately affect a background feature, test the intended consent states separately and respect the store’s requirements. Do not disable privacy controls as a permanent fix for missing tracking. For a visible widget, check whether it is present but hidden, clipped or covered by another element. A developer should inspect the actual page and errors rather than infer the cause from a screenshot alone.
Work through an illustrative theme launch
Imagine a UK footwear retailer publishing a refreshed theme. Its review app remains installed, and staff can still moderate reviews in the app dashboard. However, the review panel is absent from one product family because that family’s alternate template lacks the required block. Reinstalling the app would not by itself establish the intended placement.
The team records the assigned templates, adds the supported block to the affected layout in a preview and checks both reviewed and unreviewed products. It also checks the mobile purchase area so the widget does not displace essential sizing information. After publication, the same public URLs are tested again. The example shows why the scope should follow the missing feature rather than the entire app installation.
Make one change at a time
Save the starting configuration and change the smallest relevant setting. Recheck the same reproduction case immediately. If several toggles, app rules and theme files change together, a successful result will not tell you which action mattered. That makes future support and rollback harder, especially when a second problem appears after the apparent fix.
Avoid adding duplicate scripts while diagnosing. Two integration paths can render repeated widgets, send repeated events or conflict with each other. Before removing an older integration, establish how the provider expects migration to work and preserve a recovery path. Uninstalling an app can affect data or configuration, so it should be an informed product decision rather than the first troubleshooting experiment.
Verify behaviour as well as visibility
A widget appearing on screen is only the start of acceptance. Open it, change the relevant selection and follow the intended interaction. For a review component, check the empty state and navigation; for chat, check opening and closing without sending a message; for a product option feature, check that its selection reaches the basket correctly. Choose tests that fit the actual app.
| Case | Visible check | Behaviour check |
|---|---|---|
| Main template | Intended position | Primary interaction works |
| Alternate template | Required feature present | Correct resource context |
| Mobile page | No clipped controls | Tap targets usable |
| Different market | Intended eligibility | Local configuration respected |
| Empty state | Clear, restrained presentation | No broken controls |
| Public release | Correct published theme | Same result as approved preview |
Leave a maintainable handover
Document the integration type, theme setting, templates and app-side rules that matter. Include a screenshot of the approved placement and a short list of regression URLs. The next person updating the theme should be able to repeat the checks without rediscovering why one product family behaves differently. Store app support links with the integration record.
Review the feature again after a theme replacement or a material app change. For wider decisions about redundant tools and performance, use our Shopify app-stack audit guide. The narrow rendering fix should feed that inventory, but it does not require a full app-stack redesign when the underlying product need remains sound.
StoreBuilt point of view
An installed app is a dependency; a tested customer interaction is the deliverable. We favour clear ownership of placement, eligibility and release checks so the feature keeps working through future theme changes. Fix the specific missing layer, then leave enough evidence for the next person to maintain it confidently.
Explore Shopify development services for theme and app integration work. Contact StoreBuilt to diagnose a missing widget and verify its complete customer journey.