WooCommerce on WordPress is the usual choice when content marketing and the catalog must live in one CMS: guides, a blog, and product pages that editors can ship without a release train. It is also the stack people search as “WordPress online store” or “WooCommerce development.” I treat it as a commerce system — cart, taxes, shipping, webhooks — not as a theme install with ten conflicting plugins.

This fits content-led brands, small catalogs that will grow, and teams that already have WordPress hosting and editorial habits. It is a weaker fit when you want a fully managed checkout with no PHP operations (look at Shopify) or when 1C is the system of record for every price (Bitrix or a custom API may be cleaner). I will say no to a plugin pile that cannot be updated.

What I do: theme or block-theme work that stays updateable, product types and variations, checkout fields, Stripe or PayPal (and regional gateways when you sell into specific countries), shipping classes, and a staging site that matches production PHP and object cache. Performance is part of the job: image sizes, caching, and not loading the world on every product page. Subscriptions, memberships, and B2B price lists are in scope when we name them in the brief.

Handover includes how to add products, what not to install, and a short runbook for backups and updates. Adjacent catalog SEO is on catalog SEO and merchant feeds. If you also need a fast brand site without the shop, that is marketing sites.

A first WooCommerce store with a clean catalog often ships in 5–10 weeks. Migrations from Shopify, OpenCart, or a spreadsheet need extra time for redirects and customer passwords — the full process lives on store migration and replatforming. We do not promise “two weeks, any plugin.”