Vendor Agreement India: Key Clauses, Risks and Practical Drafting Points

What is a vendor agreement?

A vendor agreement is the core contract between a buyer and a vendor or supplier. It usually records commercial terms such as specifications, quantities, delivery timelines, price, taxes, payment, warranties, liability, confidentiality, termination, and dispute resolution. In practice, businesses often use a master vendor agreement plus individual purchase orders. The agreement sets the legal framework, while purchase orders handle order-specific details such as item description, quantity, price, and dispatch schedule. This structure usually works better than relying only on emails or one-sided purchase orders, especially in recurring procurement relationships.

Who typically needs a vendor agreement in India?

This topic is especially relevant for startups and growth-stage businesses building procurement systems, manufacturers buying raw materials, packaging, components, or outsourced production, retailers and e-commerce businesses working with stock, fulfilment, and logistics vendors, companies engaging recurring operational vendors such as IT support, maintenance, warehousing, or onboarding partners, and businesses onboarding vendors who will handle confidential information, customer data, software access, or branded materials.

Why a vendor agreement matters

A vendor agreement gives procurement relationships structure. First, it defines the supply obligation clearly. Under the Sale of Goods Act, the seller must deliver the goods and the buyer must accept and pay for them, and payment and delivery are treated as concurrent conditions unless the contract says otherwise. Second, it helps allocate delivery and timing risk. Under section 55 principles of the Indian Contract Act, failure to perform on time has different consequences depending on whether time was intended to be of the essence. Third, it helps manage quality and non-conformance because commercial parties should not rely only on implied rules. Fourth, it supports better payment discipline by recording invoice timing, document requirements, tax treatment, acceptance triggers, debit notes, and delay consequences.

• Clear specifications and delivery expectations
• Payment discipline and vendor accountability
• Inspection, rejection and replacement rights
• Reduced procurement disputes before they escalate

Key clauses every vendor agreement should consider

The agreement should clearly cover parties, goods or services, specifications, purchase orders, delivery schedules, inspection, pricing, GST, invoices, payment terms, warranties, confidentiality, data use, indemnity, liability caps, termination, and dispute resolution. For procurement-heavy businesses, these details should be written in a way that aligns with actual operational workflow rather than a generic template. Vague descriptions create avoidable disputes, so the agreement should state technical specifications, approved materials or components, packaging standards, performance standards, shelf-life or storage conditions where relevant, testing requirements, and whether supply is based on a drawing, datasheet, prototype, or approved sample.

• Parties, scope and contract structure
• Specifications, quality standards and samples
• Purchase orders, quantities and forecasts
• Delivery schedules, title and risk
• Inspection, acceptance and rejection
• Pricing, GST, invoices and payment terms
• Warranties, defects and replacement obligations
• Confidentiality, data use and compliance
• Indemnity, liability cap and insurance
• Termination, suspension and dispute resolution

India-specific legal considerations

Vendor agreements in India should reflect contract enforceability, sale-of-goods principles, MSME delayed-payment exposure, electronic execution, stamping hygiene, and data protection for digital or access-based vendors. Where the arrangement is for the sale of goods, title and risk often matter just as much as price. If the vendor is a registered micro or small enterprise, payment terms should be checked carefully against the MSMED delayed-payment framework. Electronic records and electronic signatures have statutory recognition under the Information Technology Act, 2000, but the execution method should still suit the document and evidence requirements. Stamping also should not be treated casually because the applicable framework can differ depending on the instrument and the place of execution.

• Contract enforceability under Indian law
• Sale of goods principles for title, risk, and delivery
• MSME delayed-payment exposure
• Electronic execution
• Stamping and execution hygiene
• Data protection for digital or access-based vendors

Common drafting mistakes

The most common problems are vague specifications, no delivery consequences, missing rejection and replacement process, weak payment language, and no title, risk, or data clauses. Many disputes begin because the agreement does not clearly say what counts as acceptance, what happens on delay, or how replacement will work if goods are defective. Another mistake is failing to address late delivery where timing matters commercially. Another is ignoring inspection and rejection mechanics so that receiving teams and accounts teams may treat physical receipt as acceptance even where goods are defective. Another is weak MSME and invoice drafting because payment clauses copied from old templates can create unnecessary exposure if the supplier is a protected micro or small enterprise.

• Vague specifications
• No delivery consequences
• Missing rejection and replacement process
• Weak payment language
• No title, risk, or data clauses

Practical examples

Vendor agreements are commonly used for packaging suppliers, raw-material suppliers, IT procurement vendors, logistics partners, fulfilment vendors, maintenance vendors, and software-enabled service providers. A D2C business buying custom printed boxes may need artwork approval, colour tolerances, delivery windows, rejection rights, and who bears reprint and freight costs. A business appointing a vendor to supply and maintain barcode scanners may need installation obligations, service levels, spare-part availability, replacement timelines, software licence boundaries, and data-security wording. An e-commerce company appointing a warehousing or fulfilment vendor may need inventory handling, shrinkage, reporting, service levels, reconciliation, indemnity structure, and liability caps.

• Packaging or raw-material supplier
• IT procurement or managed service vendor
• E-commerce fulfilment or logistics vendor

When professional legal review may help

Legal review is especially useful where the supply relationship is high-value or business-critical, where the vendor handles sensitive data or software access, where the contract includes recurring purchase orders or fluctuating forecasts, or where the buyer wants workable remedies for delay, defects, and vendor non-performance. Review is also useful where the counterparty has sent a one-sided procurement template, where the parties need a practical substitute-performance or step-in structure, or where the business wants to make sure the contract works in the real world instead of only on paper.

• High-value supply chains
• Multi-vendor procurement
• Custom manufacturing or installation
• Sensitive data, software access, or enterprise onboarding

Practical closing point

A strong vendor agreement does more than describe price and delivery. It gives the business a practical way to manage the full procurement relationship with clearer standards, stronger accountability, and fewer commercial surprises.