An ecommerce CRM is not a sales CRM

Almost every CRM on the market was built for a job an online store does not do: working deals. They have pipeline stages, an estimated deal value, a reminder to call the customer back on Thursday. Serious tools, built for companies that sell to a few dozen businesses a year with a salesperson working each one.

An ecommerce store has no deals. It has thousands of people who buy on their own, come back or do not, and occasionally write in. Using a tool designed for the first thing to manage the second is why, in a lot of stores, the CRM is an archive nobody opens.

Where the customer actually lives right now

Try answering this about any one customer: how much they have spent in total, what they bought last time, what they wrote to you, and whether the problem was resolved. In a normal store that answer sits in four places.

Orders are in Shopify. Conversations are in the help desk, or on WhatsApp on somebody's phone. Sent emails are in the email platform, with its own tags and segments. And the missing piece, the one that matters, is in the head of whoever has worked there longest.

This is not untidiness: it is the consequence of buying four tools that each do a different thing well. The trouble is that the customer is one person, and whoever has to decide what to say to them has to reassemble that picture by hand every time.

What a customer record actually needs

A few things, and none of them is a pipeline stage.

Everything they bought. Not the last order: the history. It is the difference between knowing somebody spent three hundred once and knowing they spend fifty every two months and have done for three years. You write to the second one differently.

What was said. Conversations next to the orders, in the same place. Asking a customer twice for information they already gave is the fastest way to look like a company that does not know them.

What they are worth, calculated rather than estimated. A customer's value in ecommerce is not guessed like a deal: it is read off the orders. If the tool holds the real data, the number is a fact and not an opinion.

Where things stand, if something is open. A return in progress, a late delivery, an unanswered question. Not an abstract stage, a concrete state somebody has to close.

The segment that goes stale, and the one that updates itself

Here is the practical difference you feel immediately. A segment built by exporting a file and uploading it into another tool is a photograph: it was true the day you took it. Anyone who bought in the meantime stays inside it, anyone who stopped buying never enters it.

A segment built on the store's live data changes by itself when the customer changes. Same idea, different job: in the first case you maintain the list, in the second it maintains itself.

Why this is a data problem, not a tool problem

The temptation is to go looking for "the right CRM for ecommerce". But the problem is not solved by choosing better between four separate boxes: it is solved when orders, conversations and content sit on the same data.

When they do, the thing that changes is not the CRM. It is that whoever answers in chat sees the order history while they type, whoever builds a campaign starts from a real segment, and whoever looks at the numbers at month end does not have to reconcile four exports to work out what happened.

Frequently asked questions

Do I need a CRM if I already have Shopify?

Shopify knows everything about orders and almost nothing about the rest. It does not hold conversations, it does not hold what you sent by email, and it does not track the state of anything in progress that is not an order. If you need that information to decide what to say to a customer, you need somewhere that keeps it together.

How is this different from a sales CRM like HubSpot?

They are different jobs, and the distinction is an honest one: a tool like HubSpot is built to keep the work of a sales team in order, and on that it goes deeper than we do. An ecommerce store has no deals to work: it has orders, conversations and a catalogue. If you have both, keeping them separate is often the sensible shape.

Where does my customer data end up?

It stays yours, and the thing to check before signing any contract is how you get it back: exportable in an open format, whenever you want, including after you stop. That applies to us as much as to anyone else, and get it in writing.

How many contacts do I need for this to be worth it?

It is not about volume, it is about repetition. If your customers buy once and never return, a customer record buys you little. If a share of them come back, every piece of information you keep pays for itself each time they do.

Do I have to import history, or start from zero?

Order history should be imported, and it is worth it: it is what makes the record useful on day one rather than in a year. Old conversations often stay where they are, and in practice little is lost: the value is in the next ones.