4Sales channels
Marketplace or Your Own Store: How to Choose a Starting Point
Choosing where to sell involves two decisions that are easy to mix up. A marketplace or an independent store determines where the customer shops. Managed hosting or self-hosting determines who operates the technology. You can run your own branded store on a managed service without managing a server yourself.
Decide what you need the channel to provide
A marketplace supplies an established shopping environment and a defined listing and checkout process. That does not guarantee visitors or sales for your particular listing. You still need accurate product information, suitable stock and a way to answer customers.
An independent store gives you more room to explain your brand and products, within the capabilities of the platform you choose. It also leaves you responsible for attracting visitors and building their confidence in an unfamiliar business.
In an illustrative example, a seller has three storage bags and six hours a week. Before choosing a channel, they write down the questions customers are likely to ask: dimensions, material, delivery and returns. The useful comparison is which arrangement lets them answer those questions and run orders reliably with the time available.
Compare the whole cost, not just the subscription
For Shopify, distinguish the plan subscription, any applicable third-party transaction fee and the payment provider's processing charges. They are different costs. Check the current plan details for your region and payment setup rather than adding a headline rate to an old example.
For a WordPress and WooCommerce store, include hosting, any paid extensions, backups and the work of maintaining the installation. WordPress.org provides open-source software; WordPress.com is a hosted service. The names are related, but they do not describe the same operating arrangement.
A low software price does not make maintenance free. Equally, paying for a managed service does not remove your responsibility for product content, account access or every store setting. Write down which tasks the chosen service actually handles.
Walk through a purchase before polishing the design
Start where a customer first sees the product. Can they find the dimensions and delivery information? If they have a question, who responds? Can they choose an appropriate payment method, and what happens if payment fails? Where will they find the returns instructions after delivery?
Assign an owner to each step, even when every owner is you. This exposes gaps that changing a theme cannot fix. For the three-bag example, preparing complete product pages and a clear support routine may be more valuable than adding another visual effect.
Choose the maintenance work you can sustain
A managed service can reduce infrastructure work, with trade-offs in configuration, customisation and platform dependence. Check the features you need, especially around checkout, permissions, exports and backups.
A self-hosted setup can provide more control, but updates, compatibility checks, security and recovery become part of the workload. A plugin installation is not a maintenance plan. Decide who will restore the site if an update causes a problem, and verify that the backups can actually be used.
Define what ready to launch means
Prepare the product information, delivery and returns terms, support contact and payment configuration. Use the provider's supported test mode to check the order flow and notifications. Test transactions simulate behaviour; they do not prove that real money reaches your account.
Before relying on live payments, verify an authorised small real transaction and its order status, receipt and settlement. Treat that as a separate check from sandbox testing. Keep the result and any unresolved task in your Workspace notes. Launch readiness is a working customer journey, not simply a finished homepage.