Catalog Consistency Across Multiple Locations

Why this matters

The moment a shop opens a second location, or brings on a second crew running a separate branch, the catalog stops being one document and starts being a coordination problem. A customer who calls branch A and then calls branch B expects the same service to mean the same thing and cost close to the same amount. When it doesn't, the inconsistency reads as either sloppiness or a bait-and-switch, and it shows up fastest in online reviews that compare notes between locations. Consistency does not mean identical: it means every location is working from the same spine, with only the parts that genuinely need to vary actually varying.

Separate what must be identical from what may vary

Not every catalog element needs to match across locations. Sorting them correctly up front prevents both false consistency (forcing a rural branch to match a dense-metro price) and false flexibility (letting service definitions drift for no reason).

Must be identical everywhere:

• Service names and scope of work. A "Drain Line Camera Inspection" has to mean the same steps and the same deliverable at every location. This is the core promise to the customer and it cannot vary by branch.
• Tiering structure, if you run a good/better/best model. The tier names and what separates them stay fixed; only the price inside each tier may shift.
• Safety and compliance minimums. Any inspection point, disclosure, or code-driven step is non-negotiable across locations regardless of local market conditions.

May reasonably vary by location:

• Price, driven by local labor cost, material cost, and market rate.
• Availability, if a location lacks the equipment, certification, or crew depth to run a given line item yet.
• Add-on and bundle mix, if local demand patterns genuinely differ (a coastal branch adding a salt-air corrosion package that an inland branch has no reason to carry).

The drift patterns to watch for

Catalog drift between locations rarely happens on purpose. It creeps in through three common paths:

• Local manager customization that never gets reported back. A branch manager tweaks a line item to close a specific deal, the tweak sticks, and six months later that location's catalog has quietly diverged from the others with no record of why.
• New-hire office staff inventing their own shorthand. Without a shared reference, two schedulers describing the same service to customers in different words creates the appearance of two different services.
• One location adopting a new line item before the others catch up. A good addition at branch A should trigger a decision for every branch: adopt it, or explicitly decide it does not apply there. What kills consistency is neither choice being made.

How to keep the catalog aligned without over-centralizing

• One master catalog, one owner. A single person or small group owns the master list of service names, scopes, and tier structure. Local managers can request additions or changes, but nobody edits the master unilaterally.
• Local price sheets, master service definitions. Let pricing flex by location inside a locked scope-of-work definition. This is the single highest-leverage split: it solves the "why is it more expensive at the other branch" question (local cost of doing business) without ever risking "why did I get a different service than what I was told."
• A standing quarterly catalog sync. Bring every location's lead into one review of what has drifted, what should be adopted everywhere, and what should be formally retired everywhere. Waiting for an annual review lets drift compound for a full year before anyone catches it.
• A shared naming and numbering convention. Give every catalog entry a stable internal code independent of the display name. When display names get locally tweaked for marketing reasons, the underlying code still ties every location's reporting back to the same service for cross-branch comparison.

The customer-facing check

The simplest test of catalog consistency: could a customer call both locations, describe the same problem, and get service descriptions that clearly refer to the same thing, even if the price differs? If yes, your consistency is solid and your pricing flexibility is healthy. If a customer would reasonably think they were being offered two different services, the drift has crossed from acceptable local variation into an inconsistency that needs fixing at the master-catalog level.

References

• See related: Auditing the Catalog for Dead or Unprofitable Entries
• See related: Building the Catalog Entry for a Brand-New Service Line
• International Franchise Association guidance on multi-unit operations standards
• Trade-standard practice for multi-location service businesses