Skip to main content
All resources

Integration guide

What data VehicleDesk imports

A plain-language guide to supported Shopmonkey record categories, local workflow data, import freshness, visible coverage gaps, and data minimization.

Subject owner
VehicleDesk Product and Engineering
Last reviewed
2026-07-11
01

Supported source context

Current import workflows cover supported customer, vehicle, service, payment, appointment, estimate, invoice, and repair-order context according to provider API availability and the configured sync scope.

02

Locally managed records

VehicleDesk may store notes, reminders, tasks, opportunity/deferred workflow state, outcomes, consent/suppression evidence, and data-quality findings needed for its own workflows.

03

Missing data remains missing

A blank field, unavailable history period, unlinked record, or provider error is shown as a coverage limitation. VehicleDesk should not manufacture prior-period comparisons or infer a source record that was not imported.

04

Minimize use

Provider and customer data is used for the approved tenant workflow. Public marketing captures use synthetic fixtures and do not read production customer databases.

Related product detail

See how this guidance appears in VehicleDesk.

Open related workflow