What dealership software
is trying to solve.

A capability is more precise than a category

“Payments” can mean sending a link, posting a cleared payment, mapping a tender code or updating paid status. It does not automatically mean closing an RO or writing repair lines. “Integration” can mean a connector exists without identifying the fields, direction, timing or allowed operations.

Each record retains a stable claim ID, canonical feature key, input/output, operation system and source. Problem labels and suggested buyers are our analysis. Vendor statements are neither performance tests nor independent certification. Beta availability is distinct from general availability; unknown is not unsupported.

Operation filters refer to the named system in the record. Reading from CDK and writing to HubSpot does not establish HubSpot-to-CDK writes. Messaging customers from a read-only integration does not make that integration read/write. Product-level features are not necessarily Fortellis endpoint capabilities.

Sources are vendor-owned public pages. The inaccessible RevolutionParts support source is retained as a clearly marked research lead; its two detailed sync claims are unresolved. Release link checks could not reopen RouteOne (403) or RedLine7 (TLS failure); their records retain vendor-source research and have not been functionally verified. Adjacent RouteOne and DealerSocket examples are useful comparators with unverified Fortellis membership. No official Tekion directory or restricted marketplace dataset was imported.

For service-specific buying questions, use the 46-record messaging comparison. For deeper prior profiles, see the marketplace research hub. Neither supplies a verified complete ecosystem denominator.

Search the problem and feature graph

Filters combine. Search includes problems, feature keys, products, vendors, source IDs and scope notes. All records remain readable without JavaScript. Export uses only the currently selected claims and their referenced entities.

69 claim records in this edition.

64 vendor claims, 3 beta and 2 unresolved; no independent tests.

Full JSON graph · Plain-text catalog

Product index and scope

This index is unfiltered, so you can inspect all product relationships and the sources supporting them.

What remains before “every product”

• Full product universe and current official membership remain unestablished.
• AutoText Denied Work Module: base product evidence only.
• Dealerlogix exact Create and Update RO SKU and CDK scope unresolved.
• RevolutionParts exact sync operations need accessible first-party evidence.
• Yooz remittance general availability after beta unverified.
• In The Car and Vision Dealer Solutions are discovery leads, excluded from product totals.
• Inventory, security, payroll and compliance categories need broader research.

Next passes should establish a permitted, deduplicated inventory across every department; resolve current vendor/brand ownership and exact product names; review each vendor’s own product, integration, API and support pages; add atomic claims with dates and scope; independently check contradictions; and record unavailable evidence rather than fill gaps by inference. An eligible count and reviewed count must use the same scope before reporting a coverage percentage.

Test promising products separately using synthetic dealership workflows, explicit permissions, failure cases and measured outcomes. This catalog is desk research. It performs no API calls, customer messaging or financial transactions. It creates no scheduled crawl.