Walmart minimum four images per listing: a four-shot batch per SKU

Walmart's image guide tells sellers to upload a minimum of four images for each listing (read 2026-10-02). If you have one photo per SKU, a four-shot batch fills the gap: a main image on seamless white, plus three more views, each made from your real product photo as a reference.

What Walmart's page requires

From the image guidelines (read 2026-10-02). The page also bars watermarks, seller logos, promotional text and accessories that are not included.

A four-shot plan

Pick four jobs that add information, not four crops of one angle.

• Shot 1: main image, product alone on seamless white.
• Shot 2: a second angle, same product, same white.
• Shot 3: a close-up of the material or the part buyers ask about.
• Shot 4: the product in use, with only what ships in the box.

Run it on Sume

Send your own photo as a reference in input_references (public HTTPS URLs only) and ask for an edit that keeps the product identical. The Image API takes n to request several images per call, but the per-model ceiling is lower than the general limit, so read the n range in the catalogue first (Image API). One job per shot is easier to retry and to audit.

On edit calls the docs recommend aspect_ratio: "auto" to match the reference, and note that omitting the field is not the same as auto. For a square Walmart main image, set the ratio explicitly instead.

Counting the cost

Four shots per SKU is four jobs per SKU, so a 500-SKU catalogue is 2,000 jobs. Price one shot first from the catalogue's pricing lines (Image API), multiply, and set a spend cap before you launch the batch. Start with a handful of SKUs, review every output, and only then scale up.

Review before you submit

A model can change a logo, a port or a stitch. Compare each output with the real product and drop any shot that shows something the buyer will not get. Sume generates the files; it does not check Walmart's rules for you, and the docs describe no Walmart integration.