Equipment Asset Tracking: Why the Equipment Needs a File, Not Just the Customer

Most field service software organizes around a customer and an address, because that is how residential work arrives. Commercial equipment service inverts it: the customer changes, the equipment stays. 4 questions come up every week that a customer-level record cannot answer, and all 4 decide money.

The short version

Ask your current system what was done to the combi at store 212 in March. If the answer involves opening a customer, scrolling through jobs and reading old invoices, your history is stored against the wrong thing.

That is not a reporting gap. It is a data model, and it was a reasonable one for the work most field service software was built around. A homeowner owns their boiler for as long as they own the house. Customer and asset are effectively the same record.

Commercial kitchen work separates them:

• A restaurant group is one account with many sites and hundreds of pieces of equipment
• Franchisees change hands and facilities contracts go out to tender
• The manufacturer, not the customer, holds the warranty

Each of those breaks the assumption that the customer is the thing you are servicing.

4 questions a customer-level record cannot answer

These come up weekly in a commercial service company, and each one has a cost attached.

The question	What it decides	What happens without a piece of equipment file
What was done to this unit last time?	Whether this is a recurrence or a new fault	The technician diagnoses from scratch, sometimes the same fault a colleague fixed in March
Is this unit under warranty?	Who gets billed	The customer is billed for covered work, or a claim is filed on an expired agreement
How many times has this equipment failed this year?	Whether to recommend replacement	No case to make, so the customer keeps paying for repairs and blames you for the downtime
Where is this equipment now?	Which site to send a technician to	The same unit booked against the address twice becomes two assets, each with half the history

The second row is the expensive one. Warranty status attached to a customer is a note somebody has to keep in their head. Attached to the equipment, it is visible before a technician is assigned.

A piece of equipment outlives the relationship that brought it to you

Contracts turn over and equipment does not. A facilities contract goes out to tender, a franchisee sells, a group changes its service provider for two years and comes back.

When history lives under the customer, that turnover erases your own institutional memory. You served that kitchen for four years, you know which walk-in has the failing door heater and which fryer was rebuilt, and none of it is retrievable in a way that helps when the work returns.

When history lives on the equipment, you walk back into a kitchen you already know. That is a commercial advantage, and it is also the reason to record equipment for customers you are not sure you will keep.

The site is not the asset either

Moving from customer-level to site-level records is an improvement and it stops short. Sites are stable and equipment are not.

Refits move equipment between locations in a group. A spare ice machine goes wherever the failure is. A reach-in gets shifted from store 212 to store 118 and, in a site-based system, becomes a second asset with no history while the first one sits at an address where it no longer is.

Location history is the attribute that speaks to this, and it is the one most often missing from a record built around an address. Roopairs holds manufacturer, model, serial number, service history, location history and warranty agreements against the unit itself, with planned maintenance contracts there rather than against the address.

Planned maintenance belongs on the equipment, not the account

A PM contract that attaches to a customer describes a visit. One that attaches to equipment describes work.

The difference shows up at renewal and at dispute. A contract covering "quarterly maintenance at the Riverside location" is ambiguous the moment equipment is added or removed. A contract covering named equipment at agreed intervals is not.

It also changes what a technician does on the day. Equipment-level PM means a schedule of what to check on which unit, based on what that unit has needed before. Customer-level PM means a visit and a checklist that is the same everywhere.

Selling the contract is easier from the equipment side too, because the argument is specific. Roopairs has written about how technicians sell PM contracts in the field, and the strongest version of that conversation is held in front of a piece of equipment with a history.

What a piece of equipment file has to hold

Six attributes, and two of them are the ones products usually skip.

1. Manufacturer. Decides the parts route and the warranty process
2. Model. Decides which parts documentation applies
3. Serial number. The only identifier a manufacturer accepts, and what resolves production revisions
4. Service history. Every job on this unit, not on this address
5. Location history. Where it has been, so a move does not create a second asset
6. Warranty agreements. What is covered, until when, by whom

Service history and location history are the two that get left out, and they are the two that make the other four worth having. A record with manufacturer, model and serial but no history is a list of equipment rather than a file.

Anything you add beyond those is a bonus rather than a requirement. Photographs of the nameplate and the installation, the position in the kitchen, and the asset tag number if you use one all earn their place quickly.

What changes in practice once the equipment has a file

The gains are not in reporting. They are in the ordinary sequence of a job.

Before dispatch. The dispatcher sees whether the unit is covered, what was done last time, and whether the same fault has been through before. That changes who gets sent and what they bring.

On site. The technician opens the record before opening a panel. Prior repairs narrow the diagnosis, and knowing a part was replaced four months ago changes what is likely.

At the invoice. Warranty status was known before the work rather than discovered afterwards, so the bill goes to the right party the first time.

At the review. When a customer asks why they keep paying to repair the same unit, you have the answer in front of you and a replacement recommendation that is evidence rather than opinion.

That last one converts a difficult conversation into a capital discussion, which is a better conversation for both sides.

Starting from customer-level records without a project

You do not need to survey everything before this starts paying.

Start capturing at the point of work. Every job on a piece of equipment you have not recorded gets manufacturer, model and serial added, ideally as a nameplate photograph. That is under a minute and it happens on jobs you were doing anyway.

Prioritize by what you touch most. The equipment generating repeat calls is the equipment where history pays first, and it is also the equipment you are already visiting.

Accept partial coverage for a year. A file on the equipment you actually service beats a complete asset register that took a quarter and nobody maintains.

If you want to see what a piece of equipment-level record looks like with history, location and warranty on the unit, Roopairs runs a product tour where you can bring one of your own multi-site customers.

What service companies in the trade say

“I have my own kitchen equipment repair business and I use Roopairs. The software its self is quick to learn and extremely easy to use. I have been a tech for 30 years i have seen alot of different types of software but nothing that makes it so easy to write an estimate or a invoice.” — Lisa Doyen

Also worth reading

• Planned Maintenance Against the Equipment
• Tracking Client History in Kitchen Equipment Service
• The future of IoT for commercial kitchen repair companies

Frequently asked questions

What is equipment asset tracking?

Holding a record for each piece of equipment you service, rather than only for the customer who owns it. The record carries what the equipment is, what has been done to it, where it has been and what warranty covers it, and it stays with the unit rather than with the account.

What is the best equipment maintenance software for a small business?

For a service company the answer depends on whether you service your own equipment or somebody else's. Maintenance software is generally built for asset owners tracking their own equipment. A service company needs the asset record inside the system that also runs jobs, parts and invoicing, because a separate asset database becomes a second place to update and then stops being updated.

Is asset tracking the same as inventory management?

No, and conflating them causes real confusion. Inventory management tracks parts you hold and consume. Asset tracking tracks equipment you service and do not own. They connect at the point where a part is fitted to a piece of equipment, which is exactly where both records earn their value.

Do I need barcodes or tags to start?

No. The record is the point and the tag is a pointer to it. Start with manufacturer, model and serial captured at the job, and add physical tags later if scanning would genuinely be faster than typing. Plenty of service companies run good asset records with no tags at all.

What if the customer owns the equipment and we might lose the account?

Record it anyway. The asset belongs to the customer and the service history belongs to you, and that distinction is worth being clear about in your terms. Accounts come back, and walking into a kitchen you already have four years of history on is the reason to have kept it.

How long does it take to build up useful records?

Useful within a quarter if you capture at the point of work, because the equipment you visit most are the ones the history helps with most. Complete takes far longer and is worth much less, since the tail of equipment you touch once every three years contributes almost nothing.