Skip to content
GullySales

Supermarkets · CRM

The register should tell the store which regular family has gone quiet.

A CRM for a supermarket is the customer register, built from billing data, that holds each family's contact, locality, usual purchases and last visit. GullySales works on setting it up from the software you already run and on the rules for using it.

Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

Grocery staff arrange produce and packaged goods

What CRM means

A CRM is the record where every enquiry, call and quote is kept against a customer, replacing separate notebooks, spreadsheets and memory. GullySales sets up or cleans an existing CRM and reports from it by enquiry outcome rather than by activity logged.

Last updated 14 Nov 2026.

For supermarkets

Where it usually goes wrong, and what we would do.

  • “The billing software holds the history but not the habit”

    Supermarket software records every bill and still cannot say who has gone quiet. Without a register built on the mobile number, the history is stored and not used.

  • “The mobile number is the key”

    If the cashier skips the number, the visit belongs to no family. A short, polite request at billing, with a reason the buyer values, decides whether the register has anyone in it.

  • “Consent must be recorded”

    A family has to agree to receive messages on WhatsApp or SMS. The register keeps the date and the channel of that agreement, so a message never goes to someone who declined.

  • “A register nobody reads is a spreadsheet”

    The record becomes useful only when a named person looks at the quiet list and acts on it. Decide who owns the list before choosing the tool.

What we do

What we deliver for supermarkets.

The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.

  1. A register set up from your billing data

    Names, mobile numbers, locality, usual product groups and last visit, loaded into a sheet or a CRM, with duplicates merged.

    Result: A list that shows who shopped last and who has not.

  2. A counter script for the mobile number

    A line for the cashier and a place on the screen to enter the number, with a reason the buyer accepts.

    Result: The number is asked for at every bill.

  3. Consent and opt-out rules

    How consent is noted, which channels are allowed and how a family opts out, written in plain words for the staff.

    Result: Every contact has a recorded permission.

  4. Segments you can act on

    Families grouped as regular, drifting and lapsed, and by locality and usual basket.

    Result: Each segment has a named message and an owner.

  5. A review habit for the manager

    A simple routine for the person who reads the quiet list and sends the follow-up.

    Result: The list leads to a message and not to a report no one opens.

How the result is measured

  • Enquiries logged in the CRM
  • Data completeness
  • Reports generated from CRM data

Recorded as a baseline before work starts, so every later report has an honest comparison.

Fields worth keeping

The fields a supermarket keeps against every household in the register.

Mobile number with consent and date
Taken by the billing staff. It is the key, and the consent record tells you who may receive a message and who asked not to.
Last visit and usual shopping day
Filled in by the billing system. It lets you spot a regular family who has gone quiet and send one reminder.
Usual staples and brands
Drawn from billing, such as a preferred rice or detergent. It lets a reminder name the item, so the message is something the family can use.
Delivery address and slot preference
Entered once at the first delivery order. It saves the family repeating it and the delivery team re-asking.
Complaint raised and how it was settled
Noted by the floor manager. A wrong bill or a short weight, recorded, shows a pattern before it becomes a review.
Household or institutional
A single flag set at the first order. Bulk buyers and households receive very different messages, so the register must separate them.

Who it is for

This is written for these supermarkets.

  • Single-store supermarkets of one floor in a residential locality
  • Two-floor supermarkets with a dedicated household and general merchandise section
  • Supermarkets inside apartment complexes and gated townships
  • Small chains of three to ten stores in one city
  • Supermarkets attached to a wholesale or cash-and-carry outlet
  • Family-run supermarkets in smaller towns that serve the surrounding villages
  • Cooperative and society-run supermarkets
  • Supermarkets that serve a hospital, college or industrial campus

Before you decide

When this may not be the right fit.

  • Your billing software cannot export a customer's history, and a separate register would start empty.
  • Staff are not trained to ask for a mobile number at the counter, so the register would fill with wrong numbers.
  • Nobody will read the register, so it would be a spreadsheet nobody opens.

Before you decide

Agree the work. Know how to judge it.

CRM for supermarkets: use these checks to prepare, choose the scope, and review what changes.

Bring the right evidence

List the records your team uses and show how an enquiry becomes an order today. Bring examples of duplicate entries, missing owners, and reports that require manual correction.

Make the scope clear

Agree the stages, required fields, access roles, and integrations before configuring the system. Separate software subscriptions from setup, data work, and training.

Check the work in use

Ask the people who will use the CRM to complete a real handover and find the next action without help. Check that the management report can be traced back to individual records.

Know when to change course

If the process is unclear, buying a more complex CRM adds more places for confusion. Start with the minimum fields and rules the team can use consistently.

These are discussion points, not a fixed package. GullySales confirms the deliverables, responsibilities, fee, and term in writing after reading your brief and speaking with you.

Before we start

What to have ready before the work starts.

The records, access and decisions this work needs from supermarkets. Anything missing is noted in the written scope, with who will supply it.

Access to the billing software's reports
The login, or the person who can run reports and exports from the billing system, on a day when we can sit beside them. Without it we cannot see what data the store holds, and the register would be started from a blank page instead of the history the billing already keeps.
A sample of bills with and without numbers
A set of printed or exported bills from a few different days. It lets us count how many carry a number and what the cashiers typed when the household gave none. If none are available, the first days at the counter become the count, which delays the start.
Cashiers willing to ask for the number
Two or three cashiers who will try the script and report what households say. Their view decides whether the question is workable at a busy counter. Without them the register stays thin, and the staff who must feed it have not had a say in how it is built.
A written line on how numbers are used
A sentence from the owner on what the store will and will not do with a mobile number, for example that it is never passed to another business. We turn it into the consent wording. Missing, the counter has nothing honest to say when a household asks why the number is wanted.
A named keeper of the register
One person responsible for the register: adding entries, correcting a wrong number and removing a household that asks to be removed. Without a keeper, numbers go stale and opt-outs are ignored, and the register becomes a risk to the store's name instead of an asset.

How it works

How the CRM work runs

The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.

  1. 1

    See what the billing software holds and exports

    We sit with whoever runs the billing system and look at what it records and what it can export: mobile numbers, bill dates, item lines, branch. You tell us whether it is an old desktop package or an online one. The result is a plain note of what data exists and in what state, which decides how the register is built and whether anything needs to be bought.

  2. 2

    Count how many bills carry a usable number

    From a sample of bills we count how many carry a usable mobile number and how many are blank or filled with the shop's own number. The cashiers explain why. You decide how much the counter can ask without lengthening the queue. This count is the starting measure of the register, and the last step reads against it.

  3. 3

    Write the counter question and the consent line

    We draft one line for the cashier to ask for the number and one sentence that tells the household what the store will use it for, with an easy way to refuse. You approve the wording with your adviser. The cashiers practise it on a quiet afternoon, and we change anything that makes them stumble.

  4. 4

    Build the register and its fields on a copy

    On a copy of the data we build the register: mobile number, locality, first visit, last visit, usual sections and consent. Fields the counter cannot fill are left out, because an empty column teaches the staff to ignore the rest. You check the layout with the manager. Nothing live is changed until the copy is approved.

  5. 5

    Draw the lists the store can act on

    From the register we draw the lists a manager can use: households that came once and did not return, households that lapsed after regular visits, and big-basket households. You choose which lists matter for the store. Each list has a purpose and a named person who reads it, so a list is never produced for nobody.

  6. 6

    Set the manager's review and read the first lists

    We agree what the manager looks at, who receives each list and what is done with it. After the first lists are used, we compare the share of bills with a number and the repeat visits against the starting count. You decide what to adjust. Nothing is promised in advance; the register shows what it changed.

Where this fits

Three pieces of sales work, in this order.

This work sits inside sales management. A target, a review routine and someone who owns the number.

  1. Step 1

    Sales audit

    Find where deals are being lost and what to fix first.

    Start here if you cannot say where orders are lost.

  2. Step 2

    Sales process design

    One written way to sell, from first enquiry to repeat order.

    Start here if every salesperson sells differently.

  3. Step 3 · you are here

    Sales management

    A target, a review routine and someone who owns the number.

    Start here if the team has targets and no routine.

Tell us what you need Your brief is read before we call. Scope, fee and term in writing.

FAQ

Questions owners ask before they call.

Not here? More answers, or ask on WhatsApp.

Do we need to buy a new CRM?
Not at first. A well-kept sheet drawn from your billing software can do the job. Move to a CRM when the sheet is too large to manage or several people need to update it.
How do we get mobile numbers without slowing the queue?
Ask at the start of the bill, while the items scan, and give a reason such as the delivery update or the offer. Do not ask the buyer to fill a form at the counter.
Is it allowed to message families from billing data?
Rules on consent and messaging apply, and they change. Record the family's agreement, give an easy way to stop, and check the current rules with your own adviser before large campaigns.
Is it allowed to message families from billing data?
Only those who agreed to hear from the store, and the agreement should be recorded when taken. Using a number given for a bill to send offers without asking is not fair. Rules on personal data apply, so check with your own adviser and give every message an easy way to stop.
Can the register hold the names of family members?
It can hold a household name and one mobile number, which is what the store needs. Names of children or other family members add risk and little benefit, so we leave them out unless the household offers them for a reason, such as delivery to a second address. The keeper decides, and the consent wording says plainly what is stored.
Who in the store may open the register?
The manager and the person who sends messages, and nobody else by default. Cashiers see only the number being entered. We set this in the tool or spreadsheet and note it on the consent sheet. A register open to every staff member walks out of the door with the first person who leaves, so access is limited and reviewed whenever the team changes.
How much does it cost?
There is no price list, because the work differs by business. The fee is scoped after we have read your brief and spoken to you, and put in writing before anything starts, split into our time, your media spend and production.
How long is the contract?
The term is agreed in writing after we have spoken, along with the fee and the reporting. It is never a default twelve months, and renewal is decided on the numbers against the baseline recorded at the start.
How soon will we see results?
It depends on the trade, the channel and what is already in place. After we have read your brief and spoken to you, we say what we would expect to move first and how it will be measured against the baseline. Nothing here is guaranteed.
Who will actually do the work?
The person you speak to before anything starts. We work from one office in Nagarbhavi, Bengaluru, with no account managers in between.

Your next practical step

Tell us what you are trying to grow, and we will read it before we call.

Eight short steps, mostly taps. Skip anything you would rather answer on the call.