Building an Ecommerce Catalogue That Can Handle Spare Parts at Scale

It's one of the most common things we hear, and it's also one of the biggest untapped opportunities for manufacturers. Once a spare parts catalogue grows past a few thousand SKUs, keyword search alone stops working. Customers need to know which part fits which machine and serial number, which part replaced an older one, and what it costs under their specific agreement, none of which a flat, retail-style catalogue was ever built to handle. Here's what actually breaks, and what a platform built for spare parts at volume needs to do instead.

A single-plant operation might carry 5,000 spare parts SKUs; a multi-site manufacturer can run past 200,000.

Caterpillar's parts database holds more than 1.4 million individual spare parts. (industry benchmark)

At that scale, a flat product catalogue and basic keyword search (the standard ecommerce toolkit) simply stops working. What's actually needed is fitment (which part fits which machine and serial number), supersession (which part replaced an older one), and cross-reference search, none of which a generic platform models natively.

Picture a service engineer standing in front of a machine with a ten-year-old serial number, needing to know exactly which impeller, filter, or gasket fits that specific unit, not the current model on the price list, the one actually on the floor. Keyword search can't answer that question. It has to know the machine's original build configuration, which parts have superseded the original, and which SKU that specific serial number now requires. Get it wrong, and the wrong part ships, the technician makes a second trip, and the entire reason the customer went looking for self-service in the first place, avoiding a phone call, is undone by a return and a re-order.

A mid-size industrial distributor might carry 50,000 SKUs across 500 customer accounts, each with its own negotiated agreement. That's potentially 25 million individual price points once every SKU-account combination is counted.

Customer-specific pricing is the single biggest reason B2B companies abandon platforms originally built for B2C. (recent industry report on B2B digital commerce)

Basic customer groups or tiered price lists (what most platforms offer out of the box) cover simple cases. They don't hold up against real contract pricing, and they duplicate data that already lives correctly in your ERP. One customer might get a set discount on fasteners and a different rate on electronics; another might have a blanket discount that only applies above a certain order volume. Multiply that by even a few hundred accounts across a mid-sized catalogue, and you're well past what a handful of customer tiers can represent accurately. When the price shown on the storefront doesn't match what the customer's contract says, the order either gets corrected manually after the fact, which erodes trust, or it goes out at the wrong price, which erodes margin. Neither outcome is one you can absorb at volume.

One customer might get a set discount on fasteners and a different rate on electronics; another might have a blanket discount that only applies above a certain order volume. Multiply that by even a few hundred accounts across a mid-sized catalogue, and you're well past what a handful of customer tiers can represent accurately. When the price shown on the storefront doesn't match what the customer's contract says, the order either gets corrected manually after the fact, which erodes trust, or it goes out at the wrong price, which erodes margin. Neither outcome is one you can absorb at volume.

Most platforms solve the ERP-connection problem with a nightly batch sync: data moves once a day, which is fine for a retailer and risky for a B2B seller.

Batch-synced storefronts run 5–8% oversold orders on average, while 74% of B2B buyers now expect real-time inventory visibility as the standard, not the exception. (industry analysis)

What's actually needed is a live, two-way connection: stock, pricing, and orders read and written in real time, with no added load on your ERP, and a webshop that keeps taking orders even if your ERP itself is temporarily down.

An oversold order is rarely just an inconvenience. It's a technician who ordered a part expecting next-day delivery, scheduled a service visit around it, and now has to reschedule because the part wasn't actually on the shelf. For a business selling spare parts at volume, avoiding oversold orders isn't a technical nicety, it's the difference between a self-service channel customers keep using and one they abandon after the first bad experience.

Bringing this together means three things working as one system rather than three tools stitched together after the fact: search built around fitment and cross-reference data rather than keywords alone, pricing that reads live from the account-specific agreement instead of a static tier, and inventory that's accurate to the minute, not the day. Each piece is hard enough to get right on its own. Built separately, on top of a platform that wasn't designed for any of them, they tend to interact badly, a pricing fix breaks a search index, an inventory sync slows the whole storefront down under load. Built as one system from the start, they reinforce each other instead.

The upside is proportional to the difficulty. Spare parts catalogues that get this right don't just reduce support calls, they turn browsing into buying, because the customer can actually find, price, and trust what they're looking at without ever needing to pick up the phone.

^{Related reading: For the business case on why spare parts sales deserve investment as a growth channel, not just a catalogue fix, see “Growing Spare Parts Sales Into a High-Margin Channel with the ERP Data You Already Have.}