In this guide 6 sections
After a fair, a spreadsheet register works for a few dozen buyers. A CRM suits long follow up. A combined order and sample tracker suits exporters who ship samples. Pick by what goes wrong most: forgotten replies, late samples or enquiries that never reach an order.
What lands in your inbox after a fair
Three days after the fair at India Expo Mart, the pile arrives. Emails, WhatsApp photos of catalogue pages, visiting cards and a request for samples from a buyer who stopped by for two minutes. Within a week the owner asks the export manager who has been answered, and the honest reply is a guess from a half remembered inbox.
Each lead needs a different next step. One wants a price list. One wants three samples by courier within the fortnight. One wants nothing until next season. Your tool must hold those differences without a legend.
- Business cards photographed on the stand
- Enquiries by email and WhatsApp
- Sample requests with article codes
- Price lists promised but not yet sent
A spreadsheet register and where it stops
A shared sheet is the right start. One row per buyer, with columns for country, products, last contact and next step. Anyone on the team can open it on the first morning. No training needed.
It stops working when two people edit the same row, or when a reply sits unanswered for nine days and nothing flags it. Sheets do not nudge. They forget who promised what. Add no column for the promised date, and nobody can say whether a buyer from Hamburg has waited two days or two weeks. Worse.
For a stand that collected thirty or forty leads, this is enough. Beyond that, the colour coding starts to carry a meaning that only its author remembers. Then it fails.
What a CRM adds, and what it leaves out
A CRM tracks every email and call against the buyer. It reminds the owner of the lead on the due date. It shows the pipeline stage, from enquiry to quote to sample to order. A CRM tool also asks staff to log every call, and a team that is already busy packing sample boxes will skip the logging unless someone checks it weekly.
What it usually leaves out is the factory side. It does not know that sample SM-204 is waiting for the polishing shop, or that the buyer asked for a different finish.
Exporters in Noida and Greater Noida with a long sales cycle and many repeat buyers get real value here. Those who mostly send samples and wait often find the CRM half empty.
- Reminders on follow up dates
- Email history per buyer
- Pipeline stage from enquiry to order
- No view of sample production
A combined order and sample tracker
The third option holds buyers, samples and orders in one place. A lead becomes a sample request. The request becomes a job with a dispatch date. The sample result becomes a quote, and then an order. When a buyer asks for the same bag in a different lining, the change lands in the sample row, and production sees it before the courier leaves.
Moradabad brass exporters tend to land here. The question that matters is rarely the sixth follow up email. It is whether the sample left on the promised date and what the buyer said.
Conversion becomes visible. You see which fair, which product and which buyer type ended in orders, and which stopped at the sample. That guides next year’s stand.
- Sample dispatch date against the promise
- Courier tracking number on the record
- Buyer feedback linked to the article
- Orders traced back to the fair
How to choose in one afternoon
Take last season’s fair leads. Count how many went quiet, how many samples shipped late, and how many enquiries became orders. The biggest number tells you where the tool must help. Add the cost of samples and courier charges to the review, because a fair that produced many sample requests but few orders may deserve a smaller stand next year.
Forgotten replies point to a CRM. Late samples point to the combined tracker. Few leads with good follow up? Keep the sheet. Run your choice for one fair, then review it.
Post fair lead and sample tracker
The page carries a lead block above a sample block. The lead block has buyer, country, source, products, owner and next step date. The sample block has article code, finish, dispatch date, courier number and buyer response. A bottom row counts leads, samples sent and orders won for the fair.
Open a blank worksheet to printQuestions owners ask
How soon should we reply after a fair?
Within the first week, while the buyer still remembers the stand. Send the price list or catalogue first, then agree the samples. A short acknowledgement the same week keeps the lead warm.
Do we need a CRM for thirty leads?
Usually not. A shared sheet with a next step date does the job. Move to something heavier when replies start slipping or more than two people work the same leads.
How do we track samples without a CRM?
Give each sample its own row with an article code, dispatch date and courier number. The buyer’s response goes in the same row, so the story stays together.
Can the register connect to our order system later?
Yes, if you keep buyer names and article codes consistent from the start. Clean codes make a later move to a tracker or CRM much easier.
