Contract Terms That Matter After The Honeymoon

Nobody reads the contract while the relationship is working. Service is good, invoices clear, the account manager picks up the phone. The document sits in a folder.

You read it on the day it stops working. That is the day you discover what you agreed to. So the honest way to review a vendor contract is to read every clause while imagining the worst quarter of the relationship, not the pitch meeting.

One thing before anything else. What follows is commercial guidance from an operator’s seat, not legal advice. Specific drafting, enforceability and the interaction with Indian law must go to your own counsel. Use this to know what to ask your lawyer for.

Service levels that actually bite

Most service level sections are decorative. They state a target, they state a reporting frequency, and they stop. A target with no consequence is a preference.

Three things make a service level real. A definition both sides can compute from the same data. A measurement source and a reporting cadence, ideally with the raw data available to you rather than a summary. And a consequence that escalates.

Escalation matters more than the size of any single credit. A fixed credit of a small percentage is easy for a vendor to absorb and ignore. A ladder that rises with repeated misses, adds a mandatory remediation plan after a defined number of breaches, and opens a termination right for persistent failure, changes behaviour long before it is ever invoked.

Also define the exclusions honestly. Vendors will carve out force majeure, client caused delays and platform outages, and much of that is fair. What is not fair is an exclusion so broad that any miss can be attributed to something upstream. Read the carve outs as if the vendor will use all of them at once, because in a bad quarter they will.

Liability, and the words that shrink it

Almost every services contract caps liability. The cap is usually expressed against fees paid over some preceding period, and the length of that period varies a great deal in practice. That in itself is not unreasonable. Vendors cannot underwrite your P and L on a services fee.

The part to examine is what sits outside the cap and what is excluded entirely. Indirect and consequential loss is nearly always excluded, and in many disputes that exclusion swallows the real damage, because lost sales during a stockout or a suspension is exactly the kind of loss that gets classified that way.

So ask which categories survive the cap. Confidentiality breaches, data incidents, intellectual property infringement and wilful misconduct are commonly negotiated as carve outs. Ask whether insurance exists, at what level, and whether you are noted on it where relevant. Ask who holds risk in transit and while goods sit in a third party facility, and reconcile that with your own cover so you are not paying twice or, worse, assuming someone else is covered.

Data ownership and getting it back

This clause is boring until the day you leave, and then it decides how long your migration takes.

Separate three ideas. Ownership of your data. Licence to use it. Portability of it. A vendor can have a broad licence to process your data and still leave you unable to extract it in a usable form. State that operational data is yours, that any aggregated or anonymised use requires your consent, and that you can pull an export in a defined format on demand, not only at termination.

Then get specific about what data means, because the argument at exit is always about scope. Order and inventory records, customer contact data where you are entitled to it, advertising account access and history, creative source files rather than only flattened outputs, listing content, and the configuration of any workflow built for you. Agencies frequently hold ad accounts and creative masters in their own environment. Fix ownership and administrator access at signing, not at exit.

Add deletion on the other side. A defined window for deletion after transition, and written confirmation that it happened.

Exit and transition assistance

The termination clause tells you how to leave. The transition clause decides whether leaving is survivable.

Ask for a stated assistance period that continues past the termination date, at rates agreed now rather than negotiated in the middle of a breakup. Ask for a named transition plan with a handover list. Ask explicitly that assistance continues even where termination is for cause or where there is a live payment dispute, because that is precisely when a vendor’s incentive to help collapses.

For physical operations, be concrete. Who packs and loads the stock. Who pays for it. What condition it must be in. Who reconciles the count and what happens to the variance. For agency and technology relationships, the equivalents are access transfer, documentation, and a defined period of parallel running.

Also read the notice period from the vendor’s side. Symmetrical notice is fair. A ninety day notice from you and a thirty day notice from them is not.

Escalation, lock ins and the renewal clock

Price escalation is legitimate. Labour, fuel and rent move. What matters is that the mechanism is defined. Prefer a formula tied to a published index or to a stated ceiling, with a fixed annual review date and advance notice. Avoid open ended language allowing revision on notice, which is not a price at all.

Lock ins arrive in several disguises. Minimum volume commitments with shortfall charges. Exclusivity across categories or channels. Implementation costs amortised across the term, so that leaving early triggers a repayment. Proprietary integrations that make switching expensive without any clause saying so. None of these are automatically bad, and a genuine commitment should buy you a better rate. Just make sure you are paid for the commitment you are giving.

Then the clock. Auto renewal with a long notice window is the single most common way brands stay in relationships they have already decided to end. Diarise the notice date, not the renewal date, and set the reminder well before it. Sixty days before the notice deadline, run a short internal review covering performance against the agreed levels, escalations raised, and whether the scope still matches the business.

Do that once a year and you will never renew by accident. Renewing by accident is how a good vendor relationship turns into an expensive one.