CRM & sales process
CRM for Multi-Location Powersports Dealer Groups: A Buyer's Guide
How a powersports dealer group should choose a CRM: the operating model to settle first, what to test in a demo, sharing records legally, and a rollout plan.
Quick answer
A powersports dealer group needs a CRM that keeps one record per customer across every store, routes each lead to one owner, shows units at sister stores, and reports by rooftop. Settle your BDC model and lead ownership rules first, then test vendors on your own cross-store scenarios, including who can see which records.
A CRM that works well in one store can cause trouble at three. The same rider gets entered twice, two salespeople call them on the same afternoon, the right unit sits at a sister store nobody checked, and the group report averages a great store and a struggling one into one number nobody can act on.
This guide is for the dealer principal, group GM or operations lead choosing a CRM for two or more powersports, marine or RV stores. It covers the decisions to make before any demo, what a group CRM has to do, how to test it on your own scenarios, the legal questions that come with sharing customer records between stores, and how to roll it out. PSX Ascend sells a CRM and multi-location BDC software, so our section is at the end. Everything before it works on any vendor.
If you are still deciding whether to open a second store, start with our guide to adding a second dealership location.
The short answer
A dealer group needs a CRM that does four things a single store can live without: one customer record across every store, one owner for every lead, inventory you can see across rooftops, and reports you can read store by store. On top of that, it needs store-level access controls, because one shared database does not mean every user should see every customer.
Most of the work is not software. Decide how leads reach the stores, who owns a customer who shops two locations, and how credit is split, then test vendors against those rules.
Where a single-store CRM breaks in a group
The problems show up in the same places in most groups:
- Duplicate customers. A buyer from store one calls store two and gets a new record. Service history sits in one record and sales history in the other. Our guide to cleaning up duplicate CRM records covers the cleanup; a group needs matching that stops it happening.
- Two salespeople, one customer. Without a written ownership rule, stores compete for the same rider and managers spend their time refereeing.
- Units nobody can see. The side-by-side the customer wants is at a sister store, the salesperson cannot see it, and the deal goes to a competitor.
- Different brands at each store. Store one sells two OEM lines, store two sells a third. OEM leads arrive for a specific store, and a lead for a brand one store does not carry has to reach a store that does.
- Reports that blend. A group average hides the store with slow response times. Leaders need each rooftop side by side, measured the same way.
- Process drift. Each store builds its own follow-up habits, notes get thin, and the numbers stop meaning the same thing from store to store.
Pick your operating model before the demo
The CRM has to fit how your group handles leads and calls. Decide this first, because it changes what you test.
| Model | How it works | Suits | What the CRM must support |
|---|---|---|---|
| Central BDC | One team answers every web lead and call for all stores, then books appointments into each store | Groups with stores close together, or the same brands at each store | Routing by brand and location, a group calendar, a clear handoff to the store that will sell |
| Store lead desks | Each store answers its own leads, with group rules on response time and follow-up | Stores far apart, or very different brands at each | Store-level queues, the same activity measures at every store, group-level reporting |
| Hybrid | A central team covers after-hours, overflow and re-engagement; stores own leads in working hours | Most groups of three or more stores | Rules that change by time of day, reassignment with full history, shared notes |
Whatever you choose, write down three rules before you see a vendor:
- Who owns a customer who buys at one store and shops at another (last store to sell them, nearest store, or the store they contacted).
- How credit is split when a customer is passed to another store, or a unit moves between stores.
- What every store must do the same way: response time, minimum follow-up, notes and dispositions, and how an appointment is counted.
Our article on lead accountability software covers what managers should be able to see once those rules are set.
What a dealer group CRM has to do
Use this table as your shortlist. The last column is the test: if you cannot see it done on screen, score it as missing.
| Capability | Why it matters in a group | How to test it in the demo |
|---|---|---|
| One record per customer across stores | Stops double follow-up and keeps sales and service history together | Enter a customer at store one, then enter them at store two with a slightly different email. Does the CRM catch the match? |
| Lead routing by store, brand and source | OEM leads belong to a store; marketplace and website leads may not | Send an OEM lead for a brand only store two carries. Where does it land, and how fast? |
| Reassignment with history | A customer moving between stores must not start over | Move a live lead to another store. Do notes, texts, calls and the unit of interest move with it? |
| Inventory across rooftops | Sell the unit the customer wants, wherever it is | Search for a unit that only a sister store has, from a salesperson's login |
| Store-level permissions | Not every user needs every store's customers | Log in as a salesperson at store one. What can they see from store two? Who can export a list? |
| Activity log | You need to know who opened or exported what | Ask for the log of one user's activity for one day |
| Rooftop-by-rooftop reporting | Group averages hide problems | Show response time, appointments and sold units for each store side by side, with the same definitions |
| Shared follow-up rules | The same standard at every store | Set a group follow-up rule, then show one store's exception |
| Consent tracking per store | Consent to one store may not cover another (see the next section) | Show where a customer's text consent is stored, and which store it was given to |
| Onboarding a new or acquired store | Groups grow; adding a rooftop should not mean a new project | Ask how a store's existing customer list is loaded and matched, and how long it takes |
For the criteria every CRM should meet, whether you run one store or ten, use the weighted scorecard in our guide on how to choose a powersports CRM, and raise the weight on multi-location and reporting.
Your DMS may already offer some of this. Lightspeed DMS, for example, describes an "All-Store List View" on its multi-store page to "See every lead, quote, and deal across the entire organization in one screen," along with a "Universal Customer List" and searching sister stores' inventory (read 20 October 2026). If you are weighing a separate CRM, compare it with what your DMS includes; our guide to powersports CRM vs DMS explains where each fits.
Sharing customer data across stores: the legal side
Most advice on group CRMs says to put every store in one database. Operationally that is right. It leaves out that many groups run each store as its own company, and federal rules treat sharing customer data between related companies differently from using it inside one store. None of the vendor guides on group CRMs we read for this article mention it, so ask about it before you sign.
This is general information, not legal advice. Take the questions below to your attorney.
The FTC Affiliate Marketing Rule
The FTC's Affiliate Marketing Rule (16 CFR part 680) "applies to any motor vehicle dealer" that uses information from its affiliates for marketing solicitations, or provides information to its affiliates for that purpose. The definition of motor vehicle it relies on, in 12 U.S.C. 5519, includes "motorcycles," "recreational boats and marine equipment," and "motor homes, recreational vehicle trailers, and slide-in campers." An affiliate is a company "related by common ownership or common corporate control."
The rule's core: a store may not use "eligibility information" about a consumer received from an affiliate to make a marketing solicitation unless the consumer got a clear notice, a reasonable and simple way to opt out, and has not opted out. There are exceptions, including a customer with whom the store already has a pre-existing business relationship, and a customer who contacted the store or asked for the offer. "Eligibility information" is defined by reference to the Fair Credit Reporting Act, so ask your attorney which of the purchase and credit history your stores share falls inside it.
Texting and calling consent
Under the FCC's TCPA rules, prior express written consent is an agreement that "clearly authorizes the seller" to send the marketing messages, and the seller is "the person or entity on whose behalf a telephone call or message is initiated." If each store is a separate company, ask whether a consent captured on store one's website covers marketing texts sent for store two. Your CRM should record which store a consent was given to, not just "consented: yes."
Access and logging under the Safeguards Rule
Dealers who arrange financing are covered by the FTC Safeguards Rule. It asks for access controls that "Limit authorized users' access only to customer information that they need to perform their duties and functions," and for controls to "monitor and log the activity of authorized users." A group-wide view is useful for the BDC and for leadership. It should not mean every salesperson at every store can open or export every customer file.
A demo script for dealer groups
Send every vendor the same script a week before the demo, and ask them to run it live on their system rather than on slides.
- Load your structure. Give them your stores, the brands each store carries, and your operating model from the table above.
- The cross-store customer. A customer bought a side-by-side at store one two years ago. They submit a web lead at store two for a new model. Show what the store two salesperson sees.
- The wrong-store OEM lead. An OEM lead arrives for a brand only store three carries. Show where it goes and who is alerted.
- The unit at a sister store. A store one shopper wants a unit only store two has in stock. Show the search, the hold and the handoff.
- The reassignment. Move a lead from store two to store one. Show that notes, messages and calls moved with it.
- The permission check. Log in as a store one salesperson and try to open and export store two's customers.
- The group report. Show last month's response time, appointments and sold units by store, side by side.
- The new store. Explain, with a timeline, how an acquired store's customer list would be loaded and matched.
Have two people score each step from 1 to 5 separately, then compare. A step the vendor could not show scores 1.
Rolling it out store by store
A group rollout fails when every store goes live at once with different habits. A steadier order:
- Clean and match the data first. Merge duplicates across the stores' lists before go-live, not after.
- Set the group rules. Ownership, credit, response time, follow-up steps, and notes and dispositions, in writing.
- Start with one store, or with the central BDC. Fix routing and permissions while the stakes are small.
- Add stores one at a time. Check each store's routing, consent records and user access before the next.
- Turn on group reporting last, once every store records activity the same way, so the comparisons mean something.
- Review monthly by store. Response time, follow-up completion and appointment show rate, side by side.
If you are moving from another system, our guide on switching dealership CRM systems covers data export and training, and our guide to what a powersports CRM costs explains how per-user and per-rooftop pricing play out for a group.
Red flags in a group CRM pitch
- The demo shows one store only, and "multi-store" appears only on a slide
- Duplicates are handled by a cleanup report, not by matching at entry
- Every user can see every store's customers, with no store-level permissions
- No activity log, or a log only the vendor can read
- Group reports show only totals, with no store-by-store view
- Consent is stored as yes or no, with no record of which store it was given to
- Adding a store is quoted as a new implementation project with no timeline
- Data export terms are not in writing
Where PSX Ascend fits
PSX Ascend builds for dealer groups as well as single stores. Our multi-location BDC software describes four group functions: multi-store lead assignment, to "route each opportunity to the right rooftop, team, and owner without losing the original customer context"; connected call coverage across locations; advanced record matching, to "bring customer activity and purchase history together before duplicate records create conflicting follow-up"; and shared inventory visibility, to help teams match a customer to a unit "even when that vehicle sits at another rooftop." Authorized teams can assign and reassign opportunities across stores while keeping the customer context and a visible next action, and group leaders get a central view to compare activity, follow-up, appointments and calendars by rooftop.
The AI-powered powersports CRM gives one customer operating view across every rooftop "without losing local accountability," and runs on one connected platform with AI inventory management and the AMP marketing automation platform.
- Calls. PSX records and tags every inbound call, and outbound calls where state law permits. Recordings live in the customer record and in a dashboard view for manager review.
- Follow-up. Associates work each new lead with quick touches. Notes and accurate dispositions are required when a sale does not happen, and managers are prompted to review stalled deals. Then ALMA, the Automated Lead Management Assistant, takes over repetitive re-engagement and brings the customer back to a live conversation with a person. ALMA makes no AI voice calls.
- Your demo. Bring the script above. Ask us the same questions you ask every vendor about permissions, activity logs, consent records, your DMS connection, moving your data and contract terms, and hold us to written answers.
You can also see the same multi-location BDC software on our sister site, PSXDigital's multi-location BDC software page.
Sources
- Legal Information Institute, Cornell Law School, 16 CFR 680.1, Purpose and scope (paragraph (b), application to motor vehicle dealers, read 20 October 2026)
- Legal Information Institute, Cornell Law School, 16 CFR 680.3, Definitions (affiliate, eligibility information, motor vehicle dealer)
- Legal Information Institute, Cornell Law School, 16 CFR 680.21, Affiliate marketing opt-out and exceptions (paragraphs (a)(1) and (c))
- Legal Information Institute, Cornell Law School, 12 U.S.C. 5519 (subsection (f)(1), definition of motor vehicle)
- Legal Information Institute, Cornell Law School, 47 CFR 64.1200 (paragraphs (f)(9) and (f)(10), prior express written consent and seller)
- Legal Information Institute, Cornell Law School, 16 CFR 314.4, Elements of an information security program (paragraphs (c)(1) and (c)(8), access controls and activity logging)
- Lightspeed DMS, Multi-Store (all-store lead view, universal customer list and sister-store inventory, read 20 October 2026)