Multi-Store Operations: How to Standardize Without Losing Control
In 1980, a successful single-location Chevrolet dealership owner decided to open a second location across town. By all accounts, it should have been a natural expansion. Same brand, same market, same owner at the helm. What he discovered, almost immediately, was that he couldn't just clone his operation. The second store's service department was bleeding money. His top service advisor moved to the new location and suddenly brought with her her own way of scheduling ROs, tracking follow-ups, and managing CSI. The parts manager at location two ordered differently than location one. Inventory fell out of sync. Process drift happened in real time.
That dealership owner didn't have software. He had phones, filing cabinets, and memo pads. But his core problem is the same one that keeps multi-store GMs awake at night today: how do you scale a working operation to a second, third, or fifth rooftop without losing the control and consistency that made the original dealership successful?
The Myth: One Process Fits All Locations
Here's the thing most dealer principals tell themselves when they're planning a second location: "We'll just do it the same way we do it here." This sounds reasonable. It's not.
Your first store has developed a culture and a rhythm over years. Your service director knows every technician's speed and quality level by heart. Your front desk team has figured out which customers prefer afternoon appointments and which ones will drop their cars off before 7 a.m. Your parts team has built relationships with suppliers that sometimes get you priority on hot parts. These are organizational muscle memory. They can't be replicated through a checklist.
But here's what can and must be standardized: the core workflow itself.
There's a meaningful difference between process (the steps) and execution (how people carry out those steps within their own judgment). You need identical processes across rooftops. You need flexibility in execution. Most dealer groups get this backwards.
Why Process Standardization Actually Matters (Even When It Feels Heavy-Handed)
Let's say you're a four-store group with $8 million in annual fixed ops revenue. If each location has slightly different ways of handling estimate approvals, parts ordering, and vehicle delivery scheduling, you're not just running four dealerships. You're running four different businesses that happen to share a brand and an owner.
Consider a typical scenario: Location A approves estimates under $500 on the spot. Location B requires customer callback for anything over $250. Location C has the service director pre-approve all labor. One vehicle—say a 2016 Ford F-150 with 89,000 miles coming in for transmission fluid service, brake inspection, and a possible steering rack replacement—hits your service lanes. Same truck, same systems. Depending on which location it rolls into, the customer gets a completely different experience. One gets a quick callback and approval within 2 hours. Another waits overnight for a manager to call back. CSI scores diverge. Days to front-line inventory gets longer at one location. Your group's average metrics become meaningless because they're averaging completely different processes.
This is when dealer principals realize that standardization isn't bureaucratic overhead,it's the foundation that lets you scale without chaos.
The Real Barrier: Change Management at the Store Level
You already know this, but it bears saying directly: process standardization fails because people resist it.
Your service director at location one has run that department their way for five years. They've got a rhythm. They know what works. Now you're telling them that location two's service advisor uses a different reconditioning workflow, and to make things consistent across the group, location one is switching to location two's method. How does that land? It lands poorly.
The change feels arbitrary to the team member. It feels like you don't trust how they've been doing things. It adds friction to their day before they see any benefit. And since adoption is uneven, the new process is half-implemented everywhere, which makes everything worse, and the team decides the whole initiative was a waste of time.
Here's where most multi-store groups fail at change management: they announce the new process and assume adoption follows. They don't.
Adoption requires three things, in order.
First: Clarity on the Why
Your team needs to understand that standardization isn't about control,it's about scale, consistency, and (honestly) their own job satisfaction. When processes drift, customers get inconsistent experiences. When CSI is all over the place, corporate attention turns inward. Bonus structures suffer. Career paths become unclear because nobody knows what the standards actually are.
Your service advisors, parts managers, and technicians care about doing good work and being recognized for it. They can't do that well if they're operating in four different systems. Show them the before-and-after numbers from a real multi-store consolidation. If one location is hitting 85% first-time fix rates and another is at 71%, why? Usually it's not talent. It's process. Once the lower-performing location adopts the higher-performing process, the gap closes in 60 to 90 days.
This is your opening argument. Lead with it. Not with policy. Not with compliance. With performance.
Second: Co-Creation, Not Decree
Do not write the standardized workflow in an office and email it to your stores. You'll get compliance theater, not real adoption.
Pull your best service directors, parts managers, and service advisors from each location into a room (or a virtual meeting, if you're spread out). Don't ask them what they think should change. Ask them what's working at their location and why. Ask them what's broken and frustrating. Then synthesize the best practices from all locations into one workflow. This does two things: it surfaces the actual logic behind your best operations, and it gives your team ownership of the new standard because they built it.
Yes, this takes time. It's worth it. A three-day workshop with eight people across your group that produces a standardized workflow saves you six months of half-hearted implementation and silent resistance.
Now here's an important caveat: some edge cases won't fit the standard. A location with a heavy body shop clientele might need slightly different parts ordering. A high-volume quick-lube location has different capacity constraints than a full-service shop. You're not creating one-size-fits-all. You're creating a framework that adapts to real operational differences, not to personal preference. Build that flexibility into the standard explicitly so that adoption doesn't feel like forcing a square into a circle.
Third: Systems That Make the New Process Easier Than the Old One
Paper, spreadsheets, and tribal knowledge made the old process work, but it was held together with memory and goodwill. The new process needs tools that make it genuinely easier to follow the standard than to revert to old habits.
This is exactly the kind of workflow automation that tools like Dealer1 Solutions were built to handle. When every location can see the same estimate approval queue in real time, when parts status updates automatically, when delivery scheduling is visible to everyone, when service advisors see technician ETAs on the detail board before committing to a customer promise,suddenly the standardized process isn't a burden. It's faster and smoother than the old way.
Without those systems, people will find workarounds. A service advisor will call the parts manager directly instead of using the new ordering system because the phone call feels faster. A technician will keep a private list of jobs instead of logging them in the shared system. Process drift accelerates.
Measurement: The Invisible Enforcer
Here's something that surprises dealer principals: once you have a clear process and the systems to support it, you don't need to police adoption. You just need to measure it and report on it transparently.
Set three to five key metrics that reflect whether the new process is being followed. Don't make them punitive. Make them diagnostic.
For service workflow standardization, this might look like:
- Average days from RO open to parts ordered (standardized trigger point)
- Percentage of estimates sent to customer within 2 hours of vehicle drop-off
- Percentage of vehicles delivered on promised date
- First-time fix rate by location
- Average CSI score (transaction level) by location
Push these metrics to your team dashboard weekly. Show each location how they're performing relative to the standard and relative to other locations. Make it visible to front-line staff, not just management.
Something remarkable happens. Competition emerges. Not the toxic kind. The healthy kind. A service director sees that location three is hitting 88% first-time fix and location one is at 79%, and they ask questions: "What are you guys doing differently?" Peer learning accelerates adoption faster than any mandate ever could.
The Scaling Problem Nobody Talks About
Here's an uncomfortable truth: the best process for one location might not be optimal for a second location. And that's okay.
But if you're managing a five-store group and each store has a "custom" process, you're not managing anymore. You're babysitting. You don't have real visibility into performance. You can't easily move talent between locations. You can't leverage scale to negotiate better parts pricing or reconditioning labor costs.
The answer isn't perfect uniformity. It's controlled variation. You have a standard process. Locations can request a documented exception with a business justification. You review it, approve it, and track it. Now variation is intentional and visible, not hidden drift.
One More Thing: Timing Matters
Don't roll out a new standardized workflow on the same day you're dealing with month-end closings, a major parts shortage, or a staff transition. Adoption will fail not because the process is bad but because your team doesn't have cognitive capacity to learn something new while fighting fires.
Schedule process rollouts for operationally calm periods. Front-load the change with training and support. Have your best people from location one spend time at location two on the first week, just to troubleshoot live. That person isn't there to police. They're there to answer questions before frustration sets in.
Multi-store operations are hard. They're harder than people think when they're opening location two. But the dealership owner from 1980 didn't have software to create operational transparency or process consistency. You do. The difference between scaling well and scaling into chaos is whether you treat standardization as a control mechanism or as a foundation for trust and performance.
Your team will adopt new processes when they understand why the process exists, when they had a hand in building it, when the systems make it easier than the alternative, and when they can see themselves succeeding against a clear standard. That's not manipulation. That's leadership in a growing organization.
The Multi-Store Advantage
One final thought: a multi-store group that executes on standardized processes has an unfair advantage against single-location competitors. You can move high-performing service advisors between locations to mentor and lift others. You can test new service packages at one location and roll them out across the group. You can negotiate better rates because you have volume. You have redundancy and resilience. When location one's detail tech is out sick, you can pull from location two for a day.
Single locations can't do any of that. They're stuck with what they have. You're not. But only if your processes are consistent enough to enable that kind of flexibility.
That's the real prize.