Who Should Build My Store, and How Do I Choose a Platform?
Ecommerce platform choice is a store’s first and most lasting decision: the wrong platform returns two years later as a migration bill. So what should decide it? 🔎
Short answer: not feature lists but portability and integrations. Do payments, shipping, accounting and marketplace links work, and can you export your data at any moment — those are the real questions.
Below: the platform types, the selection criteria, who should do the build, and the red flags. 🎯
What platform types exist?
Ecommerce platform choice moves along three roads, each with its own strength and risk.
Hosted package, open source, custom build
Hosted package: fast to start, paid monthly, limited flexibility. Open source: flexible and yours, needs technical upkeep. Custom build: full control, highest cost — unnecessary for most SMEs. 🧩
What are the selection criteria?
Feature lists are long; the decision comes down to three criteria.
Integrations: payment, shipping, accounting, marketplace
These aren’t “nice to have” but required for the business to run. Without shipping integration you print labels by hand for every order; without an accounting link, month-end becomes a nightmare. A marketplace connection prevents stock chaos — the channel balance sits in the channel article. 🔗
Where do mobile and speed sit?
In the mandatory column. Most orders come from phones; a slow product page loses the customer before the basket. Test the demo store on your own phone.
Who should do the build?
Platform chosen; now the builder.
What are the red flags?
Some signals aren’t negotiable.
What belongs in the contract?
Three clauses protect you.
The three protective clauses
One: data and account ownership — store, domain, payments and customer data in the business’s name. Two: a delivery list — which integrations, how many products, which pages, is training included. Three: post-launch support scope and duration. A client asking for these three isn’t difficult; they’re experienced. Setup steps sit in the setup article, all questions in the 18-questions hub. 📜
📝 Field Notes
One client spent two months comparing platforms and sold nothing in those two months. We eventually opened on an ordinary hosted package and put the weight on product pages; sales started. What grows a store isn’t the platform but explanation and delivery. ⏳
📖 Quick Glossary
Portability: being able to export product, order and customer data. Integration: payment, shipping, accounting and marketplace connections. Admin access: the right to manage the store. Payment setup: takings flowing into the business’s own account.
⚡ Quick Summary
Choose on portability and integrations, not features. 🔑 A hosted package suits small stores; the difference lives in product data. Avoid providers who set up payments through their own account. Put ownership, delivery list and support in the contract.
🎯 Next Step
Let’s pick the right platform for your needs in fifteen minutes — no paying for features you’ll never use: the quote page. Scope on the ecommerce consulting page. ⚙️
Frequently Asked Questions
Sık Sorulan Sorular
At the start, a hosted package or a solid open-source setup is enough. The real difference isn’t in the platform but in product data and operations. A store that spends months choosing a platform spends those months not selling. ⏳
The most critical question. Can products, orders and the customer list be exported? If not, your store lives inside the platform rather than belonging to you. The reasoning sits in the management article. 🔑
Check whether the stores they built are still standing: are product pages complete, is the site fast, is checkout short? Not everyone who builds websites builds stores; ecommerce demands operational knowledge. 🧭
This is where projects stall most. Who uploads, where the photos come from, who writes descriptions — it must be written into the quote by name. Without that line, the project freezes on product data; details in the quote article. 📸
Blocking data export, registering the domain in their own name, withholding admin access, and setting up payments through their own account. The last is especially dangerous: if your money flows into someone else’s account, the store isn’t yours. 🚩
A hosted platform gives speed and low maintenance at the start. As product count, custom integration needs or traffic grow, your own setup starts to make sense. Decide on today’s needs, but guarantee portability from day one.
Manageable when planned: products, orders and customer data are migrated and old addresses redirected. Unplanned migration costs search visibility and customers. That’s exactly why export capability matters in the first choice.
The business, in its own name, with takings arriving directly in the business account. An agency only assists with technical setup. Models where payments pass through someone else’s account carry both legal and commercial risk.
Source: MDN — web performance