Product listing image QA
Screen storefront product photography for visible AI generation, composite artifacts, or misleading staging before a SKU goes live. On marketplaces with strict 'real product' policies, a bad hero shot can pull an entire listing.
Business value
- Catches the listings where 'product on white' shots were obviously generated, before Amazon/eBay/Etsy listing review catches them and suppresses the SKU.
- Surfaces composite issues — products pasted into impossible scenes, scale mismatches with handheld props — that get flagged in review queues.
- Builds an internal asset-quality bar that scales beyond manual designer review.
Agent job to be done
Be a marketplace listing reviewer. Allow assets that read as actual product photography. Hold assets with composite or generation cues. Reject assets that would obviously fail platform review.
format: product_reviewintended_use: publishdomain: ecommerce product listing photography
Marketplace policy variance (Amazon vs. eBay vs. Etsy vs. Mercari)
Amazon's listing image rules (no logos/watermarks on main image, no decorative props, white background for main) drive different failure modes than eBay (more permissive, but strict on 'must show the actual item being sold') or Etsy (allows stylized product photography but flags compositing in 'handmade' categories) or Mercari (relatively permissive, focused on item-condition disclosure). If you sell across marketplaces, scoring is per-marketplace, not universal.
When to call VeracityAPI
After product photography/asset upload, before the listing is submitted for marketplace review or syndicated to channels.
What image URL to submit
Public HTTPS image URL for the exact asset that will appear on the listing. Submit the marketplace-resolution version (Amazon main image: 2000x2000 PNG/JPG).
Decision policy
- allow: low synthetic_image_risk, no composite cues, scale and shadow consistency.
- revise: medium risk — request a re-shoot or a different angle from the original photoshoot. Composites can usually be fixed in the next pass.
- human_review: high risk on hero/main images (the photo that decides whether someone clicks the listing).
- reject: visible heavy manipulation on assets that would fail Amazon A+ Content rules or eBay/Etsy authenticity policies.
Request template
The exact payload shape this use case sends. The sample below uses representative content for this workflow; substitute your own.
curl https://api.veracityapi.com/v1/analyze \
-H "Authorization: Bearer $VERACITY_API_KEY" \
-H "Content-Type: application/json" \
-d '{"type":"image","content":"https://veracityapi.com/demo/influencer-beauty-tonic.jpg","context":{"format":"product_review","intended_use":"publish","domain":"ecommerce product listing photography"},"store_content":false}'Automation recipe
- Listing agent receives the asset bundle (hero, secondary angles, lifestyle shots).
- Score the hero image first; if it fails, the rest of the bundle gets paused.
- Allow-tagged listings move to marketplace submission.
- Medium-risk assets enter a designer queue with evidence categories.
- Replacement assets re-enter the gate.
Evidence spans agents should inspect
- 'synthetic_texture' — material textures (fabric weave, leather grain, metallic surfaces) that don't render naturally
- 'composite_seam' — product edges that don't agree with the background lighting or color cast
- 'scale_mismatch' — products that don't make sense at the stated size next to context props
- 'impossible_geometry' — handles, hinges, hardware, or fastener details that violate how the product would actually function
Policy pseudocode
if (result.recommended_action === "allow") continueWorkflow(); if (result.recommended_action === "revise") rewriteWith(result.evidence, result.recommended_fixes); if (result.recommended_action === "human_review") queueForHumanReview(result); if (result.recommended_action === "reject") discardOrRebuild();
KPIs to track
- % of listing assets flagged before marketplace submission
- marketplace policy-violation suppression rate (target: drop by 50%+ after deployment)
- designer rework hours per 100 listings
- false-positive appeal rate
- listing time-to-live for clean asset bundles
What can go wrong
- AI-generated product photography is becoming explicitly allowed on some marketplaces (with disclosure) and disallowed on others. The score is one signal; check the platform policy.
- Lifestyle shots are different from product-on-white. Scoring thresholds should differ — lifestyle scenes have legitimate compositing reasons that would trip strict thresholds.
- Pair with a 'has real EXIF camera metadata' check for high-end listings — provenance often resolves ambiguity faster than visual scoring.
Cost and latency notes
Image analysis is a flat $0.02 per image. The endpoint accepts HTTPS image URLs, stores no image bytes, and logs only a URL hash plus hostname. Current v0.1 latency is vision-model-bound, so preflight balance and retry carefully.
Agent evaluation checklist
- Does this workflow have a costly failure mode from manipulated or synthetic-looking visuals?
- Can the agent store evidence categories without storing raw image bytes or full URLs?
- Should this workflow fail open, fail closed, or queue human review if image scoring is unavailable?
- Which field drives policy: recommended_action, risk_level, content_trust_score, or synthetic_image_risk?
- What local provenance check should complement the API score?