Skip to content
GullySales

Online pharmacies · CRM

Keep one record per household, with its list, its address and its consent to be contacted.

A CRM for an online pharmacy is the single record of each customer: who orders, for whom, which recurring items and whether reminders are agreed. GullySales works on the fields, the consent note and the daily routine that keeps the record true.

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

Realistic editorial illustration of pharmacies at work in India

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. Rules for this trade differ by state and professional body, and they change. We describe restrictions in general terms, so check the current position with your own council or adviser before you publish anything.

For online pharmacies

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

  • “The order table is not a customer record”

    Orders sit in rows by date. A pharmacy needs a record by household, showing every recurring item, the pack size, the delivery address and who placed the order, or the reminder goes out blind.

  • “Consent has to be written down at the point of ordering”

    A reminder goes only to a customer who agreed to receive one. A record without a consent field forces the team to guess, and a wrong message to a patient damages trust faster than a missed one.

  • “A parent and the child who pays are two contacts”

    The tablets go to a parent in Belagavi while the payment and messages go to a child in Bengaluru. One record needs to hold both, with a note on who may be told what.

  • “Prescription details is the field needing the tightest care you hold”

    Storing images and notes in a shared chat leaves them open to anyone with the phone. Decide who sees a prescription, where it sits and when it is removed, and write that rule down.

What we do

What we deliver for online pharmacies.

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

  1. A household record layout

    Fields for the person, the people they order for, the address, the recurring items with pack size and the preferred channel.

    Result: One record holds the whole household.

  2. A consent field and its wording

    The exact wording that asks for permission to send reminders, and a field to store when and how it was given.

    Result: Every reminder can be traced to an agreement.

  3. Access rules for prescriptions

    A short document on who sees a prescription, where it is held and how it is removed, agreed with your pharmacist.

    Result: Prescription images are not scattered across phones.

  4. A daily routine for the desk

    Steps for updating the record after a call, an upload or a delivery, so it reflects what happened.

    Result: The record matches what the team did.

  5. Lapsed-household list

    A list of households whose recurring item has dropped out of their orders, for a gentle call.

    Result: You can see which households need a call.

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 pharmacy keeps for each household, and who fills each one.

Household and delivery address
The desk fills this at the first order. One record per household stops a parent and the adult child who pays becoming two strangers, and fixes the address for refills.
Consent to be contacted
The customer gives it at ordering and the desk records the date and the wording. It decides whether a refill reminder may be sent at all.
Prescription received and checked
The pharmacist marks it, and access is limited to the pharmacy staff who need it. It shows which orders are stalled without copying the prescription into a marketing record.
Substitute offered and answer
The pharmacist records the call and whether the customer accepted. It tells the next person at the desk why an order changed and how the customer felt about it.
Source and last order date
The desk records how the household found the store and when it last ordered. It lets the owner see who has lapsed and which sources bring households that stay.

Who it is for

This is written for these online pharmacies.

  • Licensed retail pharmacies that have added a website, app or WhatsApp ordering
  • Standalone online pharmacy companies running their own app
  • Chronic care pharmacies built around monthly refill subscriptions
  • Hospital and clinic pharmacies delivering discharge medicines to the home
  • Pharmacy chains with an app and delivery in several neighbourhoods
  • Online stores for surgical consumables and home care items beside medicines
  • Corporate and insurer tie-up pharmacies serving employee health programmes
  • Specialty pharmacies for diabetes, cardiac and elderly care lists

Before you decide

When this may not be the right fit.

  • You want to store prescription images and diagnoses in a marketing tool, which should not hold that data.
  • Nobody has decided who may see the record, and a shared sheet open to all staff exposes customers' health details.
  • The store takes few online orders and the pharmacist already knows each regular customer by name.

Before you decide

Agree the work. Know how to judge it.

CRM for online pharmacies: 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 online pharmacies. Anything missing is noted in the written scope, with who will supply it.

An export from your ordering platform
A file of customers and orders, with medicine names removed if possible. We import it as the starting point. If the platform cannot export, we begin from the desk's sheet.
The pharmacist's rule on prescription access
A written statement of who may open prescription images and why. We build access around it. Without a rule, we default to the pharmacist and no one else. Name the staff who stand in when the pharmacist is on leave.
A list of staff who will use the CRM
Names and roles of those at the desk and in delivery who will enter or read records. Access is given by role. A shared login is not acceptable. Include delivery partners who will see addresses, since they are staff for this purpose.
Your current privacy notice or consent line
Whatever customers are told now about their details. We compare it with the plan. If there is none, we draft a plain one for your adviser to review. Send the version printed on the ordering page, not the one in the file.
A retention period for lapsed customer records
How long a lapsed customer's record stays and who decides to delete it. Your adviser should set this. Without it, we mark records for review and delete nothing.

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

    Look at how the desk records a customer today

    We watch the desk take an order and see where names, phone numbers and notes go: the order table, a notebook, a chat. We list every place a customer appears. The result tells us how many records one household has and where they disagree. We also ask which spelling of a customer's name the courier receives, because mismatched names are the commonest cause of duplicate records.

  2. 2

    Draw the household record on one page

    We draw a record with the orderer, the person who receives the parcel and the patient as separate contacts, linked together. You decide which details the desk may note. Prescription details are not a field in this record at all. A parent who does not use a phone is recorded with a relative as the contact, and the link between them is visible to the desk at the time of the call.

  3. 3

    Write the consent wording and where it is stored

    We draft the line the customer sees at the time of ordering, asking agreement to reminders, and the field where the answer and its date are kept. Your own adviser checks the wording. A reminder is sent only where the field says yes. The line is shown on the ordering page and read out by the desk when an order is taken by phone, and the answer is saved the same way in both cases.

  4. 4

    Set who can open prescriptions and who cannot

    With the pharmacist we write access rules: who may open a prescription image, who sees only the order, who sees only the contact. The rules are set in whichever tool you use. Staff who need less see less. A pharmacist's login and a delivery rider's login are different, and a former employee's access is removed on the day they leave.

  5. 5

    Build the desk routine and lapsed list

    We write the routine the desk follows at the start and end of each shift: new records checked, consent noted, calls logged. A list of households that have stopped ordering is built from the same record, for a call and not an advertisement. The lapsed list shows the last order and whether it ended in a problem, so the call starts with an apology where one is owed.

  6. 6

    Read the first records against the order count

    After a trial period, we compare the number of households in the CRM with the orders recorded earlier and check for duplicates. The lapsed list is read for households that left after a problem. Fields that nobody fills are removed.

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.

Which CRM should we use?
The one your team will update. We work with what you have, or with a simple tool in ordinary use in India, and we add fields before we add software. Check how any tool stores health-related data.
Can we store prescriptions in the CRM?
Only if the tool and your access rules suit sensitive records, and only as your pharmacist and legal adviser allow. Some stores keep the image in their pharmacy system and note the order in the CRM.
What if a customer asks us to delete their details?
Follow your own privacy policy and the law as your legal adviser reads it. Keep a clear route for the request and record what was done.
Which fields must the CRM never hold?
Leave out the prescription image, the diagnosis and the medicine list unless your pharmacist and legal adviser have approved the control around them. Rules on health data differ by profession and state, and a marketing tool is the wrong place for them.
Can the CRM hold a customer's allergies or conditions?
We advise against it. Health details raise the risk if the record is seen by the wrong person, and the CRM is for contact and ordering, not for clinical notes. If your pharmacist keeps such notes, they stay in the pharmacy's own system with its own access rules. Check with your adviser before storing anything about health.
What do we do when a customer asks us to remove their details?
The desk notes the request, the pharmacist confirms what must be kept for the licence and the rest is removed from the CRM and from any list for reminders. We write a short routine for this so the desk does not improvise. Your adviser decides what the law requires you to keep.
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.