BIGCOMMERCE SPARE PARTS CATALOG

BigCommerce spare parts catalog, via Stencil and Script Manager.

Q: How does a BigCommerce product know which diagram to show?

Through two product custom fields, partsy_product and partsy_model. The theme component serialises the product's custom fields into a small JSON block and the loader picks the two Partsy values out of it by name.

Q: Why is Script Manager used instead of an app?

BigCommerce has no server-side product page hook to render into. The placeholder comes from a theme component and the loader is injected site-wide by Script Manager, which is the supported way to add a script to a Stencil storefront without an app.

Q: Does the integration need the client secret?

No. The loader carries the publishable key, which is read-only and refused unless the request comes from one of your allowed storefront domains. The client secret is never placed in the theme or in Script Manager.

Partsy adds an interactive exploded parts diagram to your BigCommerce product pages. A theme component supplies the placeholder, Script Manager supplies the loader, and two product custom fields decide which diagram each product shows.

Stencil theme component · Script Manager · no app required

Start free ↗ See how the plugin works →

Breakdown diagrams for a mid-market catalogue.

BigCommerce is a strong fit for distributors and mid-market sellers whose customers buy parts they can identify but not name. A spec sheet and a keyword search assume the shopper already knows the part number; an exploded diagram does not.

Partsy brings the diagram forward from a linked PDF to an interactive product catalog on the product page: numbered callouts, a photo per part, and a View / Buy path to wherever that part is sold.

What the BigCommerce integration actually is.

Packaged as: A Stencil theme component plus a Script Manager snippet
Installed by: Create two product custom fields, add the loader in Script Manager, add the component to your theme
Product mapping: Product custom fields partsy_product and partsy_model
Credential: Publishable key, held in the Script Manager snippet
Renders via: templates/components/products/, so it travels with your theme

Install it in four steps.

Create the custom fields. Add partsy_product and partsy_model to your product custom fields and fill them per product.
Add the loader. In Storefront → Script Manager, create a script in the Head on all pages, paste the loader and set your publishable key.
Add the component. Put the supplied component into templates/components/products/ and include it from your product view template.
Apply the theme. Confirm the diagram renders below the product options.

What it does not do.

The custom field names must match exactly. The component reads them by name, so partsy-product or PartsyProduct will not be found. That is the single most common reason a BigCommerce install shows nothing.

It touches your theme, not your platform. Stencil has no server-side product hook to render into, so the placeholder is theme code. A theme upgrade means re-adding the component; the mapping and the Partsy side are unaffected.

BigCommerce spare parts catalog: common questions

How does a product know which diagram to show?

Two product custom fields, partsy_product and partsy_model. The theme component serialises the product's custom fields into a small JSON block and the loader picks the two Partsy values out of it by name.

Why Script Manager rather than an app?

BigCommerce has no server-side product page hook. The placeholder comes from a theme component and the loader is injected site-wide by Script Manager, which is the supported way to add a script to a Stencil storefront without building an app.

Does it need the client secret?

No. The loader carries the publishable key: read-only, and refused unless the request comes from one of your allowed storefront domains. The secret is never placed in the theme or in Script Manager.

Other platforms

“The diagram was already the answer. Shoppers just could not click on it.”

Partsy for ecommerce / 2026