Compare hosted and self-managed stores by the work you can own

The important difference between hosted and self-managed stores is where responsibilities sit. It is not a division between professional and amateur businesses. Either approach can fit a small merchant when the work, access and costs are understood.

Start with the responsibilities your business can reliably own. Then compare proposals against that list, rather than choosing a label and hoping the operational details follow.

Draw three layers

Separate the storefront into infrastructure, software and merchant operations.

Infrastructure includes the environment that runs the site and the arrangements for availability and recovery. Software includes the storefront, extensions and custom changes. Merchant operations include product accuracy, fulfilment, payment investigation and customer support.

A hosted service may take substantial responsibility for the first layer, but that does not transfer the merchant's promises to customers. A self-managed store may use an external maintainer for technical work, but that arrangement needs a contract and continuing access.

Avoid treating “self-managed” as a requirement to do every technical task personally. The question is whether your business coordinates and funds those tasks.

Record what is included, not what the label suggests

Ask each provider to complete the same responsibility list. Who applies updates? Who checks a failed order? Who restores deleted information? Who pays for additional storage or tools? Who controls the domain?

Mark each answer as included, extra-cost, merchant-owned or unresolved. An unresolved item is not automatically a defect. It is work that must be assigned before the shop depends on it.

For example, a hosted provider might support its checkout but not the seller's courier account. A maintainer might update software but not enter product data. These can be reasonable boundaries if everybody understands them.

Build an absence test

Imagine that the person who usually handles the store is unavailable for a week. Another authorised person should be able to identify new orders, find the support contact and understand which changes are safe to make.

This is not an invitation to share passwords. Use the access controls and recovery methods available in the chosen service.

A one-person business can keep a private operating note identifying accounts, renewals and escalation contacts. Store secrets in an appropriate credential manager, not inside an ordinary handover document that may be emailed around.

Distinguish convenience from dependency

Convenience is useful when a provider completes a task predictably. Dependency becomes risky when only that provider can explain or recover the store and no exit process exists.

Ask what you can export and what an export actually contains. Product text is not the same as photographs, customer consent records or historical order detail. A downloaded file is not proof that another system can use it.

For self-managed proposals, ask whether the business owns the hosting and administrative accounts. For hosted proposals, examine cancellation, data access and support arrangements. Do not assume either model has a perfect exit merely because it permits an export.

Compare normal work and exceptional work separately

Normal work might include updating stock, adding products and answering order questions. Exceptional work might include resolving a broken integration or moving the store to another supplier.

A merchant with a stable catalogue may need little daily technical help but still require an effective incident process. Another merchant may constantly change product configurations and need frequent implementation support.

Write down the last few changes you actually made in your business. Use those examples in the comparison. Speculative future features should not outweigh current work unless there is a credible plan to use them.

Use a small responsibility rehearsal

Give each shortlisted provider a fictional scenario: a buyer sees an unexpected total after changing a delivery option. Ask who receives the report, what evidence they request and how the merchant learns the outcome.

Do not send real customer details to a sales demonstration. The exercise is about the support path, not diagnosing a live incident.

An answer that distinguishes order status, payment status and delivery calculation is more useful than a promise that issues are “handled instantly.” Request written limits where response times or service commitments matter.

Make costs comparable

Include ongoing support, required tools and renewal terms alongside the initial setup charge. Keep business labour visible even if you do not assign it a monetary value.

A cheaper subscription may require more manual administration. A larger maintenance quote may include services another proposal excludes. Compare the same boundary before deciding one option is expensive.

For the numerical side, use a twelve-month store cost sheet. Treat forecasts as scenarios, not promises of future sales.

Choose the arrangement you can sustain

The best arrangement is the one whose responsibilities remain covered during ordinary weeks, busy launches and someone's absence. Record the unresolved work and solve it before relying on the store.

Revisit the decision when your team or catalogue changes. You can change who maintains a store without necessarily changing the platform, and you can change platforms without solving a weak operating routine.