Cuely is now open source. See exactly what it receivesCode on GitHub

Recipe · checked November 20, 2026

Online store selling products to shoppers

A store that sells physical or digital products. Start on a hosted store builder, which already has checkout, payments, shipping labels, taxes and order email, and only build a custom storefront or move to an open-source commerce framework when the store needs something the builder can't do.

Tool bills at 1,000 usersAbout $39/month
Setup steps7
Tools in the stack6

Fits when

  • You sell products (physical, digital or subscriptions) to shoppers at prices you set.
  • You want checkout, payments, shipping and taxes working without building them.
  • Non-developers will add products and handle orders day to day.

Not for

  • Marketplaces where users sell to each other and you take a cut: the marketplace recipe covers payouts.
  • Selling software subscriptions or seats: the b2b-saas recipe covers Stripe Billing.
  • Warehouse, ERP or 3PL integration across many locations: plan those systems first.

The stack

CategoryPickWhyPick something else when
Store platformCheckout, payments, shipping labels, taxes, order email and hosting in one subscription: Basic is $39/month billed monthly ($29 billed yearly). Use Shopify Payments, since any other provider adds 2% per sale on Basic.
  • Medusa: Checkout, pricing or catalog logic is unusual enough that you need your own code, or you want no platform fee on sales; you build the storefront and bring your own payments.
CMSoptionalOnly if the store has a real content side (lookbooks, guides, a blog) beyond product pages; the store builder's own pages cover the basics.
  • Payload: You build a custom Next.js storefront and want the content in the same app and database.
SearchoptionalOnly for large catalogs that need instant search with facets; the store builder's own search covers a few hundred products.
  • Meilisearch: You'd rather pay a flat $20/month with unlimited searches.
HostingoptionalOnly for a custom (headless) storefront in Next.js that reads products from the store's API; a theme-based store needs no hosting of its own.
PaymentsoptionalOnly with a custom build on Medusa or your own checkout; on Shopify, use Shopify Payments.
  • Paddle: You sell digital products worldwide and want a merchant of record to handle VAT.
AnalyticsoptionalFunnels from product page to checkout, beyond the store builder's own reports.
  • Plausible: You want simple, cookie-free traffic numbers.

About $39/month at 1,000 users in tool bills: Shopify $39. Usage profile: 1,000 monthly active users with light use: about 100,000 requests, 3,000 emails, 200,000 analytics events and 5 GB of stored files a month, and a database under 1 GB. AI apps add 50 questions per user a month at about 4,000 input and 500 output tokens each (200M input and 25M output tokens). Internal tools are priced for 10 staff instead.

Catches that change the plan

Setup steps

  1. Decide: hosted builder, headless, or custom

    Most stores should start on the hosted builder and change only when they hit a real limit.

    • List what the store must do: products and variants, subscriptions, digital downloads, countries you ship to, B2B pricing.
    • If a standard theme plus apps covers that list, use the hosted builder with a theme (this recipe's default).
    • If you need a fully custom front end but standard checkout, go headless: a Next.js storefront on the builder's storefront API.
    • If checkout, pricing or catalog logic itself is unusual, or per-sale platform fees matter at your volume, build on Medusa.

    Done when: You've written down which of the three you chose and the one requirement that decided it.

    Docs: shopify.com, medusajs.com

  2. Set up the store, products and payments

    Products, prices and payments are the core; get them right before the theme.

    • Start the trial (3 days free, then $1/month for 3 months) and pick the plan you'll keep before launch.
    • Turn on Shopify Payments if it's available in your country; on Basic, any other payment provider adds 2% per sale.
    • Add products with variants, SKUs, weights (for shipping rates) and good photos; import a CSV for large catalogs.
    • Set up collections and navigation so shoppers find products in two clicks.

    Done when: A test order with a real card goes through checkout, shows in Orders, and the refund works.

    Docs: help.shopify.com

  3. Set up shipping and fulfillment

    Shipping cost and speed decide whether shoppers finish checkout.

    • Define shipping zones and rates (flat, by weight or carrier-calculated) for every country you ship to.
    • Decide who packs orders: you, a fulfillment service or print-on-demand, and connect it before launch.
    • Buy and print labels from the store admin, and test a full order from purchase to tracking email.
    • Write a shipping and returns policy and link it in the footer and at checkout.

    Done when: A test order to each shipping zone shows the right rate at checkout and sends a tracking email once the label is bought.

    Docs: help.shopify.com

  4. Handle sales tax and VAT

    Where you owe tax depends on where buyers are and how much you sell there; the store can calculate it, but you register and file.

    • Turn on tax collection in the store's tax settings for each place you're registered.
    • Track sales by state or country; selling past a threshold can create a duty to register there.
    • For digital products sold worldwide, consider a merchant of record (for example Paddle) that registers and files for you.
    • Ask an accountant which registrations you need before launch.

    Done when: A test order to a state or country where you're registered shows the right tax, and one where you're not shows none.

    Docs: help.shopify.com

  5. Theme, content and legal pages

    Shoppers decide fast; product pages and trust signals matter more than a custom design.

    • Pick a theme close to what you want and change colors, type and the homepage rather than rebuilding it.
    • Write product descriptions with sizes, materials and care, and add reviews when you have them.
    • Publish refund, shipping, privacy and terms pages, and a contact page with a real way to reach you.
    • Add a CMS only if you'll publish guides or lookbooks regularly.

    Done when: Every product page shows price, shipping estimate, returns policy and photos on a phone screen without scrolling sideways.

  6. Go headless or custom only if you chose to

    Skip this step for a theme-based store.

    • Headless: build a Next.js storefront on the store's storefront API, host it on Vercel, and keep the builder's checkout.
    • Medusa: start a Medusa project, add Stripe as the payment provider, and build the storefront from its Next.js starter.
    • Keep product data in one place (the store platform), and cache product pages so a traffic spike doesn't hit the API on every view.
    npx create-medusa-app@latest

    Done when: The custom storefront completes a test order end to end, and product pages load from cache under a load test.

    Docs: shopify.dev, docs.medusajs.com

  7. Launch and measure

    Launch with the basics that recover sales and catch problems.

    • Connect your domain and turn on abandoned-checkout emails.
    • Place one last real order from a phone, refund it, and check every email it sent.
    • Watch the funnel: product views, add to cart, checkout started, orders.
    • Review store apps monthly and remove ones you don't use; each adds cost and page weight.

    Done when: You can see this week's conversion from product view to order, and abandoned-checkout emails are going out.

Best practices

  • Start on the hosted builder and move to headless or custom only for a specific requirement.
  • Use the builder's own payments to avoid extra per-sale fees.
  • Put weights on every product so shipping rates are right at checkout.
  • Register for sales tax where you must before you collect it, and ask an accountant.
  • Publish refund, shipping, privacy and terms pages before the first sale.
  • Keep product data in one system, even with a custom storefront.

Pitfalls

  • Building a custom checkout for a standard store and spending months on what a builder already has.
  • Using another payment provider on Shopify Basic and paying 2% extra on every sale.
  • Free shipping everywhere without checking what heavy orders to far zones cost you.
  • Collecting sales tax without being registered, or not collecting where you must.
  • Stacking many paid apps until the monthly bill passes a higher plan's price.
  • A headless storefront that calls the store API on every page view and slows down under traffic.

Costs and obligations

These point to obligations to check; they aren't legal or tax advice.