Custom workshop software development for heavy equipment
A workshop that repairs trucks, trailers, earthmoving equipment, agricultural machinery or forklifts for customers doesn't deliver a product but decisions: what is wrong, what will it cost, who approves it and what goes on the invoice. Maintenance packages assume you are maintaining your own equipment and have no approval step. Appfront builds software in which the work order is the core, with extra work, parts, warranty claims and inspections built around it.
Work for customers is different from maintaining your own equipment
Maintenance software is built around ownership. You manage your own machines, plan preventive maintenance and steer on availability and costs. Nobody needs to give permission, because you are owner and client at the same time. If that describes your situation, you want building maintenance software.
A workshop that works for third parties has an extra layer: a job with an agreed scope, a customer who approves or declines, an invoice and liability for work on someone else's equipment. Every action a mechanic takes is therefore both a technical record and a commercial line item. If you mainly repair passenger cars and vans, garage software is a better fit.
Within that customer base, two kinds of relationship also run side by side. The one-off customer arrives with a fault, wants to know what it will cost and pays on completion. The fleet customer works under a framework agreement: agreed prices per task, parts discounts, a manager who signs off on behalf of several branches and often a requirement that every job carries a purchase order number. If that number is missing, the invoice stays unpaid, however good the repair was. Software that only knows one-off customers forces your back office to apply those agreements by hand, and that is where mistakes creep in.
The second difference lies in where the history ends up. It seems logical to attach the history to the customer, since they pay the bill. For heavy equipment, that is the wrong axis. A tractor unit changes hands, a trailer is resold, and the question that matters then is not who paid for it but what has been done to this particular unit. If the history is tied to the invoice address, the record breaks after a sale. If it is tied to the chassis or serial number, it stays complete.
The customer has to say yes
Without a recorded approval, extra work is not revenue but an argument after the fact. Approval should be a process step, not a note.
The equipment isn't yours
The history belongs to the machine, not to your administration. If the asset is sold, the record moves with it.
Everything you touch is a line item
Hours, parts, call-out charges and environmental fees all belong on the same work order. Whatever isn't on it won't end up on the invoice.
The work order is the core, from report to invoice
It rarely starts neatly. A driver phones in from the road, a fleet manager emails a list, a contractor sends a photo of a leak. The system's first job is to link that report to an asset: registration number, chassis or serial number, with the odometer reading alongside. Without that anchor, the repair ends up in a customer file instead of in the machine's history, and it becomes impossible to trace later what happened to this particular unit.
That intake step also involves a few questions that determine everything later. Who is reporting, and are they authorised to give instructions? Where is the vehicle: on your premises, at the customer's site or by the roadside? Is it still drivable, or does transport need to be arranged? Does this fall under an existing contract, under warranty or under neither? If those answers stay behind on the phone call, the planner has to work them out again before anything can be scheduled. An intake screen that enforces those fields saves the rest of the chain a string of follow-up queries.
Next comes the diagnosis, and two things need to be kept separate there: what the customer reported and what the technician found. The customer says the machine vibrates; the technician reads out a fault code and finds a worn bearing. That separation between complaint, cause and repair is not academic. Manufacturers ask for it explicitly in warranty claims, and it is the only way to see which faults keep coming back.
That diagnosis also comes with a pile of data that exists nowhere else. Diagnostic software differs by brand and delivers fault codes in its own structure. The technician measures play, pressure or wear and notes values on which a later judgement rests. They take photos of the finding, because a cracked bracket in a photo is stronger than three lines of text. If those findings end up in loose folders and WhatsApp messages, they exist, but not when someone needs them. If they are attached to the work order line, they travel along with the approval, the invoice and any claim.
Then comes approval, execution and invoicing. These flows overlap: part of the job falls under the manufacturer's warranty, part under a maintenance contract, and part is for the customer's account. A system with only one invoice recipient per work order forces your administration to split things by hand.
The additional work moment
The technician is under a trailer preparing it for inspection and sees that the brake discs are worn out. That wasn't in the order. Carrying on without approval produces a line the customer can refuse; waiting means a occupied bay and an idle technician. It usually gets resolved with a phone call that nobody records, after which the argument moves to the invoice. What software needs to do here is small and concrete: the technician creates an additional work line with a photo, a description and the expected hours and parts, the customer approves or rejects it, and the system records who approved it and when. Only then does the line flow through to planning and invoicing.
The real problem is the waiting. The customer is in a meeting, the manager is on leave, the owner wants to come and take a look first. Meanwhile the vehicle is sitting on a bay you still needed that day. A system that takes additional work seriously therefore gives the work order a waiting status that is visible in the planning, so the work planner can see that this slot is not moving on. Many companies also agree with regular customers that the technician may carry on with minor findings as long as he records them. An arrangement like that belongs in the system, per customer or per contract, not in the workshop manager's head.
What the customer sees during the repair
When you carry out repair work, customer communication is not an afterthought; it is where you stand out. The customer isn't standing next to the lift. All he knows is that his machine is with you and he can't use it. Every hour without news he fills in himself, usually pessimistically, and at some point he phones. That call costs your front desk time and rarely gives him more than a status the system already knows.
The set-up that works is simple. When the mechanic makes a finding, he takes a photo with a short explanation, and both go to the customer as a proposal. The customer approves or declines digitally, with his name, the time and the exact lines he signed for all recorded. He also sees a status for each vehicle that moves along with the job: received, in diagnosis, awaiting your approval, awaiting a part, in progress, ready. That is the same information your planning board already keeps, just turned outwards. For a fleet manager with vehicles at several workshops, that is the difference between phoning and looking.
Two things deserve attention here. The first is access: a fleet manager sees all the vehicles of his company, a driver only his own, and a machine that has been sold disappears from the previous owner's view. The second is that the status is tied to a real event, such as the goods-in booking of the part, and not to a field that someone has to update by hand.
The invoice that falls apart
At the end of a repair on heavy equipment, there is rarely a single invoice with a single recipient. Part of the work falls under the manufacturer's warranty and goes to the importer. Part falls under a maintenance or repair contract and is charged according to the framework agreement. Part is damage and goes through an insurer, sometimes with a loss adjuster in between and an excess that stays with the customer. And part is simply for the customer himself. On top of that, this split only becomes clear while the work is under way, because the mechanic doesn't yet know which cause he will find when the order is opened.
That places a hard requirement on the data model: the destination belongs to the line, not to the order. Every labour line and every part line carries its own recipient, so a work order can split into several documents without double entry. If a claim is rejected later, that line must be able to change destination, with a record of who decided it. For insurance work, the supporting evidence is attached to those same lines: photos of the damage, the claim form and the assessor's report.
Lifts, pits and mechanics who aren't interchangeable
A heavy equipment workshop schedules two scarce things at once, and most systems only know one of them. The first is the location. A four-post lift for a tractor, a pit you can stand in under a trailer, a bay high enough for a fully extended crane arm: these are not interchangeable slots. A repair that needs a pit can't be done on a lift just because there happens to be room there. The second is the person: the mechanic who knows this make's driveline, the electrician who reads out a crane's control system, the certified inspector.
As long as the schedule is a list of names and days, this works fine as long as the workshop manager is there. He knows which spot is suitable for what and who can do what. If he drops out, or the company grows to a second site, it turns out that this knowledge is written down nowhere. The answer isn't a complicated algorithm but recording attributes: for each workstation what it can handle, for each mechanic which qualifications and makes he has, for each job what it requires. After that, the system only has to refuse what isn't possible. That is more useful than automatic scheduling, because the planner knows the exceptions better than a calculation model does.
The vehicle standing idle, waiting
The most expensive thing on your site is a vehicle that occupies a bay while nobody is working on it. Usually it is waiting for customer approval, for a part on order, or for a technician who is only available tomorrow. All three are known in the system, yet nobody sees them together: the planner looks at his board, the stores manager at his orders, the front desk at the outstanding approvals.
What fixes this is a work order that carries its own waiting reason and passes that reason on to the planning. An order waiting for a part should automatically become schedulable again the moment the goods receipt is booked, not when someone happens to walk past the stores. An order waiting for approval should release its bay. And when a vehicle stays for a long time, someone should be asked whether it would be better off waiting outside until the part arrives. That is not software taking over the work; it is software that makes visible what is currently going wrong unseen.
Managing lead time, first time fix and utilisation
Once the work order knows those statuses, a management tool emerges almost for free. Lead time becomes measurable as the difference between arrival and completion, split into the time actually worked and the time the vehicle spent waiting. That distinction is the whole point: a customer experiences the waiting time, while your quote only looks at the hours worked. See both side by side and it becomes clear whether your problem is capacity or logistics, and those are two very different investments.
First time fix is the second: how many jobs were completed in a single visit, without the vehicle having to return or the technician having to drive out a second time. For field service work, that is the most expensive form of rework, because you pay for the trip twice and the customer notices. The cause almost always lies in a missing part or an incomplete diagnosis beforehand, and both become visible as soon as the work order records why a visit was not completed. The third is utilisation. Here too, the figure is worth less than the breakdown beneath it, because waiting for parts calls for something different from having too little work.
- Workstations with attributes, not interchangeable slots
- Qualifications, brands and certificates recorded per technician
- Waiting reason on the work order: approval, part or capacity
- Order schedulable again as soon as the receipt is booked
- Lead time split into worked time and waiting time
- First time fix with the reason a visit did not succeed
- Utilisation per workstation alongside utilisation per technician
What workshop software for heavy equipment needs to do
These components are interconnected: a work order without an approval step leads to disputes, parts registration without an asset file makes a warranty claim impossible to prove, and a schedule without waiting reasons hides precisely the hours you are losing.
Complaint, cause and repair
What the customer reported, what the technician found and what he did, recorded separately and invoiceable or claimable per line. Fault codes, readings and photos are attached to the line they belong to.
Additional work with recorded approval
An additional line with a photo and explanation, which only flows through to the schedule and invoice after the customer has approved it digitally. Who signed and when is on record.
Asset file per machine
Chassis or serial number, meter readings, repairs, fitted parts and inspections, permanently linked to the asset rather than the billing address, so the file survives a sale.
Stock in the van and in the workshop
Each service van as its own location, with issue on the work order line, replenishment from the warehouse and a reservation on the order the part was ordered for.
Warranty claims per brand
Build claims from the work order, with the brand fields the manufacturer requires, and track them until the credit note arrives or the rejection is explained.
Inspections and certificates
Track deadlines, keep evidence attached to the asset and show it the moment an inspector asks, without anyone having to dig through a folder.
Parts, the service van and the mechanic without signal
Your stock sits in more places than the warehouse. Every service van is a location of its own, with filters, hoses, oil and wear parts. The mechanic grabs a filter set on the way, fits it and drives on. If that issue isn't tied to a work order line, the part doesn't end up on the invoice, the van isn't restocked and the count no longer adds up. Scanning in the van, linked to the active order, is therefore the foundation.
That sounds obvious, but it isn't, because the van is a workplace where scanning competes with dirty hands, rain and time pressure. A solution that only works on paper doesn't get used. What does work: a short list of what should be in this van, issuing in two steps on the phone, and replenishment that kicks off automatically as soon as stock drops below the agreed level. Stocktaking then becomes a check rather than a reconstruction.
The parts flow also has its own quirks. Some ordered parts are reserved for a specific order and can't be used freely, even though they sit on the shelf. There are exchange and remanufactured units, where the old part has to be returned before the settlement is complete, so it needs its own status and location. There are part numbers that fit several machines but differ by year of manufacture, with all the risk of ordering the wrong part. More on this under service parts software.
When the part isn't there
The interesting moment isn't the issue but the absence. The part isn't in the van or the warehouse, and there are four routes: it's with a colleague in another van, it's at the other branch, it can come from the importer, or it will take longer and the machine needs something in the meantime. If you don't have those routes in view, you pick the most expensive one: order and wait.
Software helps here by showing stock across all locations at once, vans included, and by linking the order to the work order rather than to a separate purchase document. That way everyone knows why this job is stalled and when it can continue. What happens to the vehicle while you wait is just as important. If it's put outside, someone needs to record that it's been taken apart and which loose parts belong to it. That is information that now lives in a mechanic's head and disappears the moment he takes a week off.
Integrating with manufacturer and supplier catalogues
A heavy equipment workshop rarely works with just a handful of suppliers. There's the importer with its own catalogue and part numbers, there are general suppliers for filters, brake parts and lighting, and there are specialists for hydraulics or electrical systems. Each party delivers availability and supersession numbers in its own form, from a neat file format to a portal where someone searches by hand.
The gain from an integration lies less in ordering than in looking things up. A mechanic who opens the right catalogue for this chassis number straight from the work order picks the wrong number less often than someone working from memory or an old invoice. On top of that, supersession numbers are only usable if they arrive automatically; manually maintained lists fall behind. If you build it yourself, the question of how to handle changing integrations should be on the table early, because every supplier changes its format sooner or later.
Working without signal
Then there's the engineer out in the field. On a building site behind a dyke or at an agricultural contractor's yard out on the polder, the signal drops out. An app that sends every action straight to the server grinds to a halt, and the engineer falls back on paper that is retyped later. If the app works locally, he can complete the job sheet, take photos, log hours and parts and have the customer sign, and everything syncs as soon as there is a connection. The tricky part is what happens next if the planner changed the same order in the meantime. See also building a field service app.
So working offline isn't a switch you flip on, but a choice that affects how the whole app is built. The data the engineer needs has to be on the device beforehand: today's orders, the associated asset records and the stock in his own van. And merging needs a rule that everyone understands: the hours and parts the engineer logged win, because he was there, while changes to scheduling and customer details come from the office. Anything outside that belongs on a list that someone actually looks at, rather than quietly disappearing.
- Every service van as its own stock location with its own standard stock level
- Issuing always against a work order line, in two steps
- Stock across all locations and vans in a single search
- Special-order parts reserved on the order they are for
- Returns flow and status for exchange and refurbished units
- Catalogue and replacement part numbers from the source, not by hand
- Job sheet, photos, hours and parts that work without a connection
- An explainable rule for conflicts during synchronisation
Test your idea first: a working prototype in 1 day
With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.
View OneDayBuild →Warranty claims and inspections, and why they take so much effort
A warranty claim isn't a copy of the work order but a second administration of the same repair. Every manufacturer has its own portal, its own coding for cause and operation, its own requirements for photos and diagnostic data, its own submission deadline and sometimes an obligation to keep the faulty part. The engineer writes down in his own words what he did, and someone in the office translates that afterwards into the codes the brand expects. That is where claims fall through: a missing photo, a wrong cause code or a deadline that has just passed. Until the claim is paid, you bear the costs yourself.
Software removes that manual work by asking for the brand-specific fields during the repair itself. If the system recognises that the asset is under warranty, it immediately shows the right pick lists and mandatory photos, and blocks completion until they are provided. After that, the claim is simply a status you track until the credit note arrives.
There is a second layer underneath. A claim isn't finished when it is submitted, but when it is settled, and until then the work sits in your books as something you are still owed. A claims overview that shows per brand what is open, approved or rejected is therefore not reporting for later but day-to-day management. When a claim is rejected, the reason should be stored in a usable form: missing photo, wrong coding, outside the deadline, or not accepted on its merits. After a while you can see which share of the rejections is down to your own process and which to a brand's policy.
The customer's side needs to be visible too. If warranty work runs through customer work, they receive an invoice for something they thought was covered, and that conversation costs more than the line is worth. A system that shows per line who the recipient is lets you explain it upfront instead of defending it afterwards.
Statutory inspections and the file
Inspections demand something different: a file that survives an audit. For motor vehicles and trailers over 3,500 kg, an inspection certificate under the Besluit voertuigen (Dutch Vehicles Decree) is valid for one year, and that obligation only starts a year after first registration. Under the Regeling voertuigen (Vehicles Regulation), the tachograph installation plaque may be valid for a maximum of 24 months. For work equipment such as vehicle lifts, cranes and forklift trucks, the Arbeidsomstandighedenbesluit (Working Conditions Decree) applies: Article 7.4a requires inspections to be carried out by a competent person, and the written evidence to be kept at the workplace and shown to the inspectorate on request; Article 7.20 requires lifting and hoisting equipment to be examined at least once a year. Attach the deadline, the inspector and the supporting document to the asset and you can produce it on demand, without anyone digging through a binder.
The practical side of this is scheduling. An inspection is an appointment with a final deadline, and a customer who presents their vehicle too late has a problem you could have seen coming. If your system knows the next due date for every asset, inspection work becomes predictable work that you can use to fill quiet periods. The same goes for your own vehicle lift, crane and lifting gear, which belong in the same overview.
The history belongs to the machine, not the invoice
Everything above comes together in one file per asset. With heavy equipment that is worth more than elsewhere, because the machines last a long time, change hands and need more work as they age. An excavator with a complete, traceable file is a different proposition from the same machine without paperwork, and that difference also counts when your customer sells it.
Technically, the requirement is simple and easy to get wrong: repairs, fitted parts, odometer readings, inspections, claims and photos are attached to the chassis or serial number, and the owner is a piece of data that changes over time. When a machine is sold, the file moves with it, whereas the previous owner keeps their invoices but no longer has access to the technical history. That choice is hard to fix afterwards, because by then you have spent years attaching data to the wrong axis.
This set-up also reveals patterns. Which fault occurs more often on this type after a certain odometer reading, which parts do you routinely replace on the same year of manufacture. That is the basis for targeted maintenance advice, and so for work you plan yourself.
When an off-the-shelf package is the better choice
The workshop is not a blind spot in the software market. There are mature packages for truck dealers, equipment companies and agricultural machinery, with work orders, hours, parts and invoicing in proven form. If you work as a brand dealer, part of your chain may already be fixed because the importer prescribes how claims are handled. So for some readers, a package is the wiser route, and we would rather say so now than halfway through a quote process.
If your process follows the usual pattern of report, work order, hours, parts and invoice, you buy that off the shelf, including maintenance and updates for changing regulations. Your effort shifts from building to configuring.
Custom software pays off in fewer situations than suppliers suggest. The strongest reason is a chain that no single package covers in full: workshop, field service and rental of the same equipment, where a machine is on hire today and on the lift tomorrow. The second is an approval flow that works differently, with framework contracts, mandatory purchase order numbers or a fleet manager who signs on behalf of several branches. The third is a package that does not recognise the service van as a stock location.
The downside comes with it: if you build your own, keeping up with changing regulations and brand portals is down to your own organisation. Often the middle route is the best answer: a package as the core, with custom software for the field service. If your focus is on tractors and implements, see agricultural machinery software.
If you run an agricultural machinery fleet with fault reports from the cab, take a look at our app for managing agricultural machinery.
If it is about the cubic metres the machines move and how they are settled, take a look at our app for quantity take-off in earthworks.
If you are a bodybuilder or vehicle fitter and chassis too often sit waiting for a drawing, take a look at our app for commercial vehicle body orders.
- Off-the-shelf package if your process follows the standard workshop pattern
- Off-the-shelf package if the importer already prescribes the claims route
- Custom software for workshop, field service and rental in one chain
- Custom software when van stock or a variation agreement is missing
- A middle route: a package as the core, custom software for field service
Frequently asked questions about workshop software
Maintenance software is built around ownership: you schedule maintenance on your own machines and manage availability and costs. Working for third parties adds a commercial layer: a job with an agreed scope, a customer who has to approve it, an invoice, and liability for work on someone else's equipment. That approval step is missing from most maintenance packages.
By making approval part of the work order instead of a separate phone call. The technician creates an extra-work line with a photo, a short description and the expected hours and parts. The customer approves or rejects it. The system records who approved and when, puts the line on the invoice, and shows the status to planning and the technician.
That is a design decision you make up front. An app that sends every action straight to the server grinds to a halt as soon as signal drops in a warehouse, a basement or out in the field. If the app works locally, the technician can fill in the job sheet, take photos, log hours and parts and get the customer's signature, and everything syncs once there is a connection. The difficulty lies in conflict handling when the planner has changed the same order in the meantime.
Because the claim requires different data than the work order. Every brand has its own portal, its own coding for cause and repair, its own requirements for photos and diagnostic data, its own submission deadline and sometimes an obligation to keep the faulty part. The technician writes in his own words, so someone has to translate that afterwards. A system that asks for those brand-specific fields during the repair removes that manual work.
By attaching the deadline and the evidence to the asset rather than to a calendar. For motor vehicles and trailers over 3,500 kg, an inspection certificate is valid for one year under the Besluit voertuigen (Dutch Vehicles Decree); under the Regeling voertuigen (Vehicles Regulation), the tachograph installation plate may be valid for a maximum of 24 months. For work equipment, the Arbeidsomstandighedenbesluit (Dutch Working Conditions Decree) requires that inspection records are available at the workplace and shown to the inspectorate on request.
The source code and documentation belong to the client and are kept in a repository you have access to yourself. Handover includes a description of the architecture, the data models, the integrations and the deployment, so that another party can take over without having to reverse-engineer anything first. We work with mainstream technology, because that determines how many parties can pick up the maintenance.
Related services
Service parts software
If the question is mainly about parts, stock models and the link between part number and machine: building service parts software.
Equipment and forklift rental
If you also rent out the equipment, contracts and availability come into play: equipment and forklift rental software.
Field service app
If the emphasis is on technicians in the field, with job sheets and signatures on the phone, a field service app is the most direct starting point.
Your workshop process under the microscope
Tell us how a report reaches you, what happens now when the technician finds something that was not in the job, and how a warranty claim goes out the door. Those three answers usually show whether a package, custom software or a combination fits.