MAGENTO & ADOBE COMMERCE SPARE PARTS CATALOG

Magento spare parts catalog, as a real module.

Partsy adds an interactive exploded parts diagram to Magento 2 and Adobe Commerce product pages. Breakdowns are the normal way to buy in aftermarket parts, so the exploded view belongs in the catalogue, not in a PDF attached to it.

Magento Magento 2 module · PHP 8.1+ · Adobe Commerce compatible
Start free ↗ See how the plugin works →

A spare parts catalog software layer for B2B catalogues.

Magento and Adobe Commerce handle enormous catalogues, tiers, and customer-specific pricing. What they do not model is the relationship between a machine and the parts inside it — the thing a service technician is actually looking at when they decide to buy.

Partsy adds that relationship as a product page experience: one exploded diagram, numbered callouts, a photo and part number per component, and a View / Buy link that goes wherever you sell that part. It is content your catalogue already has, made clickable.

What the Magento integration actually is.

Packaged as
Magento 2 module, app/code/Partsy/Catalog
Installed by
setup:upgrade, then setup:di:compile and setup:static-content:deploy
Configured at
Stores → Configuration → Services → Partsy (base URL and publishable key)
Product mapping
EAV attributes partsy_product and partsy_model, created by the module's install data
Renders via
A layout block on catalog_product_view with its own template

Install it in five steps.

  1. Drop the module in. Copy app/code/Partsy/Catalog into the Magento root.
  2. Run the Magento commands. setup:upgrade installs the module and creates its two product attributes; then di:compile and static-content:deploy for the environment.
  3. Configure it. Under Stores → Configuration → Services → Partsy, enter your base URL and publishable key.
  4. Allow the origin in your CSP. Add your Partsy origin to the storefront Content Security Policy for script-src and img-src. This is the step most often missed, and skipping it looks identical to a broken diagram.
  5. Map products. Assign Partsy Product and Partsy Model to your attribute set and fill them per product.

What it does not do.

The attributes have to reach your attribute set. InstallData creates them, but a product can only hold a value once the attribute is in the set that product uses. On a large catalogue that is an admin task worth planning.

It does not export your catalogue. Partsy stores the diagram, the callout coordinates and the part links. Everything commercial — SKUs, prices, tiers, MSI stock, promotions — stays in Magento and is never sent to Partsy.

Production mode needs the deploy. On a production-mode store, skip static-content:deploy and the template ships unstyled or not at all. That is standard Magento behaviour, not a Partsy limitation.

Magento spare parts catalog: common questions

Does the module create the attributes it needs?

Yes. InstallData creates partsy_product and partsy_model if they do not already exist, and does nothing if they do. The admin field and the template therefore cannot disagree: the attribute exists because the module is installed.

Why does the CSP matter?

The SDK is loaded from your Partsy origin, so that origin must be allowed in script-src, and in img-src for the diagram file itself. Without it the browser blocks the script and the page shows nothing, with only a console error to explain it.

Does it change any Magento product data?

It adds two product attributes of its own and reads nothing else. No product is exported, and prices, stock, MSI sources and catalogue rules are untouched.

Can I move the diagram within the layout?

Yes. It is added by a layout update on the product view page, so it can be reordered or relocated with a standard layout override, and it renders nothing on products with no Partsy mapping.

Other platforms

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

Partsy for ecommerce / 2026