Dealer inventory data arriving in 8 different formats. VIN fields populated with estimated specs, not decoded data. Commercial vehicle listings without GVWR, axle configuration or body type. MercuryMinds built hgvtraders.com — a live HGV and commercial vehicle marketplace — and brings that production knowledge to every automotive marketplace and dealer platform build.
The Problem
"We launched on a standard marketplace platform. It worked for the first 200 listings. Then the dealers started uploading and we realised the platform had no concept of make/model/year hierarchy, no VIN decoding, no commercial vehicle fields. We were trying to list HGVs as if they were consumer products."
Automotive marketplace data requirements are categorically different from general product marketplace requirements. VIN decoding, make/model/year/trim hierarchy, GVWR for commercial vehicles, fitment data for parts, dealer inventory normalisation from DMS exports — these are not edge cases in an automotive marketplace. They are the core data requirements. A platform that doesn't handle them natively can't be made to handle them cheaply later.
Where Automotive Marketplaces Break
Make/model/year search that doesn't work
Automotive buyers search by vehicle specification — year, make, model, trim, engine. A search index without structured vehicle hierarchy returns irrelevant results for every specification query.
VIN data that's estimated, not decoded
Dealer DMS systems often contain incomplete or estimated VIN-derived specs. Without proper VIN decoding, listings contain wrong specs — driving buyer distrust and return disputes.
Dealer feed normalisation that breaks under volume
Each dealer DMS exports in a different format. Manual feed ingestion doesn't scale past 10–15 dealers. Automated normalisation handles any number of formats without ops team involvement.
Commercial vehicle fields that don't exist in generic platforms
GVWR, payload, axle configuration, body type (curtainsider, flatbed, tipper), engine hours for plant — these fields don't exist in standard automotive marketplace schemas. They're required for every HGV listing.
What We Build
Every system below is a live production deployment — including from hgvtraders.com. The full 24 use cases span VIN intelligence, dealer management, commercial vehicle specialisation, parts fitment and AI-powered listing quality.
VIN decoding against NHTSA, DVLA and international databases — extracting make, model, year, trim, engine, transmission, drivetrain, body style, colour and GVWR for commercial vehicles. Identifies discrepancies between dealer-entered specs and VIN-decoded specs and flags for review before listing goes live.
→ Decoded vehicle attributes, discrepancy flagging, accuracy assured
Dealer-facing portal covering inventory upload, listing management, lead tracking, enquiry management, pricing management and performance analytics. Handles DMS integration (Dealer Socket, Auto Trader, CDK) so dealer inventory syncs automatically without manual re-entry. Supports single-dealer and dealer group multi-site configurations.
→ Dealer portal, DMS sync, lead routing, performance dashboard
Ingests inventory feeds from dealer DMS systems in different formats (CSV, XML, JSON, EDI, API) and normalises to a consistent vehicle data schema. Handles conflicting specs between the VIN decode and the dealer's manual entry, resolving against the VIN decode as the authoritative source. Supports daily and real-time sync depending on DMS capability.
→ Unified inventory from any DMS format, VIN-validated
Marketplace platform designed for HGV, commercial vehicles, plant machinery and trailers — with the specialist data schema those vehicle types require: GVWR, payload, axle configuration, body type, engine hours for plant, MOT/service history, operator licence category, payload capacity. Built with hgvtraders.com as the production reference.
→ Full commercial vehicle taxonomy, HGV-specific search filters
AI layer on top of listing data — detecting overpriced or underpriced listings relative to comparable vehicles in the marketplace, identifying stale listings (time on market relative to similar vehicles), and providing market valuation data to sellers as a pricing reference. Improves turn rate and buyer trust in marketplace pricing.
→ Per-listing valuation context, market comparison, stale listing alerts
Parts marketplace with fitment data — make/model/year/trim compatibility tables linked to each part listing, enabling buyers to search by their vehicle and confirm fit before purchase. Supports OEM part numbers, aftermarket cross-references and supersession chains. ACES/PIES data standard compatible for US market parts.
→ Vehicle-filtered parts search, fitment confirmation, OEM/aftermarket cross-ref
Full scope: 24 automotive marketplace use cases
Includes buyer lead management, finance calculator integration, vehicle history API, photo 360° processing, programmatic SEO and auction functionality.
Production Proof
hgvtraders.com is a commercial vehicle and HGV marketplace that MercuryMinds built and currently operates. It is the most specific production proof in the automotive marketplace space — not a case study from a client, but a platform the MercuryMinds team built, launched, operates and continues to develop.
The vehicle types on hgvtraders.com — trucks, vans, plant machinery, HGV trailers, commercial refrigeration vehicles — have data requirements that don't exist in any generic automotive marketplace platform. The specialist data schema, VIN enrichment pipeline, commercial vehicle search filters and dealer feed normalisation were all built from scratch by the same team available to your project.
Automotive Catalogue Data Services →What hgvtraders.com demonstrated
Commercial vehicle taxonomy from scratch
HGV and commercial vehicle listings require GVWR, payload, axle configuration, body type and engine hours as core fields — not optional attributes. The taxonomy and search architecture was built specifically for commercial vehicle buyers, not adapted from a passenger car schema.
What it transfers to your project
Data model, schema and VIN pipeline ready to adapt
The commercial vehicle data schema, VIN decoding pipeline, dealer feed normalisation logic and marketplace search configuration from hgvtraders.com are available as a starting reference for new automotive marketplace builds — not built from zero each time.
Intent note
We build for B2B automotive — not consumer car sales
MercuryMinds builds dealer management platforms, fleet operator portals, HGV and commercial vehicle marketplaces, and parts marketplaces. The correct target is car dealer management software — the software dealers use to manage inventory and leads. Consumer-facing vehicle sales platforms (Auto Trader, Cars.com) are a different product category.
How It Works
Four stages — vehicle data architecture to live marketplace. Schema agreed before platform build begins.
Define the vehicle taxonomy and attribute schema for your specific vehicle types — passenger cars, commercial vehicles, motorcycles, plant machinery, trailers or parts. VIN decoding source confirmed. Dealer DMS formats inventoried. Data quality requirements set. The schema is agreed and documented before any platform development begins.
Marketplace platform built to automotive spec — make/model/year/trim search hierarchy, VIN-validated listing creation, dealer portal with DMS integration, vehicle comparison tools, finance calculator integration, lead management and enquiry routing. Technology stack selected for the scale and update frequency of the inventory.
VIN decoding pipeline integrated and tested against sample dealer inventory. DMS feed normalisation built and validated against actual dealer export formats. Listing quality scoring configured for automotive-specific quality signals. Search relevance tuned for vehicle specification queries. Vehicle photography processing pipeline configured.
Initial dealer cohort onboarded with direct support — DMS connection tested, inventory normalised and validated, listings reviewed for data quality before go-live. Marketplace launched with clean, accurate inventory rather than a large volume of poor-quality listings. Growth phase supported with dealer onboarding automation as dealer count scales.
Yes. MercuryMinds builds automotive marketplace platforms across passenger cars, commercial vehicles, motorcycles, plant machinery and parts. The proof is hgvtraders.com — a commercial vehicle and HGV marketplace MercuryMinds built and currently operates. Automotive marketplace builds require specialist data architecture: VIN decoding pipeline, make/model/year/trim search hierarchy, dealer DMS integration, vehicle data quality validation and specialist schemas for commercial vehicles (GVWR, payload, body type, axle configuration). MercuryMinds designs all of these before writing any platform code — because retrofitting the data architecture after launch is always more expensive than designing it correctly from the start.
Yes. VIN data enrichment is a core automotive marketplace capability — decoding VIN numbers against NHTSA, DVLA and international databases to extract structured vehicle attributes. A standard 17-character VIN encodes the country of manufacture, manufacturer, vehicle type, restraint system, check digit, model year, assembly plant and serial number. MercuryMinds decodes this into searchable listing attributes and cross-validates against dealer-entered specs, flagging discrepancies before listings go live. Commercial vehicle VINs (HGV, trailers) are handled with additional fields: GVWR, body type, axle configuration, payload capacity. The VIN enrichment pipeline is the same one running on hgvtraders.com in production.
Dealer management software (DMS) is the platform that automotive dealers use to manage their vehicle inventory, customer records, finance applications, service bookings and sales pipeline — the operational backbone of a car or commercial vehicle dealership. Major DMS platforms include Dealer Socket, CDK Global, Reynolds & Reynolds and Keyloop. MercuryMinds builds marketplace integrations that connect to dealer DMS exports — pulling inventory, pricing and availability into the marketplace in real time without dealers needing to re-enter data manually. The dealer management portal MercuryMinds builds alongside the marketplace provides the interface for dealers to manage their marketplace presence, track leads and update inventory beyond what the DMS sync covers.
Yes — and hgvtraders.com is the production proof. Commercial vehicle and HGV marketplace builds require a data schema that standard automotive platforms don't support: GVWR (Gross Vehicle Weight Rating), maximum payload, axle count and configuration, body type (curtainsider, flatbed, tipper, box van, refrigerated, tanker, skeletal), engine hours for plant machinery, MOT and service history status, and operator licence category. MercuryMinds built this schema from scratch for hgvtraders.com and can adapt it to any commercial vehicle marketplace requirement — UK, European or US market. Fleet operator portals, HGV auction platforms and commercial vehicle dealer networks are all within scope.
Related Services
Ready to Build Your Automotive Platform?
Tell us what vehicle types your marketplace will list (passenger, commercial, HGV, plant, parts), how many dealers you anticipate, which DMS systems they use and whether you need VIN decoding, parts fitment or auction functionality. We'll come back with a scoping conversation.