What a store needs that nobody puts in the prompt
Asking for "an online store" produces pretty shopfronts that break on the third order. These are the decisions to make before generating:
- Variants. Size, colour, weight or format. Each variant carries its own stock and can sell out separately.
- Stock rules. Can out-of-stock items be ordered? Is the buyer warned? Is checkout blocked?
- Shipping. Zones, price tiers, free-shipping threshold, and who pays for returns.
- Payments. Which provider, which methods, and what the buyer sees when a payment fails.
- Orders. Where they land, how they are marked as shipped, what the customer receives by email.
- Tax and invoicing. Tax included in the price, how it is broken out, buyer tax details.
The flow to build, in order
- Product listing with photo, price, availability and basic filters.
- Product page with variants and quantity selector.
- Cart that survives a page reload and adds shipping and tax.
- Checkout with validated shipping details and provider payment.
- Confirmation and an email with the order summary.
- Seller dashboard to view orders, mark shipments and check stock.
Building in that order avoids the classic "I have a catalogue and no way to charge". If you are in a hurry, close the cart and checkout before touching design.
Custom store or hosted platform
| Option | When it makes sense |
|---|---|
| Store built with AI | Small catalogue, a story of your own, you want control of the flow and no per-sale commission. |
| Ecommerce platform | Large catalogue, shipping and invoicing solved from day one. |
| Hybrid | Own landing and flow with AI, payments delegated to a provider, order handling in a familiar tool. |
If you build it, the prompt matters more than the tool: a store without shipping rules in the spec generates a checkout that charges wrong on the very first order.
Before you charge anyone
Run the whole circuit with one small real purchase: product, cart, shipping, payment, email and order in the dashboard. And get the legal pages you need in place (terms, returns policy, seller details). It is the boring part, and it is the part that prevents problems later.
Keep going with the generator
Frequently asked questions
What should an online store prompt include?
Catalogue with variants and stock, a persistent cart, shipping calculation by zone, provider payments, order confirmation emails and a dashboard to manage orders. Anything missing gets decided while building, and you pay for it in fixes.
Should I build a store with AI or use an ecommerce platform?
With a small catalogue and your own flow, a custom store is often cheaper and takes no commission. With a large catalogue, complex shipping and invoicing, a hosted platform solves those problems sooner.
How do I handle variants and stock?
Treat each variant as its own item with its own stock, and have the cart check availability before charging. Write that rule explicitly in the spec.
How do payments work in an AI-built store?
You connect a payment provider (Stripe and similar) with your own keys. Test the flow with a small real purchase before opening the store.
Do I need terms and a returns policy?
Yes. Most jurisdictions require seller details, terms of sale and a returns policy. The prompt can include the pages; a human must write the content.
Is this prompt generator free?
Yes — free, no signup, up to 8 prompts per hour per IP.