ScaleDMS × CarGurus

Inventory feed.

ScaleDMS produces a CarGurus-formatted CSV from each dealership's live inventory and uploads it on a daily schedule. The feed is fully compliant with the dealer-info-on-every-row format documented in the CarGurus Inventory Import specification.

Transport

CSV column layout

Every row contains the dealer identity block followed by the vehicle block, exactly as CarGurus expects:

Image handling

Photos are filtered to formats CarGurus accepts before they reach the feed, so a single non-conforming upload (HEIC, WebP, etc.) cannot demote a listing to “no photo” status on cargurus.com. ScaleDMS prefers a pre-sized marketplace gallery variant when available, falling back to the original asset so freshly-uploaded vehicles still appear in the same-day feed.

Inventory scope

The feed includes only vehicles that satisfy all of the following: not soft-deleted; owner type of DEALER_INVENTORY or CONSIGNMENT; status of AVAILABLE or RESERVED. Sold and archived vehicles are omitted by construction so a dealer's CarGurus storefront mirrors their live lot.

Lead ingestion.

CarGurus lead delivery uses email. ScaleDMS provisions a unique inbound email address for every dealership and registers it as the dealer's DealerCRMEmail in the inventory feed. Every CarGurus lead notification is captured, parsed, and materialized as a structured lead record — no human re-keying, no copy-paste from inbox to CRM.

What gets parsed

Quoted-printable encoding, HTML entities, and Unicode smart quotes are all normalized so the parsed payload is clean, structured data inside the dealer's leads workspace.

Deal Rating Badge.

Dealer storefronts hosted by ScaleDMS embed the official CarGurus Deal Rating Badge on every vehicle detail page. The badge is loaded via the public CarGurus badge script and configured per the platform's published options:

var CarGurus = window.CarGurus || {};
window.CarGurus = CarGurus;
CarGurus.DealRatingBadge = CarGurus.DealRatingBadge || {};
CarGurus.DealRatingBadge.options = {
  style: "STYLE2",
  minRating: "FAIR_PRICE",
  live: true,
  liveInterval: 60000,
  debug: false
};
// Loader script:
// https://static.cargurus.com/js/api/en_CA/1.0/dealratingbadge.js

Because the badge runs against the same VIN that ScaleDMS publishes to the CarGurus feed, the rating shown on a dealer's site stays consistent with the rating shown on cargurus.com.

Operational reliability.

ScaleDMS treats CarGurus integration as a first-class operational surface, with safeguards designed to prevent the most common silent-failure modes that affect inventory feeds in this category.

1. 01

   Pre-flight validation

   Every upload — scheduled or manual — is gated behind a structured validator that checks dealer name, full street address, postal code, and a working CRM email before a single byte hits the FTP server. Issues are surfaced to operators with field-level messages instead of being deferred to a CarGurus support ticket later.

2. 02

   Zero-vehicle guard

   A feed that would resolve to zero vehicles is rejected at the source. This prevents the “deletion-by-omission” failure mode where a misconfigured query silently removes a dealer's entire CarGurus storefront.

3. 03

   Encrypted credentials

   CarGurus FTP passwords are stored using authenticated symmetric encryption. They are decrypted only at the moment of upload, in memory, and are never written to logs.

4. 04

   Structured upload log

   Every upload attempt — success or failure — produces a durable audit record with vehicle count, file size, duration, trigger source (cron vs. operator-initiated), and the precise error message on failure. This gives both Enscale operations and the dealership a single source of truth for feed health.

5. 05

   Differentiated error reporting

   Transient FTP errors, malformed dealer profiles, and upstream CarGurus rejections are reported as distinct conditions rather than collapsed into a generic “upload failed” status.

Onboarding a CarGurus dealership.

Activating the CarGurus integration on a ScaleDMS tenant is a self-serve flow inside the Enscale operations console. The dealer-success path looks like this:

1. 01

   Receive CarGurus FTP credentials

   The dealer (or CarGurus on their behalf) provides the assigned CompanyId, FTP username, and FTP password.

2. 02

   Configure the connection

   Enscale ops enters the credentials in the Inventory Feeds tab. The host defaults to ftp.cargurus.com; credentials are encrypted on save.

3. 03

   Run a preview

   A preview upload generates the CSV and surfaces the row count, file size, and any pre-flight warnings. No data is sent to CarGurus during a preview.

4. 04

   Send the first live feed

   A manual upload promotes the dealership into the daily schedule. Subsequent uploads run automatically.

5. 05

   Verify lead routing

   The dealer's auto-generated CRM inbound address is registered with CarGurus so leads flow back into the platform from day one.

Compliance & data handling.

How dealer and shopper data is segregated, secured, and audited within the ScaleDMS ? CarGurus pipeline.