Portal and DMS integration
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
A real reply from an engineer. We won't put you on a mailing list.
Short answer
Dealer portal integration connects the manufacturer or DMS system holding your parts data to your online store, so catalog, pricing and stock update automatically. Each brand is connected separately, then normalised into one searchable catalog.
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.
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.
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.
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.
| 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 |
Portal, DMS, spreadsheets or a mix. A senior engineer will tell you what can be connected and what has to be sourced another way.
Q&A