Choosing an LMS for a Dealer Network

Most learning platforms are designed for a corporate workforce: one employer, one directory, stable employment, and an HR system that knows who works there.

A dealer network is none of those things, and the mismatch is where implementations fail.

What makes a dealer network different

Multiple employers. Dealers are independent businesses. The manufacturer does not employ the technicians and has no authority over their records in the way an employer does.

No central directory. There is rarely one system that authoritatively knows who works at which dealer today.

High turnover, so the population changes continuously and joiners and leavers are the normal state rather than an exception.

People move between dealers, sometimes within a group, sometimes between groups, and their training history should follow them — which raises a real question about who owns those records.

Roles do not map cleanly. A technician at a small dealer does several jobs; the same title means different work in different places.

Franchise structure. A group may hold several franchises, so one person may need access to more than one manufacturer's content.

Poor connectivity in the workshop, and no computer at the point of work.

Language. Networks spanning markets need content and interface in several languages, and the same course in eight languages is eight things to keep in step.

The questions that actually decide it

Not a feature list. These are the ones where the wrong answer costs a year.

How do people get accounts, and who removes them?

The single most consequential question. A network of thousands of technicians with continuous turnover needs joiners and leavers handled without a central HR feed.

Options: dealer-administered accounts, with the training burden that implies; a feed from the dealer management system where one exists; or self-registration with dealer approval.

Ask specifically what happens when someone leaves. Accounts that are never removed accumulate, and in a network they accumulate into thousands of records for people who no longer exist, which corrupts every completion statistic.

Who owns the training record when a technician moves?

Ask before you need the answer. A technician moving between dealers in the same network should not start again. Between manufacturers, the answer is usually different.

And ask what a technician can take with them — increasingly a fair question and one platforms answer inconsistently.

Does it work at the vehicle?

Not "is it mobile responsive". Does it work on a phone, in a workshop, with poor connectivity, with gloves.

Does it track offline and synchronise? If not, workshop-based learning is not really supported. See mobile learning in a workshop.

What standards, which versions, and what happens to the data?

Specific versions, not "SCORM compliant". And whether xAPI is supported with a Learning Record Store, or whether one must be provided. See standards.

Then the question that is usually skipped: can you export your records, in full, in a usable form? Content portability and data portability are different. A network's training history is an asset and a compliance record, and being unable to take it out is a serious constraint discovered late.

Can dealers see what they need and nothing else?

A dealer principal needs their own people's status. A group needs several dealers. The manufacturer needs the network.

Permission structures that assume a hierarchy of departments do not fit a franchise network, and retrofitting is expensive.

Does it handle certification with expiry?

Safety-critical qualifications expire and must be renewed. See retraining for electric vehicles.

Ask: does it track expiry, notify before it, and prevent an out-of-date qualification from appearing as current. This is a records and compliance requirement, not a convenience.

Multi-language

Not just interface translation. Can one course exist in eight language versions that are managed as versions of the same course, so a content update propagates and the network can see which versions are current?

Managing them as eight separate courses is how a network ends up with the German version two revisions behind. See localising technical training.

What to ignore in the evaluation

Feature checklists. Every candidate supports every item at some level.

A demo on the vendor's data. Ask for a trial with your own content, your own account structure and a real dealer.

Total user counts. Registered accounts in a high-turnover network are not a meaningful measure.

Gamification and social features, unless you have evidence your population uses them. In workshop populations, uptake is frequently low and the features cost money.

AI features, currently attached to everything. Ask what question it answers that you have, and see it on your content.

The costs that appear later

Account administration. Someone at each dealer has to manage joiners and leavers, and that is real ongoing work for people who did not ask for it.

Content migration, if you have a library. Packages that are technically valid frequently break on transfer. See migrating courseware.

Integration with the dealer management system, if training records need to connect to workshop data — which they do if you want to measure anything. See measuring training effectiveness.

Language management, ongoing.

And the support load. A network of thousands of intermittent users generates password resets and access problems continuously, and somebody answers them.

Running the selection

Write the ten things you need it to do, in the words a dealer would use.

Trial with a real dealer, not with your own team. The people who will use it daily are the ones whose experience matters, and their objections are the useful ones.

Test the joiner and leaver process end to end.

Test the export. Actually take the data out and load it somewhere.

Ask an existing customer you found yourself, with a network of comparable size and structure.

And read the contract on data ownership and termination before signing, while you still have leverage.

The short version

Dealer networks break the assumptions most platforms are built on — multiple employers, no central directory, continuous turnover, people who move.

Joiners and leavers is the question that decides it. Accounts that are never removed corrupt every statistic in the system.

Ask who owns the record when a technician moves, and whether you can export everything.

Certification expiry is a compliance requirement, not a feature.

Trial it with a real dealer, and test the export before you sign rather than when you leave.

For public specifications and background on interoperable learning systems, see ADL SCORM project.