Quick answer. A fleet customer does not want a login to your system. They want their wash data to appear inside the system they already use, matched to their own vehicle numbers, on their own billing cycle. That means three things from you: a stable vehicle identifier, wash records they can pull, and invoices that reconcile without manual work. Everything else is negotiable.
The request arrives in the same shape every time. A fleet with a few hundred vehicles wants to know whether your system can “talk to” theirs. What they mean by that varies enormously, and the gap between the two interpretations is where these conversations usually stall.
What large fleets are actually asking for
Almost never a live connection. Ask three follow up questions and the request usually resolves into one of these.
Cost allocation. They need wash costs attributed to the right vehicle or the right depot so it lands in the correct budget line. This is the most common one by a distance, and it is a data matching problem rather than an integration problem.
Compliance evidence. Some fleets, particularly food and pharmaceutical transport, need to demonstrate that trailers were cleaned, when, and to what specification. They want a record they can produce during an audit.
Invoice reconciliation. Their accounts team wants a line per vehicle rather than a single monthly figure, so they can check it against their own records without phoning you.
All three are solvable without anything exotic. Only one of them, occasionally, actually needs an API.
The identifier problem
This is the part that decides whether any of it works, and it is almost always underestimated.
You identify vehicles by number plate. The fleet identifies them by an internal fleet number, and their maintenance system may use a third code. A plate changes when a vehicle is re registered. A trailer may have no plate that matches anything in their records at all.
The fix is to hold their identifier alongside yours on the vehicle record, from the start of the relationship. One extra field, captured during onboarding, removes an entire category of monthly dispute. Retrofitting it across four hundred vehicles two years later is a project.
Trailers deserve a specific mention because they are where this breaks most often. They get swapped between tractors, they carry a different plate convention in different countries, and the fleet frequently cares more about the trailer than the unit pulling it. If a customer’s business is trailer washing, their trailer identifier is the primary key, not an afterthought.
Three things worth exposing
If you are going to make data available to a fleet customer, these are the ones that carry weight.
- The wash record. Date, time, site, vehicle, programme, and the price charged. That single row answers most questions a fleet will ever ask, and it is worth making sure it carries their identifier rather than only yours.
- A cleaning certificate. For customers who need it, a per wash document stating what was done and to what specification. This is not a technical feature so much as a formalised output, and fleets that need it will choose you over a competitor who cannot produce it.
- The invoice, itemised. Per vehicle lines rather than a monthly total, matched to their company account structure so their depots reconcile separately if that is how they are organised.
Notice what is missing from that list: live status, booking availability, remote job creation. Those get requested during sales conversations and used by almost nobody. Build them when a customer will genuinely change behaviour because of them, not because the request sounded impressive.
Why a customer portal is not the same answer
A portal is you giving them a place to look. An integration is you putting the data where they already look. Those solve different problems, and offering the first when they asked for the second is a common way to lose the account slowly.
Portals work when the customer is small enough that one person handles it, and when checking wash records is an occasional task rather than a monthly reconciliation. Large fleets do not want another login. Their transport planner has six systems open already and yours will be the one nobody opens.
The honest test is to ask who inside their organisation would use it and how often. If the answer is “our accounts person, once a month, at invoicing”, the thing they actually need is a better invoice file, not a portal. That is a much smaller piece of work and it solves the real problem.
When integration is worth building and when it is not
Worth it when the volume justifies it and the requirement is stable. A fleet sending several hundred vehicles a month, with a compliance need that will not change next quarter, is worth engineering around. The work pays back in retained revenue and in the fact that a customer whose systems are connected to yours does not switch supplier casually.
Not worth it when the request is exploratory. A prospect asking whether integration is possible during a first meeting is checking that you are a serious supplier, not specifying a project. Answer honestly, describe what the data looks like, and let the conversation move on.
The middle case is the awkward one: a real customer with a real need whose volume does not justify custom work. That is where a good export and a clear invoicing structure earns its keep, because it covers ninety percent of the requirement for none of the engineering.
Questions we get asked
Do fleet customers really need an API?
A small number do and most do not. The question worth asking is what they will do with the data once it arrives. If the answer is that a person opens it and reads it, a scheduled export solves the same problem with far less to go wrong on either side.
Who owns the vehicle data, us or the fleet?
Practically, both hold a copy and neither is authoritative on its own. You know when the vehicle was washed and what it cost. They know what the vehicle is called internally and which depot it belongs to. Holding their identifier next to yours is what makes the two views reconcile.
What happens when a fleet renumbers their vehicles?
It happens more often than you would expect, usually after an acquisition. Keep the old identifier on the record rather than overwriting it, so historical washes still match their historical reports. Overwriting is the fastest way to make a year of reconciliation fail at once.
Should we charge for integration work?
For genuine custom development, yes, and it makes the conversation more serious rather than less. For a standard export or an itemised invoice format, no, because those should be part of how you serve any account of that size.
How do we handle a fleet that uses several of our locations?
Keep one company account with the sites underneath it rather than an account per location. The fleet wants one relationship, one price agreement and one invoice, with visibility of which location did what. Splitting them into separate customers is how a fleet ends up negotiating three different rates with you by accident.
Want to see what a fleet ready wash record looks like before you promise one? Start a free trial and run a few vehicles through it.
