Thank you- this is extremely valuable. I appreciate your response and insights- this is exactly the kind of critique I was hoping for.
I agree that a product image alone is not enough to create final, publish-ready ecommerce copy. The image gives visual context, but the seller still needs to add product facts like size, material, variants, use case, audience, etc., and review the result.
That is intentional. NOMEV is not meant to be blind automation. It is meant to compress the first-draft stage while keeping product knowledge, platform context, and human judgment in the loop.
The time savings comes from reuse and compounding context. Some details will always be product-specific, but other guidance should not have to be repeated every time: brand voice, category + platform guidance, preferred phrasing, words to avoid, prior review edits, and product templates that already work.
This came out of my own photography workflow. I sell prints, and the pain was not that I didn’t know the product. The pain was repeatedly translating the same product story into Shopify descriptions, SEO fields, alt text, Instagram copy, Pinterest language, Etsy-style copy, and sometimes a blog angle.
Even for Shopify alone, I think there is value in reducing blank-page work around product descriptions, SEO fields, alt text, and draft structure. But the time-compression benefit compounds when a seller also uses Etsy, Instagram, Pinterest, Facebook, or blog content.
I also agree that platforms are not interchangeable. That is why I’m treating guidance as category + platform specific. Photography + Etsy should not sound the same as Photography + Instagram or Photography + Shopify Product. Same product, different channel expectations.
You’re also right that multiple images matter. In the fuller workflow, NOMEV already treats the first uploaded image as the primary product image and additional uploads as gallery/supporting images. The current public preview is intentionally simpler so people can test the draft-generation flow quickly.
Your point about the “one image” framing is especially helpful. I think the better framing is:
start with a product image, add the key product facts once, then generate editable channel-specific drafts.
You clearly have experience with this problem from the migration/product-data side. If you’re open to it, I’d value your perspective as NOMEV develops and would be happy to keep you in the loop.
Best,
Mark