How do customers, locations and equipment relate in ServiceTitan?
A customer is the billing relationship. A location is a service address under that customer. Equipment records live at a location. One customer can hold many locations, which is how property managers and commercial accounts work, and one location can change customers when a house sells. Reporting on customers when you meant locations is a common and quiet source of wrong retention numbers.
Three levels, three different questions
Customer answers who pays. Location answers where the work happens. Equipment answers what you serviced. Most residential work has one customer and one location, which is why the distinction goes unnoticed until it causes a problem.
It causes a problem the moment you have property managers, landlords, multi-property owners or commercial accounts. Then a single customer record can represent dozens of unrelated buildings, and any per-customer average is meaningless.
Where each level is the right unit
- Revenue and receivables: customer. That is who is billed and who owes.
- Retention and repeat rate: location. Service relationships follow the address and the equipment, not the name on the invoice.
- Replacement targeting: equipment. Age, model and repair history at a specific unit is the only sound basis for predicting who needs replacement.
- Marketing source: the job. Because the source that produced today's call is not necessarily the source that created the customer years ago.
Address changes are the trap
When a house sells, the location stays and the customer changes. If your reporting keys retention on the customer, you will record a churned customer and a new customer for what is, from an equipment and service standpoint, a continuous relationship at one address.
Conversely, keying purely on address treats a new homeowner as a returning customer. Neither is right on its own. Sound retention reporting tracks the location and flags the ownership change as its own event — which also happens to be a strong signal for membership and maintenance outreach.
Equipment records are worth the effort they require
Equipment data is usually the least complete part of the system, because capturing model, serial and install date takes a technician's time on a call where nobody is asking for it. But it is the only field in the entire dataset that predicts future demand from physics rather than from behavior.
An accurate install-year distribution across your service base tells you how much replacement demand is sitting in your own customer list before you spend anything to find new demand. Turning that into outreach that respects who is already a member is exactly the kind of join that customer intelligence handles, and it depends on the location hierarchy being modeled correctly in the data layer.
Topics: data model · locations · equipment · retention
Have a version of this question about your own business?
The useful answer usually depends on which systems you run and how they're connected. That's a conversation, not a blog post.