Merchant CRM

Why a bolt-on CRM fails in a merchant

Standalone CRM tools are built for a sales team that works deals over weeks. A merchant works relationships over years, and the most valuable information about a customer is not what stage they are at — it is what they bought last month, what they owe, and what somebody promised them on Tuesday.

That information already exists in the till, the accounts and the order book. A separate CRM either duplicates it badly or sits empty, because nobody on a busy counter is going to type a sale into a second system.

The CRM in PlanIt EPOS is not a separate product. It is the customer record with everything already attached to it.

The customer record

One screen per customer, showing who they are and everything that has happened.

• Company details, delivery sites and named contacts
• Account terms, credit limit, live balance and aged debt
• Pricing — the trade band they sit on and any contract prices
• Every sale, quote, order, delivery, invoice, credit and payment
• Notes, tasks and communication history
• Spend over the last twelve months, and how it is trending

Whoever picks up the phone has the full picture, which is the entire point. Trade is a relationship business, and the fastest way to damage a relationship is to ask a customer to explain something you should already know.

Notes that belong to the business

The most valuable customer information in most merchants is undocumented: this customer always wants a delivery note signed, that one disputes anything not itemised, this one is good for the money but always pays at 45 days.

In PlanIt EPOS, notes sit on the customer record where the whole counter can see them, rather than in one person’s head or one person’s inbox. When that person is on holiday, the business does not lose the knowledge.

Tasks and follow-ups

Merchant follow-ups are specific and time-bound: chase a quote, confirm a delivery slot, review a credit limit, call about an overdue invoice. They fail when they live on a notepad.

Tasks in PlanIt EPOS are attached to the customer and carry a due date and an owner. They appear on the customer record and in a list of what is due, so a follow-up is something the business does rather than something an individual remembers.

Lead tracking, at merchant scale

New trade customers usually arrive by walking in, being recommended, or ringing about a price. That is a short journey, and it does not need an elaborate pipeline.

A lead in PlanIt EPOS is a customer record that has not traded yet. You capture who they are, what they asked about and who spoke to them, set a follow-up, and when they place a first order the record simply becomes an account. Nothing is re-keyed and no history is lost at the point of conversion.

Marketing permissions and communication history

Marketing consent is recorded per contact, so you know who has agreed to what. That is a legal requirement under UK data protection rules if you send marketing, and it is much easier to record at the point the customer says yes than to reconstruct later.

Every message the system sends — quotes, invoices, statements, ready-to-collect notifications — is logged against the customer, alongside notes of calls and visits. When a customer says they never received a statement, the history answers it.

Using it to actually grow

Because the CRM sits on real transaction data, it can answer questions a standalone CRM cannot.

• Which accounts are trading below their usual level this quarter?
• Which customers have stopped buying a category they used to buy every month?
• Who are the top customers by margin rather than by turnover?
• Which quotes are still open, and how old are they?
• Which accounts consistently pay late, and what does that cost?

Those are the conversations that grow a merchant. They are only possible when the customer record and the sales ledger are the same system.

Who can see what

A customer record in a merchant contains commercially sensitive information: the discount they have been given, their credit limit, how far behind they are. Not everyone on the counter needs all of it, and in a business where staff move between competitors, that matters.

Access in PlanIt EPOS is controlled by named user accounts with role-based permissions. A counter hand can see what they need to serve a customer — pricing, stock, order history — without seeing margin, aged debt across the business, or the ability to change a credit limit. Sensitive actions such as overriding a credit limit or applying a price override are recorded against the user who performed them.

That also gives you something useful when a query comes back weeks later: not just what happened, but who did it and when. It removes a whole category of unproductive conversation.

Keeping the record worth having

The failure mode of every CRM is the same: it starts accurate, then decays, and once it is unreliable people stop using it. Merchants are unusually exposed to this because a counter is busy and nobody is going to maintain a database while a customer waits.

The design answer is to make the valuable parts a by-product of work that has to happen anyway. Sales, quotes, deliveries, invoices, credits and statements attach themselves to the customer because they occur in the same system. Nobody types them anywhere.

• Contacts and sites are captured when an order first needs them, not in a data-entry session
• Marketing consent is recorded at the moment the customer agrees to it
• Notes take seconds and are visible to everyone, so they get written
• Tasks carry an owner and a due date, so they surface rather than expire quietly

What is left for someone to maintain deliberately is small — and small is the only size that survives a busy Saturday.