The Meesho Supplier Panel, section by section.
The Supplier Panel runs your whole Meesho business — orders, catalog, payments, returns, ads, support. Here is a walkthrough of what each section does, where sellers get stuck, and the one thing the panel shows you but does not do for you.
- The Supplier Panel is Meesho's seller dashboard: orders, catalog, payments, returns, ads, support.
- Orders is the busiest section; payments is the one that hides wrong deductions.
- Catalog quality feeds everything downstream — clean listings mean correct invoices and clean fulfilment.
- The panel shows you your business but does not run it — reconciling, batching and chasing charges are on you.
- Robnu sits on top of the panel and turns the seeing into doing. Free while we figure out pricing.
Every Meesho seller lives in the Supplier Panel, but few use every section well — and the sections people skip are usually the ones costing them money. This walkthrough goes section by section, explains what each is for, points out where sellers get stuck, and draws the crucial line between what the panel shows you and what it actually does for you.
The Supplier Panel is the operational home of a Meesho business — the one dashboard where orders arrive, products are listed, money is settled, and returns are tracked. Knowing where each function lives is the difference between fumbling and flowing. This walkthrough covers every major section, the traps inside each, and the single most important distinction: the panel is a window onto your business, not a hand that runs it.
The orders section: the busiest screen you own
Orders is where the day happens. It shows every order by state — pending acceptance, ready to ship, shipped, delivered, and the return and RTO states — and it is where you accept orders, generate labels and invoices, close manifests, and hand over. Because it is the busiest section, small inefficiencies here cost the most. A clean ready-to-ship view saves time; a messy one breeds the label failures and manifest mistakes covered across our dispatch chain guide.
The trap in the orders section is treating it as a to-do list you work one item at a time. The efficient reading is by state: filter to ready orders, act on the whole batch, move on. The panel supports this, but it does not enforce it — the discipline is yours, which is exactly why dispatch time varies so much between sellers running the same volume.
The payments section: where wrong deductions hide
The payments or settlements section shows what you have been paid and every deduction taken — commissions, shipping, returns, adjustments. This is the section to read most carefully, because it is where wrong charges live. A reverse charge on a pure RTO, a weight discrepancy, a duplicate, a return you were billed for but never received — all of them appear here as line items that look routine.
This is the single most valuable section to work well and the one most sellers skim. The gap between glancing at your payout and reconciling it is where recoverable money sits — the reason payment reconciliation and RTO recovery exist as disciplines rather than afterthoughts.
The catalog section: quality that flows downstream
The catalog section is where you add and edit products, set attributes and prices, manage stock, and see listing quality signals. It is tempting to treat it as a one-time setup, but catalog quality feeds everything downstream. A listing with a missing tax attribute produces a wrong GST invoice; a paused or flawed listing can block a label from generating. Clean listings are not just about discoverability — they are the foundation of correct invoices and clean fulfilment.
The returns section: track the money coming back
The returns section tracks both customer returns and RTO orders through their statuses. It is where you watch a return move through acknowledged, out for delivery, and delivered, and where you confirm stock physically coming back. Read on its own it is informational; read alongside the payments section it becomes powerful, because that is how you catch returns you were charged for but never actually received. The status vocabulary here is decoded in our courier states glossary.
Performance, ads and support — and the panel’s limit
The remaining sections round out the account. Performance shows your SLA adherence, return rates and account health; ads let you promote listings; support handles tickets and disputes. All useful — but all reporting after the fact. The panel shows your SLA once it is measured, not while the clock is running; it shows a wrong deduction as a line item, not as a flagged error to chase. That is the panel’s essential limit: it is a superb window onto your business and not a system that runs it. The gap between seeing your data and acting on it is the gap an agentic OMS fills.
Sources & further reading
Panel sections and features change over time. Confirm the current layout against the official documentation:
What each section is for
Learn where each function lives and the panel stops feeling like a maze. Here are the sections that matter most, and the trap inside each.
Orders
Accept, label, manifest, hand over. Read it by state and batch each link; the trap is working it one order at a time as an endless to-do list.
Payments
Every payout and deduction. The trap is reading the total instead of reconciling each charge against the order — where wrong deductions hide.
Catalog
Products, attributes, stock, quality. The trap is treating it as one-time setup; a bad attribute flows into wrong invoices and blocked labels.
Returns & performance
Return statuses, SLA and account health. The trap is reading them in isolation and after the fact, instead of alongside payments and in real time.
The panel shows; it does not do
Every section of the panel is a window — a clear, useful view of your business. What it is not is a hand that acts on what it shows. That distinction is the whole reason a busy account feels like unending manual work.
- It shows deductions. It does not reconcile them against what should have been charged.
- It lists orders. It does not batch the dispatch chain end to end for you.
- It tracks returns. It does not flag the ones billed but never physically received.
- It reports SLA. It does not watch the clock before a breach turns into a penalty.
Closing that seeing-to-doing gap is exactly what an OMS is for.
Turning the seeing into doing
The panel is a good window and a poor pair of hands. Robnu is an agentic OMS that sits on top of your Meesho account: it reads the same data the panel shows and acts on it — reconciling deductions to the rupee, batching the dispatch chain, tracking every return, and flagging wrong charges. It even prepares and files claims for the recoverable ones (a rare approval click while fully-autonomous filing rolls out).
You keep the panel — nothing is replaced. What changes is that the sections you would otherwise click through by hand, order by order and line by line, are run for you. AJIO and Meesho operations are live today, and the same account also gets the AI Catalog Studio for product images and video, with credits included to start.
You sell, Robnu runs the rest — the whole panel, on autopilot.
The Supplier Panel, answered
The Supplier Panel is Meesho's web dashboard for sellers — the place you manage your catalog, receive and dispatch orders, generate labels and invoices, track returns and RTO, view payments and settlements, run ads, and handle support. It is the operational home of a Meesho business, and learning where each function lives is the first step to running the account efficiently.
In the orders section, which shows orders by state — pending acceptance, ready to ship, shipped, delivered, and the return and RTO states. This is where you accept orders, generate labels and invoices, close manifests, and hand over. It is the busiest section day to day, and the one where a clean ready-to-ship view saves the most time.
In the payments or settlements section, which shows what you have been paid and the deductions taken against each order — commissions, shipping, returns, and any adjustments. This is the section to read carefully, because it is where wrong deductions live. A charge that does not match the weight or lane it should is only visible if you actually reconcile this section against your orders.
In the catalog section, where you add and edit products, set attributes and prices, manage stock, and see listing quality signals. Clean listings matter beyond discoverability — they feed correct invoices and clean fulfilment, so a listing with a missing tax attribute or wrong detail causes problems downstream in dispatch and GST.
In the returns section, which tracks both customer returns and RTO orders through their statuses. This is where you see a return moving through initiated, acknowledged, in transit and delivered, and where you confirm stock coming back. Reading it alongside the payments section is how you catch returns you were charged for but never physically received.
It shows you your business but it does not run it. The panel displays orders, deductions, returns and metrics, but it does not reconcile the deductions against what should have been charged, does not batch your dispatch chain end to end, and does not chase wrong charges for you. Those are the gaps between seeing your data and acting on it — the gaps an OMS fills.
You can operate a small account from the panel alone, clicking through each section by hand. But as volume grows, the per-order and per-section manual work — reconciling deductions, batching dispatch, tracking every return — outgrows what a person can do reliably in a dashboard. That is the point where sellers add an OMS on top of the panel rather than replacing it.
Robnu sits on top of your Meesho account as an agentic OMS: it reads the same data the panel shows and acts on it — reconciling deductions to the rupee, batching the dispatch chain, tracking every return, and flagging wrong charges. You keep the panel; Robnu turns the seeing into doing, so the sections you would otherwise click through by hand are run for you.
Related seller guides
More on the operations, money and claims that decide whether a marketplace catalogue actually makes money.
AJIO Seller Panel Guide: A Walkthrough of AJIO Seller Central
A practical, screen-by-screen walkthrough of the AJIO seller panel — onboarding, catalogue, orders, dispatch SLAs, returns and payouts — plus the reports that decide whether you get paid correctly.
Meesho orders stuck in pending: what it means and how to clear them
Blocked does not mean paused — the dispatch clock usually keeps running. The four causes, which two you can fix yourself, and what to document when you cannot.
Meesho bulk label download: 100 orders labelled in minutes
Downloading Meesho labels one order at a time does not scale. Here is the batch dispatch workflow — bulk-select ready-to-ship orders, generate labels and invoices as one merged PDF, print, and manifest without touching each order.
Meesho "Ready to Ship" label not generating: causes and fixes
Your Meesho order is Ready to Ship but the label will not generate. The exact causes — order state, listing and stock issues, payment or account holds, panel timeouts — and the step-by-step fix for each.
Meesho manifest and handover mistakes that trigger penalties
Closing the manifest, the handover scan, and the gap between them is where Meesho penalties hide. The mistakes that trigger them — manifested-but-not-handed-over, missing scans, wrong counts — and how to close cleanly.
Scan, label, manifest: the Meesho dispatch chain end to end
Dispatch is not four separate jobs — it is one chain: scan, label, pack, manifest, hand over. Run as a routine, it flows; broken up, it leaks time and triggers penalties. The full chain, in order, and where each link fails.
Meesho OMS: The Honest Buyer's Guide for Sellers
What an order management system for Meesho actually is, what to look for before you commit, the questions that separate real tools from dashboards, and where Robnu fits in as one honest option.
One Screen for All Your Orders: The Case for Centralized Order Processing
Selling on three marketplaces means three dashboards, three SLA clocks and three ways to miss an order. Here is why a single order screen — an agentic OMS that runs them all — is the fix.