Walmart bans seller logos, Coupang wants yours: one prompt per site
Walmart's image guide bars seller logos; Coupang's main-image page says to show yours clearly. Keep a separate prompt per marketplace in a Sume batch.

Walmart's image guide says images must not contain watermarks, seller logos or promotional text, while Coupang's main-image page says to feature your logo clearly (both read 2026-10-02). One shared main image will break one of the two, so keep a prompt and a shot list per marketplace and generate them as separate jobs.
The two pages side by side
Quotes are from Walmart's image guidelines and Coupang's Product main image page (both read 2026-10-02). They agree on a white, product-first main image and disagree on logos.
| Topic | Walmart | Coupang |
|---|---|---|
| Background | Seamless white (255/255/255 RGB) | White background |
| Shape | 1:1 square, 2200 x 2200 px | Square, clear angle |
| Product fill | Not stated on the page | About 95% of the space |
| Logo | No seller logos or watermarks | Logo featured clearly |
| Extra items | No accessories not included | Avoid items not in your offering |
| Placeholders | Placeholder images not allowed (except Walmart's own, temporarily) | Not stated on the page |
| Originality | Not stated on the page | Original content; no other sellers' images without permission |
Coupang's extra images
Coupang describes additional images as showing the product in use, close up and from different angles. The page read does not give a count or file size, so do not copy a number from a third-party blog.
One product, two prompts
Keep the product reference identical and change only the marketplace line. For Walmart: product alone on seamless white, no logo, no text. For Coupang: square, product filling about 95% of the frame, white background, your logo only if your artwork is supplied as a reference and checked afterwards.
A model can redraw a logo wrongly, so for Coupang it is safer to composite the real logo file yourself after generation. The Coupang post covers the 95% fill check.
Keeping the variants straight
The failure mode in a multi-marketplace pipeline is a file landing in the wrong channel. Name files with the marketplace as a prefix, store the job id next to each, and have the upload step refuse any file whose prefix does not match its destination. A Walmart image with a logo, or a Coupang image without one, then fails in your pipeline, not in the marketplace review.
Batch it
Submit one job per SKU per marketplace with its own Idempotency-Key, and put the marketplace name in the job metadata so results do not get mixed (Jobs and results). Request a 1:1 ratio on both (Image API). Sume does not publish to either marketplace; you upload through their own tools.
Sources
Related posts
More in Comparisons
- WaveSpeed task statuses (timeout, deleted) vs Sume job statuses
WaveSpeed tasks can be created, processing, completed, failed, cancelled, timeout or deleted. Sume has five job statuses. How to map them in a port.
- WaveSpeedAI API alternative: what Sume offers instead
WaveSpeedAI sells 1,000+ models behind one API with tiered rate limits. Sume offers a smaller managed catalog with plan-based concurrency. Compared.
- Best Sume image model for text in images: five catalog ids compared
Vendors pitch text rendering: Ideogram typography, FLUX.2 flex, Qwen-Image 2.0 Pro, Seedream. Which of those ids does Sume list, and how to test them yourself.
- YouTube Studio clips and Shorts tool vs Sume trim and captions
YouTube's clips tool cuts Shorts from your long videos inside Studio. Sume does the same file work by API, with trim, captions and Timeline. When to use which.
Written by Sume