LabelCropper
← All articles

What LabelCropper does for each marketplace

Four marketplaces, four different downloads, four different jobs. This page says what each one gives you, what LabelCropper does to it, and what you end up holding — in plain words, with no cropping jargon.

Meesho

Open the Meesho label cropper →

What you drop: the A4 label sheet from the Supplier Panel. As many files as you have.

What it does: a Meesho sheet uses its top half and wastes the rest. It cuts off the disclaimer and the blank bottom, and keeps the invoice Total row, because that is the bit you may need later.

What you get: the label with its total, and the SKU, size, quantity and print time in large type underneath. The stack is grouped by courier — Valmo, Delhivery, Shadowfax, Xpress Bees — then by size inside each courier.

How that helps: one sheet of paper becomes about half a sheet, and the pile comes off the printer already in the order the courier bags want it. You stop sorting by hand and stop reading SKUs out of a small table.

Flipkart

Open the Flipkart label cropper →

What you drop: the E-Kart sheet from Seller Hub.

What it does: a Flipkart label is narrow as well as short, so the cut runs sideways too, down to the label box itself. The whole invoice below goes, because there is no summary on it worth keeping.

What you get: just the label box — roughly 85% of the sheet removed — with the SKU and size beneath it. Flipkart ships through one carrier, so the stack is grouped by the seller account each label ships as, then by SKU.

How that helps: the saving is the biggest of the four, and if you sell through more than one registered business the accounts stop interleaving on the bench.

Snapdeal

Open the Snapdeal label cropper →

What you drop: the landscape sheet that prints the label beside the invoice rather than above it.

What it does: the cut runs down the page instead of across it. Everything to the right of the label is invoice, and that is what goes. Nothing at all is taken off the label — the seller address, the Snapdeal reference barcode and the notices at the foot all stay on it.

What you get: the whole label, with the SKU, size, quantity and print time underneath, grouped by courier. The caption is read off the invoice half rather than the label, because the label prints its own copy of the SKU with the hyphens stripped and the size run onto the end.

How that helps: you keep a complete, returnable label and lose only the invoice beside it. Parcels that ship on an Amazon Shipping label — where the whole label is one image with no text on it — are handled as well.

AJIO

Open the AJIO label match tool →

What you drop: two files, together — the 4 × 6 labels, and the A4 invoices.

What it does: nothing is cropped here, because an AJIO label is already exactly label-sized. The job is matching. Both documents carry the same AWB number: the invoice prints it as text, the label only under a barcode. LabelCropper reads that barcode and joins each label to the invoice bearing the same number.

What you get: each label followed immediately by its own invoice, so you work down the stack once — label on the parcel, invoice inside. The SKU and quantity are lifted off the invoice and printed on the label, which is the only way they can be read from a stack at all. The pile is grouped by courier and then by that courier’s routing code.

How that helps: matching two files by hand is the slowest job on the bench and the easiest to get wrong — and putting the wrong invoice in a parcel sends one customer’s name and address to another. A label that matches nothing is reported and left unpaired rather than paired with a guess.

What is the same for all four

A page that does not match its marketplace is never cut to the wrong shape. It comes through whole and is flagged, so you can look at it before anything is packed. Blank filler pages are dropped. Nothing is uploaded — every file is read inside the browser tab, so customer names and addresses never leave the machine you opened them on. And every export is stamped with its date and time, so a reprint is never confused with the original stack.

Keep reading