Procedures for Acknowledgement and Dispatch of Electronic Records

When you place an order on an online store and get that instant “Order Confirmed” message, you are witnessing Sections 12 and 13 of the Information Technology Act, 2000 at work. These two sections quietly answer some of the trickiest questions in e-commerce law: When is a message legally considered “received”? Does silence count as acceptance? And where, in the borderless world of the internet, does a transaction actually take place? For anyone studying e-commerce law, understanding acknowledgement and dispatch is the key to understanding how electronic contracts hold up in court.

Why the IT Act had to define these moments 🔗

Before electronic contracts could be trusted the way paper contracts were, Indian law needed to answer a basic question: does clicking “I agree” or hitting send on an email carry the same legal weight as a signature on paper? Section 4 of the IT Act gives electronic records legal recognition, treating them as equivalent to written communication under Indian law. But recognition alone is not enough. Contracts are built on offer and acceptance, and both depend on precise timing. Chapter IV of the Act, covering Sections 11 to 13, exists specifically to pin down when an electronic message is attributed to a sender, when its receipt is acknowledged, and when it is legally dispatched and received.

This matters enormously in e-commerce. An online seller, a payment gateway, and a buyer’s device may all be in different states, or different countries. Without clear rules, disputes over “I never got your confirmation” or “the order left our system on time” would be nearly impossible to resolve.

Acknowledgement of electronic records under Section 12 🔗

Section 12 deals with a simple but important scenario: how does the sender (called the originator) know that the recipient (the addressee) actually received the electronic record?

No specific method required 🔗

If the originator has not insisted on a particular form of acknowledgement, the law keeps things flexible. According to the provision, an acknowledgement may be given through any communication by the addressee, whether automated or manual, or through any conduct of the addressee that reasonably signals the record was received, as laid out in Section 12(1). In practice, this could be as simple as a buyer replying to a confirmation email, or a system auto-generating a “delivery successful” notification. Even acting on the contents of the message, such as a vendor starting to process an order, can count as sufficient conduct.

When acknowledgement is a condition for a binding contract 🔗

Sometimes the originator wants more certainty. If they explicitly state that the electronic record will only be binding once acknowledged, the law is strict: until that acknowledgement is received, the record is treated as though it was never sent at all. This is spelled out in Section 12(2), and it protects businesses that want proof of receipt before committing resources, such as a seller who wants order confirmation before dispatching high-value goods.

What happens when no acknowledgement arrives 🔗

Section 12(3) covers the in-between case, where acknowledgement was expected but not made mandatory for the contract’s validity. If the addressee doesn’t respond within the agreed or a reasonable time, the originator can issue a notice specifying a fresh deadline. If acknowledgement still doesn’t come through, the originator is entitled to treat the record as if it was never sent. This gives businesses a legal exit route instead of being stuck in limbo over an unanswered communication.

Dispatch and receipt: time and place under Section 13 🔗

While Section 12 is about confirming receipt, Section 13 answers a different question: exactly when and where does an electronic record legally leave one party and arrive with another? This becomes critical in disputes over delivery timelines, jurisdiction, and which state’s or country’s laws apply.

When is a record considered dispatched 🔗

Unless the parties have agreed otherwise, the dispatch of an electronic record occurs the moment it leaves a computer resource that is outside the originator’s control, as defined in Section 13(1). So the instant an email leaves the sender’s outgoing server, or an order confirmation leaves the merchant’s system and enters, say, the email provider’s servers, dispatch has legally occurred, regardless of when the buyer actually opens it.

When is a record considered received 🔗

Receipt is more nuanced. If the addressee has designated a specific computer resource for receiving such records, receipt occurs the moment the message enters that designated system. But if the message is instead sent to a different, non-designated resource of the addressee, receipt only occurs when the addressee actually retrieves it. If no resource has been designated at all, receipt is deemed to occur as soon as the record enters any computer resource of the addressee.

This distinction matters more than it might seem. Consider a company that has designated a specific order-processing inbox for customer communications. A message sent there is received the moment it arrives, even if nobody has read it yet. But a message sent to an employee’s personal inbox, which was never designated for that purpose, is only “received” once that employee actually opens and retrieves it.

Where does dispatch and receipt take place 🔗

Location matters too, especially for jurisdiction in disputes. Unless otherwise agreed, an electronic record is deemed dispatched from the originator’s place of business and deemed received at the addressee’s place of business, irrespective of where the servers involved are physically located. If either party has multiple places of business, the principal place of business governs; if they have no fixed place of business, their usual residence is used instead. This rule keeps things predictable even when servers, cloud storage, or intermediaries are scattered across different geographies.

How this plays out in real e-commerce disputes 🔗

Legal principles feel abstract until courts apply them to real transactions. In Trimex International FZE Ltd. v. Vedanta Aluminium Ltd., the Supreme Court examined whether an exchange of commercial emails could form a binding contract. Vedanta had confirmed acceptance of Trimex’s offer over email, and the seller relied on that confirmation to enter into further contracts with shipowners and suppliers. When Vedanta later denied a concluded contract existed, the Court disagreed, holding that communication of acceptance through email exchanges was sufficient to form a binding agreement, even without a signed physical document.

This ruling reinforces exactly what Sections 12 and 13 aim to establish: electronic communication carries real legal consequences the moment it is sent, received, or acted upon. A casual “we confirm the order” typed in an email is not a throwaway line; it can bind a business to its terms.

Why this matters beyond the exam 🔗

These provisions are not just theoretical; they shape everyday compliance in Indian e-commerce. Regulatory frameworks built on top of the IT Act echo the same logic. For instance, under the Consumer Protection (E-Commerce) Rules, 2020, platforms are required to appoint a grievance officer who must formally acknowledge consumer complaints within 48 hours and resolve them within a defined timeline. The idea of a mandatory, time-bound acknowledgement, first established in Section 12, has become a standard expectation across India’s digital commerce regulations.

For e-commerce businesses, this translates into very practical decisions: should a platform mandate acknowledgement for every order before treating it as confirmed? Should customer support inboxes be formally designated as the receiving system to avoid disputes over “we never got your message”? These aren’t just legal technicalities. They shape refund timelines, delivery SLAs, and how disputes get resolved when something goes wrong mid-transaction.

For students, the takeaway is that e-commerce law isn’t abstract theory bolted onto technology. It is the invisible infrastructure that makes millions of daily online transactions enforceable, predictable, and fair to both buyer and seller.

What do you think? If you were designing the checkout flow for an online store, would you make buyer acknowledgement mandatory before confirming an order, or rely on implied conduct like payment completion? And how might designating a specific “receiving” system for customer complaints change the outcome of a dispute?

References

1. https://www.indiacode.nic.in/bitstream/123456789/13116/1/it_act_2000_updated.pdf
2. https://indiankanoon.org/doc/1968067/
3. https://indiankanoon.org/doc/916793/
4. https://psalegal.com/issue-vi-think-before-you-type-e-mail-exchanges-can-bind-parties/
5. https://www.teamleaseregtech.com/blogs/134/e-commerce-compliance-in-india-understanding-the-consumer-protection-e-commerce-rules-2020/