A lean first store using photos and copy you already have can open on a few hundred dollars of cash plus 30–60 hours of your own time. A freelancer build usually runs into the low thousands, and an agency launch into five figures. The gap comes from who does the build and how many assets you have to create. After launch, sales volume drives most of the cost: product, payment, packaging, delivery, and returns.

So a useful budget answers three questions: how much cash you need before opening, what one month costs to run, and whether each order leaves enough to cover the fixed costs. The worked example below answers all three for a fictional store.

Budget the first year, not the monthly plan

The platform price is one line. Use this equation:

First-year cash cost = launch cash + 12 × monthly fixed cash + order volume × variable cost per order

Then calculate an economic total by adding owner labor:

First-year economic cost = first-year cash cost + owner hours × an internal hourly value

You don’t pay the internal rate out of the bank account; it makes alternatives comparable. Use the value of an hour you could otherwise spend on product, customer service, or sales. Keep inventory working capital and tax or payout timing in a separate cash-flow view so they aren’t mistaken for economic cost or counted twice.

To run these numbers on your own inputs, use the online store launch budget worksheet. Keep a low, expected, and high value for every uncertain line until you have a written quote.

The eight cost groups to budget

1. Platform

The platform is a recurring subscription. What it includes varies more than the price does. Check whether the plan covers the storefront, catalog, cart, checkout, hosting, order management, and the sales volume you expect, and whether the store you have in mind also needs a separate theme, page builder, or paid apps. Those extras belong on this line too.

Don’t copy a promotional first-month price into a twelve-month budget. Use the normal price for your billing period and note the renewal date. If the plan price or a platform commission rises with sales, model it at your expected volume, not at zero orders.

2. Domain

A new domain creates an initial registration cost and usually an annual renewal. Premium names, aftermarket purchases, privacy services, and email are separate decisions. Enter the registrar’s current quote and, more importantly, the renewal price rather than copying a generic allowance.

Domain registration does not automatically include a branded inbox. If hello@yourbrand.com matters at launch, add the email provider as its own recurring line. Plan the technical work too: connecting the domain, checking DNS, and verifying the published site. The custom-domain and publishing guide explains that workflow.

3. Payment processing

Payment processing is variable, so calculate it from customer revenue and payment count rather than entering a vague monthly allowance:

Payment cost per order = amount charged × percentage fee + fixed fee

Use the current terms for the payment methods you expect customers to use. Refunds, disputes, international cards, currency conversion, and taxes can change the result. The amount charged is revenue; only the processing cost belongs on this line. Review the checkout and Stripe setup guide before treating the payment line as final.

4. Design and build

This line covers the work that turns the catalog and brand direction into a working store: page structure, homepage, category and product pages, navigation, mobile layouts, cart, checkout presentation, configuration, testing, and publishing.

It is also the line that varies most between build models. In DIY on a theme, the cash amount can be near zero while your hours pile up adapting the theme to your catalog. A freelancer may quote a fixed project, day rate, or hourly range. An agency may include strategy, design, development, project management, and quality assurance. Ask every provider to list what is excluded: “store design” often leaves out product entry, copy, photography, payment configuration, and changes after launch.

Then ask who makes the second change. A new collection, a seasonal homepage, or a corrected dispatch promise lands on this line again, either as your evenings or as a new invoice.

5. Product and brand assets

Budget for the inputs the store needs: logo files, colors and type references, packaging artwork, product photos, lifestyle images, image editing, descriptions, dimensions, prices, and usage rights. A store builder cannot turn missing product facts into reliable merchandising.

You can spend little if good assets already exist, or several thousand dollars on a shoot and identity work. Separate creating assets from uploading and arranging them. If someone else takes the photographs, agree in writing how the store may use them; the U.S. Copyright Office notes that the photographer is generally the initial copyright owner and that another party needs permission to use the photograph. Its official photography guidance was checked 31 August 2026. Use the product images and brand assets checklist to identify gaps before requesting quotes.

6. External help

External help may include a designer, developer, copywriter, photographer, bookkeeper, lawyer, or implementation consultant. Avoid one blended “freelancer” number. Give each person a deliverable, revision limit, deadline, and ownership handoff.

Also distinguish launch help from retained help. A $1,000 setup project and a $250 monthly retainer produce very different first-year totals. If an agency requires a maintenance agreement, place that agreement under recurring operations rather than hiding it inside the build.

7. Owner labor

Founders often omit their own work because no invoice arrives. Track catalog cleanup, product facts, photo selection, feedback, shipping and tax setup, payments, and order testing.

The owner cannot outsource every decision. Even with an agency, someone inside the business must approve claims, prices, margins, brand direction, and customer policies. Estimate hours by task, not with one optimistic total. The complete store-building guide is a useful basis for that task list.

8. Ongoing operations

After publication, allow for email, analytics, support tools, creative updates, apps, accounting, maintenance, and demand generation. Model product cost, packaging, fulfillment, carrier cost, payment fees, returns, and other order-driven costs beside revenue. Customer-paid shipping is revenue; carrier and packaging charges are costs. Their difference shows how much of delivery the merchant funds.

Keep fixed and variable costs separate. A $40 monthly tool costs $480 a year even with no orders. A payment fee rises with sales. That distinction makes the budget useful when revenue differs from plan.

One worked model, with every assumption exposed

This fictional USD example shows the arithmetic; replace every input with your own.

InputFictional value
Launch cash$2,020
Launch labor40 hours × $50 = $2,000
Monthly fixed cash$600
Orders per month60
Merchandise revenue per order$120
Customer-paid shipping$5
Product cost$52
Carrier + packaging$11
Payment cost2% × $125 + $0.30 = $2.80
Returns reserve + other variable cost$3
Monthly owner labor20 hours × $50 = $1,000

Contribution per order is $125 − $52 − $11 − $2.80 − $3 = $56.20. At 60 orders, monthly contribution before fixed cost is $3,372; after $600 of fixed cash cost, $2,772 remains. The monthly fixed commitment is covered at 10.68 orders, so the practical boundary is 11 orders. To recover the $2,020 launch cash over 12 months as well, the boundary becomes 13.67, or 14 orders per month.

The modeled first-year customer revenue is $90,000. First-year cash cost is $58,756: $2,020 launch cash plus 12 months of $600 fixed cash and $4,128 a month in product and variable costs. First-year economic cost is $72,756 after adding launch labor and 12 months of owner labor. Those large totals are not a storefront quote: product cost rises because the scenario also assumes $90,000 of customer revenue.

The model still needs the merchant’s real tax basis, inventory cash timing, payment mix, seasonality, returns, and business overhead. Do not multiply the total by a blanket tax rate. Enter each cost at the amount the business bears, keep revenue and order costs comparable, and model recoverable tax timing separately when it affects liquidity.

How the four build models compare

ModelBest fitMain cash costMain hidden cost or risk
DIY on a themeSimple catalog; capable founder; flexible timelinePlatform, theme, apps, domain, assetsOwner hours, now and for every later change
FreelancerDefined deliverables that one or two specialists can ownProject fees plus platformGaps between design, build, content, and ongoing ownership
AgencyHigh-stakes brand launch or complex coordinationStrategy, creative, implementation, management, retainersLarger commitment and dependency for future changes
Platform that builds the store (Setka)Product brand with its catalog and direction ready, without build capacityPlatform, assets, targeted outside helpYour launch requirements must fit what the platform supports today

Price every option against the same outcome: a complete store with real products, checked on a phone, with working checkout, payments, a connected domain, a test order, and a known way to make the next change. A cheap quote that ends at the homepage isn’t comparable with one that covers the whole path to purchase.

Setka is our product, and it is the last row. For a first store, it usually costs much less than the theme route. A theme-based store’s real price is the plan plus a theme, the developer or evenings spent adapting it, and the apps that fill its gaps. In Setka you bring the products and the brand direction, and Setka builds the store inside the platform: homepage, category pages, product pages, navigation, cart, and mobile layouts. There is no theme to buy or adapt, so the design-and-build line shrinks to your time writing the brief and checking the result.

The second change costs less too. You open a page, describe what should change, preview the new version, and publish it, and you edit exact wording directly. Every change saves a storefront-wide version you can return to. No theme code reaches you, so there’s no maintenance line for it. On the platform line, Setka’s price doesn’t rise with your sales; Stripe’s processing fees go on the payment line as usual. The difference between the two models is laid out in AI storefront vs. Shopify theme.

What stays yours in every model: product facts and photos, prices and margins, shipping and tax rules, and a real test order before launch. Current plans are on the pricing page.

Turn the model into your budget

Take five steps before committing:

  1. Define the launch boundary. List the products, markets, currencies, payment methods, shipping regions, pages, and brand assets required on day one.
  2. Inventory what already exists. Mark every usable product photo, description, logo file, policy, and catalog field. Missing inputs create real work in every build model.
  3. Request comparable quotes. Give platforms, freelancers, and agencies the same scope. Ask for exclusions, revision limits, renewal prices, and ongoing maintenance.
  4. Model one order, then volume. Enter merchandise revenue, customer-paid shipping, product cost, carrier cost, packaging, payment terms, returns, and other variable costs on the same basis.
  5. Test the boundary. Calculate contribution per order, monthly break-even, cash required before opening, and a case with half the orders. Value owner hours separately so an option that saves cash doesn’t pass for a cheap one.

If the plan only works at the expected volume, fix the price, the product cost, or the fixed costs before you pick a build model. If it works at half the volume too, fill in the launch budget worksheet with your real quotes, and enter Setka’s current plan from the pricing page on the platform line to see what removing the theme work does to your total.