Shopify, WooCommerce, or custom: choosing without regret

Most platform advice is written by people who sell one platform. This is an attempt at the other thing: what each option costs you, including the costs that appear in month eight rather than week one.

Answer these first

The platform decision is usually made by four facts about your business, not by a feature comparison.

1. 01How many products, and how do they vary? Twelve products with one option each is a different problem from 3,000 with five options each.
2. 02Who edits the store, and how often? Daily edits by a non-technical team is a hard constraint that rules things out.
3. 03Is content selling as much as the products? If people arrive through articles and guides, the content system is not a side feature.
4. 04Does checkout have to do anything unusual? Deposits, quotes, approval steps, split fulfilment. This single question decides more than the other three.

Shopify

Right when you are selling physical products and want payments, tax, fraud and PCI compliance to be someone else's problem. The admin is genuinely good, which matters more than most people credit: a team that will actually use the tool is worth more than a slightly better tool they avoid.

Wrong when your checkout needs to behave in a way Shopify does not permit. Checkout is the most locked-down part of the platform, and every workaround lives outside it. Also wrong when you are not really selling a catalogue, in which case you are paying a per-transaction fee for a product database.

The cost nobody quotes: apps. Five at $30/month is $1,800 a year, forever, and each one adds script weight to every page.

WooCommerce

Right when content is doing as much selling as the products. A large blog, buying guides, heavy organic search. Keeping the store and the content in one system genuinely simplifies things, and there is no cut on each transaction.

Wrong when you want to stop thinking about infrastructure. Woo is cheaper in fees and more expensive in attention: hosting, updates, plugin conflicts and security are yours. That is a fair trade if someone is going to own it, and a slow disaster if nobody is.

Headless and custom

Right when something about your product is genuinely unusual. A configurator, a pricing engine, a hybrid of commerce and application. Or when page speed is a competitive advantage rather than a score you want to feel good about.

Wrong most of the time, and it is worth being blunt about that. Custom is the most expensive answer and should be the last one considered. The failure pattern is a team that chose it for the architecture and then spent a year rebuilding admin screens the off-the-shelf platform included for free.

The costs that appear later

How to make the decision stick

Write down why you chose it, in one paragraph, with the assumptions it rests on. Then write down what would have to change for the answer to be different: catalogue over a certain size, a checkout requirement, a content strategy that does not materialise.

This takes twenty minutes and saves an argument two years later, when nobody remembers whether the decision was reasoned or inherited. It also means you can revisit it deliberately instead of migrating in a panic.

The honest summary

• Selling products, want it handled: Shopify.
• Content is the growth engine and someone owns the infrastructure: WooCommerce.
• Something about the product genuinely does not fit a catalogue: custom, and expect it to cost more than the estimate.
• Not sure: start with the platform. You can move later, and most people never need to.