How to choose an ecommerce platform

The right ecommerce platform is the one that matches how you actually sell, fulfil and administer orders — not the one with the loudest ads. Start with operations, then pick a cart. Feature checklists come last, because every major platform can “do” products, payments and shipping on paper.

This is the wider map: hosted storefronts, WordPress commerce, builders, custom or headless, and marketplaces versus your own store. When the remaining decision is Shopify versus WooCommerce, use the Shopify vs WooCommerce guide — that article owns the two-way comparison.

This is not a website cost article. Get operational fit right before you argue fees.

Questions to answer before you name a platform

Write short answers. If you cannot, you are not ready to choose software.

1. What is for sale? A few signature products, a large catalogue, variants (size/colour), made-to-order, bookings with deposits, wholesale, subscriptions, or a mix.
2. Who buys? Local pickup in Perth, Australia-wide shipping, both, or B2B accounts with price lists.
3. Who runs the store day to day? You, a shop manager, a marketing person, or an agency? Be honest about technical comfort.
4. Where does inventory live? Spreadsheets, a POS, a warehouse system, or “we will figure it out”.
5. What must the marketing site do besides sell? Journal, recipes, services, locations, education — content depth changes the CMS conversation.
6. What would make you migrate in two years? If the answer is “we will outgrow this in months”, do not pick it for a short-term saving.

Retail and ecommerce businesses in Perth also hit WA-specific friction: shipping time and cost expectations, click-and-collect, and not promising next-day anywhere when you fulfil from one warehouse.

A map of the main options

Treat this as a shortlist filter. Platforms change; your operations should not be rewritten to suit a demo store.

Hosted commerce (Shopify, BigCommerce, and similar)

You are renting a commerce engine. Hosting, PCI burden and many core primitives sit with the vendor. You pay a subscription, plus apps, plus theme work.

Fits when you want less server maintenance and a team that should not be patching PHP on a Sunday.

Watch for app sprawl, theme limits, and plan costs as you grow. Unusual catalogues or wholesale may need a higher plan, apps, or a different platform.

Shopify development is the hosted path we implement most often for Perth SMEs. BigCommerce can fit some catalogue or B2B models better; we will say so rather than force Shopify.

WordPress + WooCommerce

You are owning more of the stack. WooCommerce is a plugin (with an ecosystem) on WordPress. Hosting, updates, security and performance are yours — or your agency’s.

Fits when the marketing site and the store must share one editorial world, you already run WordPress well, or you need store logic that hosted carts make awkward.

Watch for plugin quality, cheap hosting, and the maintenance burden. This is why our Shopify vs WooCommerce article focuses on operations, not feature bingo.

See WooCommerce development when that flexibility is genuinely required.

All-in-one website builders with commerce (Squarespace, Wix, and similar)

Fits when the catalogue is small, design-led, and the owner wants one simple editor.

Watch for outgrowing payments, variants, reporting, or SEO control. Many migration projects we see are businesses leaving a builder because the shop became the business. Leaving is normal; leaving in a hurry during peak season is painful.

Custom and headless

Fits when the storefront is a product: unusual configurators, tightly coupled ERP, multiple channels with one catalogue, or performance constraints a theme cannot meet. That sits closer to web application development plus a commerce backend than to a theme install.

Watch for cost, time, and who maintains it. Custom should earn its complexity. Most Perth SMEs do not need it on day one.

Marketplaces (Amazon, eBay, Facebook/Instagram shops) versus your own store

Marketplaces are distribution. Your own site is brand, margins, and the customer relationship. Many retailers need both. A marketplace is not a platform strategy by itself: you still need product data discipline and a site that explains the brand when someone searches your name.

Australian operational fit (the unglamorous filter)

Whatever you pick, walk through real ops:

• Payments: cards, PayPal, and common AU instalment methods if you will actually offer them — only add what finance and support can handle
• GST and invoices: tax settings that match how you invoice, including GST-free items if you have them
• Shipping: Australia Post / couriers, WA regional surcharges, free-shipping thresholds you can afford, click-and-collect for Perth customers
• Restricted goods: age checks, dangerous goods, food — platform and app support varies
• Support hours: who answers “where is my order?” and from which inbox

A platform that cannot represent your real shipping rules will train customers to email you for everything.

Decision framework

Work top to bottom. Stop at the first clear answer.

1. Is commerce a side feature on a content-heavy site you already want in WordPress? Lean WooCommerce — then read the two-way comparison.
2. Is commerce the product, and you want less server ownership? Lean a hosted cart, usually Shopify for SMEs we see in Perth.
3. Is the catalogue or B2B model awkward on Shopify’s standard plans even after an honest app review? Evaluate BigCommerce or a scoped custom path before you drown in apps.
4. Is the catalogue tiny and the brand highly visual, with no appetite for ops complexity? A builder can be a valid v1 — with a written “we will migrate when…” trigger.
5. Are you selling unique configured goods or running software-like workflows around orders? Scope custom/headless; do not hack a theme into an application.
6. Are you mostly testing demand? Marketplaces or a minimal hosted store beat a six-month custom build.

If you are still on the Shopify/Woo fork after this, stop here and use the comparison article. Do not reopen the whole map.

CMS choice is a different article

People conflate “what the homepage is built in” with “what the cart is”. You can run marketing on Webflow or WordPress and still sell on Shopify. Split vs combined is an editorial choice. For CMS trade-offs see Webflow vs WordPress; for design vs build skills see web design vs web development.

Migrations: the cost of being wrong

Moving carts means products, customers, redirects, apps, staff retraining and a messy month of “the old link still works?”. Reduce that risk by:

• Not choosing on a friend’s store that sells a different thing
• Not choosing on theme demos with dummy products
• Budgeting photography, shipping rules and policy pages — not only the theme
• Planning SEO URLs for products and collections from the start

If you are already on the wrong cart, treat the move as a migration with a redirect map, not a theme swap.

What to send when you want a recommendation

A useful brief for us (or anyone honest) includes:

• Approximate product count and variant complexity
• POS or inventory system, if any
• Pickup vs ship vs both
• Who will administer orders and content
• Current platform and what hurts today

Request a quote with those notes. We implement Shopify and WooCommerce as distinct services because they are distinct operational bets — and we will tell you if you should not be on either yet. For examples of commercial sites, browse work.