Qualifying Bulk-Order and GST-Invoice Quote Requests: A Guide for Indian MSMEs

A bulk or B2B quote request is ready for a person to price when it states what is needed, how much, where it must be delivered, by when and whether a GST invoice is required. Collecting those details in the first conversation, and checking the delivery location before anything else, removes most of the back-and-forth that slows Indian MSMEs down after every enquiry.

This guide is for manufacturers, traders, printers, packaging suppliers, caterers and service firms that get business-to-business enquiries through their website or WhatsApp and quote each one by hand.

The enquiry that cannot be quoted#

A packaging supplier in Ahmedabad receives this on its website: "Need corrugated boxes, please send rates." The sales person has to ask the size, the ply, the quantity, the printing, the delivery location and the date. The customer replies two days later with half the answers. By the time a quote goes out, the customer has bought elsewhere.

The supplier did not lose on price. It lost on the time it took to understand the request.

What a quote-ready B2B enquiry contains#

Start from the decision your team has to make: can we supply this, at what price, and by when? Work back from that to the details you need. For most bulk and B2B enquiries:

1. Contact details: name, mobile number or email, and company name.
2. Product or service: what exactly is needed, including specifications that change the price (size, material, grade, finish, customisation).
3. Quantity: a number or range, plus whether this is a one-time or repeat requirement.
4. Delivery location: city and PIN code.
5. Timeline: the date by which it is needed.
6. Invoice needs: whether the buyer needs a GST invoice.
7. Anything that changes feasibility: samples needed, artwork ready, site access for a service job.

Ask in that order of usefulness, not all at once. A customer who has just asked "do you make printed boxes?" should get an answer first, then one question at a time.

Check the location first#

For many MSMEs, delivery or service area decides whether an enquiry is worth pursuing. Ask for the city and PIN code early, right after acknowledging what the customer needs.

Write your coverage as clear rules your team agrees on, for example:

• Core area: cities or PIN code ranges where you deliver or serve normally.
• Conditional area: places you cover only above a minimum quantity, on certain days or with a delivery charge to be confirmed.
• Outside area: places you do not serve. Say so politely and, if you can, suggest what the customer could do instead.

Watch for common problems: the same locality name in different cities, new layouts or industrial areas that are not on older lists, and customers who give a city but not a PIN code. If a rule says "conditional", the assistant should not invent a delivery charge. It should collect the enquiry and say that the team will confirm.

Pivra documents this pattern as service-area qualification: ask for the location early, confirm whether you cover it and continue only when the job is serviceable. For a deeper template, see our service-area qualification guide, written for Australian trades but built on the same three-zone idea.

Handle GST invoices sensibly#

Many B2B buyers will ask whether you provide GST invoices. Answer that question from your approved FAQ. Then:

• Ask whether an invoice is needed, as a yes or no, during qualification.
• Collect the GSTIN only when it is needed, for example once the buyer confirms an order that needs a GST invoice. Do not make it a required field for every first enquiry.
• Do not let the assistant calculate tax. Prices, tax treatment and invoice details should come from your team or your billing system, not from a chat reply.

Collecting less at the first step is both easier for the customer and better data practice.

Keep prices with your team#

For bulk and custom work, the safest approach is for the assistant to collect details and for a person to quote. Let the assistant explain what affects price ("rates depend on size, ply, printing and quantity"), using wording your team has approved, and set an honest expectation about when the quote will arrive.

Put that wording in your knowledge base as plain text. Avoid publishing rate cards that change often unless you will update them every time. If you do publish standard rates on your website, train the assistant on that page and retrain whenever it changes (keep your chatbot up to date).

Setting this up in Pivra#

• Train on approved material. Add your product pages, a plain-text FAQ (including GST invoice and minimum-order answers) and your coverage rules (training sources). Turn on strict mode if answers must stay within that material (improving responses).
• Collect contact details. Lead capture collects name, email, phone and company, each required or optional (lead capture).
• Add quote fields. Quote capture lets you define your own fields, such as product, quantity, delivery PIN code, required date and "GST invoice needed?", with trigger phrases for quote requests. These enquiries are stored under Leads, where you can filter by quote requests (service pricing and quotes).
• Get alerted. An email Action can notify your sales person whenever a lead or quote request is captured (webhook actions and email alerts).
• Hand over when needed. A visitor can ask for a person, and your team can take over the conversation from the dashboard (human handoff).
• Test before publishing. Run 20 real enquiries, with names and numbers removed, through Chatbot → Test before going live.

Lead capture, quote capture, alerts and handoff are on the Starter plan and above. If your customers mostly message on WhatsApp, the same chatbot can answer on WhatsApp on the Pro plan and above (WhatsApp channel).

Tell customers why you collect their details#

Explain at the point of collection that you will use the details to respond to the enquiry, and link your privacy policy. India's DPDP Rules require Data Fiduciaries to issue standalone, clear and simple consent notices that explain the specific purpose for which personal data is collected and used, with an 18-month phased compliance timeline (PIB). This is general guidance, not legal advice; take advice for your own business.

A checklist for your team#

• One agreed list of quote fields for your main product or service.
• Coverage rules by city and PIN code: core, conditional and outside.
• An approved answer on GST invoices and minimum order quantities.
• GSTIN collected only when an order needs it.
• Prices given by a person, not calculated in chat.
• A named person who receives alerts and a time by which quotes go out.
• Twenty test enquiries run before launch.

Score ten recent enquiries against this list. If most were missing quantity, location or timeline, fix the questions before spending more on ads.

Next step: write your quote fields and coverage rules this week, then see how Pivra works and test them with real, anonymised enquiries.