CRM for e-commerce businesses

Connect online orders with the conversations that need human attention

For e-commerce businesses, the useful unit of work is a customer promise connected to the authoritative booking, order or supplier record. This journey shows where CRM helps and where operational systems remain in control. Consider this practical starting point: a customer asks about an order through email or social messaging while the authoritative fulfilment status sits in the commerce system. A configured CRM can keep the contact, context, owner and next action together, while the business still decides whether staff can answer, the fulfilment team must investigate or a refund or dispute process is required.

Subscribe to 121 CRM Seller, billing and cancellationSee the CRM customer journey

Customer Thread

A visible customer request from start to finish

Illustrative example

Customer message
a customer asks about an order through email or social messaging while the authoritative fulfilment status sits in the commerce system
Order matched
customer, order reference, enquiry category, channel, current authoritative status, assigned person, promised response and next action
Responsibility assigned
whether staff can answer, the fulfilment team must investigate or a refund or dispute process is required
Human decision
Resolution or formal process
through live service queues, with a daily exception review and periodic retention check

Fictional Moorland Goods example. It demonstrates an operating pattern for e-commerce businesses, not a customer result, professional recommendation or promise that every capability is included.

Commerce and hospitality

See the e-commerce businesses journey as working software

A code-built fictional view connects the customer record, owner and next action without presenting a live e-commerce businesses account or inventing a result.

121 CRM · Connected operations

Book discovery

October · illustrative availability

MTWTFSS1234567891011121314

11:3014:00

Appointment sequence

Booked

Calendar entry created

1 day before

Reminder scheduled

Exception

Owner reviews a reply

Journey summary

New

Illustrative

Owned

Illustrative

Due

Illustrative

Website

Referral

Direct

Illustrative exampleAll dates, counts and workflow states are fictional. Availability and behaviour depend on the agreed setup.

The working building blocks

Use the CRM where it improves the working day.

The same core capabilities can support different sectors, but the data, permissions, professional boundaries and handovers need to reflect the business using them.

Capability 01

Ecommerce store

Provides product listing, product detail, cart, checkout and order-confirmation pages inside a website.

How it works: Uses configured products, merchant connections and checkout rules for an eligible payment or order journey.
Why use it: Gives a small catalogue a connected storefront and CRM-aware order journey.
Plan for: Provider fees, tax treatment, disputes, settlement and feature eligibility remain separate responsibilities.
Your team owns: A responsible person must approve prices and terms and resolve refunds, disputes and fulfilment exceptions.

Capability 02

Orders and fulfilment

Tracks order, transaction, fulfilment and supported refund information after checkout.

How it works: Uses configured products, merchant connections and checkout rules for an eligible payment or order journey.
Why use it: Gives staff a working queue for what was bought and what still needs to be delivered.
Plan for: Provider fees, tax treatment, disputes, settlement and feature eligibility remain separate responsibilities.
Your team owns: A responsible person must approve prices and terms and resolve refunds, disputes and fulfilment exceptions.

Capability 03

Refund and dispute operations

Surfaces supported transaction follow-up while the merchant and payment provider retain their own responsibilities.

How it works: Uses configured products, merchant connections and checkout rules for an eligible payment or order journey.
Why use it: Makes post-payment exceptions visible to the staff who need to resolve them.
Plan for: Provider fees, tax treatment, disputes, settlement and feature eligibility remain separate responsibilities.
Your team owns: A responsible person must approve prices and terms and resolve refunds, disputes and fulfilment exceptions.

Capability 04

Contacts

Stores a person or lead with contact details, activity, ownership and related records.

How it works: Stores or organises supported business data under configured fields, permissions and record rules.
Why use it: Gives a team one place to understand who a customer is and what has happened.
Plan for: The platform does not make imported, duplicated or incomplete data accurate without review.
Your team owns: A data owner must define the record model and resolve quality, ownership and access exceptions.

Capability 05

Conversations inbox

Brings supported connected message threads into a shared operational inbox.

How it works: Handles an eligible customer interaction through a configured inbox, number or connected channel.
Why use it: Helps a team see the customer history and coordinate replies from one working view.
Plan for: Delivery, message types, geographic coverage, approval and charges vary by channel and provider.
Your team owns: A person must own sensitive conversations, failed delivery and any situation outside the approved script.

Capability 06

Triggers

Starts a workflow after configured contact, event, appointment, opportunity, course or other supported activity.

How it works: Runs an ordered sequence only after its configured trigger and conditions are met.
Why use it: Lets follow-up begin from a business event instead of waiting for someone to remember.
Plan for: Automation follows its configuration; it cannot repair poor data, unclear rules or an unavailable external service.
Your team owns: A process owner must approve, test, monitor and pause or correct faulty automation.

Start with the real enquiry

What e-commerce businesses actually need the CRM to hold

Moorland Goods is a fictional example used to make the workflow concrete. The aim is not to reproduce a sector package, but to show the minimum useful context for a team that needs give support staff context and ownership without copying or contradicting the order record.

The customer situation

Imagine a customer asks about an order through email or social messaging while the authoritative fulfilment status sits in the commerce system. Moorland Goods records the customer’s own account before interpreting it. For this e-commerce businesses team, that prevents a short message from becoming a confident but unsupported category, price or promise.

The working record

The useful record contains customer, order reference, enquiry category, channel, current authoritative status, assigned person, promised response and next action. At Moorland Goods, those fields must help a person respond, decide or understand the next handover; extra detail collected merely because a field exists adds risk and maintenance.

The ownership question

Moorland Goods names the customer-operations lead or another responsible colleague against the next action. The Moorland Goods shared view is useful only when the team can tell who must act, by when, and what happens if that person is unavailable.

Human decision

The decision that stays human

A person decides whether staff can answer, the fulfilment team must investigate or a refund or dispute process is required. On this e-commerce businesses journey, CRM presents records, reminders and history without turning incomplete information or silence into approval.

A practical customer journey

Move the e-commerce businesses conversation without losing context

A workable starting journey for Moorland Goods is Customer message → Order matched → Responsibility assigned → Resolution or formal process → Outcome communicated. For e-commerce businesses, each change should mean something observable to the team and customer rather than acting as a decorative pipeline label.

1. Capture customer message

For Moorland Goods, capture starts with the source, the customer’s words and enough contact detail to reply. The first response should set a realistic expectation and ask only for information needed now; it should not imply that whether staff can answer, the fulfilment team must investigate or a refund or dispute process is required is resolved.

2. Establish order matched

Moorland Goods asks the owner to check duplication and fill the smallest important gaps. Give support staff context and ownership without copying or contradicting the order record becomes the operating goal, rather than sending every e-commerce businesses enquiry through one sequence regardless of context.

Human approval point

3. Record responsibility assigned

At Moorland Goods, the team records the human decision, its basis and the promised next action. If information is missing, the request names it and its reviewer; if work should stop, a clear reason is more useful than leaving this e-commerce businesses record open indefinitely.

4. Complete resolution or formal process and outcome communicated

For Moorland Goods, later stages preserve the customer commitment, operational handover and outcome. Its e-commerce businesses team closes or defers work deliberately, records why, and gives future follow-up a date and purpose instead of keeping an undifferentiated list of old leads.

Reviewable by design

Make the decision and the exception visible

The second view shows how Moorland Goods could expose handovers, missing information and the point where a person must decide what happens next.

121 CRM · Reporting summary

Journey summary

New

Illustrative

Owned

Illustrative

Due

Illustrative

Website

Referral

Direct

Illustrative exampleFictional figures only. Definitions, access, data quality and interpretation determine whether a view is useful.

Fictional working example

How Moorland Goods could use the pattern in a normal week

This example uses fictional people and activity. It demonstrates how a configured CRM might support a e-commerce businesses team while keeping account availability, detailed configuration and service scope subject to agreement.

The first response

Moorland Goods receives the initial enquiry described above. The record is assigned to the customer-operations lead, the customer receives an acknowledgement that matches the actual response process, and the owner sees the missing information and a dated action rather than a vague notification.

The awkward case

The same week, a payment dispute, suspected fraud or safety issue that should leave routine service automation. At Moorland Goods, the ordinary sequence pauses while a person reviews the context and records the decision. For this e-commerce businesses workflow, the failure route matters because automation should expose exceptions rather than quietly continuing.

The handover evidence

At each handover, Moorland Goods keeps the source, time, owner, status change and next commitment. Moorland Goods attachments or sensitive details remain only where the approved design permits them. A completed e-commerce businesses task proves that an action was recorded, not that the underlying judgement was correct.

The weekly view

The team reviews messages not matched to an order, duplicate cases, promised replies overdue and refund or dispute handovers awaiting acknowledgement. For e-commerce businesses, those measures prompt investigation rather than promise performance. They help Moorland Goods only when stages are updated consistently, exceptions remain visible and someone corrects stale or misleading records.

Controls, limits and review

Keep the e-commerce businesses workflow useful after launch

The safest e-commerce businesses design is modest: a small number of meaningful fields, an owner, an observable next action and a review rhythm. Moorland Goods would test the ordinary path and the exception path before relying on either.

Human responsibility

Professional and operational boundary

CRM can coordinate the conversation; it does not replace payment-provider evidence, stock control, fulfilment, returns law, tax records or fraud decisions.

Exception handling

A payment dispute, suspected fraud or safety issue that should leave routine service automation should be visible to a named person. Moorland Goods needs a stop, escalation or manual route so that delay, missing data or unusual circumstances do not produce an inappropriate automatic message.

Access, data and communication

Use the minimum information required for this e-commerce businesses journey. Confirm Moorland Goods roles, channel consent, retention, export access and connected suppliers in the customer’s own account. Keep sensitive or formal e-commerce businesses records in the approved system for their purpose rather than copying them into CRM notes.

Review rhythm

Moorland Goods reviews the workflow through live service queues, with a daily exception review and periodic retention check. The Moorland Goods review checks a representative journey, stale records, failed actions, user access and whether fields still support a real decision. Any material e-commerce businesses change should be tested before it reaches ordinary customer communication.

Questions about this page

Useful answers, without the sales fog.

1. What is the most useful first CRM workflow for e-commerce businesses?

For e-commerce businesses, start with one common enquiry from capture to a recorded outcome: Customer message → Order matched → Responsibility assigned → Resolution or formal process → Outcome communicated. Keep Moorland Goods’s first version narrow enough that the team can name the owner, test exceptions and see where a customer is waiting.

2. What should e-commerce businesses avoid automating?

CRM can coordinate the conversation; it does not replace payment-provider evidence, stock control, fulfilment, returns law, tax records or fraud decisions. E-commerce businesses should also avoid automatic follow-up where consent, urgency, safety, suitability, a complaint or a vulnerable person needs a considered response.

3. Which information belongs in a e-commerce businesses CRM record?

Use information that supports the current relationship and next action: customer, order reference, enquiry category, channel, current authoritative status, assigned person, promised response and next action. At Moorland Goods, detailed or sensitive information is not collected simply because a custom field exists, and an authoritative professional or operational record is not duplicated without a defined reason.

4. How should a e-commerce businesses team know the workflow is working?

Review messages not matched to an order, duplicate cases, promised replies overdue and refund or dispute handovers awaiting acknowledgement. Then inspect examples behind the figures. For e-commerce businesses, a dashboard can expose patterns but cannot prove service quality, causation or correct professional judgement without reliable data and human review.

Read all CRM questions

Continue the journey

Solutions Conversations Payments Shopify Restaurants and hospitality Charities

Delegate the work. Keep the human.

Ready to organise the customer journey?

Subscribe through the approved secure checkout, or review pricing and responsibilities before you decide.

Subscribe to 121 CRM Seller, billing and cancellationCompare pricing