Back to Posts

Customer Story: SPS Commerce Modernizes SupplierWiki with Next.js

•4 months ago
Next.jsPantheonDecoupledWebOps
How SPS Commerce consolidated SupplierWiki from Netlify onto Pantheon — unifying a Next.js frontend with WordPress in an 8-day migration.
SPS Commerce SupplierWiki running on Next.js on Pantheon.

Consolidation, not migration pain. SPS Commerce — the supply chain network serving 50,000+ customers across 60 countries — runs SupplierWiki, a reference guide for supply chain professionals it inherited when it acquired SupplyPike in 2024. The catch: SupplierWiki's Next.js frontend lived on Netlify while the marketing site ran on WordPress on Pantheon — two dashboards, two support relationships, and two bills for one site of roughly 1,600 pages in five languages.

When Pantheon shipped managed Next.js, a 12-year Pantheon customer saw its opening. The team moved SupplierWiki from Netlify to Pantheon in eight days, unifying the Next.js frontend with the existing WordPress backend on one platform — one dashboard, one Dev → Test → Live pipeline, one contract.

“When Next.js became available on Pantheon, having that opportunity to consolidate our services was a no-brainer for us,” said Ryan Walker, Development Manager at SPS Commerce.

What made it work: GitHub-native deploys with Multidev preview environments per pull request; the Pantheon Cache Handler coordinating cache invalidation across WordPress and Next.js; domain masking applied to the test environment (not just production) so the two systems share one domain; and built-in Secrets Management (in Terminus Core 4.2) for centralized, encrypted keys across environments.

Read the full story: SPS Commerce Modernizes with Next.js on Pantheon, or watch the platform tour featuring SPS Commerce.

Customer Story: SPS Commerce Modernizes SupplierWiki with Next.js | NextJS on Pantheon