A product catalog with Stripe Checkout is genuinely one of the more approachable builds here — the same core pattern behind every e-commerce entry in the register, scoped down to what a small storefront actually needs.
Build it
Effort: a weekendRunning cost: $0/mo to start
Why CanICodeThis says Build it
A product catalog with name, description, price, and images is ordinary CRUD
Stripe Checkout handles payment collection and the receipt entirely — you're integrating, not building a payment processor
An orders table updated via Stripe's webhook, with a simple admin view to mark orders shipped, closes the loop
The parts that'll cause problems
Inventory sync across multiple sales channels (also selling on Etsy or in person) needs real, separate reconciliation logic
Sales-tax calculation across states and countries is a genuinely deep compliance problem — use a tax API rather than a homemade rules engine
Product variants (size, color) as combinations, each with their own price and stock, add real schema complexity beyond a flat product list
How I'd build this
frontend
Astro or Next.js
database
Supabase
payments
Stripe Checkout
hosting
Cloudflare Pages
MVP scope
Product catalog with images, description, and price
Stripe Checkout for payment
An orders table updated via Stripe webhook
A simple admin view to mark orders as shipped
Postpone to v2
Product variants (size, color) with per-variant stock
Discount codes
Automated sales-tax calculation via a tax API
What it actually costs to build
AI agent — with a subscription (Claude Pro/Max, Cursor, etc.)
$0 marginal
AI agent — pay-per-use API, no subscription
$43–$86 one-time
Hosting, once it's running
$0/mo (free tier)
Domain name, if you want your own
~$12/yr
Existing tools solving a similar problem typically run $10–$39/mo — see how they compare below.
The build prompt
Build me a simple online store, genuinely one of the more approachable builds here:
1. A product catalog (name, description, price, images) — standard e-commerce CRUD.
2. Stripe Checkout for payment — you're integrating, not building a payment form.
3. An orders table updated via Stripe's webhook.
4. A basic admin page listing orders with a 'mark as shipped' button.
Flat-rate shipping only. That's a real, working small store. Out of scope: product variants (size, color) with per-variant stock, real, additional schema complexity, and automated sales-tax calculation, a genuinely deep compliance problem — use a tax API rather than a homemade rules engine when you need it.
