The WhatsApp OMS for Indian marketplace sellers
A WhatsApp OMS is an order management system you run from a chat rather than a dashboard. Robnu accepts orders, mints and re-sends labels, receives returns, captures claims with photos and prepares GST documents, all from the WhatsApp you already have open, and every action is the same one the screens perform.
- It is the real system, not notifications. Processing from the chat calls the same run the Orders page calls, and writes the same records.
- Orders, labels, returns, claims, GST documents and plain questions, in English, Hindi or Gujarati, typed or spoken.
- Anything that changes something needs the user's own permission and a confirmation. The assistant that answers questions has no permissions at all.
Process orders without opening a laptop
Say process my orders, pick the account, confirm. The same accept, label and manifest run the Orders page starts, enqueued by the same function.
- Four gates before anything runs, and none of them is the model
- Needs the orders:process permission, read from the user's real role
- Refuses past the pickup cutoff instead of asking you to decide blind
A label back in one message
An order number, a sub-order, an AWB, or labels from this morning. The PDF arrives rendered to your own label settings, so it prints like the ones already on the bench.
- Re-sends a label you already own, never mints a new one
- Time windows reprint a whole batch when a printer jams
- Needs no special permission, so a packer can use it
Receive returns as they come off
Say return scan, then send code after code. Bag barcode, order number, sub-order or AWB all resolve, and a return received here is indistinguishable downstream from one scanned at the dock.
- Any code printed on the label works
- A double scan says already received rather than erroring
- Nothing is sent to a marketplace, it records your own bench
Capture a claim with photos and video
Describe what happened in any language, send the four pieces of evidence in any order, and Robnu answers each photo with what it actually read from it.
- An unreadable barcode is caught while you can still retake it
- Robnu identifies the parcel from the codes and shows you the product
- Capture only: a person submits the draft from the app
GST documents, prepared and emailed
Ask for a month and an account. Robnu prepares the documents and offers to send them to your accountant, using the same send the Tax documents page uses.
- The remembered accountant is one tap
- A typed address is confirmed once before anything is sent
- Same rules as the web, so nothing can drift
Ask in your own words
Order counts, handover OTPs, why a deduction was taken, what a payout covered. The same read-only assistant the app uses, answering from your live data.
- English, Hindi or Gujarati, typed or spoken
- Read-only by construction, with an empty permission set
- Says so when it is unsure rather than guessing
What a WhatsApp OMS is
An order management system holds the life of an order: accept it, label it, manifest it, ship it, take the return, get paid. A WhatsApp OMS is one you operate from a chat instead of a dashboard, so the work happens on the device already in the room rather than on the laptop in the office.
The distinction worth drawing is between a chat that notifies and a chat that operates. Plenty of tools will message you that an order arrived. Robnu runs the order from the message: the same accept, label and manifest pipeline the Orders page runs, enqueued by the same function, appearing in the same job history.
That is what makes it an OMS rather than an alerting channel. Nothing in the result is WhatsApp-specific, and nothing downstream can tell which door the work came through.
Why a chat is the right surface for marketplace operations
Marketplace work in India happens away from a desk. The parcels are at the door, the van is waiting, the person holding the label is not the person who signs in to the dashboard, and the fastest device in the room is a phone that already has WhatsApp open.
Every expensive mistake in this business has the same shape: a thing that should have been recorded at the moment it happened, recorded later or not at all. A return that came back and was never marked received. A claim whose barcode photo was taken a week after the parcel went out again. A label nobody reprinted until the courier had left.
A chat closes that gap because it is where the person already is. Robnu's WhatsApp surface exists for the moment of the work, not for a report about it afterwards.
What you can actually do from the chat
Process orders. Say process my orders, pick the account, confirm, and a real run starts: accept, labels, manifest. It needs the orders:process permission and a four step confirmation.
Get a label back. Send an order number, a sub-order number, an AWB, or a phrase like labels from this morning, and the PDF arrives rendered to your own label settings. This path only re-sends a label you already own.
Receive returns. Say return scan and then send code after code as the parcels come off the van. Each is marked received, identically to a scan at the dock.
Capture a claim. Say start claim, describe what happened, and send the AWB photo, the barcode, a photo of what arrived and the opening video. Robnu reads each photo and tells you what it read, so an unusable photo is caught while the parcel is still in your hand.
Prepare GST documents. Ask for a month and an account and Robnu prepares them and offers to email your accountant, using the same send the Tax documents page uses.
Ask anything else. Order counts, handover OTPs, why a deduction was taken, what a payout covered: those are questions, and they are answered from your live data.
In your own language, and by voice
Robnu reads English, Hindi and Gujarati, including Hindi and Gujarati typed in Roman letters, which is how most people actually type on a phone.
You can also just talk. A voice note is turned into text and handed to exactly the same router a typed message goes through, so a spoken request walks the identical confirmation steps and nothing extra can happen because you spoke. Typing Gujarati on a phone is slow enough that people do not do it, so holding the button and talking is the realistic path for a lot of sellers.
Safe enough to hand to the warehouse
A chat is forwardable and easy to mistype, and a marketplace is not forgiving. So the actions are behind the same permissions the web uses, read from the same source, plus a confirmation sequence of taps on messages sent seconds earlier.
Reading needs no permission, which is what makes a shared warehouse phone useful: it can ask for counts, OTPs and labels all day and still be unable to start a run, because the person holding it does not have orders:process. You change that through their role, not through a WhatsApp setting.
The assistant that answers questions runs with an empty permission set and is not in any action path. That separation is deliberate: a system that can both converse and act will eventually act on something it misread, and the cost of that on a marketplace is real orders.
AJIO and Meesho live today. The rest in honest order.
One agentic OMS, built marketplace-agnostic, so the same operating model lights up each new marketplace as we ship it. Every coming-soon page has a real waitlist.
An order management system you operate from a WhatsApp chat rather than a dashboard. The useful distinction is between a chat that notifies you and one that does the work: Robnu's chat starts the same accept, label and manifest run the Orders page starts, and the result is the same records in the same places.
Real processing. The chat calls the same enqueue the Process button calls, so it accepts pending orders, mints labels and closes the manifest, and the run appears in your Jobs list like any other. Nothing about the result is WhatsApp-specific.
Order processing runs on Meesho and AJIO today. Robnu also reads Amazon, and reconciliation, returns and reporting cover the marketplaces your account is connected to. The chat is a surface over whatever your account already does, so it gains a marketplace when the account does.
Yes, and it is the usual setup. Reading needs no permission while acting does, so a warehouse phone on a role without orders:process can ask for order counts, handover OTPs and label reprints all day and still be unable to start a run.
No. The assistant runs with an empty permission set and is not in any action path. Actions are reached by short exact phrases that go to ordinary code, and every branch of those flows is code, so there is no step where a model decides what you meant.
Yes, both, including when typed in Roman letters. You can also send a voice note instead of typing, which is turned into text and handed to the same router, so speaking changes nothing about what can happen.
That is WhatsApp's rule rather than Robnu's. A business may send free-form replies only within 24 hours of your last message to it, and outside that window only pre-approved templates. Send any message and the window reopens, and replies go back to normal.
You sell. Robnu runs the rest.
Live for AJIO, Meesho, and Amazon.in. Free during early access, no card, no caps. Forever free under 25 orders/day.