Shopify, WooCommerce, or Custom: Choosing a Platform for a Book Store

Every platform comparison you read online is written by someone who sells one of the platforms. Here is the version written from the position of actually maintaining these sites for publishers afterwards, which is where the real differences show up.

What makes book retail different

Before comparing anything, it is worth naming why a bookshop is not a generic store.

Catalogues are large relative to revenue. A publisher with forty titles has forty products, each with several formats, and each needing structured metadata that most ecommerce platforms have no field for. ISBN, format, extent, dimensions, publication date, contributors with roles, and series relationships all matter to buyers and none of them are standard.

Shipping is disproportionately complicated. Books are heavy, dense, and shipped internationally more often than most product categories, and shipping cost frequently approaches the product margin.

Pre-orders are normal rather than exceptional, and they need to work properly, including partial orders where one item in a basket is not yet published.

Shopify

The strongest reason to choose Shopify is that it works and someone else maintains it. Payments, security, hosting, and PCI compliance are handled, and the checkout is genuinely better than most teams could build.

Where it constrains a publisher: the product data model has a limited number of custom fields before you are relying on metafields and apps, and it has a hard ceiling of three product options, which becomes a real problem for a title with format, edition, and signed variants.

Pre-orders and mixed baskets need an app. Complex international shipping rules usually need an app. Subscription or standing order arrangements need an app. Each app is a monthly fee and a dependency, and app costs on a mature publisher store frequently exceed the platform fee itself.

Choose it if your catalogue is under a few hundred titles, you sell direct to consumers, and nobody on your team wants to think about infrastructure.

WooCommerce

The strongest reason to choose WooCommerce is control. It is WordPress, so the content side is strong, custom fields are trivial, and the product model bends to fit books rather than the other way around. There is no transaction fee beyond your payment processor.

The cost is that maintenance is now yours. Updates, backups, security, and hosting performance are your responsibility, and a WooCommerce store that nobody has updated in eighteen months is a genuine liability rather than a mild one. Performance degrades noticeably with a large catalogue unless it is hosted and cached properly.

Choose it if you have significant editorial content alongside the shop, you need custom product data, and you have a developer relationship you can rely on continuously rather than occasionally.

Custom

Custom is right in a narrow set of circumstances, and it is chosen far more often than those circumstances occur.

It is justified when your business model does not fit standard ecommerce. Subscription publishing with tiered access. A large rights or licensing catalogue where the shop is one part of a larger system. Deep integration with a distributor’s systems. Selling digital and physical bundles with entitlement management.

It is not justified because you dislike the look of a theme, or because you want a specific checkout flow, or because you have been told the platform fees add up. The build cost is the smallest part of custom. The maintenance obligation is the real number, and it does not stop.

The question that actually decides it

Ask who maintains this in two years. If the honest answer is nobody in particular, choose the hosted platform, whatever else the comparison says. An unmaintained self-hosted store fails slowly and quietly, usually at checkout, and usually without anyone noticing until sales drop.

A practical middle path

For many publishers the best answer is a hosted store for commerce with a separate, well built content site for editorial and marketing, connected rather than merged. You get the reliability where money changes hands and the flexibility where the content lives, and neither system is being forced to do the job of the other.