Preparing images for five products is a photography task. Preparing images for five hundred is an operations task. The problems change completely: it is no longer about one perfect photo, but about keeping track of which image belongs to which SKU, making the whole catalogue look consistent, and getting files into the right format for every marketplace without errors.
This guide covers a workflow that holds up at scale, built around a simple spreadsheet.
Why bulk catalogues go wrong
Most bulk catalogue problems are not about image quality. They are about organisation.
- Mismatched images. The blue kurta's photo ends up on the green kurta's listing.
- Inconsistent look. Half the catalogue is on white, half on grey, shot in different light on different days.
- Missing files. Some SKUs have five images, some have one, and no one notices until listing day.
- Wrong sizes. Images that are fine for one marketplace are rejected by another.
- Re-work. One mistake means finding and fixing images across hundreds of rows.
A spreadsheet-first workflow solves most of these before they happen.
Step 1: Build the master spreadsheet
Start with one row per SKU. The spreadsheet becomes the single source of truth for both your images and your listings.
| Column | Example | Why it matters |
|---|---|---|
| SKU | KRT-0142-BLU-M | Unique key that links image to listing |
| Product name | Cotton straight kurta | Helps reviewers spot mismatches |
| Category | Apparel | Decides which style and rules apply |
| Colour / variant | Blue | Prevents colourway mix-ups |
| Image 1 (front) | Link or file name | Main image source |
| Image 2 (back) | Link or file name | Supporting views |
| Image 3 (detail) | Link or file name | Close-ups |
| Status | Ready / Needs reshoot | Tracks progress |
Put the SKU in the file name of every photo. "KRT-0142-BLU-front.jpg" can never get lost or mixed up the way "IMG_4532.jpg" can.
Use the marketplace's own template where you can
Each marketplace has its own listing template with required fields and allowed values. If you are going to upload through a flat file, build your spreadsheet around that template from the start, rather than copying data across later.
Step 2: Shoot in batches with a fixed setup
The secret to a consistent catalogue is not editing. It is a fixed setup.
- Fix the spot. Same table, same window, same backdrop every time.
- Fix the phone position. Mark the floor or use a stand at a set height.
- Fix the time. Daylight changes through the day. Shoot at the same hours.
- Shoot by category. All kurtas, then all dupattas, then all bottoms. Fewer setup changes, fewer mistakes.
- Shoot the same views for every SKU. Decide your shot list once and stick to it.
Size matters at scale
Small source photos are the most common silent problem in bulk work. If a photo is too small, enlarging it for a 2000 px marketplace canvas produces a soft image that QC may reject as blurry. Use your phone's full-resolution photos and avoid images forwarded through chat apps.
Step 3: Decide the look once
Before generating or editing anything, decide the look for the whole batch:
- One background style per marketplace
- One model and a small set of poses for apparel
- One framing and crop rule
Writing these decisions down stops the catalogue from drifting as different people work on it over different days.
Step 4: Produce marketplace-specific versions
The same product often needs different images for each marketplace. This is where bulk work multiplies fast.
| Marketplace | Shape | Size we target | Background |
|---|---|---|---|
| Amazon | 1:1 | 2000 x 2000 px | Pure white main image |
| Flipkart | 1:1 | 2000 x 2000 px | Pure white main image |
| Meesho | 1:1 | 1000 x 1000 px | White, neutral or clean lifestyle |
| Myntra | 3:4 | 1080 x 1440 px | Clean studio, on-model |
File rules differ too: Flipkart and Myntra expect JPEG, Meesho caps files at 5 MB, Amazon and Flipkart at 10 MB. For the detailed rules, see our Meesho product photo guide and Flipkart image checklist.
Track versions, not just files
When you redo an image, keep the SKU in the new file name and update the status column, so nobody uploads the old version by mistake. A simple suffix such as "-v2" is enough. At the end of a batch, the spreadsheet should tell you exactly which file is final for every SKU and every marketplace, without anyone having to open a folder and guess.
Step 5: Review before you upload
Never upload a bulk batch unchecked. A quick review pass catches most problems:
- Spot-check one image in every ten against the physical product
- Sort by SKU and scroll through, looking for the odd one out in colour or framing
- Check every SKU has its full set of images
- Confirm sizes and file types match the target marketplace
- Mark the status column as you go
Fixing ten images before upload takes minutes. Fixing ten rejected listings after upload can take days.
How VisionLab helps
VisionLab's Bulk Studio is built for catalogue-scale work. Pick a category and a look once, then upload a spreadsheet of product images or a batch of photos. Every product is shot with the same model, pose and background, so the catalogue looks consistent, and you can download the full set at once. When you export listing images for a marketplace, VisionLab fits them to that marketplace's canvas and file rules, and flags source photos too small to export sharply before they cause a rejection.
New accounts get 5 free credits to start, no card needed. Start free and shoot your whole catalogue in one go.
Frequently asked questions
How do I organise images for hundreds of SKUs?
Use one spreadsheet row per SKU with columns for variant, category and each image. Put the SKU in every image file name so images can never be mixed up.
How do I keep a bulk catalogue looking consistent?
Fix your setup: same spot, phone position, light and shot list for every product. If you generate images, apply the same model, pose and background across the batch.
Do I need different images for each marketplace?
Often, yes. Amazon and Flipkart want square images on pure white, Meesho allows clean lifestyle backgrounds, and Myntra uses 3:4 portrait on-model shots.
Why do some bulk images get rejected as blurry?
Usually the source photo was too small and was enlarged to fit the marketplace size. Use full-resolution phone photos and avoid images forwarded through chat apps.



