Odoo CRM Consultant in India

Place of supply, HSN codes and the right GST split on quotes

Indian GST makes the quotation a tax document in all but name. Whether a line carries CGST and SGST or IGST depends on the place of supply, which for most goods follows where they are delivered. The rate depends on the HSN or SAC code. Get either wrong on the quotation and the error travels into the purchase order and the invoice.

In Odoo, much of this is automatic once the data exists. The Indian localization can choose intra-state or inter-state tax through fiscal positions based on the customer's state, and products carry HSN codes and tax rates. The CRM has to supply the missing pieces:

• GSTIN and state captured at conversion for registered customers, with the state also set on each delivery address where goods go to a different location.
• Unregistered and consumer buyers identified, because their invoicing and reporting differ.
• Product masters cleaned before quoting, with HSN codes and rates agreed with your chartered accountant rather than copied from old Tally items.
• Freight, packing and insurance as separate lines with their own tax treatment, confirmed with your accountant.

Tax decisions are your accountant's. My part is ensuring the quote a sales executive sends matches the invoice accounts will raise. E-invoice and e-way bill handling on the accounting side is covered on my Odoo Accounting India page.

GSTIN as the customer key, and which of your GSTINs sells

Duplicate customers are common in Indian CRMs: one executive enters the company name, another the proprietor's name, a third creates a fresh record for a branch in another state. A GSTIN solves most of this, because it identifies a registration precisely and contains the PAN of the legal entity. Two GSTINs that share a PAN belong to the same business registered in different states.

How I use that in Odoo CRM:

• GSTIN required before a registered business lead becomes a quoting customer, with a format check.
• Branches grouped under a parent company where the PAN matches, so you see the full relationship while each registration keeps its own address and tax treatment.
• Duplicate checks before imports from Tally, spreadsheets or a previous CRM. Odoo flags similar records; fuller deduplication depends on edition.

Your own GSTINs matter too. A manufacturer with plants or depots in several states needs each quotation issued by the company or branch that will dispatch and bill. In Odoo I link each sales team to that entity and its warehouse, so the quotation, delivery challan or tax invoice and e-way bill all come from the right registration. The structure is designed with the accounting setup, described on my Odoo consultant India page.

Marketplace leads, trade fairs and dealer reorders

Indian B2B pipelines draw on a mix that few other markets share. B2B marketplaces send a steady stream of inquiries, many of them also sent to competitors. Trade fairs produce batches of visiting cards. Google Ads and the website bring direct inquiries, and existing dealers reorder by phone or WhatsApp.

What I set up for each:

• Marketplace inquiries pulled into Odoo as leads through a connector or the marketplace's API where one exists for your setup. These are usually third-party modules, so check who maintains them and whether they suit your Odoo version.
• Quick assignment by product line and region, with a response-time view for managers, because a slow callback loses a marketplace buyer.
• Trade fair imports tagged with the event as a campaign and checked against existing GSTINs and mobile numbers.
• Dealer reorders entered directly as quotations against the dealer's price list, kept out of the new business pipeline.

Executives in the field can use Odoo on mobile to log visits and send quotations. WhatsApp and calling integrations exist in various forms; whether they are native, Enterprise-only or third-party depends on your version, so I check before promising them. For paid acquisition, see Google Ads management.

Dealer schemes, export quotes and regional language documents

Manufacturers and brands selling through distributors need pricing that reflects dealer category, region and volume. Odoo price lists can handle tiered and category-based pricing, and discounts beyond an agreed level can be routed for approval. I keep schemes visible on the sales order, so accounts can see why a price was given and the scheme cost can be reported later.

Exporters need a different flow. Quotations go out in dollars or euros with Incoterms, payment by advance or letter of credit, and an export tax treatment that your accountant confirms, for example supplies under a letter of undertaking. In Odoo these customers get their own fiscal position and price list, and the sales order carries the currency through to the invoice while the books stay in rupees.

Language is the third element. Many customers and dealers prefer Hindi or a regional language for communication. Odoo prints documents in the language set on each customer where translations exist. In practice I usually keep tax documents in English, which buyers and auditors expect, and prepare email and message templates in the languages your executives use daily. Test any non-Latin script on real printouts before rollout.

For the wider order-to-cash view, see manufacturing ERP.

Community or Enterprise, other CRMs and when Odoo CRM is not right

Many Indian companies run Odoo Community with third-party modules for GST, marketplace connectors and reports. That can work, but it makes you dependent on each module's author for updates. The core CRM app is in Community; VoIP, Studio, some messaging features and parts of the Indian e-invoicing integration may be tied to Enterprise. I check your edition and modules against requirements before design is signed.

Some Indian companies already use Zoho CRM, and subsidiaries of global groups often use Salesforce. Keeping them can make sense when marketing workflows or group reporting depend on them. Then Odoo owns customers, quotations, orders, dispatch and invoices from an agreed stage, and status flows back.

Odoo CRM is a weak fit when:

• Secondary sales at FMCG scale need retailer-level orders, schemes and distributor stock across a very large outlet base.
• Odoo will hold only accounts, so the order-to-invoice link is lost.
• The business depends on heavily customized marketplace workflows nobody will maintain.

See the global Odoo CRM page, CRM consulting, the ERP consultant India page and the India hub.