Choosing an e-commerce platform: hosted, open source or marketplace

Tuesday morning, a meeting room: the founder asks, "We need an online store — which platform is best?" One person argues for a hosted package, another for open source on the company's own server, a third says "let's start on a marketplace." All three are right inside their own frame, because nobody is answering the same question. Until you have settled how many products the catalog holds, who packs the orders and who can safely touch a server, "the best platform" does not exist.

This piece treats the platform decision not as a feature-list contest but as a question of who carries which responsibility. We open up the three main paths — hosted package, open source on your own server, marketplace — plus the fourth reality most businesses arrive at, then the criteria that decide the case, ten questions to answer before you sign, and the mistakes we see most often.

Hosted packageOpen sourceMarketplaceHybrid for mostYour sales model

"Which e-commerce platform is best?" is the wrong question

Platform selection looks like a technology question and behaves like an operations question. The same software can be perfect for a boutique shipping a few orders a day and punishing for a wholesaler processing hundreds. The difference sits in your variant count, your returns flow, your accounting connection, and what your team can genuinely do.

The real question splits into four. How many products and variants will you manage? How does your operation run — stocked goods, made to order, or services? Who owns the technical work? How fast do you plan to grow over the next two years? Honest answers shorten the shortlist on their own. Where you sell is a separate call, covered in our piece on your own store versus a marketplace; here the focus is who carries the weight underneath.

Three main paths and a fourth reality

The hosted package (SaaS)

A ready-made store you rent, where setup and maintenance belong to the provider. Servers, updates, security patches, backups and usually the payment connection come inside the package, so your attention goes to products, prices, content and orders. In exchange, flexibility has walls: you customize as far as the provider allows.

Open source on your own server

You install a store whose code is open to you, run it yourself and change anything — theme, checkout, shipping rules, dealer pricing. In exchange, updates, security, performance and backups become your job. "The license is free" does not include maintenance, and how that math lands is worked through in our comparison of open source versus commercial software.

Selling on a marketplace

Instead of building a store, you list inside a marketplace that already has traffic. Storefront, search, buyer trust and usually checkout arrive finished; your job is product data, price, stock and on-time delivery. In exchange the platform sets the rules and keeps most of the customer relationship. That channel's daily operation is walked through in our guide to selling on a marketplace.

The fourth reality: hybrid

What we see most often is none of the three alone but a blend: the brand's own site plus one or two marketplace storefronts. The site carries brand, content and customer ownership; the marketplace carries volume and discovery. Hybrid turns "which one" into "which one carries what," on one condition: stock and orders must meet in one place, or the channels will sell each other's inventory.

The real decision: which work are you taking on?

Rather than comparing feature lists, ask one question: when the site is down at midnight, whose phone rings? Here is how responsibility typically falls.

Responsibility	Hosted package	Open source	Marketplace
Version updates	Provider	You	Platform
Security patching	Provider	You	Platform
Payment setup	Mostly ready	You build it	Platform
Performance	Limited control	Entirely yours	Platform
Backups	Provider	You	Platform
Customization	Bounded	Nearly unlimited	Almost none
Customer data	Yours via export	Entirely yours	Restricted

Every "you" cell is a cost and a risk; every "provider" cell is a convenience and a dependency. Balance the columns against the capacity your team actually has, not the one it wishes it had.

Choosing an e-commerce platform is not buying software. It is deciding which jobs land on your own team's desk tomorrow morning.

Catalog complexity: not the product count, the rule count

Most teams size a catalog by the number of products, but what strains a platform is rules, not counts. An apparel brand with size and color combinations runs a few hundred products and several thousand variants; a food business needs batches and expiry dates; a parts supplier needs vehicle compatibility.

So take the three hardest products in your catalog and build them in the candidate for real. If the variant matrix, bundles, barcodes, units and minimum order quantities go in comfortably there, the rest will follow — and if they do not, the pretty product card in the demo will not save you. One back-office record for variants, stock and barcodes is what keeps inventory honest behind every order.

Are you selling B2B or B2C?

This single question eliminates half the shortlist. On the B2C side, cart, campaigns, coupons and fast checkout decide it. On the B2B side you need dealer price lists, running accounts and credit limits, tax-inclusive or exclusive display, ordering from a quote, minimum quantities and case multiples. Many hosted packages were built for B2C, and imitating dealer logic with add-ons produces a fragile stack.

If most revenue comes from dealers, a closed ordering portal often beats a public storefront; we show how to build one in our piece on the B2B dealer order portal. If you do both, make sure one platform carries two pricing logics without duct tape.

Languages, currencies and selling abroad

Selling only domestically today does not mean the platform should assume that forever. Cross-border selling asks for three capabilities: language (not just the interface, but product copy and URL structure), currency (pricing, exchange rates, refunds), and delivery with customs rules. "Multi-language supported" is not the same as separate product copy, meta tags and address structure per language. So ask plainly: is a second language a setting, or a second store? If it is the second and export is on your roadmap, price that in now.

Do not leave integrations for last

The most expensive mistake here is postponing integrations with a casual "we'll sort that out later." A store is not an island; orders have to flow into accounting, shipping, marketplaces and the CRM.

• Accounting and invoicing: If invoices are typed by hand at order close, that becomes somebody's full-time job as volume grows.
• Shipping and delivery: If labels, tracking numbers and return records are not automatic, every campaign peak locks up the warehouse.
• Marketplace connection: Running hybrid, stock and price must sync both ways; one-way transfer leads straight to overselling.
• Customer relationships: When order data never reaches the CRM, you lose who bought what and who asked what, and repeat business becomes accidental.

Building the relationship behind the order is covered in our guide to e-commerce and CRM integration. In Rocketly, WhatsApp, Instagram, Telegram and email land in one shared inbox, with the order and the balance on the same record. Your site also carries legal obligations; we collected them in our piece on legal requirements for e-commerce sites. Rules change, so confirm the current position with your accountant or lawyer.

Design, content and SEO control

Search traffic is cheaper growth than advertising over the long run, but only if the platform hands you control. Check concrete things: can you set the URL structure, edit title and description tags page by page, create redirects yourself, and touch images and code for page speed?

On a marketplace nearly all of that belongs to the platform: your page lives inside its architecture and your visibility follows its ranking logic. On your own site, the blog, the guides and the category copy are yours. Starting from zero? Our guide to starting an online store places this decision inside the bigger picture.

Team skills, support and total cost of ownership

Open source is powerful when "my own team runs it" is true, and the most expensive path available when it is not. Answer honestly: who applies server updates, how fast a disclosed vulnerability gets patched, and what happens when the one capable person resigns? In a hosted package those questions belong to the provider, and the price of that comfort is living inside their limits.

Do not think about cost as a single line either. Subscription or license, setup and development, themes and add-ons, maintenance, support, training — and the least visible line of all, downtime risk. A single day of lost access can cost more than any other item. That calculation is laid out line by line in our piece on total cost of ownership, and the logic transfers directly to e-commerce.

Data ownership, migration and an exit plan

Nobody thinks about leaving while choosing, but a good decision accounts for the exit. Can you export products, customers, orders and content in a standard format? Does invoice history travel? If your address structure changes, can you set up redirects? Without those answers, today's choice will hold you in place a few years from now; our piece on vendor lock-in and data portability shows how to measure that risk.

In a migration what suffers most is not data but the value accumulated in search. When product addresses change, old links break, and a move without a redirect plan costs months of traffic. Schedule it for a quiet period, map old addresses to new, and test payment and shipping with a real order first.

Answer these before you choose: ten questions and three classic mistakes

Work through the list below out loud, as a team. Every item you cannot answer comes back as an invoice after the contract is signed.

1. How many products and variants in two years?
2. Is your main buyer an end consumer or a dealer?
3. How many different pricing logics do you run?
4. Which accounting and shipping systems must you connect?
5. How many languages and currencies will you need?
6. Do you control the URL structure and meta tags?
7. Who will own the server and security work?
8. How does support work, and how fast does it respond?
9. In what format can you export your data?
10. If you wanted to leave, how long would that take?

Three mistakes we see most

First, choosing for today's product count: a platform that fits now becomes a cage exactly when sales climb. Second, falling in love with the demo — the store in a sales presentation is always clean, fast and thinly stocked, never tested against the real mess of your catalog. Third, leaving integrations for last: a store with no working accounting or shipping connection is technically alive and operationally a burden.

The right platform is not the one with the longest feature list; it is the one that leaves your team a workload it can genuinely carry. The next step is turning every order into a relationship — you can create a free Rocketly account and bring orders, messages, quotes and balances into one place.