A friend selling handmade candles on Etsy spent more on quarterly photo shoots than on ads. Her photos were fine — phone on the kitchen table — but they didn't look like the rest of the marketplace. She didn't need "AI art." She needed listing-ready scenes without reshooting.
That's why I built Trend Packshot.
The product (30 seconds)
Upload a product photo → pick a marketplace scene (Amazon, Etsy, Shopify, TikTok Shop, eBay, Walmart) → preview free → export HD when ready.
Background/scene only. Labels, logos, textures, and colors stay on the product. We isolate the product and generate the environment — not a generic "make my product look different" tool.
If you sell online, try the free preview. No credit card for preview; sign in only when you export HD.
Why not another AI image toy?
Most image models happily repaint your SKU. Marketplace sellers care about fidelity more than wow-factor. Our pipeline is built around:
- Product isolation first, scene second
- Marketplace-specific style presets (white-bg Amazon looks, Etsy boutique scenes, etc.)
- Preview before pay — reduces "AI roulette" anxiety
Stack (what actually ships it)
I'm running this on a multi-site TanStack Start monorepo, one Cloudflare Worker per site:
| Layer | Choice |
|---|---|
| Frontend + SSR | TanStack Start / Router |
| Compute | Cloudflare Workers |
| Database | D1 (SQLite) + migrations |
| Auth + billing | Better Auth + Stripe |
| Assets / config | KV, R2 |
One wrangler deploy per site; shared src/ for auth, admin, and marketing modules. Local dev:
pnpm dev:site trendpackshot # port 3002
Not trying to convince you this is the only valid stack — it's what let me ship fast with SSR, edge deployment, and sane billing hooks without running a separate Node server.
Three things that were harder than expected
1. "Don't change my product" is a product requirement, not a prompt tweak.
Sellers will zoom into label text. Background-only generation + clear UI copy beat fancier models.
2. Preview vs export is a business model, not just UX.
Free preview lowered support tickets ("why did I pay for that?") and improved conversion for people who already liked the scene.
3. Attribution on a static marketing site.
First-touch UTM cookies (?utm=devto) → saved on signup → visible in admin. Simple, but necessary when you launch on PH, DEV, Reddit, and directories the same week.
Launch day
We're going live on Product Hunt the same day as this post. If you're building commerce tools or running a small catalog side hustle, I'd love your feedback — especially on scene quality and export workflow.
Links
Question for you
If you've shipped a vertical SaaS (not devtools): what surprised you most about choosing edge/workers vs a traditional Node host?
Thanks for reading — happy to answer stack questions in the comments.
DEV front matter (optional — if importing via Git or CLI)
---
title: I shipped Trend Packshot — AI product photos for marketplace sellers on Cloudflare Workers
published: false
tags: webdev, cloudflare, ai, indiehacker
cover_image: https://trendpackshot.com/og-image.png
---
Pre-publish checklist
- [ ] 70% value / 30% product — post still worth reading with all links removed
- [ ] At most 2–3 code blocks (DEV readers skim)
- [ ] Cover image + at least one before/after or workflow screenshot in body
- [ ] All links use
?utm=devto - [ ] Cross-promote with Product Hunt same day; PH first comment can mention DEV post
- [ ] Reply to every comment within 2 hours of publish
Do not
- ❌ Paste landing-page bullets from Product Hunt or directory listings
- ❌ Clickbait titles ("This AI will 10x your sales")
- ❌ Spam many links or affiliate tone
- ❌ Pure ad with no technical substance
Top comments (0)