Start an online store without choosing the software first
We may earn a commission if you buy through links on this page. How we make money
A practical planning guide from SoloOps Stack, an independent, affiliate-supported review site.
Before comparing platforms, describe what your store needs to do. Not the store you might run one day: the first useful version you are prepared to maintain alongside your freelance work.
This guide gives you a working brief, a cost checklist and an order rehearsal. Use them on their own, whether or not you read a review or follow a commercial link.
1. Write a one-sentence store brief
Complete this sentence:
“I want to sell [specific product] to [specific customer], take payment in [currency], and deliver it by [method].”
Keep the description concrete. A downloadable template, a short course and a parcel of printed stationery create different planning questions. Your job at this stage is to identify those questions, not force every future idea into the first launch.
Your first-page brief
| Question | Your answer |
|---|---|
| What is the first product or tightly defined product range? | ______ |
| Who is it for, and what information will they need before buying? | ______ |
| Is delivery a file, course access, a parcel or a manually delivered service? | ______ |
| Where will you initially accept orders? | ______ |
| Which currency will you display and accept? | ______ |
| Who will answer an order enquiry when you are doing client work? | ______ |
If an answer is unclear, mark it as a decision to make. A platform subscription is not a substitute for that decision.
2. Map one complete order
Draw the buyer's route on paper:
Product information → payment → confirmation → delivery → help if something goes wrong.
For each stage, write down what the customer sees and what you must do behind the scenes.
- Product information: contents, options, limitations and a clear description of what is being purchased.
- Payment: the intended method, currency and information the customer needs before confirming.
- Confirmation: what was ordered and what happens next.
- Delivery: who supplies the item or access, and how you will check that it happened.
- Aftercare: how an enquiry, failed delivery or refund request will be handled.
This is a planning exercise, not a claim that any particular platform includes every step automatically.
3. Separate must-haves from preferences
Make two lists before looking at a feature table.
Must-haves are requirements that would stop the store working for your intended offer: perhaps a particular payment method, a required product option or a delivery process you cannot change.
Preferences are things you can simplify: a decorative page effect, an additional channel you do not plan to use yet or a reporting view you can live without.
Use a short evidence sheet:
| Requirement | Included in the exact plan? | Official source and date | Still needs checking? |
|---|---|---|---|
| ______ | ______ | ______ | ______ |
| ______ | ______ | ______ | ______ |
| ______ | ______ | ______ | ______ |
A similar feature name is not enough. Ask what it does in your actual scenario and whether the relevant plan includes it.
4. Build a complete cost sheet
List the following before committing:
- The standard subscription after any introductory period.
- Whether billing is monthly, annual or another commitment.
- The currency charged, rather than your own rough conversion.
- Applicable tax or VAT treatment for the purchase.
- Domain purchase or renewal, where relevant.
- Hosting, where it is not included.
- Any theme, extension, app or other extra tool you actually need.
- Payment processing and any separate platform transaction fee.
- Packaging, postage, storage or other delivery costs for your offer.
- Setup, maintenance or specialist help you decide to buy.
Leave an amount blank until it is verified. Do not replace it with zero just to make the comparison look complete.
Why the headline price needs context
Shopify's US Basic plan is listed at US$39/month on monthly billing and US$29/month equivalent with yearly billing. The UK page separately lists £25 GBP/month and £19 GBP/month equivalent with yearly billing. The lower annual equivalent is not a month-to-month subscription price. S1 S2
Systeme.io lists a Free plan, but its official help documentation also states a US$10,000 lifetime sales cap on Free before upgrading is required to keep accepting payments. Free does not mean that every capacity limit disappears. This is a product limitation, not a sales forecast. S3 S4
These examples were checked on 2026-11-06. They illustrate what to investigate; they are not a complete quote for your store.
5. Choose a platform category, then a plan
Use your brief to decide which route to investigate:
- A dedicated product store: compare the product, order and delivery workflow against your checklist.
- A focused funnel or course offer: check the funnel, email, course and access requirements you actually need.
- A store built around an existing website: investigate the complete setup, including hosting and maintenance responsibilities.
Do not choose a category because its marketing promises less effort. Choose it because you can explain how a complete order will work.
6. Rehearse the awkward situations
A polished home page is only one part of a store. Before launch, plan a controlled test using the vendor's permitted test tools or process, and confirm whether any live test purchase would incur fees.
Include the situations you would rather not discover through a real customer's complaint:
- A customer enters the wrong delivery information.
- A payment fails or the confirmation is unclear.
- A product option is unavailable.
- A file or course-access message does not arrive.
- You need to cancel or refund an order.
- Someone asks a product question while you are unavailable.
Write down the next action and who owns it. This checklist does not guarantee that every problem can be prevented; it gives you a way to identify gaps before relying on the setup.
Common pitfalls to avoid
Choosing annual billing before checking the workflow. Compare the commitment as well as the equivalent monthly amount.
Confusing “available” with “included”. Record the exact plan, relevant limits and any extra component.
Treating free software or a free plan as a full cost estimate. Complete the sheet, including delivery and payment costs.
Launching with policies you have not worked through. Get appropriate advice on your own customer terms, privacy, returns, tax and jurisdiction-specific obligations. This guide is not legal or tax advice.
Adding every future idea to the first version. Our suggestion is to start with a clearly defined offer and an order process you understand, then reassess additional requirements deliberately.
Your readiness checklist
- I can explain the first product and the customer it is for.
- I have mapped payment, confirmation, delivery and aftercare.
- My must-haves are checked against official sources for the exact plan.
- My cost sheet distinguishes unknown amounts from zero-cost items.
- I understand the billing term, currency and relevant limits.
- I have planned a permitted order and refund rehearsal.
- My customer information and operating responsibilities are ready for review.
You do not need to pick a platform from this page. If the brief is still unclear, finish that first.
Want help with the shortlist?
related affiliate-supported guides:
- Read the independent Shopify review if you are investigating a dedicated store.
- Compare four ecommerce routes for freelancers if you want alternatives.
- Compare Shopify with Systeme.io if the choice is between a shop-first and a funnel-and-course-first setup.
These guides contain commercial product links. Their role is to support a decision, not to promise business results.
Sources
Source markers in the copy point to the official sources below. Access dates record research, not a guarantee that a price remains available.
This site is designed to use affiliate links. When an approved affiliate relationship is active, I earn a commission from qualifying purchases made through those links.
- S1 — Shopify US plan names, monthly/yearly prices, hosting, SSL, staff accounts, checkout and payment fees — https://www.shopify.com/pricing — accessed 2026-11-06. Live US/USD pricing page; no overall publication/update date shown. A separate finance footnote is dated 2026-11-04, but that is not a date for the whole pricing table. Finance and promotional claims are not used.
This site is designed to use affiliate links. When an approved affiliate relationship is active, I earn a commission from qualifying purchases made through those links.
- S2 — Shopify UK/GBP plan prices and regional payment-fee examples — https://www.shopify.com/uk/pricing — accessed 2026-11-06. Live regional pricing page; no overall publication/update date shown. GBP figures are displayed UK prices, not currency conversions.
This site is designed to use affiliate links. When an approved affiliate relationship is active, I earn a commission from qualifying purchases made through those links.
- S3 — Systeme.io plan names, monthly USD prices, contacts, funnels, courses, email sending and platform transaction-fee statement — https://systeme.io/pricing — accessed 2026-11-06. Visible FAQ says last updated April 2026; public JSON-LD says dateModified 2026-10-20. Both are within the last 12 months. USD is verified in the official page's Offer.priceCurrency fields. The main comparison grid returned null values; only readable FAQ and matching structured-data facts are used. Conflicting student-limit statements are not used.
This site is designed to use affiliate links. When an approved affiliate relationship is active, I earn a commission from qualifying purchases made through those links.
- S4 — Systeme.io Free plan lifetime sales cap and need to upgrade — https://help.systeme.io/article/1509-how-systeme-io-subscription-plans-are-moderated — accessed 2026-11-06. Updated 2026-10-07; within the last 12 months. States a US$10,000 lifetime sales cap. The pricing-page JSON-LD agrees on the cap but describes a three-day upgrade window, while this help page describes payment pages stopping at the cap. Exact enforcement timing is not asserted.