WordPress vs Custom Website vs Shopify: Which Should an Overseas Business Choose?

The short version #

Don't pick the tool first. Name the business stage first. WordPress fits content-driven, inquiry-driven B2B sites and ships in six to eight weeks. A custom build (Next.js or Nuxt with a headless CMS) fits deep ERP/CRM integration, complex product configurators, or performance-critical apps, and starts at ten to fourteen weeks. Shopify wins when you sell directly, have clean SKUs, and need standard checkout, which mostly means B2C. Treat "going overseas" and "selling overseas" as different problems: a B2B factory is almost always WordPress or custom; a DTC brand is Shopify. When you compare costs, include the next twelve months of content, maintenance, and SEO, not just the build quote. The table further down is the version we hand to clients before kickoff.

Roughly 60% of the overseas builds we've taken on in the last three years were WordPress, 25% were custom front-ends, 15% Shopify or hybrid. The scoping question is rarely "which one should we use". It's usually "why can't we put the B2B inquiry site on Shopify too", or "why does our small factory need a custom build". A bearings exporter, a DTC apparel brand, and an industrial SaaS team are three very different businesses with three different right answers, and getting that part clear matters more than comparing themes.

Business first #

The tool isn't the starting point. Three questions on the whiteboard before anything else:

• How does the customer buy? Credit card at checkout, or email/WhatsApp inquiry leading to a contract? The first leans commerce platform, the second leans content site.
• How many SKUs? Under 20 products, each needing a long description, case studies, and spec tables — content site. 500+ SKUs with variants, promotions, and inventory — commerce platform.
• What's the biggest variable in the next 18 months? Content growth (blog, case studies, whitepapers)? Product expansion (more SKUs, more markets)? Or integration with your factory ERP and sales CRM? The honest answer drives the CMS choice.

The most expensive mistake we've seen was a B2B factory with 200 inquiries a year that spent the equivalent of US$60K on Shopify Plus and never got hreflang right, because Shopify's surface for multilingual B2B inquiry flow is weak. We've also seen the opposite: a brand with eight SKUs and a $30 average order pushed into a custom Next.js build with a homemade admin, where every price change required a developer.

Until you've answered those three questions, "WordPress is cheaper than Shopify" and "custom is more flexible than WordPress" are just noise.

WordPress #

Who it fits: about 85% of small and mid-sized overseas businesses. Content-driven, inquiry-driven, six to eight weeks to launch, budget in the US$10–35K range for the build.

Why we recommend it often:

• Fast launch. A clean theme (Astra, Kadence, or Blocksy) plus a small set of plugins (Yoast or RankMath, WPML or Polylang, WP Rocket) gets you running. Six weeks to v1 is realistic.
• Editorial freedom. Marketing or a contracted native writer can edit directly. No developer ticket for a copy change.
• Mature SEO toolchain. Schema, sitemaps, hreflang, Open Graph — all available without writing code.
• Long-term scalability for case studies and a blog. The structure still holds when the library hits 200+ articles two years in.

Where it bites:

• Theme and plugin sprawl will slow the site down. An overseas-region host, a CDN, and WebP/AVIF images are the floor; the plugin and performance setup in WordPress Overseas Website Architecture goes deeper.
• Don't lean on machine-translation plugins. WPML and Polylang both support a real human translation flow, and combined with proper hreflang that's the right pattern.
• Maintenance has to belong to someone. WP core, themes, and plugins update every month. A year of neglect quietly turns into a security incident, not just a bug.

Typical fit: a factory making industrial valves, primary markets in Europe and Southeast Asia, 500–2000 inquiries a year, English plus German plus Spanish, an active case-study library. That's the WordPress sweet spot.

Custom build #

Who it fits: complex interactions, performance-critical apps, deep integration with back-office systems. Concretely:

• Product configurators that price in real time by spec, material, or color.
• Customer logins that show orders, quotes, or technical documents.
• Live integration with factory ERP, sales CRM, or quoting systems.
• Single-page conversion paths that need continuous A/B testing and a front-end engineer in the loop.

The stack is usually Next.js, Nuxt, or SvelteKit plus a headless CMS (Strapi, Sanity, Contentful, or Payload). The front-end gets the speed and SEO benefits of SSR/ISR; content stays editable by marketing in the CMS.

Why it isn't the default:

• Two to three times the timeline of a WordPress build. Ten to fourteen weeks minimum.
• Budget starts around US$45K and goes up. Complex builds run US$100–250K. The first year of iteration and maintenance adds materially on top.
• A front-end engineer has to stay involved. The "install a plugin" pattern from WordPress doesn't exist here. Every feature is code.
• Steeper learning curve for the content team. Headless CMSes give up the WYSIWYG editing experience WordPress users are used to.

When it's actually time:

• A WordPress site has been running for 12–18 months, SEO traffic has plateaued, and performance or interaction is now the next growth lever.
• The business needs sub-200ms TTFB and 90+ Lighthouse scores across the board, which a heavily-tuned WordPress can't reliably hit.
• The product is closer to an app than a site, where interactions matter more than long-form content.

Counter-example: a factory shipping its first overseas site, no content history, going straight to Next.js and Strapi. Six months in: slow development, slow content, weak SEO, fewer inquiries than expected. Ship v1 on WordPress, prove the business, and then consider custom. Almost always the cheaper path.

Shopify #

Who it fits: direct B2C selling, or light B2B (small wholesale). Clean SKUs, consistent pricing, credit card and PayPal checkout, no complex quoting flow.

What it actually does well:

• Standard ecommerce. Cart, checkout, inventory, refunds, taxes, shipping, subscriptions are all built in.
• International payments. Shopify Payments, Stripe, and PayPal cover most markets out of the box.
• App ecosystem. There are mature apps for shipping, email, loyalty, UGC, and retargeting.
• Security and compliance. PCI, SSL, and fraud detection are handled for you.

What it doesn't do well:

• B2B inquiry flow. Shopify Plus has a B2B module, but the "browse, WhatsApp, email quote, contract, wire" sequence most factories run on doesn't fit cleanly.
• Content-led SEO. The blog feature is weaker than WordPress. URL structure, template flexibility, and schema control are more constrained.
• Heavily customized product pages. If every product needs PDF datasheets, case studies, video, and spec tables, custom Section development tends to cost more than expected.
• Multilingual. Shopify Markets is much better than it used to be, but for hreflang granularity and per-language SEO control it still trails WordPress + WPML.

Typical fit: a home fragrance brand with 30 SKUs, primary markets in North America and Australia, average order value $40–80, traffic mostly from Meta and Google Ads. That's the Shopify sweet spot.

If you're a factory with under 200 orders a year and every order goes through a contract, forcing Shopify usually makes a simple thing complicated.

At a glance #

This isn't absolute. Every project weighs these dimensions differently. If your business doesn't fit any column cleanly, go back to the three questions in the previous section.

Version one #

If you're validating an overseas market for the first time, the lighter the v1 the better. Our default sequence:

1. Domain plus a one-page landing plus a WhatsApp button — live in a week. Use it to validate whether your ad channels actually produce inquiries.
2. WordPress content site with five to eight core pages — phase two, three to four weeks. This carries SEO and case studies.
3. Add commerce or custom functionality later — once the business is real, decide whether to add WooCommerce, migrate to Shopify, or invest in a custom front-end.

Don't spend six months on a "perfect site" before you know what your overseas customer looks like. One thing that consistently surprises domestic teams is how fast direction changes overseas. Pivoting every six months is normal. A v1 that ships, can be edited, and produces data beats a v1 that just looks expensive.

For phasing and typical budget breakdowns, see Website Renovation Cost and Timeline.

When to migrate #

WordPress isn't the end of the road, but it isn't a forced migration either. Common triggers:

• WordPress to Custom: when two of these hit at once: 200+ articles in the library, a real configurator requirement, and a clear performance ceiling.
• WordPress to Shopify: the business shifts from inquiry to direct sales, and monthly orders cross 100.
• Shopify to Custom + headless commerce: GMV in the multi-million-USD range plus deep checkout or B2B customization.
• Custom to WordPress: rare but real. When a team without a permanent front-end engineer can't maintain a custom build, falling back to WordPress is sometimes the only thing that actually ships.

Every migration is an SEO risk. Walk through the 301 and indexing protection list in How to Preserve SEO During a Website Rebuild, and read the official Google site move guidance before you touch URLs.

One-off or ongoing #

Stack choice is the first half. The second half is who adds content, runs SEO, and watches performance after launch. That's less about the tool and more about team structure.

• One-off build package: works when the budget is fixed and you have an internal marketing-plus-tech pair who can carry the site after handoff. We deliver, document, transfer credentials, and you run.
• Monthly growth service: works when sales is strong but marketing is thin. Steady content, optimization, and a monthly review delivered by us.

Plenty of WordPress sites look great in year one and turn sluggish in year two because nobody owned them. By year three the team wants to switch but worries about SEO loss. That isn't really a WordPress problem. It's a no-owner problem. More on the trade-off in One-Off Website Rebuild vs Monthly Growth Service.

References: WordPress official documentation, Google Search Central — ecommerce URL and product page guidance, and the SEO Starter Guide.

FAQ #

Can WordPress really handle real traffic? #

Yes. WordPress sites doing a million page views a month are common. The variables are hosting, caching, CDN, image optimization, and plugin discipline. Almost every "WordPress can't handle it" story we've audited turned out to be 30+ plugins, a heavily modified theme, and no cache strategy.

We already have Shopify. Do we still need a WordPress content site? #

If the business is mostly ecommerce and most SEO traffic comes from product pages, probably not. But if you want long-form content, case studies, and inquiry-generating articles, Shopify's blog is genuinely weak. A common pattern is Shopify on the primary domain plus WordPress in a subdirectory (or subdomain) for content. The subdirectory route tends to be friendlier for SEO consolidation.

Does headless WordPress count as custom? #

It's a hybrid. WordPress as the back-end with Next.js as the front-end gives you something close to custom-build speed while keeping the WordPress editing experience. The trade is roughly double the engineering effort versus plain WordPress, and your team needs to be comfortable with a decoupled architecture. It fits when the editorial team is already fluent in WP admin but the front-end has to be best-in-class.

What if the v1 budget is only US$7K? #

WordPress, a clean paid theme, an overseas host, and write the English copy yourself. Spend on hosting and content; skip premium plugin subscriptions and elaborate design. Decide on upgrades after the first wave of inquiries comes in.

Get a diagnosis #

If you're stuck on stack choice, or you've shipped a v1 and realized you picked the wrong path, bring your current site, target markets, and team setup. We'll run this exact comparison with you in a free initial review under our overseas website build and SEO/GEO support service, and tell you which path fits your current stage, plus where the likely migration points are in the next twelve months.