A dealer using CDK inquires about implementing Desktop as a Service (DaaS) or Azure Virtual Desktop (AVD) at their dealership, noting that while these technologies are established elsewhere, adoption remains limited in automotive retail. The post seeks peer experiences and feedback from other dealers who have attempted DaaS deployments with various DMS platforms to inform their decision-making process. No conclusion or key insights emerged in the original post—this is an open question awaiting community responses.
A dealership marketing professional explores running CDK and PBS DMS software on Apple Silicon Macs, sharing hands-on results after ordering an iMac M1 for front reception. CDK proved frustrating, requiring Parallels and a server-side config change from a 'hard' to 'soft' OS check after CDK support blamed the Mac rather than their own legacy code. PBS, by contrast, installed effortlessly via Parallels with virtually no friction, highlighting a clear compatibility gap between the two DMS providers.
The thread addresses a critical operational gap in multi-store dealership groups: while DMS systems reliably capture sales and service transactions, post-transaction workflows (titles, funding, recon approvals, follow-ups) often lack standardization and fall into informal tracking methods like spreadsheets and emails, creating inefficiencies and errors at scale. The original poster asks the community how they maintain visibility and consistency across these backend processes in multi-location operations and whether standardized group-wide solutions exist to bridge the DMS-to-operations gap.
A startup DMS vendor announces an upcoming product launch featuring comprehensive dealership management capabilities (image management, test drive logging, invoice customization, margin tracking, VAT compliance) and website templates, positioning themselves as a bespoke alternative to larger competitors. The team emphasizes their consultancy background and passion for the product, noting they plan exclusive launch offers for a limited set of initial clients. The post appears incomplete, cutting off mid-sentence before revealing specific launch details or pricing information.
An automotive industry job candidate seeking interview preparation asks DealerRefresh members to share which service department software they use at their dealerships and what they like or dislike about their current systems. The candidate hopes to gather talking points and locate tutorial videos to better understand dealership software products before their interview. This is a straightforward information request aimed at gaining competitive knowledge about the market and common pain points in service management solutions.
Vincario, a vendor partner, introduces their VIN decoder API to automotive professionals, highlighting capabilities like 99.8% accuracy across 110 countries, support for 2,200+ vehicle brands, and automation of tasks such as form pre-filling and compliance reporting with a claimed 48% reduction in manual work. The post invites industry professionals to share their VIN decoding use cases and offers 20 free lookups for testing. This appears to be a product announcement rather than a discussion thread with peer feedback or real-world implementation insights from dealers.
A dealership owner seeks input on developing AI use policies after noticing employees using ChatGPT and similar tools without oversight, risking exposure of proprietary dealership data to AI training models. The discussion emphasizes the need for clear internal guidelines about what data employees can safely share with AI tools and recommends staff training on both responsible AI use and prompt engineering techniques. The key insight is that dealerships should establish formal policies now rather than wait, given widespread unsanctioned AI adoption already happening among staff.
A user with nearly two years of DealerTrack experience expresses significant frustration with the platform's reporting capabilities, describing them as essentially nonexistent and criticizing the system's core design as inherently flawed for data quality and reporting functionality. The poster questions the value of DealerTrack's add-on modules (DealerOps, Stone Eagle, Advanced Report Writing) and invokes the "garbage in, garbage out" principle, suggesting the system actively enables poor data entry rather than preventing it. The key insight is that DealerTrack may be fundamentally inadequate for dealers requiring robust reporting and data integrity features.
A DealerTrack user seeks guidance on integrating with the platform's DB2 database via ODBC, specifically asking how to identify which tables contain recently modified deal data when documentation is unavailable. One experienced respondent expresses frustration with DealerTrack's lack of documentation and overall management, suggesting this is a known pain point in the community.
A developer seeking free work experience in automotive warranty administration reaches out to dealership owners and GMs, but struggles to get traction beyond initial rejections. Respondents note that many dealerships either handle warranty in-house or hire specialized external companies, with one commenter highlighting that manufacturers like GM are particularly stringent about warranty claims, creating demand for experienced specialists who know how to navigate denials. The thread suggests that gabrielm's entry point may be limited without either local connections or expertise that addresses a specific pain point dealers face.
Alex Snyder highlights Dominion DMS's new VUE Net backup system as an important security solution for dealerships, particularly in light of recent cybersecurity threats like the CDK hack. A Dominion representative confirms their availability to answer detailed questions about the product, positioning it as a viable option for dealers concerned about DMS downtime and data protection.
Automotive dealers discuss the FTC's CARS Rule (Combating Auto Retail Scams Trade Regulation Rule), with a forum member preparing to meet with the FTC's Director of Financial Practices to advocate for industry concerns. The thread covers Florida's independent enforcement efforts against undisclosed fees and reports that a federal court vacated the CARS Rule on procedural grounds (inadequate notice), though dealers acknowledge the underlying transparency goals have merit and a compromise may eventually emerge. The key insight is that while dealers view the rule as overreaching, the industry recognizes legitimate consumer protection concerns around pricing transparency, and the outcome may depend on political factors including potential White House oversight of the FTC.
A new industry employee asks for guidance on financing processes for dealerships without captive finance departments, specifically inquiring about financing software, lender relationships (brokers vs. direct bank/credit union connections), and satisfaction with current approval timelines and rates. The thread appears to explore whether working with multiple lenders improves deal flow and pricing outcomes compared to limited financing options.
Tekion has filed an antitrust lawsuit against CDK Global, alleging anticompetitive practices that obstruct dealer access to their own data and unfairly disadvantage DMS competitors. The discussion centers on whether Tekion's legal action will succeed or if CDK's market dominance will allow them to escape consequences, with a notable case example involving Asbury Park that required a Georgia court's preliminary injunction to force CDK to release dealership data for a Tekion pilot program. The thread reflects industry frustration with CDK's alleged data-withholding tactics and skepticism about the effectiveness of legal remedies against the dominant player.
A dealer seeks recommendations for affordable VIN decode APIs, specifically for basic year-make-model (YMM) data without minimum commitments. The thread quickly converges on the NHTSA free VIN decoder API as the consensus recommendation, with additional mentions of low-cost alternatives on RapidAPI and a free third-party tool also powered by NHTSA data.
A CDK outage survivor-turned-entrepreneur solicits feedback from dealers on cybersecurity vulnerabilities and potential product solutions through a survey, but receives skepticism from community members about clicking external links in a security-focused discussion. The thread highlights a tension between the poster's market research efforts and the forum's appropriate wariness about security risks, with one member requesting the survey questions be posted directly instead of via link. No clear consensus or solution emerges, though the exchange underscores dealers' genuine concerns about data protection and business continuity following the recent outage.
A dealer using PBS DMS expresses frustration that while the system excels for service operations, it has significant sales functionality limitations including lack of autosave on quotes, inventory locking issues, and inflexible pricing adjustments. The thread reveals a broader industry problem: dealers are often constrained by manufacturer-approved software restrictions, leaving them stuck with suboptimal solutions and unable to supplement with third-party CRM tools without workflow complications and compliance issues. The consensus emerging is that most DMS platforms force dealers to choose between service-focused and sales-focused functionality rather than excelling at both.
A fraud prevention professional presents data showing the auto finance industry faces $1.8 billion in synthetic identity fraud exposure and asks dealers if they'd be interested in advanced fraud prevention solutions. Responses are limited, with one non-dealer pointing to an existing identity verification service (Gather Technology) and another suggesting legal remedies as the primary defense. The thread reveals that while synthetic identity fraud is a significant industry problem, there appears to be limited dealer engagement on potential technological solutions.
Dealership professionals debate strategies to mitigate catastrophic downtime from vendor cyberattacks like the recent CDK breach, with the core tension being whether diversifying across multiple vendors is worth the integration costs and operational complexity. While participants agree that concentrating all critical systems with one vendor creates unacceptable risk, they acknowledge that DMS vendors often impose high "taxes" (API fees) to allow competing systems access to data, and achieving seamless integration across multiple platforms remains technically challenging. The emerging consensus is that dealers must push back on vendors' lock-in tactics and demand better integration, though this likely requires sacrificing some operational efficiencies in exchange for business continuity protection.
Following a CDK cyber incident on June 19th, dealers using CDK's inventory aggregation service experienced broken syncing to Cars.com—both pricing updates and vehicle additions/deletions stopped working. The thread reveals that dealers using alternative syndication routes (like Homenet/vAuto, which is owned by Cox) were largely unaffected, suggesting CDK's outage specifically disrupted their data pipeline to Cars.com, forcing some dealers to manually manage inventory with backlogs of 80+ vehicles.
A vendor is promoting a webinar about NADA Vault, a data security solution designed to help dealerships comply with updated FTC regulations. The key offering is training on how the platform enables dealers to better control and secure their data. No discussion or insights from dealership professionals are present—this is a straightforward promotional announcement.
A dealership manager using ERA Access on the blue screen interface experiences frequent logouts every few minutes, even mid-transaction, while other users have normal session lengths. Respondents suggest troubleshooting steps including testing the user's account on a different machine, clearing browser cache, restarting the workstation, and contacting R&R TAC support, with the consensus that the issue is likely machine-specific rather than a software configuration problem, despite a 60-minute automatic logoff setting existing in program 6210.