Portal and DMS integration

Dealer portal integration is the whole parts ecommerce project.

The storefront is the easy part. What decides whether an equipment dealer sells parts online is whether the catalog, the pricing and the availability come from your systems automatically, or from a person with a spreadsheet.

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

Three sources, three different problems

Parts data reaches a dealership from more than one direction, and each direction has its own failure mode. Treating them as one problem is why so many parts store projects run long.

Manufacturer portals hold the authoritative catalog but are built for counter staff, not machines
Your DMS holds the commercial truth: your price, your stock, your lead time
Supplier and aftermarket feeds fill gaps but arrive in inconsistent formats

How the connection is actually built

The pattern that holds up across brands is a normalisation layer sitting between the sources and the storefront. Nothing talks to the store directly. Everything is mapped into one shape first.

That layer is what makes a second and third brand cheap. The first connection carries the design cost. After that you are writing a mapping, not rebuilding the pipeline.

Map what the brand exposes and what it withholds, before any code is written
Pull catalog data on a schedule into a normalised structure
Resolve supersessions and duplicate part numbers across brands
Layer your DMS pricing and availability on top, always overriding catalog data
Publish into WooCommerce or Shopify with fitment and diagram relationships intact
Monitor the pipeline, because manufacturers change formats without telling anyone

When a brand gives you nothing

Some manufacturers simply do not offer a usable feed to individual dealers. This is not a reason to leave the brand off your store, it is a reason to source the catalog differently.

For Scholten's Equipment, CLAAS and JCB were connected through DealerAPI v2. Kubota had no equivalent, so we built a structured data approach against a reliable parts source and layered the dealership's own pricing over it. The customer sees one catalog. They never know the data arrived by two different routes.

What integration is worth

The obvious return is online orders. The less obvious one is counter time. Scholten's Equipment saved roughly 200 hours that had been going into availability calls, because customers could answer their own question at 9pm without picking up a phone.

The other return is accuracy. A connected catalog is right by default. A hand-built one is wrong by default, and wrong pricing costs more trust than having no online store at all.

Data sources and what each one gives you

Source	What it provides	Typical constraint
Manufacturer portal	Authoritative catalog, diagrams, supersessions	Human-facing, rarely machine-readable per dealer
DealerAPI v2	Programmatic parts data for supported brands	Brand coverage varies, mapping still required
Dealer management system	Your price, your stock, your lead times	Access ranges from full API to nightly export only
Structured data sourcing	Catalog for brands with no dealer feed	Needs normalisation and ongoing monitoring
Supplier and aftermarket feeds	Coverage for consumables and non-OEM lines	Inconsistent formats, duplicate part numbers

Questions dealers ask

Dealer portal integration means connecting the manufacturer system that holds your parts data to the storefront your customers use, so the catalog, pricing and availability flow automatically instead of being re-entered. It is the difference between a parts store that stays correct and one that is wrong within a month.

In most cases, yes. Dealer management systems usually expose either an API, a scheduled export, or a database view. Any of the three is enough to drive pricing, stock and order writeback. Where a DMS is fully closed, we work from a scheduled export instead and the storefront refreshes on that cadence.

DealerAPI v2 is the interface we used to connect CLAAS and JCB parts data for Scholten's Equipment. It exposes parts information programmatically, which means the catalog can be pulled and refreshed rather than copied. Not every manufacturer offers something equivalent.

We build a structured data approach for that brand. For Kubota we sourced parts data structurally rather than through a dealer feed, normalised it, and layered the dealership's own pricing on top so the listings were still accurate and still sellable.

Orders can be pushed back as notifications to the counter, as email or Slack alerts, or written directly into the DMS where the system allows it. Most dealers start with notifications, then add writeback once the volume justifies it.

Nightly is the usual cadence for catalog data, and near real time for pricing and stock where the source supports it. The right answer depends on how fast your prices move and what your source system can handle without slowing down.

The integration is built once per brand, then monitored. Manufacturers change their formats occasionally, so a small ongoing maintenance allowance is sensible. What you do not need is a person retyping parts data every week.

Yes, and that is normally the goal. Each brand is connected separately because each exposes data differently, then everything is normalised into one catalog so your customer searches once and sees everything you can sell them.