One customer record across sales, service and commerce
An illustrative retail programme: three CRM instances, two support inboxes and a commerce platform consolidated into a single customer record that sales and service both trust.
By IT NET Solution
- Sector
- Multi-channel retail (illustrative)
- Scope
- CRM consolidation, service design, commerce integration
- Platforms
- Zoho CRM, Zoho Desk, commerce platform, Sapier
- Engagement
- Design, migration and ongoing operations
The challenge
Three commercial units had each bought their own CRM at different times. A customer who ordered online, returned an item in a store and then called support existed as three unrelated records, and none of the three could be trusted as the current state.
Service agents switched between two ticketing tools depending on where the order had come from. Reporting required a monthly export that two analysts assembled by hand, and the sales leadership had quietly gone back to a shared spreadsheet for pipeline review.
The approach
- 01
Agree the customer definition
Before any configuration, the programme fixed what counts as one customer, which identifier survives a merge and who is allowed to change that record.
- 02
Design one module model
Accounts, contacts, orders, returns and service cases were modelled once, with a deliberately small set of mandatory fields and clear ownership per field.
- 03
Migrate in waves
The largest unit moved first with a frozen data set, so the second and third migrations reused a tested mapping instead of inventing their own.
- 04
Automate the handovers
Order and return events from the commerce platform create and update records automatically, with escalation rules replacing manual inbox monitoring.
The solution
Zoho CRM became the single record for accounts, contacts and opportunities, with Zoho Desk running service processes against the same customer data. A commerce integration built on Sapier keeps orders, returns and entitlements synchronised, and every message carries the originating order reference.
Reporting moved into the platform: pipeline, service volume and return rates are assembled from the same modules the teams work in, so the numbers reviewed in management meetings no longer depend on a separate export process.
What changed operationally
- One record structure for sales, service and commerce, with documented field ownership.
- Service agents see order and return history inside the case, without switching tools.
- New commercial units are onboarded by configuration rather than by a new CRM instance.
- Data quality is reviewed through scheduled exception reports instead of monthly reconciliation.
Topics
- CRM consolidation
- Service processes
- Data migration
- Commerce integration
Related reading
Designing a CRM your sales team will actually use
Most CRM problems are design problems, not software problems. A practical view of module structure, pipeline logic and the fields that decide whether adoption holds.
Where Zoho CRM ends and a custom application begins
Approval chains, internal tooling and operational processes rarely belong in a sales CRM. A decision framework across CRM configuration, Zoho Creator and a separate service.
Order-to-invoice flow across commerce, ERP and logistics
An illustrative integration programme: nightly exports and manual reconciliation replaced by a monitored, queue-based flow between a commerce platform, SAP Business One and a logistics provider.
Working on something similar?
Describe the systems, the constraints and what needs to change. We will outline a realistic path and the trade-offs behind it.