Skip to main content
All resourcesIntegration guide

What data VehicleDesk imports

A plain-language guide to the Shopmonkey records VehicleDesk imports, the workflow data it keeps, how freshness is tracked, and how coverage gaps stay visible.

Written by
VehicleDesk Product and Engineering
Content updated
September 17, 2026

Imported source records

Import workflows cover customer, vehicle, service, payment, estimate, invoice, and repair-order records according to the Shopmonkey API and the configured sync scope.

  • Customers: identity, contact, and relationship linkage
  • Vehicles: ownership, identifiers, mileage, and service linkage
  • Services, estimates, and repair orders: active-work and recovery context
  • Invoices and payments: recorded financial context for value and reporting

Records VehicleDesk keeps

VehicleDesk stores notes, reminders, tasks, appointment requests and schedule state, opportunity and deferred workflow state, outcomes, contact-eligibility evidence, and data-quality findings for its own workflows.

Missing data stays visible

A blank field, an unavailable history period, an unlinked record, or a provider error shows as a coverage gap. Prior-period comparisons and source records come only from what was actually imported.

Your shop's data stays yours

Provider and customer data serves the tenant's own workflows. Public marketing captures use synthetic fixtures and never read a production customer database.

Worked example: reading a coverage gap

Sync Health shows the last successful import and the period it covered. If a provider error interrupted a window, that window appears as a gap.

A report comparing two periods uses only the imported records. When a period is short, the comparison says so instead of implying a trend that the data does not support.

The team decides whether to re-run the import or wait for the next scheduled job, and the decision stays visible in the job state.

Checklist: using imported data responsibly

Run this before a number leaves the building.

  • Confirm the freshness timestamp before quoting a figure
  • Check that the period you compare is fully imported
  • Treat unlinked or blank fields as gaps, not zeros
  • Keep provider facts separate from VehicleDesk workflow notes

Common questions

It imports the record types the Shopmonkey API exposes and the configured sync scope requests: customers, vehicles, services, estimates, invoices, payments, and repair orders. Anything outside that scope shows as a coverage gap.

More guides

Other integration guides

Browse all 13 guides

See this workflow in a demo.

Thirty minutes on your own shop: we'll show where your revenue is leaking and how VehicleDesk would win it back.

Prefer to talk? Call 201-650-7371.