Multi-Location Detailing Software Done Right

Opening a second location is supposed to feel like a win. Growth. Proof the thing you built actually works and can work twice. Then you switch on most shop software and watch your two locations collapse into one big blurry pile — the crew at shop A staring at shop B's jobs, two schedules bleeding into each other, a customer list where you can't tell which front counter the car walked into. That's not multi-location. That's one confusing shop wearing two name tags.

I see the failure mode a lot, and it's almost always the same root cause: the software treated “location” as a label you slap on a work order instead of a real wall between two businesses. A tag doesn't stop your Sunday-shift tech from scrolling the other shop's calendar. A tag doesn't keep the reporting honest when you're trying to figure out which bay is actually making money. And the second your data is mixed, everything downstream gets mushy — scheduling, payroll math, close rates, all of it averaged across two shops that have nothing to do with each other.

We're all installers before we're business owners, and the instinct when you grow is to just keep doing the next job — now in two buildings. But two buildings is exactly the moment the plumbing underneath your tools stops being optional. So here's the requirement I'd hold any multi-location detailing software to: each shop has to run as its own shop, and you — and only you and the people you trust across the whole company — get to see across all of them. Isolation for the crews, oversight for the owner. If a system can't give you both at once, it isn't multi-location software. It's single-shop software you're paying to abuse.

Start with the model, because the model is what everything else inherits. In Service VIN you have one organization — your company — and under it, one or more shops. Each shop is a real entity with its own roster, its own roles, its own schedule and its own customers. It is not a filter view of one giant shared pool. It is a boundary.

That distinction sounds academic until you live in it. When a location is a genuine boundary, the North bay's calendar is the North bay's calendar. The Southeast shop hires an apprentice and that apprentice shows up on the Southeast roster, not on some company-wide list where your other manager has to squint to figure out who works where. Roles are per shop too, so the person who is a lead installer at one location isn't automatically handed the keys at the other. You build each shop's team the way that shop actually runs.

This is the same roster and role machinery Service VIN uses for a single shop — the per-shop roster and roles with invites, skills, schedules and permissions — just applied honestly across more than one location. Nothing about running two shops forces you to flatten them into one. Each keeps its own shape.

Here's the part that actually matters, and it's the part most people never think to ask about until it burns them: how is the wall enforced? Because “each shop has its own data” is easy to say on a marketing page and hard to mean in the code.

In Service VIN, access is scoped by shop membership. You belong to a shop; you see that shop's work. A tech on the North roster pulls up the jobs board and sees North's jobs, North's customers, North's calendar — not the whole company's. That scoping isn't a checkbox in a settings screen that someone can forget to tick. It's built into how the data gets queried in the first place. Every read is filtered to the shop you're acting in.

Why does that distinction earn its own section? Because the honest version of this feature is a guardrail, not a vibe. Without that membership scoping baked into the query, a person who belongs to more than one shop would pull back rows from every shop they touch — other locations' customers, other locations' jobs — simply because the database has no reason to hold them apart. The filter is what keeps one person's access from leaking into data that isn't theirs. “Isolation by hope” is when the wall only holds as long as nobody clicks the wrong thing. “Isolation by membership” is when the wall is the foundation, and there's no wrong thing to click. It mirrors how the team tools already work inside one shop — owners see the whole shop, techs see only their own work, by role rather than by nagging — and extends that same discipline to the line between locations.

Real shops are messier than a clean org chart, and any system that can't handle the mess is going to make you fight it. The classic case: a manager who covers both locations. Your best detailer who fills in at the other bay on busy Saturdays. The mobile guy who floats. You need those people to move between shops without tearing a hole in the isolation you just built.

The way Service VIN handles it is simple and it doesn't cheat. A person who works across locations is set up as a member of each shop they work at — not handed a magic god-mode badge that sees everything everywhere. When they log in, the app remembers which shop they last acted in, so they land where they left off instead of guessing. And when they book a job or touch a record, it gets stamped to the shop they're actually acting in, not smeared across both.

That last bit is the whole game. Cross-location flexibility is easy if you don't care where the work lands — you just let everyone see everything and call it a feature. But then your reporting is garbage, because you can't tell which shop did the job. Doing it right means the person moves freely while the data stays put. The manager can switch to the Southeast shop, run their Saturday, and every booking they make belongs to the Southeast shop — cleanly — because the system knew which shop they were standing in. Flexibility for the human, no leakage for the data.

Now the other half of the promise, because isolation alone isn't the goal. If all you did was wall off every shop, you — the owner — would be locked out of your own business, forced to log in and out of each location to figure out how the company is doing. That's a different flavor of broken.

The point of scoping the crews is precisely so it can be lifted for the people who need the whole picture. Front-line staff stay pinned to their location; owners and multi-shop roles operate across all of them. You get the wide view — every location, one company — while each of your crews gets a focused, uncluttered view of just their shop. That's the both-and that makes multi-location actually work: a clean daily surface for the techs, and real oversight for you.

This is where cross-location reporting stops being a nice-to-have. When each shop's work is genuinely its own, the numbers you pull up across locations mean something — revenue by shop, margin by shop, who's busy and who's quiet — because they were never mixed in the first place. You can only compare two locations if the software kept them separate to begin with. Isolation isn't the enemy of oversight. It's the thing that makes oversight honest.

Here's the contrast the way I'd draw it on a whiteboard for an owner about to sign a second lease. It's an architecture picture, not a performance benchmark — the bars below are a conceptual illustration of what “done right” means, not a measurement of anyone's shop. On the left, the mixed pile: every location dumped into one bucket. On the right, true isolation with owner oversight sitting on top.

Read it as a checklist of things you want to be true. Staff should see only their shop's work. Schedules should stay separate per location. The owner should still see across everything. A mixed pile fails all three at once; true isolation is designed to pass all three without you having to police it by hand.

Straight answer on tier, because I hate when this stuff is coy. Multi-shop lives in the Command plan — CAD $399/mo — which is the tier built for shops covering more than one location. It's built for up to three shops under one login — that one-login multi-shop switch is still rolling out, so you'll see it flagged “coming soon” on the pricing page — and it's bundled with the calling suite, because the shops big enough to run two locations are usually the same shops drowning in phone calls. You can see the full breakdown on the Command planand decide whether the timing's right.

I won't pretend every shop needs it on day one. If you're running a single bay, stay where you are — the same shop software stack that quotes for margin and books without double-booking is the same stack that'll be waiting when you're ready to add a location. That's the point of building it this way. You don't rip out your system and migrate to “the enterprise version” the day you sign a second lease. The multi-shop model is the same model, scoped up.

But if you're about to open number two, or you're already limping along running two shops through software that treats them as one, this is the tier designed to keep them separate and keep you sane. Growth should feel like growth — not like you traded one clean shop for two blurry ones. Do the isolation right and each location gets to be its own shop, your crews get a view that actually fits their day, and you get to sit above all of it and finally run the company instead of refereeing it.