Get a shipping label back, in the chat
A parcel in one hand and a phone in the other. Type or say the order number and the PDF comes back. The one rule that outranks everything here: this path downloads, it never processes.
Send an order number, a sub-order number, an AWB, or a phrase like labels from this morning. Robnu finds the label it already holds and sends the PDF into the chat, rendered to your own label settings. It refuses anything that would accept an order or mint a new label.
- Works from an order number, a sub-order number, an AWB, or a time window such as this morning or yesterday.
- The PDF is built to your label settings, the same ones the web download uses, so what prints at the bench is what you expect.
- It only serves labels you already have. Asking for a label does not accept an order, does not mint, and does not run a manifest.
- That restriction is the whole reason the module exists. Before it, a message containing the word label could start a full accept run on an entire account.
- Works by voice, so a packer with both hands full can ask for a label without typing.
This is the most used thing on the whole WhatsApp surface, because it matches what actually happens at a packing bench. A parcel is in front of you, the label is smudged or was never printed, and the order number is right there on the slip. The useful version of that is one message and a PDF coming back, not a laptop and six clicks. The careful version of it is making absolutely sure that asking for a label never does anything other than give you the label.
The four ways to say which label you want
By order number. Send it on its own and Robnu finds the parcel it belongs to. Sub-order numbers work too, which matters on Meesho where one order can carry several.
By AWB. If what you have in your hand is the courier number rather than the order number, send that instead. It resolves the same way.
By time window. Phrases like labels from this morning, today's labels or yesterday's labels work, and this is the one people underuse. It is the fastest way to reprint a batch you already minted when the printer jammed halfway through.
By voice. Hold the button and say the number. The voice note is turned into text and handed to the same parser, so there is no separate voice behaviour to learn and nothing extra can happen because you spoke instead of typed.
It downloads. It never processes. That line is load-bearing
This is worth stating plainly because the alternative existed first and was genuinely dangerous. Before this module, a message containing the word label was routed to the processing intent parser, which mapped anything mentioning labels to a full accept, label and manifest run across a whole account.
So a seller asking for one PDF they already owned was being offered a marketplace mutation on everything pending. That is not a hypothetical risk, it is the documented history of this surface, and it is why the label path now sits above the processing path and refuses every minting phrase before it reads anything else.
What it is allowed to do is deliberately narrow: serve a label already in Robnu's storage, or call the re-download path for orders that are already ready to ship or already labelled. It accepts nothing. There is no path from here to a new label.
The practical consequence for you is that this is the safe thing to hand to a packer. The worst outcome of a mistyped order number is that Robnu cannot find it.
What comes back, and why it matches your printer
The PDF is rendered with your own label settings rather than a generic default. If you have set a label size, trimmed the invoice section, or configured what prints alongside the barcode, the chat copy carries all of it.
That is on purpose, and it is the difference between a feature that gets used and one that gets abandoned. A label that comes back in a different shape from the ones already on the bench means re-cutting, re-sticking, or a mismatch a courier can reject. The chat is a different door to the same file, not a different file.
If Robnu does not hold the label, it tells you that rather than quietly making one. That is the correct answer, and the next step is usually a processing run, which is a separate, deliberate action with its own confirmation.
A day at the bench
One batch in the morning, and every exception answered without finding a laptop
Where this fits in a packing day
The common pattern is a batch mint in the morning from the app or from the chat, then this path for the exceptions all day: the one that did not print, the one whose label tore, the one a courier handed back.
It also covers the case where the person packing is not the person who processes. Fetching a label needs no special permission, so a warehouse phone can pull labels all day without being able to start a run. The permission split is the point: the ability to reprint is not the ability to mint.
For handover, the same chat gives you the courier OTPs, so the bench can finish a pickup without leaving WhatsApp.
The part of this Robnu does for you
Robnu reads your Amazon account and reconciles every settlement line back to the order that caused it, so a wrong deduction is visible the day it lands.
- Orders, returns, payouts and inventory synced
- Every settlement line matched to its order
- FBA units Amazon has not made good, listed
Where this sits in the rest of your Amazon operation
On Amazon, Robnu syncs your orders, returns, payouts and inventory, reconciles every settlement line back to the order that caused it, lists the FBA units Amazon's own ledger has not made good, flags a return that never came back before the SAFE-T window closes, and scans returns in at your dock. It reads your Amazon account rather than writing to it, so accepting orders and making labels run on AJIO and Meesho today. Related reading:
Sources & further reading
- Robnu, the product the behaviour described here is the product's own. The WhatsApp surface calls the same endpoints the screens do, with the same permissions, so anything you can check on a screen is the same fact. Read 2 November 2026.
- Meta, WhatsApp Business Platform onboarding Meta's own page. It states that the 24 hour customer service window applies to messages sent through the Cloud API, and that a window opens when a person messages a business already onboarded to it. That rule is why a reply can arrive as a template rather than as free text. Read 2 November 2026.
Not legal or tax advice. Amazon changes fees, windows and policies without notice, and the detailed style guides and account-health thresholds sit behind a Seller Central login, so any figure quoted here as convention is not Amazon-published. Check anything you plan to act on against your own Seller Central account first.
Questions sellers ask
An order number, a sub-order number, an AWB, or a time window phrase such as labels from this morning or yesterday's labels. Sub-orders matter on Meesho where one order can carry several parcels. You can send any of them as a voice note instead of typing.
No. This path only serves a label that already exists, or calls the re-download route for orders that are already ready to ship or already labelled. It refuses minting phrases before it reads anything else, and there is no path from it to an accept or a manifest. If Robnu does not hold the label it says so rather than making one.
Yes. It is rendered with your own label settings, the same ones the web download uses, so size and layout match what is already on your bench. A chat label arriving in a different shape would mean re-cutting or a courier rejection, so it is the same file through a different door.
Yes, and it is the usual arrangement. Fetching a label needs no special permission while starting a run needs orders:process, so a warehouse phone can reprint all day and still cannot mint. The ability to reprint is deliberately not the ability to accept.
Yes, with a time window. Asking for this morning's labels or today's labels returns the batch rather than making you send numbers one at a time, which is the fastest fix when a printer jams partway through a run.
It tells you plainly. That usually means the order has not been through a processing run, so the next step is to process, which is a separate action with its own confirmation sequence. The label path will not start that for you.
Related seller guides
More on the operations, money and claims that decide whether a marketplace catalogue actually makes money.
Receive Returns By Sending Codes In A WhatsApp Chat
Say return scan, then send AWB after AWB as the parcels come off the van. Each one is marked received the moment it lands, and shows up everywhere a scan from the web dock does, reports included.
How to Download the Meesho Shipping Label (2026)
How to download the Meesho shipping label from the Supplier Panel, for one order or in bulk. Where it lives, the print settings that stop rejected parcels, what the label contains, and common problems.
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 label not downloading? Every cause & fix
The 7 real reasons a Meesho shipping label won't generate or download, order state, AWB assignment, browser blocks, sale-day queues, each with its fix, and what a stuck label costs in SLA penalties.
Process Your Marketplace Orders From A WhatsApp Chat
Say process my orders in a WhatsApp chat, pick the account, confirm, and Robnu runs the real accept, label and manifest pipeline. Four gates stand between a tap and a live run, and the assistant is not one of them.
Capture A Claim On WhatsApp, With Photos And Video
Say start claim, describe what happened in any language, and send the AWB photo, the barcode, a photo of what you received and the opening video. Robnu reads each photo and tells you what it read. The draft is finished and submitted from the app.
What A WhatsApp Chat Can And Cannot Change In Your Shop
Running a shop from a chat is only sensible if a chat cannot do something you did not intend. Here is the whole safety model: who the sender must be, which permission each action needs, and why the assistant cannot act at all.
Someone else created the ASIN for your product
Finding your product already has a page another seller built is normal and usually workable. What you can change, what you cannot, and when a new ASIN is the right answer.