Interactive exploded diagrams
Buyers click the part straight off the schematic and add it to the cart, no part number required.
Nobody servicing a machine starts with your SKU. They start with the unit in front of them and work inward, through the assembly, to the component that failed. Uncap builds machinery and equipment parts ecommerce on Shopify around Uncap Diagrams, where buyers click the part straight off an interactive exploded diagram and add it to the cart with no part number required, with dealer pricing and ERP availability behind it.
Parts commerce for machinery fails in a specific place, and it is never the checkout.
Parts commerce for machinery fails in a specific place, and it is never the checkout.
A parts manager, a dealer or an end user trying to keep a machine running knows the model, often the serial, and what broke. What they do not know is the part number, and your catalog is organized by part number. What they want is a model lookup that ends at the right component. What they get is a call, or a PDF parts book where they read a callout number off a scanned page and somebody keys it in manually. That is the whole business, running on a document format from before the web.
The exploded view is the navigation, and most sites do not have one. The parts diagram is how this trade thinks, and the schematic is the index to the machine. A product grid is not a substitute for either.
Parts supersede, sometimes more than once. A catalog that does not resolve a superseded part either sells nothing or sells the wrong thing, and on a machine down, the wrong thing costs a second day.
Assemblies and kits break the one-line-one-part assumption. An order line is often several physical components, and a buyer needs to drill from the assembly to the sub-assembly to the individual part without losing where they are.
Dealers are not end users and should not see the same store. A dealer portal needs its own pricing, its own account structure and its own visibility. Running dealers and end users through one undifferentiated storefront damages both relationships.
Your parts data is probably the real project. Diagrams live in PDFs, CAD files or a legacy parts book. Nothing is mapped to a SKU. This is the work that decides whether the site succeeds, and it is the work most proposals quietly leave out.
Start with the diagram, because that is where the buyer starts.
The piece that usually decides the project.
No part number required.
Because a repair is rarely one component.
Start with the diagram, because that is where the buyer starts.
Uncap Diagrams puts an interactive exploded diagram on the storefront with clickable hotspots mapped to live SKUs. Buyers click the exact part off the schematic and add it to the cart, no part number required, and pinpoint several parts on the same diagram to check out as one order. It is fitment-aware, filtering by model, year or assembly automatically, so the diagram a buyer is looking at is the one for their machine. Assembly trees let them drill from assembly to sub-assembly to part without losing their place. It is PIM-connected, so parts data stays in sync with your catalog rather than drifting from it.
The piece that usually decides the project is diagram import. Existing schematics come in and callouts get mapped, which means your parts books become navigation instead of staying as documents. Most vendors treat that digitization as a separate engagement, or as your problem. It is part of the product here.
Around the diagram sits the commercial layer. Uncap Portal carries the dealer accounts with their own pricing, their own users and their own permissions, kept separate from the end user experience. Uncap Connect keeps Shopify and your ERP in sync in real time, embedded in Shopify rather than sitting in middleware, so availability and pricing on the diagram are the availability and pricing your operation will honor, with the ERP staying the system of record.
Two things this page will not pretend about, because you are going to test them in a demo. Serial-level lookup, where a serial number resolves to the exact build of that specific machine, and supersession chains, where an obsolete part resolves forward to its replacement, are not published capabilities of Uncap Diagrams today. Uncap Garage does publish parts reorder by VIN, model or serial number from a customer-managed equipment and asset registry, which covers reordering for a machine an account has already registered. Resolving a serial number to an exact build inside the diagram is different, and it is built as an extension of Diagrams, along with supersession, on top of an engine that already handles diagrams, model fitment and assembly trees in production. That is a different proposition to building the whole thing from nothing, and it is the honest version of where Uncap stands.
The parts-finding experience, with dealer pricing and ERP availability behind it.
Buyers click the part straight off the schematic and add it to the cart, no part number required.
A buyer sees the diagram and the parts for their machine rather than everything you sell.
Drill from assembly to sub-assembly to part, the way a technician actually searches.
Existing schematics brought in and callouts mapped, built into the product rather than quoted as a separate program.
Pinpoint several parts on the same diagram and check out once.
Uncap Portal gives dealers their own login, account structure, price list and users.
Parts data stays in sync with the catalog, which stops a diagram from slowly becoming wrong.
A part that looks available on the schematic is available in the warehouse.
Built on top of the Diagrams engine rather than shipped in it. Reordering by serial number for a registered machine is already published in Uncap Garage.
Interactive exploded diagrams with clickable hotspots. Buyers click the part they need straight off the schematic and add it to the cart, no part number required. This is Uncap Diagrams working as shipped.
Fitment-aware by model, year and assembly. The catalog filters automatically so a buyer sees the diagram and the parts for their machine rather than everything you sell.
Assembly trees. Drill from assembly to sub-assembly to part, which is how a service parts catalog is actually structured and how a technician actually searches.
Diagram import from your existing parts book. Bring in existing schematics and map the callouts, turning legacy parts books and CAD assets into live navigation. This is the hardest part of the project and it is built into the product rather than quoted as a separate program.
Multi-part selection as one order. Pinpoint several parts on the same diagram and check out once, because a repair is rarely one component.
Dealer portal with its own pricing. Uncap Portal gives dealers their own login, their own account structure, their own price list and their own users, separate from the end user storefront.
PIM-connected parts data. Parts data stays in sync with the catalog, which is what stops a diagram from slowly becoming wrong.
ERP availability and pricing behind the diagram. Uncap Connect keeps stock and price current, so a part that looks available on the schematic is available in the warehouse.
Serial-level lookup and supersession, built as an extension. Serial-to-build resolution and superseded part chains are built on top of the Diagrams engine rather than shipped in it. Named here plainly so it can be scoped rather than discovered.
You are going to test this in a demo, so here it is plainly.
Shopify Platinum Partner, on Shopify since 2013, with 380+ storefronts launched. Shopify B2B supplies company accounts, company-specific catalogs and customer-specific price lists enforced at login, which is the dealer pricing layer. The parts-finding experience is what Uncap builds above it.
The diagram engine exists and is in production. This is the thing worth checking on every vendor you speak to. Interactive exploded diagrams, hotspots mapped to live SKUs, model and assembly fitment, assembly tree navigation, diagram import and PIM connection are documented capabilities of a shipped Uncap product, not a described outcome of a future build. Ask to see it working before you ask what it costs.
Uncap has delivered fitment-led parts commerce and catalog scale. Kooks and E3 Spark Plugs are published builds where fitment drives product discovery. ULE Group runs over a million SKUs on Shopify with Epicor, Akeneo and Algolia, with published outcomes of a 6X increase in online sales and a 559% year on year increase in traffic. Different trades to heavy equipment, and worth reading as evidence that the architecture holds rather than as a claim about your machines.
Selling MRO supply as well as machinery parts? MRO is a procurement-led business rather than a fitment-led one. The buyer is a maintenance or purchasing manager whose organization raises requisitions inside Ariba or Coupa, the catalog runs past a hundred thousand items and needs faceted search rather than diagrams, and the recurring revenue sits in vending, vendor managed inventory and blanket purchase order releases. If that is the half of your catalog you are trying to fix, start with industrial supply and MRO. Distributors carrying both run them from one Shopify store and one ERP connection.
Every parts order that arrives by phone is a buyer who knew exactly what they wanted and could not find it. That is not a demand problem. It is a navigation problem, and it is fixable.
Book a free strategy session. We will look at what state your diagrams and parts data are in today, how your dealer pricing is structured, whether serial-level resolution is genuinely needed or whether model and assembly is enough, and what your ERP can feed.
Not ready to build yet? Uncap Blueprint maps the parts data model and the phased plan before a dollar goes into development.
It depends entirely on whether the parts-finding layer exists or has to be invented, and that is the honest answer rather than a defensive one. The case against a general platform is real: parts identification, not checkout, is the hard problem, and a storefront with parts logic bolted on afterwards usually disappoints. The case for Shopify with Uncap is that the parts-finding layer is not being invented here. Uncap Diagrams is a shipped product doing interactive exploded diagrams, hotspots mapped to live SKUs, model and assembly fitment, assembly trees and diagram import today. What you get alongside it is a commerce platform your team can actually operate, an ecosystem of apps and people, and no dependency on a single specialist vendor for your entire storefront. Where a specialist platform wins is if you need serial-level build resolution on day one and are willing to accept a narrower platform to get it. Ask both kinds of vendor to demo against your own diagrams and judge it there.
Yes, and this is the product's core function. Buyers click the exact part off an interactive exploded diagram, with clickable hotspots mapped to live SKUs, and add it to the cart with no part number required. They can pinpoint several parts on the same diagram and check out as one order. Navigation is fitment-aware by model, year or assembly, and assembly trees let them drill from assembly to sub-assembly to part.
Partly, and you should be told exactly which part rather than finding out in a demo. Uncap Garage publishes parts reorder by VIN, model or serial number from a customer-managed equipment and asset registry. Uncap Diagrams currently publishes fitment by model, year and assembly, not serial-level build resolution, and does not publish supersession chains. Both are built as an extension of the Diagrams engine during implementation. The distinction matters commercially: you are extending a parts-finding product that already runs in production rather than commissioning the whole capability from nothing, which is a different cost and a different risk. If serial-level resolution is essential on day one, say so in your first conversation with any vendor, including this one.
They become the navigation. Diagram import brings existing schematics in and maps the callouts to SKUs. This is usually the largest single workstream on a parts build, and most vendors scope it as a separate digitization engagement. Treat it as the first question you ask, not the last, because a beautiful storefront on unmapped diagrams is not a parts business.
Yes. Uncap Portal gives dealers their own login, account structure, users and permissions, with dealer pricing enforced at login through Shopify B2B company catalogs and price lists. The end user storefront stays separate, so you are not showing dealer pricing to retail buyers or retail pricing to dealers.
It is a fair concern and it comes from Shopify's own documentation, which notes that some external integrations are not fully compatible with Shopify B2B companies and catalogs. That warning is about the integration, not the platform. A dealer logging in has to resolve to the right company record and the right catalog before any price is shown, and an integration built against Shopify's B2B APIs does that while one that treats a B2B store like a retail store does not. The failure shows up as a dealer seeing a price they were never quoted. Ask any vendor, including us, to demonstrate a dealer login landing on dealer pricing against a real account.
Uncap publishes integrations for twelve ERP systems, each with its own documented integration page: Acumatica, Cin7, Epicor, Fishbowl, Infor, Microsoft Dynamics, NetSuite, Odoo, Oracle, QuickBooks, Sage and SAP. Uncap's own framing is that these connect to Shopify "whether through an owned Uncap Connect app or a managed iPaaS integration", so the delivery mechanism differs by system rather than one size fitting all. Epicor Prophet 21 is the integration published on the Uncap Connect product page itself. It runs embedded in Shopify rather than as separate middleware, so parts availability, dealer pricing, accounts and orders move both ways in real time. For a specific ERP and the depth of sync your operation needs, the Uncap team confirms fit directly rather than claiming a connector that has not been built.