Simplifying an Overgrown Catalog

Why this matters

A catalog that grows for years without anyone pruning it turns into a maze: dozens of near-duplicate entries, dead line items nobody has quoted in years, and inconsistent naming that makes techs guess which one applies. New hires can't learn it, dispatchers pick the wrong entry under time pressure, and customers get quotes that look arbitrary because two similar jobs are priced from two entries that drifted apart. An overgrown catalog is not a sign of thoroughness. It is technical debt, and it slows down every single quote until someone cleans it up.

Step 1: Pull a usage report before you touch anything

Before deciding what stays and what goes, get the data. Pull every catalog entry and how many times each was used over the last year or two. Do not rely on memory or gut feel about "what we use a lot"; usage patterns are almost always more skewed than people expect, with a small fraction of entries covering the large majority of jobs.

• Sort by frequency, lowest to highest.
• Flag anything with zero or near-zero usage in the review window.
• Note entries used only by one specific tech or team, which often signals a personal habit rather than an actual shop standard.

Step 2: Group near-duplicates before you delete anything

Overgrown catalogs are rarely full of useless entries. More often they are full of redundant ones: three versions of essentially the same job created at different times by different people, each slightly different in wording or scope. Before deleting, group these clusters and ask which single entry should represent the group going forward.

• Look for entries with near-identical descriptions but different names.
• Look for entries that differ only by a modifier that could instead be a documented add-on or difficulty tier, rather than a whole separate line item.
• Merge into the clearest, most accurately worded version, and retire the rest.

Step 3: Retire, don't just delete, dead entries

A dead entry (zero usage, no clear reason to keep) should be retired, not silently removed. Deleting outright breaks historical job and invoice records that reference it. Mark it inactive or archived so it drops out of active quoting while past records stay intact. This also gives you a clean audit trail if anyone asks later why a service is no longer offered.

Step 4: Standardize naming and categories as you go

While you are already inside every entry, fix the two things that make a catalog hard to navigate day to day:

• Consistent naming convention. Pick one pattern (verb-first, noun-first, whatever fits the trade) and apply it across the board, so techs can predict what an entry will be called before they search for it.
• Consistent category and subcategory placement. An entry filed under the wrong category is functionally invisible to anyone browsing rather than searching by name.

Step 5: Rebuild descriptions for anything that survives the cut

An entry worth keeping is worth describing properly. See related: Writing Catalog Descriptions That Set Accurate Expectations. Use the simplification pass as the occasion to fix vague or outdated descriptions on the entries you are keeping, since you are already touching every one of them.

Step 6: Set a cadence so it does not regrow

A one-time cleanup buys a year, maybe two, before the same drift starts again. Prevent the regrowth instead of just repeating the cleanup:

• Require a reason to add a new entry rather than a duplicate of an existing one with a tweak. Whoever owns the catalog should ask "does an existing entry already cover this with a modifier?" before approving a new line item.
• Schedule a lightweight annual review, focused on usage data, not a full re-audit every time.
• Assign catalog ownership to one person or a small group. A catalog anyone can add to without review is a catalog that regrows within a year.

Recap

Pull usage data first, merge near-duplicates before deleting anything, retire (don't delete) dead entries, standardize naming and categories, rewrite descriptions on what survives, and put a light ownership process in place so the mess does not come back.

References

• Trade-standard practice for periodic price-book review
• See related: Writing Catalog Descriptions That Set Accurate Expectations
• See related: The Catalog and the Price Book: Keeping Them in Sync