E-Commerce template

    E-Commerce Store template

    A full-featured online store with product catalog, shopping cart, Stripe checkout, order management, and admin dashboard for inventory tracking.

    ReactFastAPIPostgreSQLStripe

    What's included

    Product catalog
    Shopping cart
    Stripe checkout
    Order management
    Inventory tracking
    Customer accounts

    What gets generated

    Two details separate a store that works from a store that loses money. Order lines copy the price at the moment of sale, so changing a product price never rewrites past invoices. And stock is reserved at checkout rather than decremented at payment, so a slow card authorisation cannot oversell the last unit.

    The data model

    • products with variants — size and colour as their own rows, because a variant has its own price, stock and SKU
    • inventory with reservations, so two people checking out the last item does not oversell it
    • carts, persisted server-side so they survive a device change
    • orders and order_items — order_items copies the price at the time of sale rather than joining to products, so a later price change does not rewrite history
    • addresses, shipments and refunds

    The screens

    • Catalogue with filtering by category, price and attribute
    • Product page with variant selection and stock state
    • Cart and a checkout that handles Stripe's 3D Secure flow
    • Order history and order detail with tracking
    • Admin: products, stock levels and order fulfilment

    All of it is generated as source code — React or React Native, Python and SQL — in a repository, with migrations, so the schema above is a starting point you can change rather than a fixed structure you have to work around.

    How to use this template

    1

    Start from this prompt

    The E-Commerce Store prompt below is the starting point — edit it first if any of "What to change first" applies to you.

    2

    Generate the whole stack

    Appifex writes the React and FastAPI pieces together with the database and the deploy, not just the interface.

    3

    Ship it

    Your app is deployed and running, and the repository is in your GitHub account.

    What to change first

    Tax and shipping. The checkout is Stripe and it works, but rates are the part that is jurisdiction-specific and cannot be guessed — say where you sell and the calculation arrives with the order model rather than bolted onto it afterwards.

    What this template does not include

    No tax or shipping-rate calculation — those are jurisdiction-specific and cannot be guessed, so say where you sell. No multi-currency, no discount codes, and no abandoned-cart recovery.

    Ask for any of it in the same prompt — the template is a starting point, not a fixed product.

    Sample prompt

    "Build an e-commerce store with product catalog, shopping cart, Stripe checkout, order management, and an admin dashboard for inventory"

    Build your e-commerce store now

    Generate a production-ready e-commerce store in minutes. Free to start.

    About the E-Commerce Store template

    What does the E-Commerce Store template include?

    A full-featured online store with product catalog, shopping cart, Stripe checkout, order management, and admin dashboard for inventory tracking. It is generated as a complete project rather than a starting skeleton: product catalog, shopping cart, stripe checkout, order management, and more. The stack is React, FastAPI, PostgreSQL and Stripe, and the whole thing lands in a GitHub repository you own.

    Can I change the E-Commerce Store template after generating it?

    Yes, in two ways. You can describe the change in plain language and Appifex regenerates the relevant code, or you can open the repository and edit it directly — it is ordinary React, FastAPI, PostgreSQL and Stripe with no proprietary runtime or shim to work around. Most people start with the template and diverge from it immediately.

    Can the E-Commerce Store template become a mobile app?

    Yes. Appifex can generate a native iOS and Android app against the same backend and database, so the web app and the mobile app share one data model rather than being two separate products to keep in sync.