Check a Buyer's History by Suborder ID
One parcel in a batch always looks doubtful. The useful question is not whether the order feels risky, it is what this same person did the last four times you shipped to them — and you already own that answer.
The lookup lives in the workspace Premium panel, so it opens once your wallet has coins. It costs nothing per lookup — the 1 coin per label charge applies to the crop, and only when a premium option is switched on.
One ID in, a whole buyer out
- 1Paste the suborder ID into "See user history by Suborder ID" in the workspace Premium panel.
- 2That seed order is located in your own label data and the buyer behind it is identified.
- 3Every other order that buyer placed with you opens as one table, with the seed order kept at the top.
The buyer is matched, not just the order number
Identity is name plus address line 1 plus pincode, normalised — not the order ID and not the name alone. A tolerant second pass forgives the small OCR differences a scanned label produces in a name or a street line, but the pincode has to be equal either way. So the same repeat buyer still lands in one history when the spelling wobbles between orders, and a different household in the same pincode never gets folded in.
What the table gives you
- ›Total purchases, RTO count and customer-return count for that buyer, across the top.
- ›One row per order: order ID, print date, SKU, quantity, size and colour on Meesho, order status, Sold by and payment mode. Order ID, print date, SKU, quantity, order status and Sold by can each be sorted on.
- ›Order status comes from the payment or settlement sheet you imported — Delivered, Shipped, Cancelled, Customer Return or RTO. An order with nothing imported yet says so instead of guessing.
- ›Meesho and Flipkart never mix. A lookup stays on the platform its suborder came from, even when the same person bought on both.
Bounded to your own account
Only your records are scanned. A buyer ordering from you for the first time has no history here and a suborder ID that is not in your label data comes back as not found, rather than showing you somebody else's customer. That also sets the limit honestly: what the page knows is what you have cropped and settled.