CRM · ScoutRV → DP360
ScoutRV and DP360
Every lead your site generates lands in DP360 in the format it expects, routed to the right store and the right team.
How it works
- Leads are written on the Scout side before delivery, so nothing depends on DP360 being reachable at that moment.
- A failed delivery is retried rather than dropped, and the retry re-posts only the leg that failed rather than duplicating the lead everywhere else it was already delivered.
- Scout also produces an inventory feed for DP360 where a dealer uses it on the merchandising side.
Other integrations
Lightspeed → ScoutRV
Lightspeed DMS
Automatic inventory sync from Lightspeed, including multi-store feeds.
Read more
IDS → ScoutRV
IDS DMS
Automatic inventory sync from IDS, the most common DMS in RV retail.
Read more
ScoutRV → RV Trader
RV Trader
Outbound inventory feed to RV Trader, with monitored delivery.
Read more
Questions
DP360 CRM questions
What happens if DP360 is down when a lead comes in?+
The lead is stored on our side and retried. You do not lose it, and it is visible in the Scout admin regardless.
Can we route by location?+
Yes — per location and per lead type.
Do we keep our existing DP360 setup?+
Yes. Scout delivers into it; nothing inside DP360 changes.