E-commerceModule 1: The online-store modelLesson 2 of 11
Course progress9%
15 min lesson · Updated August 2026
How do you choose an e-commerce platform?
Choose an e-commerce platform by matching the business model, catalog, markets, payment and fulfilment needs, integrations, control, risk and long-term operating capacity—not by feature count alone.
What you will learn
By the end, you will understand:
Compare hosted, WooCommerce, marketplace and custom options
Evaluate total cost, portability and ecosystem dependency
Create a requirements-led selection process
Visual explainer
See the idea clearly.
1
✓
Business requirements for catalog, checkout, markets, integrations, control and operations are compared across hosted platform, WooCommerce, marketplace and custom commerce options.
Start with the operating model
B2C/B2B/subscription/marketplace
Physical/digital/service
Catalog/variant volume
Inventory locations
Markets/languages/currencies
Payments
Tax/shipping/returns
Accounts/roles
Integrations
Content/SEO
Reporting
Accessibility/security/compliance
Main platform routes
Route
Strength
Tradeoff
Hosted commerce platform
Integrated hosting, checkout, updates and app ecosystem.
Platform rules, subscriptions/fees, customization and portability limits.
WooCommerce/self-hosted
WordPress content flexibility, ownership and broad extensions.
Hosting, updates, plugin compatibility, performance and security ownership.
Marketplace
Existing audience and commerce infrastructure.
Fees, competition, limited customer relationship and policy dependence.
Custom/headless
Specific experience, channels and system integration.
High engineering, QA, security and long-term product ownership.
Feature lists hide workflow gaps
A platform may “support returns” but not the approval, warehouse, refund, exchange and accounting flow the business needs. Test realistic scenarios with actual roles and data.
Prioritize must-have workflows; distinguish native capability, extension, custom work and manual workaround.
Total cost of ownership
Subscription/hosting
Transaction/payment fees
Apps/extensions/licenses
Design/development
Content/data migration
Integrations
Accessibility/security QA
Operations/support
Updates
Internationalization
Exit/export cost
Downtime risk
Payments and compliance scope matter
Hosted payment pages or components can reduce direct card-data handling, but exact PCI DSS responsibilities depend on implementation and eligibility. Confirm with the acquirer/payment provider and qualified support.
Do not store raw card data unless the organization has the justified architecture and compliance capability.
Run a proof of concept
01
Define must-have scenarios
02
Create representative catalog
03
Configure one market/payment/shipping flow
04
Test staff workflow
05
Test customer task/accessibility
06
Validate integration/data export
07
Model cost/risk
08
Decide with evidence
Real-world example
Example: a cheap plan becomes expensive
Example
A wholesaler chooses a low-cost hosted plan, then discovers it needs account-specific pricing, purchase orders and approval. Apps and manual work exceed the price of a suitable B2B route. A scenario proof would have revealed the gap.
Try this
Test five real scenarios
Write five must-complete journeys—such as variant purchase, partial return, out-of-stock, international tax/shipping and data export. Evaluate each platform using evidence, not sales labels.
Common questions
Questions beginners ask.
What is a hosted e-commerce platform?
A service providing commerce software, hosting and managed infrastructure under platform terms.
What is WooCommerce?
An open-source commerce plugin for WordPress that requires hosting and operational maintenance.
Should a business sell on a marketplace?
It may provide useful reach, but fees, policy dependency, competition and customer-data limits should be considered.
What is headless commerce?
An architecture separating the customer-facing experience from commerce back-end services through APIs.
Which platform is best?
There is no universal best; fit depends on model, workflows, markets, risk, resources and ownership.
Can platforms be migrated later?
Yes, but products, customers, orders, URLs, content, subscriptions and integrations make migration costly.
Does hosted checkout remove PCI responsibility?
It can reduce scope, but eligibility and remaining duties depend on the exact implementation and program requirements.
Should app count influence selection?
Only insofar as maintained extensions solve required workflows safely without excessive dependency.
