Service History Portal for Equipment Dealers
By MDMS Team · 18 November 2026

Service History Portal for Equipment Dealers

A service history portal is a secure online view of everything that has happened to a machine: every job, part, warranty claim, rental and invoice, tied to its serial number. For an equipment dealership, the portal works best when it is not a separate tool. It should be a window onto the same dealer management system (DMS) your workshop, parts counter, rental desk and finance team already use, so the history is written once, as the work happens. We build MDMS that way, and we have added AI on top so staff can find the right record faster.
This guide is for dealership owners and department managers. It covers what a portal holds, how staff and customers use it, how it links to accounting and ERP data, where AI helps, and what to settle before you roll one out.
TL;DR
- A service history portal gives staff and customers a searchable record per asset: jobs, parts, warranty, rental and invoices, all keyed to the serial number.
- It is only as good as the data behind it. A portal fed by the same system that runs your work orders stays complete without double entry.
- AI adds the most value at retrieval and admin: finding the right asset, summarising a history, and drafting job notes from records that already exist.
- Settle access levels, data ownership and security before launch, because service records contain customer personal information.
- MDMS modules start at 59 AUD per month each, and MDMS AI is 449 AUD per month with seats at 29 AUD per month.
Table of Contents
- What a service history portal is, and what it holds
- Why a standalone portal falls short
- How a portal supports each department
- How staff find the right asset quickly
- Where AI fits in a DMS and ERP
- Customer self-service: what to put in front of customers
- Access, data ownership and security
- Rolling it out without disrupting the workshop
- What MDMS offers for service history
- Our view: history is the asset, AI is the lever
- FAQ
- Sources
What a service history portal is, and what it holds
The phrase covers two things, and dealerships usually need both.
An internal view for your team. A service manager, parts interpreter or rental coordinator searches a machine by serial number, customer or unit number and sees its full lifecycle: when it was sold or commissioned, every work order, parts fitted, warranty claims, hours at each service and any rental periods.
An external view for customers. The customer logs in and sees their own fleet: past services, upcoming maintenance, invoices, and a way to request work or order parts.
Manufacturers already run portals of this kind. DEUTZ’s Australian service portal lets customers register an engine and track what happens to it, and customers can register the engine serial number when they buy a new engine. The same announcement says the portal lets customers connect with a local service partner and buy spare parts online, while dealers can receive parts orders around the clock. That is a useful picture of the scope: history, parts and service requests sit in one place.
For a dealership, the records worth holding against each asset are:
| Record | Why it matters | Who uses it |
|---|---|---|
| Serial number, model, build and commissioning details | Identifies the machine and what was fitted at handover | Sales, service, parts |
| Work orders, labour and technician notes | Shows what was found, done and recommended | Service, customer |
| Parts fitted and part numbers | Lets the counter quote the right part first time | Parts, service |
| Warranty claims and recovery status | Keeps claim evidence with the machine | Service, finance |
| Maintenance contract and schedule | Drives the next service and recurring revenue | Service, customer |
| Rental periods, returns and damage checks | Separates rental wear from customer-caused issues | Rental, finance |
| Invoices and payments | Links the history to the ledger | Finance, customer |
Why a standalone portal falls short
Many dealerships first try a portal as a bolt-on: a spreadsheet, a shared drive, or a customer website fed by manual exports. The problem is what happens at the workshop bench. If a technician finishes a job, the office keys it into the accounting package, and someone else updates the portal later, the history is always a step behind and sometimes wrong.
Three failure patterns show up again and again:
- Gaps. A job done in the field never reaches the record because it lived on a paper job card.
- Duplicates. The same machine appears under two customer names or two spellings of a serial number.
- Stale data. Parts fitted and hours at service are entered days later, so the next quote is built on guesswork.
The fix is structural, not a matter of discipline. Data should travel once: captured at the point of work, then reused by the portal, the invoice and the warranty claim.
How a portal supports each department
Service and field service
The technician opens the job, sees the machine’s prior history, records findings and parts, and closes the job. A paper process is slow and error-prone, and SAP’s 2024 Weir Minerals case says digital service notes improved the availability of service information to staff and customers and avoided time-consuming, error-prone paper processes. Our service management software and field service software are built around that same idea, and the mobile app is offline-capable, so a job on a remote site still lands in the record.
Parts
A parts interpreter who can see which parts were fitted to a serial number quotes faster and makes fewer wrong-part returns. History also shows what a machine will likely need next. See how this works in our parts management software.
Rental
Rental units are the machines whose history changes fastest. Pickup and return condition, hours used, and service between hires all belong on one timeline. Our rental contract and fleet software keeps rental contracts and fleet records together with workshop history.
Finance
Warranty recovery and job costing depend on the history being right. When the record, the invoice and the claim share one source, finance does not rebuild the story from emails. MDMS integrates with Xero and MYOB and handles Australian GST, so the same job that builds the history also feeds the ledger.
How staff find the right asset quickly
Speed of lookup decides whether staff use the portal or go back to asking the longest-serving technician. A good search should work from whatever the caller gives you:
- Serial number or unit number, the most reliable key.
- Customer name, returning every machine linked to that account.
- Job or work order number, when the customer quotes an invoice.
- Model or part, to find every unit that might share an issue.
Test the setup with real calls. Pick five machines of different ages, then time how long it takes someone to find the last three jobs, the parts fitted and the warranty status on each. If it takes more than a minute, the data is split across places or the search is weak.
Where AI fits in a DMS and ERP
AI in dealer software is most useful where records are plentiful and time is short. Because a DMS or ERP already holds structured history, an AI layer can work with real data rather than guessing. The practical uses for a service history portal are:
- Retrieval. Ask a plain question such as which units are due for a 500-hour service, and get an answer from the records instead of building a report.
- Summaries. Condense a long job history into a short briefing before a technician goes on site or a service manager calls a customer.
- Admin drafting. Turn technician notes into a clear job description or customer message, so staff review rather than write from scratch.
- Cross-department visibility. Surface the link between a warranty claim, the parts used and the rental history of the same machine.
The condition is the one above: AI is only as reliable as the records beneath it. That is why the order matters. Get the history captured cleanly in one system, then add AI to use it. In MDMS, the AI option is MDMS AI at 449 AUD per month, with AI-enabled users at 29 AUD per month per seat, so you can switch it on for the people who benefit most, such as service managers and parts leads, rather than the whole team.
Whatever AI you use, keep a person accountable for the output. A drafted job note or a summary should be checked by the technician or manager before it reaches a customer or an invoice.
The same logic applies to ERP data
The Weir Minerals case describes integration between SAP ERP and SAP Field Service Management that enabled digital service-history reporting and centralised, real-time data collection. The lesson for a dealership of any size is not the brand of software. It is that service history, inventory and finance should sit in connected systems so that a number entered in the workshop is the number finance sees. MDMS covers general ledger and operations, procurement, supplier management and AP alongside service and parts, so the history is joined to cost and margin.

Customer self-service: what to put in front of customers
A customer portal reduces inbound calls and lets customers order parts outside business hours. Start with a short list of things customers ask for most:
- Service history for each of their machines.
- Upcoming maintenance due, based on hours or dates.
- A form to request a service or book a job.
- Parts ordering linked to the machine.
- Invoices and statements.
We cover the commercial side in our guides to a customer service portal for equipment dealers and a service booking portal. Maintenance agreements fit naturally here too: see maintenance contract software.
Access, data ownership and security
This is the part dealerships skip and later regret. A service record names customers, sites and sometimes contacts, so it is personal and commercial information.
Access levels. Decide who sees what before launch. A typical split: technicians see their jobs and the machine history; parts staff see parts and pricing; finance sees costs and claims; customers see only their own assets and invoices. Review access when people change roles or leave.
Security. Under Australian privacy law, the OAIC’s guidance on APP 11 says an organisation must take reasonable steps to protect personal information from misuse, interference, loss and unauthorised access, and to destroy or de-identify it when it is no longer needed, unless a law requires you to keep it. Whether the Privacy Act applies to your business depends on its size and activities, so ask your lawyer or accountant if you are unsure.
Data ownership. You should be able to take your records with you. With MDMS you keep complete ownership of your data with no lock-in, which matters because service history is an asset that builds value over years.
Completeness. Set a rule that no job closes without the serial number, hours and parts recorded. Mandatory fields at job close do more for record quality than any later clean-up.

Rolling it out without disrupting the workshop
You do not need to switch everything at once. Pick the department with the most pain and start there:
- Choose the first module. Service workshop is the usual starting point because it generates most of the history. MDMS is modular, so you can add parts, rental, warranty and finance later.
- Load your existing data. Customers, machines and past jobs make the portal useful on day one. Our data upload service is 259 AUD one-off per module.
- Train the team. A training package is 499 AUD one-off per module.
- Switch on the customer view once staff trust the records.
- Add AI when the history is clean enough to be worth summarising.
Setup of the platform itself takes under an hour, and contracts are monthly rolling, so you can test it on a real workload before widening it. For a larger rollout, white-glove implementation is 39,950 AUD one-off.
What MDMS offers for service history
If your service history lives in job cards, spreadsheets and one person’s memory, the Service Workshop module is the place to start, at 59 AUD per month. It sits with the rest of the platform: parts, rental, warranty, customer portal and finance, each also 59 AUD per month, with the General Ledger & Operations module and the Equipment Dealer Suite at 259 AUD per month each. You can see the full list on our pricing page, and the wider equipment dealer platform shows how the modules connect. There is a free trial.

For the history to be useful across the business, pair the workshop with the asset lifecycle view, so every machine carries its story from sale to service to resale.
Our view: history is the asset, AI is the lever
We think of a service history portal as a by-product of doing the work well, not a project of its own. When a technician closes a job, the machine’s record, the customer’s invoice, the warranty claim and the ledger entry should all be created by that one action.
That is why MDMS is one platform for sales, service, parts, rental and finance, with modules you adopt as you need them. The portal is a view onto data you already capture, and you own that data.
AI follows the same rule. We built MDMS AI to work with the records in your system, so a service manager can ask a question and get an answer from the machine’s own history. It is available per seat, so you can give it to the people who spend their day searching and writing.
Start with the department that hurts most, get the records clean, then widen. That order is how dealerships save the admin hours, and it is the one we recommend.
ModernDMS
FAQ
Can customers view their equipment service history online?
Yes, through a customer portal linked to your DMS. Each customer logs in and sees only their own machines, with past services, upcoming maintenance and invoices. In MDMS this is the Customer Portal module at 59 AUD per month.
How do staff view service history by serial number?
The serial number is the best search key because it is unique to the machine. In a DMS, searching it should return the full timeline: jobs, parts, warranty and rental. If your team cannot do that in a few seconds, the records are probably split across systems.
Does a service history portal need to connect to my accounting software?
It should. Invoices, parts costs and warranty recoveries all affect the ledger, and re-keying them invites errors. MDMS integrates with Xero and MYOB and handles Australian GST, so jobs flow through to finance.
What does AI add to a service history portal?
AI makes existing records quicker to use: finding units, summarising a machine’s history and drafting job notes for review. It depends on clean records, so capture history in your DMS first. MDMS AI is 449 AUD per month, plus 29 AUD per month per AI-enabled user.
Who owns the service records?
Your dealership should. Choose software that lets you keep and export your data. With MDMS you have complete data ownership with no vendor lock-in.
Sources
- Introducing S-DEUTZ: A New Dimension of Service (DEUTZ Australia)
- Weir Minerals: Digitalizing customer service execution (SAP, 2024)
- Chapter 11: APP 11 Security of personal information (OAIC)