I have worked with open-source e-commerce sites and platforms including Volusion, Magento, and Shopify. I have also built websites with Dreamweaver. Working across those different tools gives me a useful starting point: the name of the platform does not tell me whether it is the right fit for a particular business.
Before I would recommend one, I want to know what the business sells, how customers buy it, and what happens after an order comes in. A storefront is only one part of that process. The people running it have to live with the rest.
Start with the catalog and the order
Ten straightforward products create a different problem from thousands of items with variants, compatibility rules, and changing stock. A subscription, a custom quote, and a one-time purchase also have different requirements. I would write down the real cases rather than choose a platform from a feature count.
Consider a hypothetical shop that sells both online and at a counter. I would ask where inventory is maintained, what happens when the last item sells in person, and how returns update the records. These questions reveal integration needs that a beautiful storefront preview will not show.
| Question | What I would verify |
|---|---|
| What are you selling? | Products, variants, subscriptions, and custom-order rules. |
| How will orders work? | Payments, shipping, fulfillment, returns, and stock updates. |
| Who will run it? | Editing tasks, staff access, training, and support. |
| What must connect? | Accounting, inventory, physical sales, and other business tools. |
| What happens later? | Ongoing costs, maintenance, data export, and migration options. |
Walk through an ordinary working day
I would want to see how someone adds a product, changes a price, fulfills an order, processes a refund, and answers a customer question. A system can be flexible for a developer and awkward for the person who needs to use it every morning.
That is why I would test representative tasks early. Put a real variant structure into a trial catalog. Check the information staff need on an order. Confirm that shipping and payment options fit the business. Requirements can depend on the plan, region, provider, or extension, so they need to be verified against current documentation.
Shopify's launch checklist, for example, provides a useful list of setup and testing tasks for its platform. It is a starting reference, not a substitute for checking the store's particular requirements.
Be clear about who owns the ongoing work
A hosted platform and a self-managed system distribute responsibility differently. With any option, I want a clear answer about updates, backups, access, extensions, and support. I would verify the actual service agreement instead of assuming that “managed” means every possible problem is covered.
More control can be valuable, especially when a business has unusual requirements. It can also mean more work. Paying for convenience may be sensible if it frees someone to run the business. The decision depends on the needs, the available support, and the total cost of keeping the store useful.
Ask what custom development will buy
I would not recommend a custom storefront simply because it sounds impressive. If the standard experience can meet the requirement cleanly, that deserves a fair look. If a custom flow removes a specific obstacle or supports a genuinely different buying process, it may earn its cost.
The same applies to headless commerce, where the storefront is separated from the commerce backend. It can offer flexibility, but it introduces integration and maintenance decisions. Before choosing it, I would want a concrete requirement that the added freedom helps solve, plus a plan for who will maintain the connection.
Plan the exit before the move
If an existing shop is moving, I would inventory products, customer records, content, images, URLs, and external connections. I would then verify what can be exported, what can be imported, and what needs a separate migration process. Those details vary; I would never assume everything moves intact.
A migration plan should include redirects for important old addresses, a way to reconcile orders during the change, and checks on the new buying journey. I would test a representative selection of products and edge cases before treating the store as ready.
My aim is to choose a platform the business can sell through and operate confidently. The best recommendation is one I can explain in plain language: here is what you need, here is how this choice meets it, and here are the responsibilities that come with it.
