CUSTOM, HEADLESS & BESPOKE STOREFRONTS

Interactive spare parts catalog software for any storefront.

Q: What do I need to add Partsy to a custom storefront?

A page that can render HTML and load one script. You place a container element where the diagram should appear and load the Partsy script once per page; the script finds every container and renders a diagram into each.

If your storefront can render HTML, it can run Partsy. A container element and one script tag are the whole integration, so a custom build, a headless front end or an unusual platform gets the same clickable exploded parts diagram as a packaged one.

No platform requirement · one script tag · works headless

Start free ↗ See how the plugin works →

An interactive parts manual, wherever you sell.

Most spare-parts businesses already have the diagram: it is in a service manual, a CAD export, or a photograph of a printed sheet. What they lack is a way to make it the entry point to buying, on the site they already run.

Partsy is that layer, and it deliberately does not care what is underneath. It renders a digital spare parts catalog into a container element, so the surrounding storefront — your routes, your cart, your checkout — stays exactly as it is.

What the generic integration actually is.

You add: One container element per product, and one script tag per page
Product mapping: Data attributes on each container: product and model
Credential: Publishable key, or a short-lived embed token where your server renders the page
Discovery: The SDK finds every container on the page, so one script covers a whole catalogue
Hosting: Nothing to host: the SDK and the diagrams are served by Partsy

What you paste.

Emit one container per product wherever your template renders a product, then load the SDK once:

<div data-partsy-catalog
     data-product="Drill Machine"
     data-model="BH-123"></div>

Load the SDK once per page and call PartsyCatalog.autoMount(). It finds every container on the page, so a catalogue listing and a product page need the same three lines. Products you have not mapped render nothing.

What it does not do.

Your page must allow a script. A Content Security Policy that blocks third-party scripts needs your Partsy origin added to script-src and img-src. Without that the browser blocks the SDK and the container stays empty.

It does not become your catalogue. Partsy stores the diagram, the callout coordinates and the part links. Products, prices, stock and orders stay in your own system, and no product data is copied into Partsy.

A sandboxed frame needs a token. Where the page runs inside an iframe whose origin is not your shop domain, allow-list that origin or mint an embed token server-side, so the request is authorised by the token rather than by the page origin.

Built for automotive and machinery catalogues

Automotive parts catalog. Vehicle assemblies and sub-assemblies are already drawn as exploded views, and buyers identify a part by position rather than by number. Partsy maps each callout to your own product page, so a diagram becomes a route into the catalogue instead of a PDF beside it.

Machinery parts catalog. Industrial equipment and plant machinery share the same shape: a maintenance engineer knows the component and where it sits, not the part number. A clickable diagram converts that knowledge into an order.

Distributor and dealer portals. The same integration runs behind a login, so a dealer extranet or B2B ordering system can show the same interactive catalogue your public store does.

Custom storefront: common questions

What do I actually need to add?

A page that can render HTML and load one script. Place a container element where the diagram should appear and load the Partsy script once per page; the script finds every container and renders a diagram into each.

Does it work on a server-rendered or headless front end?

Yes. Where the page is rendered by your own server, or runs in a sandboxed iframe whose origin is not the shop domain, your server exchanges its client secret for a short-lived embed token and the page renders with the token instead.

Is it only for ecommerce platforms?

No. It is a container element and a script, so it also works on a distributor portal, a dealer extranet, a B2B ordering system, or a marketing site that needs an automotive or machinery parts catalogue.

Can one page show more than one diagram?

Yes. The SDK finds every container on the page and mounts each one, so a comparison page or a multi-product page works without extra JavaScript.

Platform integrations

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

Partsy for ecommerce / 2026