Cost and scoping

What an online parts store costs and what actually drives the number.

Dealers usually ask for a price before describing their brands, which is understandable and also backwards. The storefront is close to a fixed cost. The integrations are not, and they are most of the project.

Talk to us

Get your parts store scoped.

A real reply from an engineer. We won't put you on a mailing list.

Book a 30-min call

Five things that move the number

If you want a rough sense of where a project will land before you speak to anyone, these are the variables that matter.

Brand count. Each brand is a separate integration and separate normalisation work.
Data availability. A brand with a usable feed is far cheaper than one that needs structured sourcing.
Fitment depth. Part number search only is cheap. Model, serial range and diagrams are not.
Freight complexity. Parts ranging from an O-ring to a loader bucket need real shipping logic.
System writeback. Order notifications are simple. Writing orders back into a DMS is not.

What barely moves the number

It surprises dealers that catalog size is almost irrelevant. Once the pipeline exists, publishing three million parts costs about what publishing thirty thousand costs, because nobody is typing either one.

Design also matters less than expected. A parts store is judged on whether the right part is found in three clicks, not on how the hero section looks. The money belongs in search and data.

Three ways dealers start

There is no requirement to build everything at once, and most dealers should not.

Start with one brand: prove the integration on your largest parts line before committing further.
Full catalog build: all brands connected and a complete storefront delivered in one project.
Fix what you have: you already have a store, but the data is stale, search is poor, or nothing is connected.

What the return looks like

The revenue side is orders placed when your counter is closed, which is largely incremental rather than shifted from the phone. The cost side is counter time. Scholten's Equipment recovered roughly 200 hours previously spent answering parts availability questions, across a catalog of over 3.5 million parts and five connected brands.

The quiet third benefit is accuracy. A connected catalog is correct by default, so you stop paying for the returns, credits and apologies that a hand-maintained parts page generates.

Where the effort goes in a typical parts store project

Workstream	Effort	Why
Brand integrations	High	Repeats per brand, and data quality varies wildly
Catalog normalisation	High	Supersessions, duplicates and inconsistent naming
Fitment and search	High	Model hierarchy plus a tuned search index
Storefront build	Medium	Largely repeatable once the data model is settled
Freight and payments	Medium	Oversized and freight rules need real carrier logic
Design and content	Low	Function beats polish in a parts catalog
Ongoing maintenance	Low	Monitoring the pipeline, not re-entering data

Questions dealers ask

Cost is driven almost entirely by how many brands have to be connected and how much catalog normalisation is involved, not by page count or design. A single-brand pilot is a fraction of a full multi-brand catalog build, which is why most dealers start with one brand and expand once the pattern is proven.

Because the same storefront costs very different amounts depending on whether your brands expose usable feeds. Two dealers with identical catalogs can be a month apart in effort based on what their manufacturers make available. We scope after a short call rather than publish a number that would not apply to you.

One brand, connected end to end, with search, checkout and order notifications live. It proves the integration, gives your counter something real to test against, and produces a pattern the rest of the catalog can follow at lower cost per brand.

Not in the way dealers expect. Going from ten thousand parts to three million parts costs little extra once the pipeline exists, because the catalog is generated rather than entered. Going from one brand to five costs real money, because each brand is a new integration.

Hosting or platform subscription, payment processing, and a maintenance allowance for the integrations. Manufacturers change formats occasionally and the pipeline needs monitoring. What you should not be paying for is anyone re-entering parts data by hand.

A normal ecommerce quote prices design and templates. A parts store quote prices integrations and data normalisation, because that is where the work is. If a quote for a parts catalog looks like a quote for a clothing shop, the integration has not been thought about.

Two things. Parts orders placed outside counter hours, which are incremental rather than shifted revenue, and counter time recovered. Scholten's Equipment saved roughly 200 hours of counter time previously spent on parts availability calls.

Scholten's Equipment launched a five-brand catalog with over 3.5 million parts in about four months. A single-brand pilot is meaningfully faster because there is one data source to map and one set of edge cases to solve.