Skip to content
Robnu

Account health: which numbers actually bite.

Marketplaces surface a lot of metrics and act on very few. Here is which ones carry real consequences, what the warning sequence looks like before a restriction, and the one metric worth protecting above the rest.

Free during early access · Forever free under 25 orders/day
app.robnu.com/process/sla-watchdogSLA watchdogHeadroom against the manifest deadlineHealthyHEADROOMBelow 30%Below 10%Above 50%
TL;DR
  • Dispatch reliability and seller cancellations are the two metrics that consistently carry direct consequences.
  • RTO rate hurts your margin far more than it hurts your account standing.
  • The warning sequence is quiet at the start — metrics drift long before anyone tells you clearly.
  • Most metrics use rolling windows, so recovery takes sustained performance, not one good week.
  • Robnu protects the dispatch metric by holding every clock for you. Free while we figure out pricing.

Seller panels display a wall of numbers with no indication of which ones matter. The practical question is not “what is being measured” but “what will actually happen to me” — and the answer is narrower than the dashboard suggests.

Account health is the platform’s composite view of how reliably you operate, and it decides how much visibility your catalogue gets and, at the extreme, whether you can keep selling. But marketplaces surface many metrics and act on very few. This guide covers which metrics actually carry consequences, what the warning sequence looks like, and the one metric worth protecting above the rest.

Not all metrics are equal

Marketplaces care most about outcomes that affect a customer who has already committed, which is why dispatch reliability and seller-initiated cancellations consistently carry the sharpest consequences — both break a promise the platform made on your behalf. Return-related signals sit a tier below; they matter but act more slowly, because a return can be caused by many things outside a seller’s control. Rating and responsiveness metrics tend to be influential rather than punitive. A high RTO rate hurts your margin far more than your standing.

How trouble actually arrives

Restrictions are rarely sudden. First metrics drift quietly, with nothing announced — the cheapest point to intervene and the one almost everyone misses. Then warnings appear in the panel, easy to dismiss during a busy week. Then catalogue reach is reduced, so orders drop without an obvious cause, often misread as a demand problem. Finally harder restrictions apply. The early stages are almost invisible, which is exactly why the damage accumulates before anyone tells you clearly.

Protect dispatch reliability first
It is the highest-consequence metric and the most controllable. Sellers who get dispatch right rarely find themselves in account-health trouble from the other metrics alone. See SLA status.

Recovery takes sustained performance

Most metrics are computed over a rolling window, so recovery requires a sustained period of good performance rather than a single good week. That is why letting metrics slide is expensive even when nothing visible has happened yet — you are digging a hole that takes weeks to climb out of. The specific names and thresholds differ across marketplaces, but the underlying concerns are consistent: did you dispatch on time, did you cancel, did the customer get what they expected. Watching the dispatch metric weekly, and catching orders drifting toward a breach before they miss, is the single most valuable thing you can do — which is why our agentic dispatch tracking holds every clock and surfaces at-risk orders before the platform flags them. If your account is already restricted, see account blocked.

The bigger picture for your catalogue

Whatever the specific status, charge or process, the underlying reality of selling on Indian marketplaces is the same. The platforms are built to move enormous volume, their interfaces speak in operational shorthand rather than plain language, and the money at stake hides in charges that arrive as silent settlement deductions requiring no approval from you. The sellers who stay profitable are not the ones who avoid every problem — that is impossible at scale — but the ones who understand what each event means, know which charges are genuinely owed, and reconcile every settlement so the wrong ones are caught and reclaimed while the claim window is still open.

That discipline is simple to describe and hard to sustain by hand, because it is precise, repetitive work layered on top of actually running the business. It is exactly the kind of task that a two-person team does inconsistently under volume and that software does reliably every cycle. Robnu exists to close that gap: it runs the daily operations these guides describe, reconciles the charges they represent against what you actually shipped and sold, and files the claims you are entitled to — so the vocabulary becomes something handled rather than something you have to master and police yourself. You sell; Robnu runs the rest, and makes sure every rupee is paid correctly.

Sources & further reading

Charges, policies and processes vary by marketplace and category and change over time. The details here are drawn from official documentation and reputable industry sources; always confirm current specifics against your own seller panel and settlement reports:

The hierarchy

Not all metrics are equal

Marketplaces care most about outcomes that affect a customer who has already committed. That is why dispatch failures and seller-initiated cancellations carry the sharpest consequences — both break a promise the platform made on your behalf.

Return-related signals sit a tier below. They matter, but they are noisier and slower to act on, because a return can be caused by many things outside a seller’s control. Rating and response metrics influence how you are treated more than they trigger anything specific.

The metric sellers over-worry about
RTO rate. It is genuinely expensive, but it is a margin problem rather than a compliance one. Meanwhile dispatch reliability — which is both more consequential and more controllable — often gets less attention.
app.robnu.com/account/metric-severityWhich metrics carry consequencesConsequence severity, not measurement frequencyDispatch reliabilitydirect penaltySeller cancellationsdirect penaltyQuality / QC failuresslower effectRTO ratemargin, not standingIllustrative severity ranking. Exact thresholds vary by marketplace.
The sequence

How trouble actually arrives

Restrictions are rarely sudden. The problem is that the early stages are almost invisible.

Stage 1

Quiet drift

Metrics degrade. Nothing is announced. This is the cheapest point to intervene and the one almost everyone misses.

Stage 2

Warnings appear

Notifications in the panel. Easy to dismiss during a busy week, which is exactly when they tend to arrive.

Stage 3

Reach reduced

Visibility falls. Orders drop without an obvious cause — often misread as a demand problem.

Stage 4

Restriction

Catalogue or account action. See account blocked for the recovery path.

app.robnu.com/ajio/ordersOpen ordersSynced from the marketplace · normalised into one schemaOrderSKUStageStatusManifestedManifestedConfirmedConfirmedSlip readySlip readyAwaitingAwaitingOpenOpenManifestedManifestedSlip readySlip ready
The Robnu way

Protecting the metric that matters most

Dispatch reliability is the highest-consequence metric and also the most controllable — which makes it the obvious thing to defend. It degrades not through carelessness but through orders that fell out of attention on a busy day.

Robnu is an agentic OMS. It holds the dispatch clock on every open order across AJIO and Meesho, surfaces orders drifting toward their deadline before the platform flags them, and catches the ones stalled in pending where the clock is still running. The metric stays healthy because the underlying behaviour does.

You sell. Robnu runs the rest — and makes sure every rupee is paid correctly.

FAQ

Account health, answered

It is the platform's composite view of how reliably you operate as a seller — measured through dispatch performance, cancellation behaviour, return and quality signals, and customer-facing outcomes. It matters because it influences how much visibility your catalogue receives and, at the extreme, whether you can continue selling.

Dispatch reliability and seller-initiated cancellations are the two that consistently carry direct consequences across marketplaces, because both directly affect a customer who has already paid or committed. Quality and return-related signals matter but usually act more slowly and diffusely. Rating and responsiveness metrics tend to be influential rather than punitive.

Less directly than sellers fear. RTO is a delivery outcome rather than a policy breach, so it is not usually penalised the way a missed dispatch is. It does signal underlying listing or targeting problems, and it destroys margin regardless. Treat it as an economics emergency rather than a compliance one.

Generally: metrics degrade quietly, then notifications or warnings appear in the panel, then visibility or catalogue reach is reduced, then harder restrictions apply. The important point is that the early stages are easy to miss because nothing dramatic happens — the damage accumulates before anyone tells you clearly.

Weekly is enough for most small sellers, and far better than the common pattern of checking only when something goes wrong. The purpose is to catch a trend while it is still a trend. By the time a warning is explicit, you have usually been drifting for some time.

Dispatch reliability. It is the one you control almost entirely, it is measured on every order, and failures compound into both penalties and lost sales through cancellation. Sellers who get dispatch right rarely find themselves in account-health trouble from the other metrics alone.

Yes, but slowly, because most metrics are computed over a rolling window. That means recovery requires a sustained period of good performance rather than a single good week — and it is why letting metrics slide is expensive even when nothing visible has happened yet.

The specific names, thresholds and calculation windows differ, but the underlying concerns are remarkably consistent: did you dispatch on time, did you cancel, did the customer get what they expected. If you sell on more than one platform, the operational discipline transfers even where the metric definitions do not.

Keep reading

Related seller guides

More on the operations, money and claims that decide whether a marketplace catalogue actually makes money.

The Never-Get-Suspended Checklist for Marketplace Sellers

Account suspension is almost always the end of a slow decline, not a bolt from the blue. The metrics that trigger it and the habits that keep your account healthy across marketplaces.

Amazon India account deactivated: what works in appeals

Deactivation stops your income overnight and generic appeals fail. The Plan of Action that gets an account back — root cause, correction, prevention — and how to never need it.

What You Actually Signed: The Marketplace Supplier Agreement, Clause by Clause

You clicked 'I agree' to sell — but the supplier agreement decides your fees, your deductions, your payment timing and how disputes go. Here are the clauses sellers ignore and should not.

Flipkart Account Deactivated: The Appeal Path That Works

Why Flipkart seller accounts get deactivated, what each status means, and the step-by-step appeal path — the evidence to gather, the ticket to raise, and how to prevent it happening again.

Myntra Partner Account Problems and How to Fix Them

Approval delays, brand authorization rejections, QC and listing suspensions, inventory sync errors, payment holds, SLA warnings, login and GST mismatches — the common Myntra partner account issues and the practical steps to resolve each one.

Appeal Letters That Get Marketplace Accounts Reinstated

A good appeal is a specific, evidenced plan of action — not a plea. The structure that works, the mistakes that get appeals rejected, and how to write yours clearly.

Meesho QC errors: why listings fail and how to fix them

The seven checks behind most catalog rejections, how to find and resubmit failed listings, and the pre-upload checklist that keeps failures off your account record.

Meesho catalog blocked: triggers and the unblock path

What a catalog-level block does to orders and visibility, the usual triggers, the panel-first appeal that works, and how to stop one block becoming an account review.

build e7713058ee9ee67dffe938623a3f859dcb157b2a · 2026-07-24T12:14:00+05:30