A shop where changing a price is one edit, in one file.

Why this exists

Everything here comes out of a single file. Add a product to it and you get a card on the shop, a landing page of its own at its own address, and a working checkout. Delete a line and all three go away.

This is code, not a prompt pack. You need to be able to run a build command and paste a key into a hosting dashboard. If that sentence worries you, this isn't the one to buy.

What you get

This exact storefront, the checkout behind it, and the research that set the prices.

There's also the part that isn't code. The pricing worksheet shows how every number in this catalog was set, including the product I marked down after the research came back and said the category I'd put it in has almost no pricing power.

And the deploy step is worth the money on its own if you've ever been caught by it. It refuses to report success until it has fetched the live site and confirmed the new build is the one being served. I lost a day to a deploy that logged green while production sat on the old version.

• The storefront: one catalog file driving the shop page, a landing page per product, and the payment session
• Card payments through Stripe, with the key living only on the server and never in the page
• Download links that expire, so a paid file does not end up on a public URL
• A terms page and a final-sale policy written to be readable rather than defensive
• The deploy step that fails when production is still serving the old build — the mistake that cost me a day
• The pricing worksheet: how each number in this catalog was chosen and what evidence sat behind it
• The research method, so you can price your own catalog the same way instead of guessing