← All articles
November 4, 2026
Technology partners

Automotive DMS, inventory software and a trust layer: what each one does

The DMS runs the store. Inventory software prices and markets the cars. A trust layer checks the record before anyone else uses it. Here's how they fit.

Michael Cirillo
Co-founder, ÆTHR
6
MIN READ
A low stone records hall, a leaning glass tower and a colossal pentagon-shaped monolith stand on a desert plain under a clear sky. Beams of light run from the monolith to dealership screens that all show the same SUV.

An automotive DMS runs the dealership's business: deals, accounting, parts and service. Inventory software helps the team buy, price and market the vehicles. A trust layer for automotive inventory data checks each vehicle record after it leaves those systems and before websites, ad platforms and partners use it. They do three different jobs, and they work best together.

In this article

The three get mixed up all the time. A dealer hears that the DMS "has the inventory," so they assume every listing is right. A partner building a product asks which system to pull vehicles from and gets three different answers.

Each answer is partly right. Each system holds part of the vehicle's story, and none of them was built to check the record on its way out the door.

What an automotive DMS does

The DMS is the dealership's operating system. Sales, finance, service, parts and accounting all run through it, and each department writes to the same database. A finished deal posts to the books. A part added to a repair order comes out of parts inventory. Each vehicle is tracked from the day it's bought to the day it's sold, with its cost and its days in stock (Corpay).

That makes the DMS the system of record for the money. It knows what the store paid for a vehicle and whether it's been sold. It wasn't built to describe a vehicle to a shopper. Trim names, equipment and photos often live in short codes, or somewhere else.

Most of the industry's integration work starts here. STAR, the nonprofit standards group whose members include dealers, manufacturers and dealer system providers, published its Automotive Retail Domain Model in January 2026. Its stated aim is to reduce fragmentation across dealer management systems, OEM platforms and third-party applications (STAR).

What dealer inventory software does

Inventory software is where the vehicle side of the business gets managed. Used-car managers use it to appraise trades, price against the local market, track how long each unit has been on the lot and get vehicles ready to list. Merchandising lives here too: photos, descriptions and the details that end up on the vehicle detail page.

It usually pulls from the DMS and adds what the DMS doesn't hold. That makes it the place where a vehicle starts to look like something a shopper would buy.

It's still a tool for the people inside the store. It decides what the vehicle should cost and how it should look. What every other system receives is a separate question.

Where the vehicle record goes next

From the DMS and the inventory tool, the record travels. It goes to the dealer website, listing sites, ad catalogs, OEM programs, partner apps and AI assistants. Each one expects its own format and its own fields.

Google's vehicle ads are a good example. Every vehicle in the data source needs a VIN, price, condition, brand, model, year, mileage, color, an image link and more (Google Ads Help). Google also compares that data with the vehicle's page on the dealer website. Price, condition, mileage, VIN, brand and model all have to match, and vehicles get disapproved when they don't. Since April 2026, those mismatches show up as issues in the dealer's Merchant Center account (Google Merchant Center Help).

So a vehicle can be right in the DMS, right in the inventory tool and still wrong in the ad. The mileage got rounded on the way out. The price changed on the website and nowhere else. The trim code never got translated. None of those systems is broken. Nobody checked the record between them.

Stop passing bad data downstream.

What a trust layer adds

A trust layer for automotive inventory data sits after the systems that create vehicle records and before the systems that use them. It does one job: make sure what moves downstream can be trusted. For the full definition, read What is a trust layer for automotive inventory data?

It doesn't replace the DMS or the inventory tool. It reads from them, along with OEM build data and other sources describing the same VIN. When those sources disagree, it catches the conflict. It maps each record into the format each receiving system expects, fills gaps from real vehicle data and passes changes on when they happen.

Then it checks the result where shoppers see it.

How the three fit together

Each system answers a different question.

  • The automotive DMS: What did we sell, for how much, and what do we owe? Its users are the office, F&I, service and parts.
  • Inventory software: What should this vehicle cost, and how should we show it? Its users are the used-car and inventory managers.
  • A trust layer: Does every system showing this vehicle have it right? It serves every system downstream, plus the partners who build on dealer data.

For a technology partner, the difference matters. Building a separate connection to every DMS and every inventory tool means handling every format, every gap and every schedule yourself. Building on a trust layer means receiving a record that's already been checked, in the format you need. Why that matters for timing is covered in From inventory files to inventory events.

Where ÆTHR fits

ÆTHR is the trust layer for automotive inventory data. It takes in data from any number of sources, including the DMS and inventory tools a dealer already runs, and works through four stages:

  • Validate cross-references each record with OEM build and incentive data and the other sources describing the same vehicle.
  • Standardize maps every source to one consistent record and delivers it in the format each receiving platform expects.
  • Enrich adds VIN-level vehicle descriptions written from the vehicle's real data.
  • Stream delivers each record to websites, ad platforms and partners through one open API.

You can follow one vehicle through each stage in the ÆTHR engine. Prism, part of ÆTHR, then looks at what's actually live on the dealer website and pushes a fix when something doesn't match.

Dealers keep the systems they run today, with no change to how their teams work. ÆTHR also keeps a dealer-owned backup of their inventory data that they can recall, so the data isn't tied to any one vendor.

Key takeaways

  • An automotive DMS runs the dealership's business and is the system of record for deals, accounting, parts and service.
  • Inventory software helps the team price and merchandise vehicles. Neither system was built to check what every downstream platform receives.
  • A trust layer like ÆTHR checks each vehicle record between those systems and everything downstream, so partners and platforms get the same vehicle.

Next step

See what ÆTHR does for technology partners.

Sources

Michael Cirillo
Co-founder, ÆTHR
No items found.

Get Transmissions in your inbox.

New articles on inventory data, sent when they're published. No spam. Unsubscribe anytime.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

See where your own inventory breaks.

Start your free trial
No credit card required.