The Dealer Management System (DMS) is no longer just a warehouse tool, vehicle sales orders, or service planner. Occasionally, I hear it is a good tool for printing invoices.

In fact, a modern DMS is a dealer’s Digital Asset Management platform, and dealers should treat it accordingly.

From nuts and bolts to bits and bytes

The automotive industry is shifting from hardware to software, becoming increasingly software-driven as both vehicles and their components evolve rapidly. New electronic part types and their associated data must be effectively managed and integrated into workshop processes to enable accurate repair analysis, estimation, installation, and updates.

Robust Dealer Management Systems (DMS) are continually (blindly) evolving, adding new features and adapting and fine-tuning existing processes to meet emerging automotive needs. However, the most effective DMS is streamlined and built on modular functional frameworks, allowing features to be turned on or off as needed without altering the core codebase. This ability is the difference between a “Monolithic” and a “Composable” DMS.

DMS Modularity enables dealerships to adapt quickly to an ever-changing automotive environment.

. . .

The ability to adapt quickly is the reason I want to start my next article with Heraclitus’s quote: “The only constant in life is change.”

I want to break down how a modern composable DMS must handle new “Software (Soft) Parts” using an architectural approach, so-called functional frameworks, instead of adding new fields and functions on top of the existing core layer. Let’s answer the following question.

Does tracking software parts in dealers’ inventory make sense?

Short answer: Yes, absolutely, but not in the way we track brake pads.

Vehicle Parts are no longer just physical components you can store on a warehouse shelf; they can be a line of code, a digital certificate with an expiry date, or a license key.

What do we know about software parts?

Software parts include part numbers, associated costs, retail price, essential data (digital license key, software version, or tokens), and vehicle compatibility rules.

Let’s summarize the most common Vehicle Software Parts.

Digital Key Code to unlock Feature-on-Demand (FoD)

A customer purchases a vehicle with heated-seat hardware installed, but the software required to enable it is locked. The “part” the dealer sells is the digital unlock key.

Firmware & Calibration Files

Specific software versions are required for a hardware-based Electronic Control Unit (ECU) (e.g., a transmission control module).

Cybersecurity Keys & Digital Certificates

Modern vehicles require encrypted “handshakes” to install new parts (Gateway Security). These digital certificates are consumable and must be tracked.

Update Packages (OTA Over-the Air)

Large data packages that fix bugs or add new features.

New types of vehicle software are added daily; the list of vehicle software components is dynamic. This also reflects the need for a dynamic approach to DMS management.

. . .

We can now begin with DMS and its role.

Historically, software updates were hidden in “labor hours” (the technician’s time). But if a software update adds 50hp to an electric motor, it is a product with a retail price; it cannot be handled as a service anymore. It must be in inventory to be sold.

If dealers don’t track it, they often forget to charge for it. Tracking it ensures the dealership gets paid for the value it delivers to customers. Other reasons to track software parts in DMS are Warranty & Inventory History, Software Compatibility Rules, and Security.

In detail, Software Parts are managed in DMS under a new parts category (Digital Parts) but share the same data structure as physical parts (Parts Number, Cost, Retail Price, and Vendor Information).

See a real-life example from DMS below:

Secondly, instead of a physical shelf, dealers should use a “Virtual Bin” in their “virtual warehouse “ to store licenses for deployment.

Lastly, for me, the most interesting aspect is how software components are delivered (shipped to repair orders): when a software part is “sold,” the DMS shouldn’t print a picking ticket for a warehouse runner; instead, it should trigger an API request to the software manufacturer to release the license or download token.

Two more practical examples of software parts:

A dealer pre-purchases 50 “Full Self-Driving” licenses from the OEM. These sit in a digital inventory account on the dealer’s virtual warehouse bin until sold (deployed) to customers.

Another good example is the so-called TRP Parts (Theft-Relevant Parts), which are, in fact, a combination of a physical item (a vehicle key) and VIN-specific software that unlocks the key. I named such items and the Coded Parts; the DMS must be smart enough to handle all data properly during the repair process.

. . .

Did you find it interesting to read?

If yes, please follow my next article, scheduled for publication on 31.01.2026.

In my next article, I want to continue covering software components for vehicle systems and delve deeper into DMS configuration logic, using real DMS examples.

Dr. Juraj Hanus, hanus@taxapa.com

Data Analytics & Automotive Applications Expert for Dealerships

The post Stop Giving It Away. Why Dealerships Must Treat Software Updates as Inventory appeared first on TaXaPa.

In my writing, we plan to explore the significant shift occurring in the automotive industry: the transition from traditional paper-based checklists to cutting-edge, AI-powered solutions. I will focus on three key workshop processes: reception, inspection, and pickup, and how service checklists are utilized within each.

You may find a comprehensive description of these processes in the table below, detailing their primary goals, scope of checklists, time requirements, and the various challenges that dealerships face. To illustrate this evolution, I will also explain the checklists employed at each stage, from “static” paper forms to “dynamic” digital tools and intelligent systems driven by AI and OEM telematics.

Throughout my explanation, I included my observations and insights I learned, particularly on the transformative potential of AI and smart gate technology in revolutionizing vehicle inspections and data capture, + include real examples of that checklist for a better overview.

I hope you like it. So let’s start with it.

Summary, key insights.

Automating repetitive tasks presents a significant opportunity for dealers, as it would allow service personnel to focus more intently on customer needs. AI tools, such as license plate recognition, scheduling systems, smart gates, and other digital applications, are key enablers that help workshops achieve this.

Every part of the service process, including vehicle pickup, is crucial to the overall customer experience. Dealers should not underestimate its importance and focus on details that make THE difference.

Recognizing the limitations faced by busy service advisors who can only handle a limited number of tasks, we can observe that proactive dealers have begun establishing what are known as Business Development Centers (BDCs) for their aftersales operations. All involved understand that the key is to get the FOCUS, and I learned how BDCs operate, have evolved, and expanded their scope rapidly, creating momentum to build future business. BDC is one way to go. I plan to go deeper into BDC topics in my next writing.

Initially, I wanted to give you a quick overview of the various checklists we use in the automotive world. However, as I started writing, many additional details came to mind that I couldn’t help but share with you. I genuinely hope you find it interesting, and I appreciate you taking the time to read it.

Please feel free to leave any comments, questions, or remarks here. I’ll be sure to read and respond to each one. Thank you!

Dr. Juraj Hanus, hanus@taxapa.com

Data Analytics & Automotive Applications Expert for Dealerships

Additional Details on terminology.

The term “static” means that the given report has a predefined layout and checkpoints, and does not include answers or results that suggest the next steps. On the other hand, dynamic reports are now possible due to their digital forms. Tools can automatically suggest the following steps based on the collected and recorded data. For example, a vehicle diagram is proposed automatically based on the vehicle type.

The post Shift from Paper to AI appeared first on TaXaPa.

In the automotive industry, one has various aspects to consider. For instance, handling of collision repair processes including estimating damage as well as the creation of a repair plan. In damage calculations, each requested repair can have various operations to be selected and each replaced part can easily have countless types of alternatives from different OEMs, etc.

How does one ensure that the right operation has been selected?

How can one know that all of the damaged parts where included in the estimate?

Or if any extra parts were added to damage calculations by mistake?

Without a doubt finding correct answers for such questions used to be a rigorous job for insurers. Here was the point where Damage Calculation systems could be devised and spread among insurers to produce a safe repair estimate which complies with their standards.

Audatex or Silver DAT II are two examples of Damage Calculation Systems well-used among insurers and car-dealers. Such applications enable repair facilities to provide accurate estimating of costly repairs and processioning insurance claims comfortable.

On top of that if both the DMS and the Damage Calculation System are connected via an interface, then submitting of service repairs from DMS as well as receiving accurate estimates from Damage Calculation Systems makes the claim process uncomplicated to handle for all parties.

For dealers, to better organize repair orders, for insurers to control claim process according to their standards and finally for customers to get their cars back on the road faster. This win-win situation boosts customer experience to the next level!

If you are one of the people who want to know more about that, please follow my next article related to data flow between both DMS and Damage Calculation Systems.

Looking forward to your feedback and genuinely interested in your opinion on it.

Useful links:

https://www.audatex.de/startseite/?source=post_page—–a676d1e57d40—————————————

https://www.dat.de/?source=post_page—–a676d1e57d40————————————-

Dr. Juraj Hanus, hanus@taxapa.com

Data Analytics & Automotive Applications Expert for Dealerships

The post Damage Calculation Systems and DMS (Part I.) appeared first on TaXaPa.