The Catalog and the Price Book: Keeping Them in Sync

Why this matters

In most shops, "the catalog" and "the price book" describe the same set of underlying services, but they are maintained as if they were two different documents: one describing what the service is, the other describing what it costs. When they drift apart, a customer sees a description that no longer matches the price attached to it, a tech quotes off memory instead of either one, and the office ends up manually correcting mismatched quotes on a regular basis. Keeping the two in lockstep is not a nice-to-have; it is what makes the catalog trustworthy enough for anyone to quote off without double-checking.

Why they drift apart in the first place

The catalog (the description of what the service is and includes) and the price book (the number attached to it) usually get edited by different triggers, at different times, by different people:

• The price gets updated when material costs move, when labor rates change, or during a scheduled price review, often by whoever owns the numbers.
• The description gets updated when the scope of the work actually changes, or when someone finally notices the wording is unclear, often by whoever owns customer-facing content or by a tech flagging it after a dispute.

Because these two triggers rarely fire at the same time, a price change can land without the description being touched, and a description change can land without anyone re-checking whether the price still fits the newly worded scope. Neither editor necessarily even knows the other type of change happened.

What "out of sync" actually looks like

• The description implies more than the price covers. A description promises something ("includes a full inspection") that was quietly dropped from scope when the price was last cut to stay competitive, but the wording was never updated to match.
• The price reflects a scope the description no longer states. A price was raised to cover an added step, but the description still reads like the old, smaller job, so the customer has no idea why the number went up.
• Two entries reference the same real-world job with different prices, because one was updated during a price review and its near-duplicate sibling was missed.

Any of these produces the same symptom on the ground: a tech or a customer catches the mismatch, and it reads as sloppiness even when the underlying work is done well.

A structure that keeps them tied together

The most reliable fix is procedural, not a one-time cleanup: treat every catalog entry as one object with two attributes (description and price) that must be reviewed together, not two separate lists that happen to reference each other.

• Route every price change through the same entry the description lives on, rather than a separate pricing spreadsheet that gets copied over periodically. A single source of truth removes the sync problem structurally instead of relying on someone remembering to update both.
• Require a one-line "why" on every price change, and check whether that reason also implies a description change. A price bump for "added a required second visit" almost always means the description needs a line too.
• Review both fields in the same pass during a scheduled catalog audit, not the price in one pass and the description in another. See related: Simplifying an Overgrown Catalog.

A quick sync check you can run anytime

If you suspect drift but do not have time for a full audit, spot-check a handful of your highest-volume entries: read the description out loud, then look at the price, and ask whether a customer reading only the description would expect a number in that range. If the answer is no, on more than one or two entries, it is worth a full review rather than a patch on just the ones you happened to check.

References

• Trade-standard practice for price-book governance in field service
• See related: Simplifying an Overgrown Catalog
• See related: The Catalog Price vs the Quoted Price Mismatch Decision Tree