The Catalog Entry for a Service You Rarely Do

Why this matters

Most shops have a handful of jobs they do a few times a year, not a few times a week: an unusual repair, a job type left over from a past specialty, a request that only comes up in a certain season. The temptation is to leave these out of the catalog entirely and price them fresh every time, or to leave a stale entry in from years ago and quote off it without checking. Both habits cost the shop money in different ways, and both are avoidable with a small amount of structure around low-volume entries.

Why rare entries need different treatment than common ones

A high-volume catalog entry gets corrected by its own repetition. If the price is off, a tech notices within a month because they run the job constantly, and someone flags it. A rare entry gets no such feedback loop. It can sit wrong for years because nobody runs it often enough to notice the price has drifted from reality, materials costs have shifted, or the scope described no longer matches how the shop actually does the work.

This means rare entries need to be more carefully specified than common ones, not less, even though the instinct runs the opposite way ("we barely do this, why bother polishing the entry").

Three honest options for a rarely-used service

Not every rare service belongs as a fixed-price catalog entry. Be deliberate about which of these three treatments fits:

• Keep it as a fixed catalog entry, reviewed on a fixed schedule. Right for a service that is rare but predictable in scope every time it comes up (a specific seasonal job, a specific unusual repair with a known procedure). Put a review date or a review trigger on it explicitly, since it will not get organically caught by volume.
• Convert it to a "starting at" or range entry. Right for a service that is rare and variable in scope. This sets an honest expectation that the final number depends on site conditions, without pretending a single fixed price covers every version of the job.
• Remove it from the catalog and route it to custom quoting. Right for a service so rare and so variable that a stale catalog entry does more harm than good. See related: Custom Quote vs Catalog Price Decision Tree. A removed entry is not a lost sale; it is an honest acknowledgment that this job needs eyes on it every time.

Signs a rare entry has gone stale

Because rare entries do not get corrected by volume, build a habit of checking them deliberately rather than waiting for a customer complaint to surface the problem:

• Materials or components referenced in the description are described in a way that predates a supplier or process change. Even without naming a brand, a description that assumes an old procedure is a sign the entry has not been touched in a while.
• The last job run against this entry required a manual price override. If the catalog price and the actual invoiced price do not match the last one or two times it was used, the entry is out of date and everyone quoting off it is guessing.
• Nobody on the current crew remembers why the entry is priced the way it is. Institutional memory around a rare line item fades fast. If the reasoning is gone, the number should be re-derived from current cost, not assumed correct because it has "always been that price."

A light review cadence that actually happens

A full catalog audit once a year will always deprioritize the entries used twice a year, because they are easy to skip past. Instead, tag low-volume entries specifically and review that short list on its own, separate cadence: once when the entry is created, and again the next time it is actually used, before the quote goes out. That second checkpoint, tied to real usage rather than a calendar date, is the one that actually happens in a busy shop.

References

• Trade-standard practice for periodic price-book review
• See related: Custom Quote vs Catalog Price Decision Tree
• See related: Simplifying an Overgrown Catalog