Every business deal, whether it’s a multi-crore merger or a student selling an old scooter, starts the same way: two people agreeing on something. In law, that “agreement” isn’t just a friendly nod. It has a precise shape, laid out in Section 2(e) of the Indian Contract Act, 1872, and understanding that shape is the first real step into contract law. Once you see how an agreement actually forms, through an offer, an acceptance, and something lawyers call consensus ad idem, the rest of the subject stops feeling abstract and starts looking like the everyday mechanics of business.
Table of Contents
- What Section 2(e) actually says
- Offer and acceptance: how a promise is born
- The proposal, or offer
- Offer versus invitation to offer
- The acceptance
- From promise to agreement
- Consensus ad idem: the meeting of minds
- The case of the two ships named Peerless
- The same problem, closer to home
- Why this precision matters in business
What Section 2(e) actually says
Section 2(e) defines an agreement as a promise, or a set of mutual promises, that forms the consideration for each other. In plain terms, an agreement is a promise backed by something of value that each side is giving the other. That value, called consideration, is what stops a promise from being just a casual statement of intent.
A simple way to remember this: agreement equals promise plus consideration. But a promise doesn’t appear out of nowhere. It’s the result of two earlier steps, an offer and its acceptance, both of which the Act defines with equal precision.
Offer and acceptance: how a promise is born
Before there’s a promise, there’s a proposal. And before there’s an agreement, that proposal has to be accepted. These aren’t formalities. They’re the actual test the law uses to check whether two parties genuinely intended to strike a deal.
The proposal, or offer
Under Section 2(a) of the Act, a person makes a proposal when they signal to someone else their willingness to do, or not do, something, with the intention of getting that other person’s assent. If A tells B, “I’ll sell you my laptop for ₹30,000,” A has made a proposal. A is the offeror, and once accepted, A becomes the promisor, while B becomes the promisee.
An offer has to be definite and communicated with the intent to be bound. Casual price talk, or a general statement of intention, usually doesn’t rise to the level of a legal offer.
Offer versus invitation to offer
Students often mix up an offer with an invitation to offer. A shopkeeper’s price tag, a newspaper advertisement, or a company’s product catalogue is usually only an invitation for customers to make an offer, not an offer itself. A classified advertisement reading something like “cocks and hens, 25 shillings each” has, in fact, been held not to constitute a valid offer to sell, precisely because it lacked the definiteness the law expects. This distinction matters commercially too: a retailer displaying goods in a shop window isn’t legally bound to sell to every customer who walks in wanting them at the marked price.
The acceptance
Section 2(b) covers the other half of the equation. When the person to whom the proposal is made signifies their assent, the proposal is said to be accepted, and it turns into a promise. If B replies, “Yes, I’ll take the laptop for ₹30,000,” the offer has been accepted, and a promise now exists between A and B.
Acceptance has to be absolute and unqualified. A counter-offer, say B replying “I’ll pay ₹25,000 instead,” doesn’t count as acceptance. It kills the original offer and creates a fresh one that A must now accept or reject. Courts have also recognised that an offer doesn’t always need a named recipient. In the famous English case of Carlill v Carbolic Smoke Ball Co., a company’s advertisement promising a reward to anyone who used its product and still fell ill was treated as a genuine offer to the world at large, one that any individual could accept simply by performing the stated conditions. This reasoning, though English in origin, continues to guide how Indian courts read promotional offers and public promises.
From promise to agreement
Once B accepts A’s offer, the proposal becomes a promise. That promise, paired with the consideration flowing between the parties (the laptop from one side, the money from the other) is what the law calls an agreement. Teachers of business law often summarise the whole sequence as a chain: offer plus acceptance equals promise, and promise plus consideration equals agreement.
| Term | What it means | Governing section |
|---|---|---|
| Proposal | Signalling willingness to do or not do something, to obtain another’s assent | Section 2(a) |
| Acceptance | Signifying assent to a proposal, turning it into a promise | Section 2(b) |
| Promise | An accepted proposal | Section 2(b) |
| Consent | Two or more persons agreeing on the same thing in the same sense | Section 13 |
| Agreement | A promise, or set of promises, forming consideration for each other | Section 2(e) |
It’s worth remembering that not every agreement is enforceable as a contract. Legal commentary on the Act points out that while every contract is necessarily an agreement, the reverse isn’t true, an agreement becomes a contract only once it also satisfies conditions like free consent, lawful consideration, and a lawful object.
Consensus ad idem: the meeting of minds
Offer and acceptance can sound mechanical, almost like ticking boxes. But underneath both lies something the law treats as non-negotiable: the two parties have to actually be talking about the same thing, in the same way. This principle is known as consensus ad idem, Latin for “agreement on the same thing,” and Indian law captures it in Section 13 of the Contract Act, which defines consent as existing only when two or more persons agree upon the same thing in the same sense.
This is a subtle but crucial shift. It isn’t enough for A to say yes and B to say yes. Both have to be saying yes to the identical subject matter. If their understanding diverges, even without any dishonesty on either side, the law treats no real agreement as having been formed at all.
The case of the two ships named Peerless
The classic illustration is the old English case Raffles v Wichelhaus, still taught in Indian classrooms today. A seller agreed to deliver cotton arriving on a ship called the Peerless, sailing from Bombay. Unknown to either party, two different ships bore that exact name, one sailing in October and one in December. The buyer had the October ship in mind; the seller meant the December one. When the cargo arrived later than the buyer expected, he refused to pay, and the court agreed there was no binding contract. Both parties had used the same word, but they weren’t agreeing on the same ship. Without a genuine meeting of minds, the law found no agreement had ever come into existence.
The same problem, closer to home
The identical logic plays out in ordinary Indian transactions. Suppose a seller owns two houses on the same street and offers to sell “the house on MG Road,” meaning the older bungalow. If the buyer accepts, believing the offer refers to a newer flat on the same road, both parties have technically said yes, but not to the same thing. There is an apparent offer and an apparent acceptance, yet no agreement exists in the eyes of the law, because the parties never truly agreed on what was being bought and sold. The absence of consensus ad idem defeats the deal regardless of how sincerely each side believed a bargain had been struck.
Why this precision matters in business
For anyone heading into sales, procurement, or contract drafting, this isn’t just exam theory. Vague product descriptions, unclear delivery terms, or simply assuming the other party “obviously” understood what was meant, are exactly the gaps where consensus ad idem breaks down. Well-drafted commercial agreements spell out the subject matter, specifications, quantities, and timelines in detail, precisely so that both sides are provably agreeing to the same thing. This is also why courts examining a dispute look closely at the actual communication between the parties, emails, quotations, purchase orders, rather than stopping at the final signed document, to check whether a genuine meeting of minds existed at the moment the deal was struck.
It’s a useful reminder that ticking the procedural boxes, sending an offer, receiving a signed acceptance, isn’t the same as forming a valid agreement. Without shared understanding of the subject matter, a business can end up with a document that looks binding on paper but carries no real legal weight.
What do you think? If two parties act in complete good faith but still end up misunderstanding the subject matter of their deal, should the law protect the party who relied on the agreement, or should it always treat the deal as void for lack of consensus ad idem? And in an age of quick WhatsApp confirmations and rushed email chains, how easily do you think a misunderstanding like the Peerless case could still happen today?
References
- https://indiankanoon.org/doc/1089645/
- https://www.jettystudy.com/topic/Agreement-Proposal-Offer-and-Acceptance-Under-Indian-Contract-Act-1872.14.html
- https://lawbhoomi.com/case-brief-louisa-carlill-v-carbolic-smoke-ball-co/
- https://www.legalserviceindia.com/legal/article-7796-section-2-of-the-indian-contract-act-1872.html
- https://indiankanoon.org/doc/1463968/
- https://en.wikipedia.org/wiki/Raffles_v_Wichelhaus
Leave a Reply