Integration Hub

Connect your dealership to the systems it already runs on. Car Dealer Tracker Enterprise.

Car Dealer Tracker Enterprise connects the dealer operating system your team already uses to your existing DMS, ERP, or manufacturer portal through an isolated Integration Hub — with durable event capture, controlled connectors, reconciliation, and a full audit trail. Built for dealer groups and networks; priced and scoped after a real qualification.

ArchitectureIsolated Integration Hub
DeliveryDurable acceptance, at-least-once
Communication100% Async / Email & Messengers
Pilot Terms100% credited discovery
Integration Hub

One dealership platform. Your systems stay the source of truth where they should.

Duplicate entry between your DMS and your dealer app is not an integration strategy. The Integration Hub exchanges operational events — vehicle identity, inventory lifecycle, purchase milestones, valuations, holding cost, sale status — while each system keeps its responsibilities explicit.

01

Canonical vehicle metadata

Every exchanged event maps onto one canonical vehicle model, so three systems stop disagreeing about the same car.

02

Durable event ledger

Accepted events are recorded durably before anything is processed, with per-tenant retention and audit entries.

03

Reconciliation, not hope

Scheduled reconciliation detects missing, duplicate, stale, and conflicting records — even when transport reported success.

04

Connector-specific ordering policy

Ordering is never assumed globally. Each connector defines how it handles out-of-order events using occurrence time, source versions, or vendor rules.

Integration Hub

A controlled boundary — not a database pipe.

The Hub runs as an isolated project with its own credentials, queues, and policies. External systems never touch the shared production backend directly, and every credential resolves to exactly one tenant.

Every credential, queue, ledger row, and audit entry is tenant-scoped, and cross-tenant access is covered by negative tests.

  • A body tenant_id is never trusted as authorization; it must match the authenticated tenant.
  • Credentials are least-privilege, revocable per connector, and stored only in managed secret stores.
  • Logs carry identifiers, states, timing, and error classes — never full payloads, tokens, or customer PII.
  • The audit trail answers who changed what, when, through which connector, without storing business payload values.
01

Bi-directional event synchronization

Inbound and outbound events for vehicle identity, inventory lifecycle, purchase milestones, valuation, location/bay, holding cost, and sale status.

02

Retries, dead-letter queue, replay

Bounded exponential backoff with jitter, per-failure-class retry policy, a dead-letter queue for exhausted events, and controlled replay under approval.

03

Signed webhooks

Outbound deliveries carry event, delivery, and correlation IDs plus an HMAC-SHA256 signature with a replay window.

04

Security review before production

Authentication options (OAuth client credentials, mTLS, scoped API credentials), secret management, and IP allowlists are settled during paid discovery and reviewed before any pilot goes live.

Delivery semantics

Delivery semantics we will actually stand behind.

Integration marketing often promises magic. These are the exact guarantees the Integration Hub is built to provide.

Guarantee 01

Durable acceptance

An event is acknowledged only after it is durably recorded in the tenant's ledger. If acceptance fails, the sender knows.

Guarantee 02

At-least-once delivery

Transport may retry; duplicates are expected and handled. We do not claim exactly-once transport, because it does not exist between real systems.

Guarantee 03

Idempotency

(tenant, idempotency key) uniqueness and idempotent downstream calls mean a retried or replayed event does not create a duplicate business action.

Guarantee 04

Reconciliation

Independent checks catch what transport success can hide: missing, duplicated, stale, or conflicting records are surfaced for controlled correction.

How engagement works

Qualification, discovery, pilot — then production.

Enterprise integration is not self-serve checkout, and we do not promise a fixed price before understanding your systems. The path is short and explicit.

01

Free async qualification (Email / Messengers)

Submit your rooftop count, systems, volume, and APIs. We review your architecture and tell you clearly in writing if the Integration Hub is the right fit. No sales calls required.

02

Integration Readiness Sprint ($2,500)

A fixed-price discovery: system inventory, API and sandbox assessment, data-flow diagram, canonical mapping, volumes, security gaps, pilot scope, and a fixed quotation. Credited 100% toward a pilot signed within 30 days.

03

One-rooftop pilot

Read-only or shadow ingestion first; agreed outbound events after reconciliation succeeds; limited write-back only after per-operation authorization and rollback testing; a 30-day parallel run with your DMS.

04

Production rollout

Production onboarding includes incident contacts, severity definitions, runbooks, monitoring, and — only after load and failure testing — negotiated service levels. Expansion to more rooftops and connectors is gradual and reversible.

Enterprise pricing

Clear “from” pricing. Fixed quotes only after discovery.

Recurring platform fees are separated from one-time implementation labor, so you pay once for unique work and an accessible rate to keep it running.

Business

$49per rooftop / month, or $490/year

Established independent dealerships

  • Unlimited active inventory and full team governance
  • Business exports and repeatable standard connectors
  • Everything in Dealer Pro for every rooftop
Request written qualification

Enterprise Group

from $999per month

Multi-rooftop dealer groups

  • Up to five rooftops, two certified connectors
  • Higher accepted-event allowance
  • Priority support
Request written qualification

OEM / Dealer Network

from $1,499per month

Regional networks and manufacturer-led programs

  • Negotiated governance and regions
  • Connector portfolio options
  • Support and SLA options defined in contract
Request written qualification

Add-ons and implementation

Additional rooftopfrom $199/month
Beyond the plan's included rooftops
Additional certified connectorfrom $249/month
Repeatable, already-built connectors
Integration Readiness Sprint$2,500 one-time
100% credited toward an approved pilot signed within 30 days
Net-new custom connectorquoted after discovery
Undocumented vendor APIs remain paid implementation work

These are target enterprise packages, not a live billing catalogue. Enterprise plans are sold through a signed agreement, not self-serve checkout. A fixed implementation quote is issued only after the Integration Readiness Sprint.

Unchanged promise

Small dealer? Car Dealer Tracker stays built for you.

Nothing about enterprise changes the product you already use. Dealer Pro keeps its current price and billing, the free tier keeps up to two active vehicles, and dealers who already hold an active paid subscription keep their promised unlimited-inventory grandfathering through any future packaging change. New packaging limits apply only to future buyers after a separately communicated rollout — never retroactively to existing paid subscribers.

Qualification

Start with a free written qualification.

Tell us about your dealership group and the systems you need connected. Everything is handled asynchronously by email or your preferred messenger — no sales calls. This form composes an email draft in your own mail client — the website stores nothing.

Enterprise FAQ

What dealer groups ask first.

Do you already have a connector for our DMS?+

The Integration Hub is provider-agnostic, and the certified-connector catalogue grows with each production integration. Whether your specific vendor is already covered is exactly what the free written qualification determines. We never promise a connector for a system we have not verified.

Is delivery exactly-once?+

No honest integration layer claims exactly-once delivery between independent systems. The Hub provides durable acceptance, at-least-once delivery, idempotency keys that prevent duplicate business actions, and scheduled reconciliation that surfaces anything the transport missed.

Can Car Dealer Tracker replace our DMS?+

Not today, and we will not pretend otherwise. Enterprise integration connects Car Dealer Tracker to your existing DMS or ERP. A fuller DMS remains a long-term direction delivered module by module based on verified demand.

What about security review and compliance?+

Security options (machine identity, mTLS, IP allowlists), secret management, data residency, and subprocessor questions are resolved during paid discovery and documented before a pilot. We claim no certification — such as SOC 2 or ISO 27001 — that has not been independently completed.

Why is discovery paid?+

The Integration Readiness Sprint produces real deliverables — system inventory, API assessment, canonical mapping, security gaps, pilot scope, and a fixed quote — whether or not implementation turns out to be feasible. If it is not feasible, you receive a written gap report. The fee is credited 100% toward a pilot signed within 30 days.

Does this change pricing for small dealers?+

No. Dealer Pro keeps its current price and billing products. Enterprise packaging applies to new enterprise agreements only, and existing paid subscribers keep their promised unlimited-inventory grandfathering through any future packaging change.

Next step

Bring your dealership group's systems together — safely.

Start with a free written qualification, request an Integration Readiness Sprint, or message Enterprise about a multi-rooftop program.

Car Dealer TrackerFree · iPhone, iPad & Android
iOSAndroid