crispfront.
All articles
Platforms··9 min

WordPress, OpenCart, or custom — pick the right tool for your business

Most agencies pitch the platform they prefer, not the one that fits your business. A straight-talk comparison of WordPress, OpenCart, and custom builds — when each wins, when each fails, and how to choose.

Three different agencies, three different platform recommendations. Sounds familiar?

That's because most agencies pitch the platform they're best at — not the one that fits your business best. A WordPress shop will tell you you need WordPress. A Shopify partner will explain why Shopify is the only sensible choice. A Next.js studio will write you a long argument about why "you're going to need custom anyway."

Here's an honest look at where each platform actually wins, where it actively hurts, and a framework for picking without being held hostage to anyone's preferences.

WordPress

The default choice for 43% of all websites worldwide. There's a reason.

What it's genuinely great at:

  • Content-heavy sites — blogs, news, service catalogs, marketing sites. The admin interface is the gold standard for non-technical people updating content.
  • Long-tail business sites — local services, B2B consultants, small manufacturers. You'll find a WordPress developer in any city if you need one in five years.
  • E-commerce via WooCommerce — 30%+ of all online stores run on WooCommerce. Mature payment integrations, shipping calculators, inventory management. Lower long-term cost than Shopify (no monthly platform fee, no transaction cut).
  • SEO — proper WordPress sites still dominate search results for non-trivial keywords.

What it actively hurts:

  • Speed without effort — out of the box WordPress is fine. WordPress with 30 plugins and a marketplace theme is heavy and slow. Requires deliberate care.
  • Modern interactive UIs — possible but painful. If your site needs heavy JavaScript interactivity (calculators, configurators, real-time dashboards), WordPress fights you.
  • Security if neglected — needs regular updates. Auto-update helps; checking it monthly is mandatory.

When WordPress is the right answer:

  • You'll have someone (you or a junior employee) updating content regularly
  • Your business is in a normal vertical (services, content, retail, small e-com)
  • You want to keep ongoing costs low (no platform monthly fees)
  • You may want to find another developer in the future without being locked in

OpenCart

The e-commerce specialist still popular in CIS countries and some EU markets, less common in US/UK.

What it's genuinely great at:

  • Complex catalogs — heavy product hierarchies, variants, attributes. OpenCart was built for stores; product management feels more native than WooCommerce.
  • CIS-specific integrations — out-of-the-box support for НоваПошта, ПриватBank, LiqPay, Fondy, 1C synchronization through readily-available extensions.
  • Storefront flexibility — multiple stores from one admin (useful for multi-brand or multi-currency businesses).

What it actively hurts:

  • Modern web standards — out-of-the-box themes can look dated. Requires custom theming for a modern feel.
  • Content marketing alongside the store — blog functionality is bolted-on, not native. If your store strategy depends heavily on content SEO, WooCommerce is friendlier.
  • Developer pool — smaller than WordPress. Fine in CIS, harder elsewhere.

When OpenCart is the right answer:

  • You're already on OpenCart and want to evolve, not migrate
  • Your business is pure e-commerce (not a content site with a store on the side)
  • You operate in CIS markets and benefit from the local payment/shipping ecosystem
  • You have a complex catalog where WooCommerce's product model feels limiting

Custom (Next.js / React)

Building from scratch on a modern JavaScript framework. Most flexible, most expensive, most rewarding when used appropriately.

What it's genuinely great at:

  • Speed — Next.js sites with static export load instantly. Lighthouse scores in the high 90s are normal, not exceptional.
  • Unique interactive experiences — calculators, configurators, dashboards, animations that respond fluidly to user input. The kind of thing that makes a site feel like a product, not a brochure.
  • Integration with custom backends — if you're building software around your business (custom CRM, internal tools), the site can be a first-class part of that ecosystem rather than an external silo.
  • Future-proofing for growth — easy to add complex features later without refactoring everything.

What it actively hurts:

  • Content updates by non-developers — without a CMS layer on top, every text change requires a developer. Adding a CMS (Sanity, Contentful, Strapi) means another monthly fee and learning curve.
  • Cost — more development time, more design time, more decisions. A custom site that matches a $3k WordPress site quality typically runs $6–10k.
  • Developer dependency — you'll need the same developer (or one comfortable with the same stack) for ongoing changes. The talent pool is large but more expensive.

When custom is the right answer:

  • The site is closer to a product than a marketing piece
  • You need top-tier speed and Lighthouse scores for ad campaigns or SEO competition
  • You have specific interactive features that off-the-shelf platforms can't deliver well
  • You have budget for ongoing development relationship, not just a one-shot build

A simple decision matrix

If you need only one criterion to decide:

Your priority Pick
Lowest ongoing cost WordPress
Easiest content updates WordPress
E-commerce in CIS markets OpenCart or WooCommerce
E-commerce globally WooCommerce
Fastest possible loading Custom (Next.js)
Unique interactive features Custom (Next.js)
Find a developer anywhere in 5 years WordPress
Run multiple stores from one admin OpenCart
You're already on platform X Stay on X (migration is usually a bad idea unless X actively hurts you)

What we do

We work with all three. WordPress is our default for business sites and most e-commerce. OpenCart when you're already on it or when its specific strengths matter. Custom Next.js for landings where speed is critical, or when your project genuinely belongs in the custom bucket.

We pick at the brief stage, not before — and we'll be honest if your project doesn't actually need what we'd be charging you for. If a $1,000 Tilda landing solves your problem, we'll tell you. If you really do need a $6k custom build to compete, we'll explain why.

See packages → · Start a project →