cd /news/generative-ai/how-i-m-building-an-ai-that-generate… Β· home β€Ί topics β€Ί generative-ai β€Ί article
[ARTICLE Β· art-115653] src=dev.to β†— pub= topic=generative-ai verified=true sentiment=Β· neutral

How I'm Building an AI That Generates a Full E-Commerce under a Minute

A developer is building Storeaxe, an AI-powered e-commerce generator that creates a complete online store from just a business name and industry. The system uses AI for copy and product generation while relying on rule-based theme matching, and defaults to cash on delivery to avoid payment gateway barriers. The project aims to simplify store creation by skipping the traditional template-and-drag model.

read2 min views5 publishedAug 30, 2026

Most website builders β€” Shopify, Wix, Webflow β€” still follow the same basic interaction model: pick a template, drag some blocks around, manually fill in every section. It works, but it assumes the user already knows what a "good" store looks like.

I wanted to try a different model entirely: skip the blank page completely. Enter a business name and pick an industry β€” two fields, no free-text prompt, no lengthy form β€” and let AI generate a complete, working store β€” copy, products, theme, checkout β€” before the user makes a single design decision.

That's what I'm building with Storeaxe. Here's a look at how it actually works under the hood.

1- Merchant enters: business name + industry (two fields)

2- AI infers tone/style from the industry (no free-text to parse)

3- AI generates: homepage copy + sample product catalog

4- Theme matched from industry/tone (rule-based, not AI) 5- Merchant reviews / edits everything

6- Store published β€” live, real checkout, real orders

Keeping the input to two structured fields instead of a free-text prompt was a deliberate choice, not a limitation. A short open-ended prompt sounds more "AI-native," but it also introduces parsing risk β€” vague answers, missing info, inconsistent tone extraction. Two fixed fields are trivial to validate, faster to fill in on mobile, and give the downstream generation step reliably clean input to work with. The AI still does the interesting work β€” copy, catalog, tone inference β€” it just isn't asked to do information extraction on top of generation.

The key design decision beyond that: not every step needs AI. Generating copy and products benefits from a language model. Picking a theme doesn't β€” that's a straightforward tag-matching problem, and doing it with rules instead of a model call is faster, cheaper, and more predictable.

Card payment gateways assume a level of infrastructure and business registration that a lot of small, first-time sellers don't have yet β€” especially outside a handful of countries Stripe directly supports. Rather than forcing merchants through a payment gateway approval process before they can sell anything, Cash on Delivery is the default, zero-setup payment method. Card payments via Stripe/PayPal are opt-in, connected later if and when a merchant wants them.

This turned out to matter more for real-world adoption than any AI feature did.

The live product is at ** storeaxe.com** if you want to see the actual generated output. Happy to answer questions about the architecture, the AI pipeline, or the payment-method tradeoffs in the comments.

── more in #generative-ai 4 stories Β· sorted by recency
── more on @storeaxe 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain β€” perfect for shipping the agent you just read about.

$git push zahid main
β†’ Live at https://your-agent.zahid.host βœ“
Get free account β†’ Pricing
from €0/mo Β· no card required
LIVE [news/how-i-m-building-an-…] indexed:0 read:2min 2026-08-30 Β· β€”