From Hard-Coding to Functional Frameworks: A Guide for Modern Dealerships Management

In my previous insight, I discussed how dealers shift their mindset from “nuts and bolts” to “bits and bytes” when managing electronic parts in their Dealer Management Systems (DMS). Continuing that topic of DMS architecture, I want to share a guiding principle I live by:

“The cheapest line of code is the one you don’t have to write.”

I have always prioritized configuration over custom code. During my time as a DMS product manager, I was constantly asked to add new tables, fields, or options to existing functional products. But that approach has clear limits.

Past Horror Story to Future Vision

I remember an older DMS version where we ended up creating two employee cards for the same person because we couldn’t fit all the business rules into a single one. That is no joke, we literally hit the “physical” limit of the user interface.

This absurdity is exactly what happens when you try to solve complexity by writing more code rather than building a configurable DMS that can adapt dynamically. This is the real difference between “Monolithic” and “Composable” DMS applications.

. . .

Let’s look at three practical examples of how we handle electronic software parts using old vs. new methods.

1. The Feature Request: New Part Types & Data Fields

The Old DMS Approach: Developers must write code to create a new database table for “Software Parts.” The same applies to hard-coding additional fields onto the existing parts page to make them visible.

The Modern DMS Approach (Functional Framework): The user simply configures a new “Part Attribute” named “Digital” and assigns it to an existing item class. No code is deployed; the system simply adapts.

Example: Microsoft Dynamics 365 Business Central, with the flexible “Item Attributes” feature.

2. The Feature Request: New Workflows

The Old DMS Approach: Developers write a hard-coded script (Code Unit):

“IF vehicle = EV, THEN prompt users to enter the battery level.” This script is rigid and hard to modify.

The Modern DMS Approach: Users can freely configure the user interface (page) with customizable fields. They define the required technical information steps before, during, and after vehicle repair without calling a developer.

Example: Vehicle Profile functionality

3. The Feature Request: Supplier Integration

Old DMS Approach: Developers build a custom, hard-wired file-sharing data bridge to a specific parts supplier or OEM. Now, imagine a dealer has 50+ parts suppliers using 50+ different communication methods. This is extremely expensive to maintain.

Modern DMS Approach: The DMS exposes a standard API layer that serves as a single “universal door” for potential suppliers. The supplier integrates with the framework using standard keys (credentials). The secure connection is established instantly, allowing Vehicle Software Parts Details to be shared automatically.

. . .

The Power of Frameworks

Modern DMS frameworks stand out for their ability to freely customize workflows (such as the steps needed to open a new repair order) and to automatically adjust the UI based on vehicle type and make. These features simplify DMS maintenance and help dealers expand operations more efficiently, particularly in environments with high-frequency updates or diverse dealer activities within a single DMS.

Recently, I participated in a product demo of a modern automotive DMS platform that allows users to go even deeper. They can build their own rules using visual workflow designers, dragging and dropping functional blocks to create logic like: “Trigger Battery Check Step when Fuel Type = Electric.”

Example of practical usage workflow editor designer in Microsoft Power Automate

This is currently the most advanced way to handle functional frameworks. It allows DMS to adapt to new technologies (like EVs) without touching the core code. Excellent way.

The Next Step: AI Automation

However, I believe it will go even further. While drag-and-drop is a significant improvement, I am looking forward to AI-driven automation handling this entire area.

In the near future, we shouldn’t even “draw” the workflow. The AI will analyze incoming vehicle data and automatically configure the necessary logic steps to meet the required business operations.

This is the ultimate goal: Zero code, zero friction, maximum efficiency.

Thank you for reading. Feel free to contact me if you need further assistance. When searching for a new DMS, keep in mind what you’ve learned here.

Dr. Juraj Hanus, hanus@taxapa.com

Data Analytics & Automotive Applications Expert for Dealerships