The OEM Mandate Stack

The OEM Mandate Stack

AI Summary

Every major U.S. OEM operates a software mandate program for its franchise dealers. The programs vary in name and scope but share a structural pattern. The OEM selects a vendor, qualifies that vendor at the factory level, and then enrolls the dealer in the vendor's product as a condition of certification, co-op marketing eligibility, or factory program participation. The dealer pays the bill. The dealer did not select the vendor. The dealer cannot opt out without putting certification at risk.

The mandated software sits on top of the dealer's freely chosen stack. It rarely replaces what the dealer already runs. It overlaps. The dealer absorbs duplicate workflows at the rooftop, parallel dashboards at the management layer, and parallel compliance obligations at the principal layer. The economics of the mandate stack run between three hundred and twelve hundred dollars per rooftop per month, on top of the dealer's freely chosen stack. The factory understands the leverage and prices the program accordingly. The dealer principal absorbs the cost as a non-negotiable line in his operating budget.

Source: Brevmont Labs, OEM mandate stack analysis, December 2025.

---

The factory as a software customer with leverage

The dealer principal is the customer of the freely chosen software stack. He selects the CRM, the equity tool, the digital retailing platform, the BDC software, and the inventory pricing tool. He negotiates the contracts. He renews them on the cycle that matches his operating preference.

The factory is the customer of the mandated software stack. The factory selects the vendor. The factory negotiates the master agreement. The factory enrolls the dealer in the vendor's product. The dealer pays the bill but does not select the product, does not negotiate the price, and cannot exit the relationship without putting his certification at risk.

This dual-customer structure produces a vendor incentive that is aimed at the OEM, not the dealer. The mandated software vendor's product roadmap optimizes for OEM compliance reporting, OEM-branded program features, and OEM-mandated lead source integrations. The dealer's actual pain is downstream of all of this. The vendor invests in the relationship that controls the largest single line of revenue, which is the factory, not the rooftop.

The dealer principal sees this structure on his AP report as a software line he cannot negotiate. The vendor is qualified by the factory. The pricing is set at the factory level. The renewal is automatic because non-renewal threatens certification. The dealer's leverage in this relationship is structurally close to zero.

The categories the OEM mandates

The categories of software the major OEMs mandate vary by manufacturer, but the pattern is consistent across the industry.

Digital retailing is the most visible mandated category. Each major OEM operates a digital retailing program with a designated vendor or a small set of qualified vendors. Ford runs Blue Advantage. GM runs Premier. Toyota runs SmartPath. Stellantis runs its retail platform. Hyundai runs Click to Buy. Each program enrolls the dealer's website into a factory-branded retailing experience that the dealer pays the vendor for and the factory promotes through national marketing. The dealer's freely chosen digital retailing platform, where the dealer has selected one, runs in parallel.

Lead routing and lead management is the second mandated category. The OEM operates a lead aggregator that routes factory-generated leads, OEM website leads, and incentive-related leads through a designated CRM module or third-party routing tool. The dealer's freely chosen CRM may receive these leads through a separate ingestion path, often delayed and often with field mapping inconsistencies that the rep absorbs.

Compliance reporting is the third mandated category. Each OEM requires the dealer to report on a defined set of operational metrics through a designated compliance dashboard. The dashboard is operated by a vendor the OEM selects. The dealer pays for the dashboard. The dealer's compliance team or sales manager populates the dashboard on a cycle defined by the OEM.

Inventory pricing and management is the fourth, though less universally mandated. Some OEMs, particularly in luxury segments, operate or recommend an inventory pricing system that the dealer is expected to use. The dealer's freely chosen inventory pricing tool may run alongside it.

Service-side software, including service scheduling, technician productivity, and recall reporting, follows a similar pattern. The OEM mandates a tool. The dealer pays. The dealer's freely chosen alternatives, where they exist, run in parallel.

The economics of the mandate

The dealer's monthly software cost includes a mandate-stack contribution that varies by manufacturer and program enrollment. The contribution lands between three hundred and twelve hundred dollars per rooftop per month across the major OEMs, with luxury and premium brands at the higher end of the range and mass-market brands at the lower end. A dealer principal running a five-rooftop group across multiple OEM brands carries a mandate-stack cost between eighteen thousand and seventy-two thousand dollars per year.

This cost sits on top of the freely chosen stack. The freely chosen stack already runs eight to fifteen thousand dollars per rooftop per month, as documented in our earlier stack analysis. The mandate stack adds another three hundred to twelve hundred. The aggregate, including both layers, exceeds nine hundred thousand dollars annually for a five-rooftop group at the high end of the range.

The principal cannot reduce the mandate-stack cost through procurement. The OEM's master agreement sets the price. The principal cannot consolidate the mandate stack into the freely chosen stack because the OEM does not allow substitution. The principal cannot defer enrollment because non-enrollment threatens certification. The mandate stack is a price-taking line on the operating budget.

The factory understands this. The pricing is calibrated against the maximum the dealer can absorb without exiting the franchise relationship, which is a high ceiling because exiting a franchise relationship is itself a multi-million-dollar event. The mandate stack's economics reflect this calibration. The dealer absorbs the cost because the alternative is worse.

The duplicate workflow at the rooftop

The mandate stack's larger cost, beyond the line item on the AP report, is the duplicate workflow it produces at the rooftop level.

When the OEM mandates a digital retailing program and the dealer also runs a freely chosen digital retailing platform, the rep ends up working leads through two parallel funnels. The OEM-branded funnel surfaces leads from the factory's marketing programs. The dealer-branded funnel surfaces leads from the dealer's marketing programs. The two funnels do not integrate cleanly. The rep tracks pipeline stage in both. The manager reviews dashboards from both. The reporting from each parallels the other without composing into a single view.

The same duplication exists in lead routing. The OEM-mandated routing tool delivers leads on its own schedule, often with field mappings that differ from the dealer's CRM standard. The rep's first action on receiving an OEM-routed lead is often to manually copy the lead into the dealer's CRM so the lead enters the dealer's pipeline reporting. This rekeying takes minutes per lead, multiplied across hundreds of OEM-routed leads per month at a typical rooftop.

Compliance reporting produces a third duplication. The OEM-mandated compliance dashboard requires the dealer's data to be exported from the freely chosen systems and uploaded into the OEM's dashboard on a cycle the OEM defines. The export-upload step is rarely automated. The compliance staff or sales manager spends hours per week on this work. The dealer principal sees the cost as compliance overhead and not as a mandate-stack cost.

Across the duplicated workflows, the rooftop's labor cost compounds. Conservative estimates of the duplicated-workflow labor cost place it between ten and thirty thousand dollars per rooftop per year, on top of the line-item cost of the mandate-stack vendors themselves.

Why the OEM-mandated vendor wins despite being inferior

The OEM-mandated vendor is rarely the best product in its category. The freely chosen vendors the dealer would have selected on competitive evaluation are usually deeper, better configured, and better integrated with the rest of the stack. The mandated vendor wins not on product but on the OEM's enrollment leverage.

The mandated vendor's roadmap reflects this commercial reality. The vendor invests in OEM-facing features, including required compliance reports, branded UI elements, and preferred data export formats. The vendor invests less in dealer-facing features, including the rep's daily workflow and the integration with the dealer's freely chosen systems.

The principal experiences this gap as a product that feels structurally less polished than the freely chosen alternative. The rep experiences it as a tool that does not fit the day's workflow. The manager experiences it as a dashboard that reports on the OEM's KPIs rather than the rooftop's KPIs. None of these gaps generate competitive pressure on the mandated vendor because the dealer cannot defect.

This is the structural condition the mandate produces. The vendor's product quality plateaus because the OEM relationship is the moat. The principal absorbs the gap because exit is not available.

The franchise law context

The franchise law framework that governs the U.S. dealer-OEM relationship constrains both parties. The dealer cannot be terminated without cause. The OEM cannot mandate software in ways that cross the legal threshold for restraint of trade. Most state franchise laws have language that limits the OEM's ability to coerce the dealer into specific vendor relationships.

In practice, the legal language has not slowed the mandate stack's growth. The OEM structures the mandate as a condition of voluntary program participation, not as a hard contractual requirement. The dealer can decline the program. Declining the program forfeits the co-op marketing dollars, the factory incentives, the Certified Pre-Owned designation, or the Trade-In Plus program eligibility. The economic cost of declining is meaningfully larger than the cost of enrolling. The dealer enrolls.

The legal framework therefore protects the OEM from formal coercion claims while preserving the OEM's economic leverage to drive enrollment. The dealer principals' associations have raised concerns about this dynamic across multiple legislative cycles. The framework has not materially changed.

The mandate stack persists because the legal scaffolding around it is stable.

What the next layer can and cannot do about the OEM mandate

The execution layer Brevmont is building above the dealer stack does not eliminate the OEM mandate. The mandate exists at the franchise relationship layer, not at the software-architecture layer. The dealer continues to pay the OEM-mandated vendors.

What the layer can do is absorb the duplicate workflow cost. The layer reads the mandated tool's surface, captures the lead and activity data, and writes the same data into the dealer's freely chosen tools through the rep's authenticated session. The rekeying disappears. The compliance export gets automated. The dashboards finally compose because the layer composes them.

The layer does not change the OEM's leverage over the dealer. It changes the operational cost the dealer absorbs in serving that leverage. The principal continues to write the check to the mandate-stack vendor. The principal stops paying the duplicate-workflow tax. The economics improve at the operational layer even when they cannot improve at the contract layer.

This is the achievable scope. The architecture extends across the mandate stack as cleanly as it extends across the freely chosen stack. The integration job is the rep's session in both cases.

---

*Brevmont Labs publishes original research on the execution layer beneath relationship-driven sales. The mandate-stack ranges in this essay represent typical category observations across U.S. franchise OEMs, not single-manufacturer or single-rooftop measurements.*