Custom ecommerce or Shopify: what are you actually buying?

Start with the selling process

A distinctive design is not, by itself, a reason to commission a bespoke commerce system. Start by writing down how you sell: the products and variants, the purchase choices, how orders are fulfilled and what customers need to manage after paying. Those answers do more to choose the platform than a list of visual references.

For a straightforward catalogue and familiar checkout, we would first consider an established commerce platform. Custom development becomes worth discussing when the buying experience or the business process needs behaviour that the available tools do not fit well. A useful proposal explains that difference in concrete terms.

There are three different routes

A conventional Shopify store uses its storefront and commerce administration together. You can adapt the design and use compatible apps for additional functions. Before assuming an app covers your requirement, walk through the actual customer journey and the work your team will do in the admin.

A custom storefront can still use Shopify behind the scenes. Shopify calls this headless commerce: the public interface is built separately, while its commerce backend and checkout remain part of the system. Custom design and a platform backend are therefore not opposites.

A bespoke store with a payment provider such as Stripe is a different scope. You are commissioning the storefront and the agreed commerce behaviour around payments. Specify who supplies the catalogue, order records, customer management and operational tools. A payment integration alone is not a complete store.

Subscriptions need an operating plan

Subscriptions are available through Shopify subscription apps as well as custom builds; they are not a reason on their own to reject a platform. Check the supported payment methods and sales channels against your intended setup before choosing an app or architecture.

Then write down the rules: delivery interval, recurring price, how a customer cancels, what happens after a failed payment and who handles a change of address. Ask the builder to demonstrate those paths alongside a successful first purchase. Your fulfilment team needs to know which orders to send, and your customer needs to know what they have agreed to.

A real example: HairKhair

Our HairKhair build is a custom storefront for a focused hair-supplement brand. The scope includes Stripe payments, one-off and subscription options, and simple store analytics. The cream and lavender design keeps the product and its daily ritual at the centre of the experience.

At the time of writing, the public site is a pre-launch first look. This is an example of the design and commerce scope we delivered, rather than evidence of sales performance. It shows the questions a small catalogue still raises: how the product is explained, how purchase choices are presented and what the business needs behind the page.

Compare the complete cost

Ask each supplier to separate the build, platform or hosting charges, paid apps, payment processing, ongoing support and future changes. A low build quote that excludes order administration is not directly comparable with one that includes it. Equally, owning custom code does not make maintenance disappear.

Ask who controls the domain, payment account, repository and product data. For any platform, establish how records can be exported and what remains available if you change developer. For a bespoke build, include documentation and deployment access in the handover, with the responsibilities written into the proposal.

The brief to send a developer

Send a sample product with its variants and purchase options, the countries you will sell to, your fulfilment process, any existing systems and the launch constraint. Add the customer actions that matter after checkout. That gives a developer something concrete to assess rather than a request for an attractive shop.

We can review that brief through our custom ecommerce development service. The useful first outcome is a recommendation about what to build and what to use off the shelf, followed by a defined scope if a custom build fits.