Start here
Define the job before comparing the tools
CRM can mean two different things in ecommerce. A sales CRM helps a team manage leads, deals, wholesale accounts, and follow-up. A commerce help desk helps agents answer order questions, make safe changes, and keep customer conversations together. Some businesses need both, but they should not buy both jobs by accident.
Write down one customer journey before opening a demo. Name the person doing the work, the information they need, the action they take, and how the next person knows it is finished. That simple map will eliminate more products than a long feature checklist.
The starting point
Choose the primary job: sales pipeline, wholesale account management, ecommerce support, retention work, or a deliberate combination. If the team cannot agree on the job, it is too early to choose the software.
The process
Work through the decision in a sensible order
Name the team and the next action
Start with the daily work, not the word CRM. A salesperson following a wholesale opportunity needs a different screen from an agent handling a damaged-order request.
- • Who opens the record?
- • What decision do they make?
- • What must happen next?
- • How is completion recorded?
Choose the minimum useful customer record
Keep only data that staff can explain and use. More fields create more cleanup, privacy work, and opportunities for two systems to disagree.
- • Contact and company identity
- • Orders and products
- • Consent and communication history
- • Owner, stage, and next activity
Set permissions before importing data
Decide who can view orders, export contacts, issue refunds, change ownership, edit consent, build automations, and administer integrations.
- • Least access for each role
- • Approval for sensitive actions
- • Audit history
- • Fast removal when someone leaves
Draw the system boundaries
Pick the owner of customer identity, orders, marketing consent, support conversations, sales stages, and reporting. A connector should move data; it should not create two competing records.
- • Source and destination for each field
- • Update direction
- • Duplicate handling
- • Failure alerts and repair owner
Price the working setup
Include users, contacts or tickets, marketing hubs, support channels, onboarding, integrations, storage, and the staff time needed to govern the system.
- • Normal and growth-year volume
- • Required plan for permissions
- • Implementation help
- • Internal system owner
Pilot one complete journey
Use a small clean data set and one representative workflow. A useful pilot ends with an export and rollback plan, not only a successful demo.
- • Realistic records
- • Every intended role
- • Reports and duplicate controls
- • Export, deletion, and rollback
Owner worksheet
Write down these decisions
| Item | What to record |
|---|---|
| Primary customer job | The one sales or support journey the new CRM must improve. |
| Required data | Only the customer, order, consent, activity, and ownership fields needed for that journey. |
| Sensitive actions | Exports, refunds, deletions, integrations, and administrative changes that need tighter access. |
| Success measure | A clear outcome such as fewer handoffs, faster follow-up, cleaner pipeline reporting, or fewer tab changes. |
| Exit path | What can be exported, what must be recreated, and how the old workflow is restored. |
Red flags
Slow down when any of these appear
- The demo uses a perfect customer record but never shows duplicate or missing store data.
- The required permissions exist only on an unbudgeted plan.
- A support tool is being bought to fix a sales-pipeline problem, or the reverse.
- The integration description does not say which system wins when a field changes in two places.
- Nobody owns field definitions, automations, consent, or monthly data cleanup.
- The contract is moving faster than the pilot and exit review.
Action plan
Turn the guide into a short piece of work
- Interview one person from sales, support, marketing, and operations.
- Choose one journey and write the current steps on a single page.
- Create the minimum customer record and permission map.
- Shortlist three products that solve the same primary job.
- Run the same journey in each with a clean sample.
- Compare adoption, data quality, permissions, cost, and exit—not the longest feature list.
If a configurable sales CRM and the wider Zoho suite match the worksheet, review Zoho CRM's current plans (opens in a new tab) as part of the same controlled comparison.
Editorial method
How this guide was prepared
Commerce Stack Guide reviewed the official sources below and translated the decision into a small-business workflow. The guide does not claim hands-on testing and does not replace accounting, legal, privacy, security, or other professional advice where those reviews are needed.
Product prices and limits change. Use the worksheet to verify current details with representative data and a reversible test before committing.
Sources