---
title: "Legacy Blueprint Themes: Compatibility and Support"
description: "**Legacy compatibility notice:** Blueprint is BigCommerce’s older theme engine. PRIKID.APP retains a manual script path for non-Stencil stores, but this is not a guarantee that a Blueprint theme will display charts, popups or tabs correctly. Ask support to assess your…"
url: "https://prikid.app/docs/how-to-make-the-app-work-with-a-blueprint-based-theme/"
updated: "2026-10-14"
category: Advanced and Legacy
---

# Legacy Blueprint Themes: Compatibility and Support

**Legacy compatibility notice:** Blueprint is BigCommerce’s older theme engine. PRIKID.APP retains a manual script path for non-Stencil stores, but this is not a guarantee that a Blueprint theme will display charts, popups or tabs correctly. Ask support to assess your store before making theme changes.

## What is different on Blueprint?

PRIKID does not automatically install its storefront script when the connected store reports that Stencil is disabled. [BigCommerce’s Scripts API documentation](https://docs.bigcommerce.com/developer/docs/integrations/scripts#blueprint-themes) also states that Blueprint does not render scripts added through the Scripts API or Script Manager. The Stencil **Reinstall the script** workflow is therefore not the Blueprint installation method.

Loading the script is only one requirement. The app must also identify the product, find an appropriate placement and work with the theme’s layout. A manual installation or a working integration on another store does not establish compatibility with your theme. Tabs, custom layouts, quick view and mobile behavior need separate checks. This guide does not establish support for additional storefronts, multi-storefront configurations or Catalyst/headless stores.

## Check with support before installing manually

Open PRIKID and go to **App → Settings → Script installation**. For a store reported as non-Stencil, the app’s manual instructions show a store-specific snippet and refer to **Footer Scripts**. If you see different instructions, cannot find Footer Scripts in your BigCommerce control panel, or are unsure which theme engine is in use, stop and [contact PRIKID support](https://support.prikid.app/new-ticket).

If support confirms that a manual installation is appropriate, use the snippet supplied for your own store by the current app. Back up the existing footer scripts and theme before editing; preserve unrelated code and avoid adding a second PRIKID script. Do not copy a snippet from an old screenshot, another store or an archived ticket. Your theme developer may need to help with placement. The Stencil template paths in the [placement and theme guide](https://prikid.app/docs/how-to-place-a-size-chart-link-elsewhere/) are not Blueprint template instructions.

After any agreed change, check a saved, published item that matches the exact product on the live storefront, on desktop and mobile. Confirm that the content appears in the intended position and opens or renders correctly. If it fails, revert only the change just made and report the result; repeatedly reinstalling the app is not a compatibility fix. Use [Why Your Size Chart, Popup or Tab Is Not Showing](https://prikid.app/docs/content-not-showing/) for publication, matching and display checks.

## Send the details needed for a compatibility review

Include the store and affected product URLs; theme name/version and known customizations; storefront/domain and theme engine if known; item name, display mode, published state and matching Preview screenshot; the Script installation screen; what is missing or failing; desktop/mobile screenshots; and any recent theme or script changes. Do not send passwords, API tokens or unrelated customer data. Support can assess whether an adjustment is feasible; a successful result is not promised.

**Using Stencil instead?** Follow [Install PRIKID.APP on BigCommerce](https://prikid.app/docs/installation-to-the-bigcommerce-store/) and the placement guide. For other topics, return to the [documentation overview](https://prikid.app/docs/about/).