A Meesho catalogue rejection is one of four things: the image is judged unfit, the image is judged not yours, the image carries more than the piece, or the photograph was never the problem. The reason string names the family and stops there.
That string sits in the supplier panel beside the catalogue, and on a bulk upload in the error file’s error message column, one line per row. Read yours before changing anything. The rest of getting listed and staying listed turns on which of the four you are in.
Most jewellery rejections land in the first family, so the fastest thing to do this afternoon is run the photo through the checks the platform itself runs.
Every platform behaviour below was read in the supplier panel in August 2026, and Meesho rewords its reason strings without notice, so treat the wording here as the family and your own panel as the authority.
Meesho catalogue reject ho gaya kyu?
Find your string in the left column below. Four families cover almost every jewellery rejection, and they fail at different stages of the same check.
| Reason string, as it recurs | Family | What the check is reading |
|---|---|---|
| “Image not clear”, “poor image quality” | The image is unfit | Sharpness, the resolution of the file uploaded, and the surface behind the piece |
| “Duplicate image” | The image is not yours | Whether this file, or one close to it, already sits on another catalogue |
| “Text or watermark on image”, “logo on image” | The image carries more than the piece | Anything drawn onto the main image that is not the product |
| “Wrong category”, “mandatory field missing”, price and HSN errors | The photograph was never the problem | Whether your fields agree with your title, and with the category you filed under |
Where the string fits none of the four cleanly, look at which rows carry it. Every row failing the same way is almost always a field or a category problem. A fault on a few rows out of a whole catalogue is almost always those few photographs.
What does “image not clear” mean when the photo looks sharp?
“Image not clear” is read off the uploaded file, not off the photograph you took, and the three commonest causes happen after the shutter.
Blowing the file up is one of them. A 600 px crop pushed up to a 1500 px square holds no more detail than the crop did, so the softness is real even though your original was sharp. Start from the largest file the phone saved.
Next is the round trip. A photo sent on WhatsApp, saved from the chat, sent on again and then uploaded is re-compressed at every hop, and the blocking around a thin chain reads as unclear. A screenshot of a photo is worse still.
Last comes the ground. Shot on a printed dupatta, a dark tray or a wood-grain counter, a piece gives the check no clean edge to find. Lifting that surface is what the Background Whitener is for, and it says honestly when a background is too busy to lift at all.
No tool anywhere can put back detail a photograph never held, which is why re-shooting the piece on white paper near a window takes minutes, beats every fix on this page, and is the only one that also improves the listing after it goes live.
Why does Meesho call my own photo a duplicate image?
You bought the lot, the wholesaler sent a folder of catalogue photographs, and every other seller who bought that lot was sent the same folder. The first catalogue up owns those files as far as the check is concerned, and every one after it reads as a duplicate. In jewellery that reseller case is usually the one.
The flag itself reports a match against an image already sitting somewhere on the platform, and carries no accusation of copying.
The other case is your own doing. You photograph one jhumka, then list it in two catalogues — a colour variant, a second size, a relist after a block — and the same file goes up twice. Give each catalogue its own frames, even of the same piece.
Shoot the piece yourself; that is the one fix that holds. Re-cropping, mirroring or brightening a supplier file is an attempt to fool the matcher, and it stops working the day the matcher gets better. Your own frames also end the more expensive version of this: where many listings carry one image, a buyer has nothing to choose between them except price.
What counts as text, a logo or a border on the main image?
Sellers usually know a shop name across the corner counts. The rest of the list is where people get caught: a size chart panel beside the piece, a “bestseller” or “free delivery” badge, a coloured or gold frame drawn around the square, two angles collaged into one file. A price sticker still tied to the piece and legible in the shot counts, and so does the shop handle sitting on a model’s photograph.
The main image seat on Meesho, Amazon and Flipkart wants the piece on a ground of RGB 255,255,255 and nothing else in the frame, and all three block the same additions.
A marked image gets the catalogue blocked, without a penalty attached, and the same photograph passes once the marking comes off it, with no re-shoot at all.
The marked copy still has a job: WhatsApp, Instagram, the folder you send resellers. The Bulk Watermark Adder is where it gets made; only the main image seat has to stay clean.
Why is a listing rejected when the photographs passed?
A title reading “gold jhumka” with the base metal field set to brass is a contradiction the panel sees without opening a photograph, and so is a title reading “silver” on a piece whose material field says alloy. Title, bullets and attribute fields have to say one thing.
That is the fourth family, read entirely off your own fields, and its jewellery version is a purity word in the title that the base-metal field contradicts.
Wording plated stock so it is honest and still sells is a job on its own.
Putting the same purity language into the title and the bullets in one pass is what the Description & Caption Writer is for, including when 916 or BIS hallmarked may be written at all.
Category is the other half of this family. A piece filed under a category whose mandatory fields do not include plating cannot be described correctly there, so the catalogue keeps failing on a field you cannot fill. Move the piece before editing the row again.
Can a catalogue be rejected on the price?
The price can fight itself: a selling price and an MRP that make no sense against each other, or a price typed into the wrong column of a bulk sheet. In the tax field, a missing or wrong HSN code stops a row on its own.
Price and quality flags are the family sellers argue with hardest, because none of them has anything to do with the photographs.
Then there is the category band. Meesho publishes no price floor for jewellery, and no figure on any blog is one. The panel reads your price against the category the piece is filed in, so a piece in the wrong category can be rejected on a price that would have passed in the right one. That is the field problem above again.
Quality flags arrive later and behave differently. An approved catalogue can be blocked weeks afterwards on return behaviour, or on complaints that the piece delivered was not the piece shown. Those are answered with evidence, and no amount of resubmitting reaches them.
In what order should I fix a rejected catalogue?
Fix in the order of what is cheapest to change and most often blamed on the wrong thing, which means the fields come before the photographs every time.
- Read the string and write it down; on a bulk upload that means the error file’s error message column, worked row by row.
- Correct the fields first: category, base metal, plating, purity, weight, HSN, price. They cost nothing to change and are the family most often mistaken for an image fault.
- Then fix the image once, in a single pass: ground, square, fill, file size. Changing one thing per resubmission is how a two-day fix becomes a two-week one.
- Replace rather than re-upload anything flagged as a duplicate. The same file is matched the same way.
- Resubmit once, and wait for the decision before touching the catalogue again.
Meesho publishes no resubmission limit, though every blind pass costs position in the queue, rejoining it at the end, and before a festival those days are the whole margin.
What do I do to the photo before I upload it again?
One pass, four steps: start from the largest original the phone saved, lift the ground to white, square the frame and check the fill, and check the file size last. Compressing before resizing throws away the quality you just paid for.
The square, the pixel dimensions for Meesho, Amazon and Flipkart, and the fill check are read together by the resizer. File size is a separate failure that comes back in the same words. Bringing a photo under Meesho’s 2 MB cap without visibly losing the shine is answered on the Image Compressor.
Then upload a single catalogue. If it clears, the same four steps carry the rest of the shoot; if it comes back, there is one reason string to read.