IT Guidance for Automotive Clients in the Pacific Northwest

The parts manager at a Subaru store in Tukwila called last month because their inventory system had gone offline during a recall parts surge. The dealership had taken on OEM allocation for a national service campaign, which meant higher than normal parts traffic, tighter vendor delivery windows, and about 40% more service ROs per day than baseline. When the system went down at 11am on a Tuesday, they had techs waiting on parts lookups, advisors unable to quote labor, and a parts counter that couldn't process orders or confirm stock. The actual problem turned out to be a VLAN misconfiguration that happened during a weekend firmware update the previous IT provider had run without documented rollback. By the time we were on site, the dealership had lost three hours of parts throughput during peak recall volume.

That's the thing about automotive IT. The tolerance for downtime is zero, and the operational dependencies are higher than most other verticals. A law firm can tell clients to come back tomorrow. A retail store can process credit cards manually for an afternoon. A dealership loses the deal, loses the service appointment, and often loses the customer entirely. The GSM opening deals at 7am needs the desking software up. The service drive needs DMS access from the moment the first car rolls in. F&I can't close a deal jacket if the credit application portal is timing out. And all of it runs on infrastructure that was frequently installed piecemeal over 15 years by whoever the previous GM knew.

Here's what that looks like in practice for most Pacific Northwest dealerships. You have a DMS that's either CDK or Reynolds, and that DMS has strict on-prem requirements that were set in 2009 and haven't materially changed. You have desking software that runs on specific Windows builds and doesn't handle network latency well. You have F&I applications that need consistent uptime because the banks on the other end of those credit pulls don't wait. You have service lane workflow tools that were bolted onto the DMS years ago and nobody quite remembers how. And you have a parts department running inventory software that talks to the DMS, talks to OEM allocation systems, and talks to third-party vendors, all of which expect sub-200ms response times or they start throwing errors.

That infrastructure has to stay up during the highest-margin hours of your day. A Saturday morning in the service drive. The last week of the month when F&I is closing volume. A recall campaign that the OEM drops on you with 72 hours of notice. The IT decisions you make have to account for those realities, not the sales pitch about cloud migration that works great for a SaaS company but falls apart the first time your desking software can't reach the DMS.

The FTC Safeguards Rule changed the posture requirements for dealerships starting in 2023. If you're storing customer financial data—and you are, because every credit app, every deal jacket, every service RO with a stored payment method qualifies—you now have mandatory incident response planning, access controls, and vendor risk assessment obligations. That's not optional and it's not theoretical. It shows up as a compliance question when you're trying to close deals with certain lenders. It shows up during audits. And it shows up as liability if something goes wrong and you can't demonstrate you had controls in place.

Most dealerships in this region are running a mix of on-prem DMS, cloud-based add-ons for CRM and inventory tools, and a handful of vendor portals that advisors and F&I managers use throughout the day. That hybrid architecture is fine. But it has to be documented, it has to be monitored, and someone has to know what happens when one piece fails at 9am on a weekday. The previous IT provider for that Subaru store didn't have network diagrams. They didn't have a rollback plan for firmware updates. And they didn't have anyone on call who understood how the parts VLAN was configured or why it mattered.

Ryan Collier has worked in IT since around 1996. The team at TCG has cumulative decades of experience across industries, but automotive is different. The operational tempo is higher. The vendor dependencies are stricter. And the cost of getting it wrong is a line of customers who don't come back.

If you're running a dealership in the Pacific Northwest and your current IT setup feels like it's one bad morning away from costing you deals, that's worth a conversation. We work with automotive clients who need infrastructure that actually fits how dealerships operate—not how IT vendors think they should operate.

Schedule a consult at craftworkgrp.com and we'll walk through what your current environment actually looks like and where the gaps are.