Prompt Kits

Build an Online Store

An online store has to keep four promises at once: show the right product, charge the right amount, avoid selling stock that is not available, and tell both the customer and owner what happens next. This kit builds those promises in five sequenced prompts — the public catalogue, variant-level stock, cart and delivery logic, real checkout, and order management — with a visible test after each step. It suits a small or medium catalogue of physical products, digital products, or both; a large retail operation with warehouses, complex tax rules or many sales channels may need a specialist commerce system.

Project type: Online store Difficulty: Intermediate Time: 2-3 days Works with: Base44 / Lovable / v0

What you'll have at the end

  • A public storefront and product catalogue that work well on a phone
  • Product pages with real descriptions, real image placeholders, selectable variants and clear stock availability
  • A cart that checks current prices and stock, then shows the right shipping, pickup or digital-delivery choices
  • A secure checkout that takes a real one-off payment without your site handling card details
  • An order confirmation page and email that tell the customer exactly what happens next
  • An owner area where you manage products, stock and orders
  • A fulfilment flow for shipping, pickup, local delivery or protected digital downloads

Before you start

  • A small real catalogue. Prepare at least three products with names, descriptions, prices, categories and stock. For every option such as size or colour, write down the exact combinations you sell and the stock for each combination.
  • Real product images. Gather your own clear photos or images you have permission to use — editing your own product photos yourself (lighting, background, crop) is fine and often makes a small shop look far more professional. Until they are ready, this kit uses labelled placeholders; it never asks the builder to invent product photos or generate a product that doesn't exist.
  • A fulfilment decision. Choose whether you sell physical products, digital products or both. For physical products, decide where you deliver, which methods you offer, what each method costs and the delivery estimate. For digital products, prepare the real files and a clear download policy.
  • A payment provider account. Stripe is a common choice. Keep it in test mode until step 4 works from start to finish, and store any private key only in your builder's secure settings.
  • Customer-facing policies. Draft your shipping or delivery policy, returns or refund policy, privacy policy and terms. Requirements vary by place and product, so use advice appropriate to where you operate.
  • Two email addresses you control. Use one as the customer and one as the owner so you can see both sides of a test order.

Which platform suits this

Base44 is the smoothest fit for a custom small or medium store because product data, owner screens, accounts, security rules and Stripe checkout can live in one app. Its Stripe setup starts in test mode, but Stripe products are not automatically a complete store catalogue, so this kit deliberately asks for one clear source of product, variant and stock information. Lovable is a strong fit for digital products and one-off payments. It can also support physical sales, but stock, shipping and fulfilment still need to be built and tested separately rather than assumed to come with checkout. v0 is especially strong for the storefront experience and can connect payment and database services; but a fully custom v0 store leaves the product data, accounts, stock and order wiring for you to build and verify yourself. On any platform, use a specialist commerce system instead of this kit when you need multiple warehouses, advanced returns, many sales channels or high-volume inventory coordination. Shopify vs Base44 vs Lovable explains where that line falls, and how a Lovable storefront can sit on top of Shopify.

Start with the first prompt on a free plan. Extra usage and some connected services may cost more as you build out the project.

Build it on

How we make money

The steps

1

Build the storefront and product catalogue

When to use this

Start here, in a brand-new project, before adding accounts, a cart or payments.

A complete public store shape where people can browse products and understand what they are buying.

The prompt

Build the public storefront for [STORE NAME], which sells [PHYSICAL PRODUCTS / DIGITAL PRODUCTS / BOTH] for [WHO THE PRODUCTS ARE FOR].

Create a home page that explains what the store sells, why a customer should trust it and how to browse. Create a catalogue page where people can browse products by [YOUR MAIN CATEGORIES]. Create one reusable product page that shows the product name, real description, price, available options, stock message, image area, delivery or download summary and a clear purchase action. Also add an about page and a contact page using [CONTACT EMAIL].

Save products as editable information rather than writing each product permanently into a page. Each product needs a name, short description, full description, category, price, product type, status, image, delivery summary and whether it is featured. Product type is physical or digital. Status is draft, active or unavailable. Only active products appear to visitors.

Add three example products that are clearly labelled as examples for me to replace. Use labelled image placeholders saying [REAL PRODUCT IMAGE NEEDED]. Do not use stock photos and do not generate product, customer or lifestyle images from scratch. Editing my own real product photos is fine; only invented or generated products are the problem, because they misrepresent what the buyer receives.

Do not build customer accounts, a cart, checkout or payment in this step. Show the purchase action as [BUTTON LABEL, e.g. Choose options], but do not pretend an order can be completed yet.

Design the store to feel [THREE BRAND ADJECTIVES]. Use [COLORS] and [TYPOGRAPHY PREFERENCE]. Keep the product information easy to scan, use restrained spacing and make every page comfortable on a phone. Do not invent reviews, sales numbers, scarcity messages, certifications or customer claims.

When finished, tell me where I edit products and which text and images are still examples.

Check it worked

  • You can move from the home page to the catalogue and open each example product
  • Editing an example product changes what visitors see without rebuilding its page
  • Draft and unavailable products do not appear as ordinary products for sale
  • Every image area is clearly labelled for a real image you must supply
  • The purchase action does not lead to a fake checkout
  • The catalogue and product pages are easy to read on your phone

You'll know it worked when:

A public storefront where you can browse three editable example products from the home page through to a full product page.

Watch out for

Example products often survive into launch by accident. Give every example an obvious label and do not remove those labels until the real name, description, price and image have all been supplied. A pretty product grid is also not a store catalogue if every item is written directly into the page; prove that one edit in the product area updates the public page.

2

Add variants, stock and owner product controls

When to use this

Once the storefront looks right and before building the cart.

One dependable source of product truth, including the exact stock for every selectable version.

The prompt

Add product options, stock control and a private owner product area to this store.

A variant means one selectable version of a product, such as a blue shirt in size medium. For each product, let me choose whether it has no variants or has options named [OPTION NAMES, e.g. size and colour]. Save every valid combination separately with its own price when needed, stock quantity, identifying code and active or unavailable status. Do not create combinations I do not sell.

On the product page, the customer chooses each required option before the purchase action becomes available. Show the price and availability for the exact combination they selected. If that combination is unavailable or its stock is zero, say so plainly and do not let it continue toward purchase. Never show a vague in-stock message based only on the total across every option.

Add a private owner area where I can add and edit products, upload my real product images, create valid option combinations, change prices, adjust stock and mark a product draft, active or unavailable. Only I can open or use this area. A visitor must not reach it by typing its address directly.

Keep one source of truth for product names, prices, variants and stock. The public catalogue, product page, future cart and owner area must all read from that same saved information rather than keeping separate copies.

Add a stock history that tells me what changed, by how much, when and why. Manual changes require a short reason such as [STOCK ADJUSTMENT REASONS]. Do not reduce stock yet because no order can be paid for in this step.

Keep all work from step 1 unchanged. Use my real images where I upload them and keep labelled placeholders everywhere else. Do not generate product images from scratch or invent a product; editing my own real photos is fine.

Check it worked

  • You can create a product with [OPTION NAMES] and only the combinations you really sell appear
  • Selecting a different combination changes the displayed price or availability when it should
  • A combination with zero stock is visibly unavailable and cannot continue toward purchase
  • Changing one price in the owner area updates the catalogue and product page
  • Logged out, you cannot open the owner product area even by pasting its address
  • A manual stock change appears in the stock history with your reason

You'll know it worked when:

One product with real option combinations whose price and stock you can change privately and verify on the public product page.

Watch out for

One stock number for an entire product is wrong when options differ; it can sell a size or colour you no longer have. Track stock for the exact combination. Avoid keeping one price in the payment provider and another in the product area without a clear sync rule, because they will drift. The product area must be the source used to calculate the future cart, while the payment step rechecks it before charging.

3

Build the cart and delivery choices

When to use this

After variant stock works and before connecting real payments.

A cart whose contents, totals and fulfilment choices can be tested without charging anyone.

The prompt

Add a working cart and fulfilment choices to this store without connecting payment yet.

A customer can add the exact selected product variant, change its quantity, remove it and continue shopping. Keep the cart if they move between pages or refresh. Before adding or increasing a quantity, check the current saved stock and never allow more than is available.

Calculate each line and the subtotal from the current saved product price, not from a price sent by the customer's browser. Show product name, selected options, quantity, price and a small real product image or labelled placeholder. If a price, status or stock level changed after the item entered the cart, explain the change and require the customer to review it.

This store sells [PHYSICAL PRODUCTS / DIGITAL PRODUCTS / BOTH]. For a cart containing physical products, offer only these valid fulfilment choices: [SHIPPING / LOCAL DELIVERY / PICKUP OPTIONS]. Explain the cost, where each choice is available and the delivery estimate using [YOUR REAL RULES]. Collect only the address or pickup details that choice needs. For a cart containing only digital products, do not ask for a shipping address and show digital delivery as free unless [YOUR REAL DIGITAL DELIVERY RULE] says otherwise.

Show a clear order summary before checkout with the subtotal, delivery charge, any discount I have explicitly configured and the total. Do not invent tax rules. Show tax only when the connected payment setup can calculate it correctly for the customer, otherwise tell me what remains to be configured before launch.

Add a review order button that stops at a clearly labelled payment not connected screen. Do not create a fake success message and do not mark anything as ordered or paid.

Test the cart with [ONE IN-STOCK VARIANT], [ONE LOW-STOCK VARIANT], [ONE OUT-OF-STOCK VARIANT] and every fulfilment choice. Tell me in plain language what happened in each test.

Check it worked

  • You can add two different products with the exact options you selected
  • Refreshing or visiting another page does not empty the cart
  • You cannot raise a quantity above the stock that is actually available
  • Changing a product price or stock in the owner area is caught before review
  • Physical orders show only valid delivery or pickup choices and the total changes correctly
  • A digital-only order does not ask for a shipping address
  • The review button stops before payment and never claims the order succeeded

You'll know it worked when:

A test cart containing two products whose quantities, delivery choice and final total you can change and verify without paying.

Watch out for

Shipping rules that look simple often fail at boundaries, such as an unsupported area, a mixed physical and digital cart, or pickup selected without a pickup location. Test each one. Never trust a price stored only in the visitor's browser; the store must re-read price and stock from the protected product information before checkout. If taxes cannot be calculated reliably, do not show a confident zero or invented amount.

4

Take payment and create a confirmed order

When to use this

Only after the cart blocks unavailable stock and every fulfilment total is correct.

One secure test payment that produces one paid order and the right confirmation for both customer and owner.

The prompt

Connect this store to [PAYMENT PROVIDER, e.g. Stripe] in test mode and turn the reviewed cart into a real checkout.

Before checkout opens, check the current product status, exact variant stock, price and fulfilment cost again from the protected saved information. Create a short stock reservation for [RESERVATION TIME, e.g. fifteen minutes] so two customers cannot both buy the final item. Release the reservation if payment is cancelled or not completed in time.

Send the customer to the payment provider's secure checkout to enter payment details. My site must never collect or store card details. The amount charged must come from the checked cart total, not from anything the customer's browser can change.

Treat an order as paid only after the payment provider sends its trusted payment confirmation. Returning to the success page is not proof of payment. On trusted confirmation, create one order with a unique order number, mark it paid, reduce each purchased variant's stock exactly once and clear the customer's cart. A delayed or repeated confirmation must never create a second order or reduce stock twice.

Show a confirmation page with the order number, items, amount paid, fulfilment choice, customer contact details and what happens next. Send the same useful summary to [CUSTOMER EMAIL] and send a new-order alert to [OWNER EMAIL]. For a physical order, include the delivery or pickup estimate. For a digital order, provide the purchased files through a protected download that only the paid customer can use; never expose a permanent public file address.

Add a basic private owner order view showing the order number, customer, items, amount, payment state, fulfilment choice and date. Do not expose payment secrets or full payment details.

Show me where to complete my payment provider connection and which steps I must perform myself. Then guide me through one successful test payment, one cancelled payment and one declined payment.

Check it worked

  • Checkout opens on the payment provider's secure page with the correct items and total
  • A successful test payment returns to a confirmation showing one order number
  • The customer confirmation email and owner new-order email both arrive
  • The paid order appears once in the owner order view
  • Purchased stock falls once, while a cancelled or declined payment does not reduce it
  • Reopening or refreshing the confirmation does not create another order
  • A digital test file opens only for the paid customer and not from a copied public link

You'll know it worked when:

A full test order: reserve stock, pay, receive confirmation, see one order in the owner area and confirm stock changed once.

Watch out for

A success page can be opened without a successful payment, so it must never be the signal that marks an order paid. Repeated payment confirmations are normal and must be safe to process more than once. Test and live payment settings are separate; after switching to live mode, make one small real order to yourself and refund it. Stock reservations need an expiry, or abandoned checkouts can make available products look sold out. Digital files need protected delivery, not a permanent link that can be shared.

5

Add fulfilment and complete the owner workflow

When to use this

After the full test order in step 4 works from payment through confirmation.

Give the owner a manageable order queue and customers accurate updates after they pay.

The prompt

Complete the order fulfilment workflow and owner controls without changing the working payment or stock rules.

In the private owner area, let me filter orders by [FULFILMENT STATUSES, e.g. paid, preparing, ready for pickup, shipped, delivered, cancelled and refunded]. Opening an order shows the customer details needed for fulfilment, purchased items and variants, delivery or pickup choice, payment state, stock changes and a dated history of status changes. Let me add a private note that customers cannot see.

For shipped orders, let me add [DELIVERY PROVIDER NAME] and a tracking reference or tracking link. For pickup or local delivery, let me add clear collection or arrival instructions. For digital orders, show whether the customer received access and let me safely resend the protected download message without creating a new order.

Send the customer an email only for the status changes I choose: [STATUS CHANGES THAT SHOULD SEND AN EMAIL]. Each message must use the real order details, explain what changed and tell the customer what to do next. Never include private owner notes.

Add low-stock alerts at [LOW-STOCK LEVEL] and show which exact variant needs attention. If I cancel and refund an order through the payment provider, update the order after trusted confirmation and ask me whether sellable physical stock should be returned. Do not automatically return damaged, lost or downloaded digital goods to available stock.

Let me export the order information I need for fulfilment using [FIELDS I NEED], while excluding payment secrets and unnecessary personal details. Keep access to products, orders and exports owner-only.

Run the tests from steps 1 through 4 again after these changes and report anything that no longer works.

Check it worked

  • You can find the test order, change its fulfilment status and see a dated history
  • The customer receives the correct update for the status you chose and no email for a status you excluded
  • Tracking or pickup instructions appear on the order and in the right customer message
  • A low-stock warning names the exact product option that is running low
  • A refund updates the order without blindly putting every item back into stock
  • Logged out, you cannot open the order area or export customer information
  • The storefront, stock checks, cart and payment test still work after the owner tools were added

You'll know it worked when:

A paid test order you can move through fulfilment while the customer receives accurate updates and the stock history remains correct.

Watch out for

Refunded does not always mean restockable; damaged physical goods and delivered digital files need different treatment. Status emails can become noisy or contradictory if every internal change sends one, so choose the customer-facing moments. Exports contain personal information: include only what fulfilment needs, restrict access and delete old copies according to your policy.

Going live

  • Replace all example products and labelled image placeholders with accurate descriptions and real product images you own or have permission to use
  • Check every price, option combination, stock quantity and low-stock level from the owner area
  • Test an in-stock item, the last available item, an out-of-stock item and a price change while an item is already in the cart
  • Test every shipping, local-delivery, pickup and digital-delivery choice you actually offer, including an address or area you do not serve
  • Switch the payment provider from test to live settings, make one small real order to yourself, confirm both emails arrive and refund it
  • Confirm the live refund, cancellation, stock adjustment and protected digital-download behavior
  • Publish clear delivery, return, refund and contact information before checkout
  • Add your privacy policy and terms with the legal pages prompt
  • Connect your email service with the transactional email prompt and test from more than one inbox
  • Connect your custom domain with the custom domain prompt, then repeat checkout on the live domain
  • Open the full shopping journey on a real phone and a slow connection, from catalogue through confirmation
  • Keep a recoverable export of products and orders, and know who can reach customer information

Spend fewer credits

Every builder charges you for the work its AI does — so the cheapest habit is thinking before you build. These six rules cut most of the waste, whichever platform you choose.

  1. Plan in a free chat first. Sketch the whole thing in ChatGPT, Claude or Gemini — pages, features, what each form collects, what it should look like. Thinking there is free; thinking inside a builder is billed.
  2. Start from a written prompt, not a sentence. "Make me a website" is the most expensive sentence in AI building. A complete first prompt — like the ones on this site — saves dozens of correction rounds.
  3. Don't be lazy with the details. Every detail you leave out comes back as a correction you pay for. Business name, colors, every page, every form field, what happens after someone submits — put it all in the first prompt.
  4. One change per message afterwards. "Fix the header, and the form, and the colors" produces a tangle that costs more to unpick than it saved.
  5. Stuck? Stop patching. If the same fix fails about three times, don't send a fourth correction — describe the whole section's desired end state in one fresh message instead.
  6. Start free. Upgrade when you need more. Use the free allowance to build and explore your first version. Upgrade when you need more usage or paid features, and check any connected service costs before launch.

The prompts on this page are written to do most of this work for you — that's the point of them.

Read the full guide

Last reviewed: 2026-07-27

FAQ

We use cookies to analyze traffic and track affiliate clicks. By continuing, you agree to our Privacy Policy.