The Grievance Redressal Posture Indian Sellers Need

Every seller has a support inbox. Far fewer have a grievance mechanism. The two are not the same thing, and the gap between them is where most Indian ecommerce brands get hurt.

Support is a service function. It answers questions, chases couriers, issues refunds and closes tickets. A grievance mechanism is an accountability function. It is the named, published route a customer takes when the service function has already failed them. It exists so that a dissatisfied buyer has somewhere to go inside your company before they go outside it.

If you sell online in India, you should assume that route will be used. The frameworks that govern it are the Consumer Protection Act, 2019 and the Consumer Protection (E-Commerce) Rules, 2020, with the Central Consumer Protection Authority as the regulator that acts on patterns of unfair trade practice. Platforms that operate as intermediaries also carry grievance obligations under the IT Rules. What these instruments require in principle is stable. The specifics are not. Response windows, who exactly must appoint a grievance officer, and the thresholds that trigger extra obligations are set by rules that get amended, and they read differently for a marketplace, an inventory seller and a small third party seller. Confirm the current position for your category and your turnover with your own counsel. Do not take a number from a blog post, including this one.

Support answers the customer. Grievance handling answers for the company.

The practical difference is authority. A support agent can act inside policy. A grievance function decides what the company will do when policy and the customer disagree, and it records why. That means it needs three things a support queue usually does not have: a named human who owns the decision, a route that does not depend on the agent who already said no, and a written closure that states the outcome and the reason.

Most brands fail on the second one. The escalation path loops back into the same queue, the customer gets the same scripted answer twice, and the third attempt is not made to you at all. It is made to the marketplace, to the National Consumer Helpline, or on a public timeline. By then you have lost control of the narrative and the record.

Publish it where a frustrated buyer can actually find it

A grievance mechanism buried in the terms of service is a mechanism that exists on paper. The test is simple. Open your site on a phone, imagine you are angry, and try to find who to complain to. If it takes more than a few seconds, your route is not reachable.

Put the contact point in the footer of every page, inside the order detail view, in the shipping confirmation email and on the returns page. Give a working email address that is monitored, and a name and designation for the person who owns it. Keep it current. A published contact that bounces is worse than no published contact, because it converts a service failure into a credibility failure that is trivially easy to evidence against you.

The same discipline applies to your marketplace storefronts. Buyers who bought on a platform will often try the brand directly, and a brand that cannot be reached looks like a brand that is hiding.

Record keeping is the thing that actually protects you

When a complaint escalates, nobody is interested in your intentions. They are interested in what you can show. The brands that come out of these processes cleanly are the ones that can produce a complete, dated file in one sitting.

For any order that could become a grievance, you want the order identifier and timestamp, the exact product listing and price as displayed at the time of purchase, the payment reference, the courier docket and full scan history, proof of delivery, every message exchanged with the customer across every channel, the refund or replacement reference with its date, and a note of who decided what and on what basis. Keep the version of the policy that was live on the purchase date, not the one live today. Policies change and customers are judged against the terms they actually saw.

Store this so it can be retrieved by order ID, not by agent memory. Retention should be long enough to cover the period in which a claim can still be brought, which again is a question for your counsel and not for a template.

Where the complaint goes when it leaves your building

Once a buyer gives up on you, the ladder is roughly this. They raise it with the marketplace, which runs its own policy process and often decides in the buyer’s favour on the balance of convenience. They raise it on the National Consumer Helpline, which routes it to the company for a response. If that does not satisfy them, they can file formally before a consumer commission, and filing is now largely online. Separately, the Central Consumer Protection Authority can act on its own or on a class of complaints where the pattern suggests an unfair trade practice or a misleading claim, and its interest is triggered by volume and repetition rather than by any single angry buyer.

Notice what that ladder rewards. Each rung is cheaper for the customer than the last and more expensive for you. A refund you refuse at rung one costs you the refund plus your time at rung two, plus a documented pattern at rung three. The commercial logic of resolving early is not softness. It is arithmetic.

Build the posture before you need it

Name an owner. Publish the route in four places. Write a two page internal note that says what your grievance function can approve without further sign off. Log every escalated complaint in one place with a category, a resolution and a date, and read that log monthly for the three failure modes that generate most of it. Fix those upstream.

None of this is expensive at small scale. All of it is very expensive to retrofit at the point when a regulator, a marketplace and a customer are all asking you the same question in the same week.