Amazon / Marketplace Sellers: Batch Listing Images on a Local Shelf

Amazon / marketplace sellers: batch listing images on a local shelf when the job is nine SKUs × seven images, not one hero photo in Shopify admin. The single-SKU storefront loop lives in clipboard shelf for ecommerce. This post is the batch lane: SKU-role filenames, stacks, FBA/A+ exceptions, and file drop into whatever uploader Seller Central (or another marketplace) is showing this week. UI chrome is not documented here because it changes.

Win+V will not do this. History is 25 text / HTML / bitmap items, 4 MB. Explorer JPEGs are files — Windows clipboard history does not store files. Unpinned history clears on restart.

Microsoft’s browser Drop (OneDrive) is gone as of Edge 152 (27 August 2026). Do not put a catalog ZIP into a random clone unless you intend to run a share server. Leave Windows clipboard sync off. Listing images and MAP notes are not the text that toggle is for.

Amazon / marketplace sellers: batch listing images on a local shelf

Marketplace dimension and color-space rules belong in current seller help, not in a blog from memory. Amazon Seller Central — product image requirements (G1881) is the living MAIN/file page; it changes, so read it.

Numbered FBA / Seller Central batch loop

1. On disk first. A folder per batch: amazon\2026-10-21-run\. Files named with SKU and role, for example SKU1044-MAIN.jpg, SKU1044-PT01.jpg. Inventory feeds stay in the feed tool. They are not clipboard work.
2. Do not dump a photographer WeTransfer ZIP onto the shelf. Extract to the batch folder, pick the SKUs for this upload window, stage those files. If the ZIP is the only copy, duplicate it to your catalog disk first. A shelf card is not a backup of 400 images.
3. One SKU visible on the shelf at a time. Drag that SKU’s images onto a local hover shelf as files. If the shelf supports stacks (Edge Drop stacks cap at 10), stack MAIN+PT01+… so they travel together. Pin the SKU string as text. Do not also stack SKU1045 — that is how MAIN images swap. Variant listings fail when MAIN for size S is still on the shelf while you upload size M.
4. Drop into the uploader as files. Prefer the bulk image upload / spreadsheet+images flow your account already uses. A shelf is for the exceptions: the SKU the bulk job rejected, the image you just recropped, the infographic the other marketplace wants. Drag from the shelf into the drop zone. Bitmap paste is how you get a nameless blob that fails zoom. Payloads: copying files vs copying file contents.
5. Rejected images: recrop from the disk master, save a new file, stage that. Do not restage a compressed CDN copy you downloaded from the live listing as the new master. ShareX or a photo tool for recrops; save file; stage file. ShareX pairing.
6. A+ / Brand Registry: export derivatives to disk at the module’s current aspect. Stage the set as a stack, drop in the order the module shows, then wipe. Do not screenshot the A+ preview and upload the screenshot. Do not keep last season’s A+ stack pinned through a rebrand.
7. Wipe that SKU and load the next. Pins for the store’s boilerplate alt-text pattern can stay if they contain no supplier costs. After the batch, empty the shelf even if you will list again tomorrow. Yesterday’s MAIN is how the wrong hero ships on SKU 1045. Multiple marketplaces (Amazon + eBay + a Shopify channel): still one SKU on the shelf; change the export preset on disk, not by pasting the Amazon MAIN into eBay as a bitmap.

edgedrop.app is Apache-2.0, Windows 10/11, hover or Alt+C, OLE drag, local. It is not Seller Central. It is not a DAM for a team of catalogers — when several people own the same SKUs, use the shop’s asset library and let the operator stage only this hour’s rejects. Staging without living in Explorer: how to stage files between apps.

When Edge Drop fits / does not

Fits. Bulk upload handled most of the run. You still hop reject recrops, a stubborn ASIN form, or an A+ set into a drop zone. You name files with SKU and role. You show one SKU on the shelf at a time. Sync is off. Masters stay on disk.

Does not. You already have a working bulk image upload and filenames match — stay in Explorer + the uploader. You needed the Shopify/Etsy one-SKU admin loop — that is post 530. You needed OCR/AI to write bullets from a photo — that is a different (and leaky) app class: 2026 clipboard apps. You needed FBA carton labels, shipment IDs, and inbound feeds on a clipboard. You needed vendor/wholesale cost screenshots next to MAIN images. You needed a DAM.

If bulk upload handled most of the catalog and you still hop reject images into a stubborn form, a local file shelf is the remaining exception lane. edgedrop.app is free on Windows 10/11. Keep masters on disk. Keep the shelf empty between runs.

Batch mistakes that are not the same as post 530

• Bulk spreadsheet column vs image file. The sheet has the SKU; the shelf has the pixels. Keep them paired with filenames, not with “I remember which JPEG is MAIN.”
• SWATCH / color-chip images mix easily with lifestyle shots. Filename prefixes beat memory. If the shelf shows thumbnails, glance at the chip before you drop.
• Infographics with text claims (grams, certifications) are listing-copy problems. Stage the file; do not invent the claims on a text card unless they already live in your approved copy doc.
• FBA inbound is a feed and a warehouse process. Do not stage packing slips with addresses next to MAIN images. Different hour, or pause the watcher.
• Vendor / wholesale cost screenshots do not belong next to MAIN images.

Say the SKU out loud (or keep it pinned as the first card) before you drop. For per-ASIN forms, one variant at a time.

Photographer drops, CDN copies, and MAP notes

Download the current live MAIN from the marketplace only if you need to compare. Do not restage that CDN file as the master.

Images that live only in a photographer’s cloud gallery you do not own: download once to disk, then batch. The shelf is a handful of JPEGs, not the archive.

MAP notes and supplier costs: pause the watcher. Those are not alt-text.

Soft CTA

If bulk upload handled most of the run and you still hop reject images into a stubborn form, a local file shelf is the remaining exception lane. edgedrop.app is free on Windows 10/11. Keep masters on disk. Keep the shelf empty between runs. For one SKU in Shopify admin, use the ecommerce post.

FAQ

Can I copy all 200 JPEGs into Win+V and paste them into Seller Central? No. History does not store those files, and 25 bitmap slots would not be a catalog. History is text, HTML, and bitmap at 4 MB each.

Is this a replacement for Amazon’s bulk image tools? No. It stages exceptions and recrops beside the form. Prefer the bulk image upload your account already uses when filenames match.

Should listing images go through clipboard sync to a phone? No. Use the marketplace’s mobile app or a deliberate file send. Sync is optional Microsoft text, not a catalog pipe.

Is this the same as the Shopify one-SKU shelf workflow? No. That post is one product in a storefront admin. This post is batch ASINs, role-named files, A+ sets, and reject recrops.

Related reading

• Clipboard Shelf for Ecommerce: Stage Product Photos Before Shopify or Amazon
• Windows Clipboard History Does Not Store Files
• Files vs File Contents
• How to Stage Files Between Apps Without Living in Explorer

Sources

• Windows clipboard history
• Amazon Seller Central — product image requirements (G1881) — current MAIN/file rules; they change, so read the live page
• Using the clipboard (Microsoft Support)
• Microsoft Edge 152 Stable notes
• Edge-Drop GitHub
• edgedrop.app

Copy. Stack. Drop.

Transform your clipboard into an interactive edge shelf. Stack, pin, and drag assets into any app with zero friction.

Download for Windows Get from Microsoft Store

How to Install Guide · First 10 Minutes Guide · Drag & Drop Guide · Edge-Drop vs Win+V · Support