Why starting with needs works
Platform websites are built to impress, and feature lists are long. If you begin by browsing them, you tend to end up wanting whatever looks most impressive rather than what your store needs. Starting with a written list of your own requirements flips the process: the business sets the terms, and the options have to meet them.
This is a practical, repeatable method. It takes an hour or two and can prevent a costly wrong turn. For the broader question of which families of platform exist, see the discussion of platform choice in the overview of the whole decision.
Step 1: Describe the business in plain terms
Write a short paragraph answering:
- What do you sell, and roughly how many products?
- Where are your customers, and where will you ship?
- How do you expect orders to arrive: a few a week, or many a day?
- Who will manage the store, and how technical are they?
- What is your realistic budget for setup and monthly costs?
Keep it specific to the next year or so. Guessing at a distant future usually produces a list that is both expensive and wrong.
Step 2: List requirements in categories
Work through the areas of a store and note what you need in each. Typical categories:
- Catalog. Product variants, digital files, bundles, subscriptions, bulk upload
- Checkout and payments. The payment methods your customers expect, guest checkout, saved details
- Shipping. Rate options, label printing, local pickup
- Taxes. Support for the tax rules where you sell, which vary by place
- Marketing and search. Editable page titles and addresses, discount codes, email connections
- Design. Mobile-friendly templates and control over the look
- Content. Pages, a blog if you plan one
- Reporting. Sales and customer reports
- Support and reliability. Documentation, help options, uptime expectations
- Exit options. Exporting products and customers in common formats
Not everything will apply. A store selling one digital product has very different requirements from one shipping fragile goods abroad.
Step 3: Sort into must-have, important and nice-to-have
This step does the most work. Be strict about “must-have”: a requirement belongs there only if the business cannot operate properly without it. Everything else gets a lower rank.
A quick test: if a platform lacked this feature, would you walk away from it? If yes, it is a must-have. If you would work around it, it is important or a nice-to-have.
Be wary of requirements you only want because someone else has them. Ask what problem each one solves.
Step 4: Assign weights
Give each requirement a weight that reflects its importance. A simple scale works well:
- Must-have: 5
- Important: 3
- Nice-to-have: 1
Must-haves also act as a filter. An option that fails one outright should usually be dropped, whatever its total score.
Step 5: Score the candidates
Pick two to four candidates. For each requirement, give each option a score from 0 to 2, where 0 means it does not meet the need, 1 means partly or with a workaround, and 2 means fully. Then multiply by the weight and add up.
Here is a small, hypothetical example with three requirements and two candidate platforms:
| Requirement | Weight | Option A score | Option B score |
|---|---|---|---|
| Product variants | 5 | 2 | 2 |
| Local pickup | 3 | 1 | 2 |
| Built-in blog | 1 | 2 | 0 |
Option A: (5 × 2) + (3 × 1) + (1 × 2) = 10 + 3 + 2 = 15. Option B: (5 × 2) + (3 × 2) + (1 × 0) = 10 + 6 + 0 = 16.
The totals are close, which tells you something too: the choice may come down to cost, ease of use or support rather than features. The numbers here are invented purely to show the arithmetic.
Step 6: Add cost and effort
Features are only one side. Add the total cost of ownership for each candidate: subscription or hosting, payment fees, add-ons you would need, and the time or money for setup. Compare these against the budget you wrote in step 1, and against your expected profit margin, since fees that look small can matter on thin margins.
Step 7: Verify, do not assume
Marketing pages can be vague, so confirm claims yourself:
- Use free trials or demos where available
- Add a few real products and run test orders, including a payment, a shipping choice and a tax calculation
- Check the documentation and support options
- Read the terms about data ownership and cancellation
- Try exporting data, to see how portable it is
Treat a requirement as met only after you have seen it work.
Keep the list alive
Your requirements will change as the store grows. Save the list and revisit it once a year, or when something starts to feel limiting. If the gap grows large, you will already have a clear record of what you need when considering a move to a new platform. No scoring method removes uncertainty, but it makes the decision explicit, and that tends to produce better choices than going on impressions alone.