Equipment dealers: what manufacturer dealer agreements say about your data

Who controls the data an equipment dealer creates?#

An equipment dealer generally creates and holds its own sales, parts and service records, but control over that data is shared through the dealer agreement, the DMS contract and the manufacturer's portal terms. Dealer agreements may give the manufacturer broad rights to receive and use dealer data, and some say more about ownership than dealers remember signing.

Three kinds of data need separate answers. Dealer-created records, such as work orders, invoices, quotes and rental contracts, usually start with the dealer. Manufacturer content, such as service manuals, bulletins, parts catalogs and diagnostic software output, starts with the OEM. Machine data from connected equipment usually sits on the OEM's telematics platform under terms with the end customer.

Dealer agreement clauses that decide what you can license#

Dealer agreement clauses that decide what you can license are spread across the main agreement, its schedules and the policy and warranty manuals it incorporates. The table lists the ones to find and how each tends to affect licensing; the effect in your case depends on the exact wording.

DMS contracts and OEM portals add a second layer#

DMS contracts and OEM portals add a second layer of terms that apply even when the dealer agreement is silent. The dealer management system license sets how data can be exported, whether bulk extracts need the vendor's help, and whether the vendor claims rights to usage data. Read its data, confidentiality and termination sections before planning any export.

OEM portals for warranty, parts ordering, technical support and telematics are licensed to the dealer for running the dealership. Data pulled from those portals, including fault code descriptions, repair procedures and machine histories, is usually governed by the portal terms rather than owned by the dealer. Keep portal content out of scope unless the OEM agrees in writing.

Service records: the strongest dataset and its limits#

Service records are an equipment dealer's strongest dataset because they capture how technicians diagnose and repair real machines in real conditions. A work order that records the customer's complaint, the technician's cause and correction notes, parts used, labor time and whether the machine came back tells the story diagnostic and service AI tools need.

Those same records carry content that is not the dealer's to license. Technician notes may quote OEM procedures or bulletin text, warranty claims include the OEM's adjudication codes, and serial numbers can link to telematics data held by the OEM. Preparation removes or generalizes that content while keeping the dealer's own diagnosis and outcome.

• 1Keep: complaint, cause and correction notes written by your technicians.
• 2Keep: parts used, labor operations and comeback or repeat-repair flags.
• 3Generalize: model and serial numbers where they could identify a customer's fleet.
• 4Remove: text quoted from OEM manuals and bulletins, and portal screenshots.
• 5Remove: customer names, operator names, jobsite addresses and contact details.

Customer data and machine telematics#

Customer records usually start with the dealer but carry confidentiality and privacy limits, while machine telematics usually is not the dealer's to license at all. Account names, contacts, fleet lists and rental histories describe customers with confidentiality expectations, and individual contacts are personal data, so those details are removed or replaced with codes before any outside use.

Telematics data from connected machines is another matter. Hours, locations, fault codes and usage patterns generally flow to the OEM's platform under terms between the OEM and the machine owner, and the dealer sees them through OEM access. A dealer rarely has the right to license that data, even when it can view it. Rules and public debate on equipment data access continue to change, so check current requirements with counsel rather than assuming.

Illustrative: a multi-store dealer reads its agreements first#

Illustrative: a fictional dealer with several stores sells and services compact construction and agricultural equipment for one main manufacturer and a few short-line brands. It runs a DMS for parts, service and rentals, and uses the main OEM's portals for warranty and telematics.

Before any talk of licensing, the dealer's general counsel reads the main dealer agreement, its warranty manual and the DMS contract. The dealer agreement requires extensive reporting but leaves dealer records with the dealer. The portal terms limit portal data to dealership use. The DMS contract allows exports of the dealer's own data. One short-line agreement states that the manufacturer owns all service data for its products.

The dealer scopes a package of work orders for the main brand and the other short lines, removing OEM text, portal content and customer details. The short line that claims ownership is excluded, and telematics stays out entirely. The dealer principal approves the scope before a fit check begins.

How SourceX handles records with several rights holders#

Equipment dealer records usually have several rights holders, so SourceX sorts them before anything else. In the Rights step of the SourceX five-step transaction (Supply, Rights, Preparation, Approval and Delivery), counsel reads the dealer agreement for each brand, the warranty and policy manuals it incorporates, the DMS contract and the portal terms, and tags each record family as dealer-controlled, shared or OEM-controlled.

That sorting goes into a SourceX Evidence Packet for each package, so the OEM-related exclusions sit in one place next to provenance, licensing rights, permitted use, the privacy record and release authorization. The first fit check collects metadata only, the dealer keeps ownership of its records, and data is licensed, not sold outright.