Technote

Themes & plugins Practical

Series Turning the site into revenue Part 3 of 8

When you genuinely need a shop system

WooCommerce is a fine piece of software. It is also a great deal of machinery to maintain for a single one-off product. Start by naming what it actually buys you.

Once you decide to take payments, the next question is usually “so, WooCommerce?” The honest answer is that sometimes it is right and sometimes it is far too much. The software is not the problem; the size is.

What WooCommerce actually buys you

Give it a fair hearing first. A shop system already contains things that take a long time to build yourself.

What a shop system already has — a multi-product business needs all of it eventually

If more than half of that list applies to you, WooCommerce is a good choice. You get months of work as an installation, plus documentation and a large developer ecosystem behind it.

The cost of putting it behind one product

If what you sell is a single one-off service, the picture changes. Of that list you will realistically use “order states” — and everything else arrives anyway.

Conceptual — the gap between what you use and what you maintain. The real ratio varies by business

Concretely: shop tables are added to your database, product, order, coupon and report menus appear in the admin, and cart and checkout assets load on the front end. Attaching a payment method and a delivery option each brings another extension plugin, each with its own release cadence. Shop software updates frequently — which is a good sign of active maintenance — and each update is something to test before it goes live.

None of that is a defect. It is a question of whether the tool matches the scale. If you plan to add products, today’s spare capacity is tomorrow’s foundation. If you do not, it is simply weight.

Five questions to decide

Two or more of the top four means a shop system; the bottom two mean something smaller

When neither applies — the smaller build

One product, one fixed price, modest order volume: you need three things. An application form, an order record, and one payment method. The order record only has to carry a state — received, awaiting payment, complete — and the payment method is whichever of the next part’s options fits your customers.

The advantage of this shape is that it has few places to break. Less code to update, easier to trace when something misbehaves, and straightforward to migrate onto a shop system once the business grows. Going the other way — unpicking a shop system later — is considerably harder.

The relationship between plugin count and maintenance load is covered further in the Themes & plugins archive, and how we unpick an already-heavy site is published on our process page.

Next part

With the shape settled, it is time to actually take money. The next part covers payment options in the Korean market, where bank transfer, a domestic card gateway and overseas payment each demand quite different things of you.

More on this topic

All technotes

Themes & plugins Practical

Decide the editable regions before you design them

A design the CMS cannot express stays up for negotiation long after it ships. Deciding what editors may change, first, removes the negotiation entirely.

Designers 6 min read

₩270,000 · Join the program