How to Evaluate Dealer Portal Vendors Without Getting Burned

Manufacturers with dealer or distributor networks rarely have a dealer portal problem; they have a coordination problem. Orders arrive on WhatsApp, price lists live in Excel, scheme claims are settled by email, and your sales ops team becomes a human integration layer. If you run a 50-300 dealer network, this hits finance (GST invoices, credit notes, TDS), sales (secondary sales visibility), and IT (yet another app to maintain). Evaluating vendors is hard because every demo shows a clean dashboard and none of them show month-end reconciliation.

What a dealer portal must actually do

Before you compare vendors, write down the five jobs the portal must do. Most manufacturing portals need:

• Order capture with dealer-specific price lists, slabs, schemes, and credit limits.
• Approvals for credit overrides, discounts, and stock allocation.
• GST-compliant documents: tax invoices, e-way bill data, credit/debit notes for claims and returns.
• Visibility: primary sales, secondary sales, inventory at distributor, and outstanding.
• Collections: payment links, UPI, NEFT references, and receipt matching.

If a vendor cannot map these to a live workflow in a sandbox, the demo is theatre. Ask for a sandbox with your own SKUs and dealer tiers loaded. A serious vendor will do this in 1-2 weeks, sometimes for a small fee.

The questions that separate serious vendors

Use this list in the first call. The answers tell you more than any brochure.

• Can we see the data model? You need to know how dealer, distributor, order, invoice, claim, and inventory records relate. If they cannot explain it simply, integrations will be painful.
• Which ERPs do you integrate with natively? For Indian mid-market manufacturers, that usually means Tally (different versions), SAP Business One, Zoho Books, Busy, Marg, or a custom ERP. Ask for reference implementations, not just API docs.
• How do you handle GST edge cases? Inter-state vs intra-state, HSN summary, place of supply, e-invoicing for turnover above ₹5 crore, e-way bill generation, credit notes against scheme claims, and TDS deductions on dealer payments.
• What is the WhatsApp strategy? Many dealers will not install an app. Can they order via WhatsApp and have it flow into the portal? WhatsApp Business API pricing is usage-based, typically per conversation; ask who pays and how it appears on your invoice.
• What happens when connectivity drops? Can dealers place orders offline and sync later? Can your sales officer place an order on behalf of a dealer and tag it correctly?
• Who owns the data? You should. Ask for export in CSV/JSON, a documented schema, and a clear exit process. If the vendor holds your dealer master, you are renting your business.
• How do you handle DPDP Act compliance? Dealer contact data, GSTIN, bank details, and purchase history are personal and business data. Ask about consent, retention, access controls, audit logs, and data residency.
• What is the implementation timeline? For a 100-dealer network with one ERP integration, expect 6-12 weeks for a focused rollout. If a vendor promises 2 weeks, ask what they are skipping: master data cleanup, UAT, training, or integration testing.

Pricing, GST and TDS: where budgets leak

Vendors quote in different ways, so normalise every proposal to a 3-year total cost. Common components:

• Implementation: ₹2-10 lakh depending on integrations and data cleanup.
• Subscription: ₹30,000-₹1.5 lakh per month for 100-300 dealers, often tiered.
• Usage: per order, per invoice, per WhatsApp conversation, per payment gateway transaction.
• AMC/support: 15-20% of license annually, or a retainer.
• Change requests: hourly or day rates for new reports, workflows, or ERP changes.

Ask whether GST is extra (it usually is) and how TDS applies. Software services often attract TDS under Section 194J at 10%, but confirm with your CA. If the vendor is offshore, check place of supply and whether you need to pay under reverse charge. These details change the effective cost by 10-18%.

Worked example: a 120-dealer industrial products manufacturer with ₹60 crore annual revenue. Current process: 1,200 order lines per month, 3 staff spending 60% of their time on order entry, scheme claims, and reconciliation. A portal quoted at ₹6 lakh setup + ₹80,000/month = ₹10.2 lakh in year one, plus WhatsApp and payment gateway usage. If it cuts order processing time by half and reduces scheme leakage by even 0.5% on ₹60 crore, that is ₹30 lakh in avoided leakage. The portal pays for itself if the numbers hold. But you must validate leakage and time savings with your own data, not the vendor's ROI slide.

Integration and data ownership

The portal is not an island. It will sit between your ERP, payment gateway, WhatsApp, and possibly a CRM. Ask for an integration architecture diagram and a named technical contact. Test the hardest integration first: usually sales order creation or invoice posting into your ERP. If that fails, everything else is decoration.

Also check:

• Role-based access for dealers, distributors, sales officers, finance, and admins.
• Audit logs for price overrides, credit limit changes, and invoice edits.
• Backup and disaster recovery with defined RPO/RTO. Ask for the last test date.
• API rate limits and webhook reliability. If your ERP is throttled, orders will queue.
• Exit assistance: data export, parallel run, and knowledge transfer.

Where to start

Shortlist three vendors. Give each the same sandbox test: load 20 SKUs, 10 dealers, two price lists, one scheme, and one credit-limit exception. Ask them to show the order-to-invoice flow, including GST and WhatsApp fallback. Score them on integration risk, data ownership, and 3-year cost, not dashboard polish. If you want a second pair of eyes on the evaluation or a custom portal built around your ERP, Maysan Labs has done this work for manufacturers and can help you ask better questions.