Challenge

Mizuno North America was running on a monolithic legacy platform that had been heavily customized over many years. While those customizations once served a purpose, they had become a liability, making it costly, slow, and technically complex to introduce new functionality, run campaigns, or respond to evolving customer expectations.

Three pain points stood out most acutely. First, inventory and overselling risk. The existing platform could not synchronize inventory in real time across locations. This was particularly damaging during high-demand events like limited-edition product launches, where items can sell out within minutes. Without accurate availability data, Mizuno faced order cancellations after purchase, eroding customer trust and creating operational headaches.

Second, a broken checkout experience. Customers navigating checkout faced a cumbersome six-to-seven step process with an average completion time of three minutes. The friction was significant, contributing to high cart abandonment and lost revenue.

Third, slow campaign deployment. Marketing and merchandising teams were constrained by the platform's rigidity. Deploying new promotions or site content required significant lead time, limiting Mizuno's ability to respond quickly to market trends, seasonal moments, or competitive shifts. Personalization capabilities were minimal, and custom uniform orders required manual back-and-forth with customer service.

Strategy

In early 2024, following a nine-month implementation timeline, Mizuno North America launched a new composable commerce platform on BigCommerce. The nine-month end-to-end timeline covered technology evaluation, partner onboarding, system integration, UI/UX development, testing, and go-live, and was completed significantly faster than would have been possible on a traditional monolithic platform.

Rather than adopting a simple lift-and-shift, Mizuno built a genuinely modular architecture with clear separation of concerns across the stack. BigCommerce handles the core commerce engine including catalog, cart, checkout logic, and storefront APIs. Deck Commerce manages order routing, multi-location inventory visibility, and OMS functions. Bolt owns the checkout experience layer. Amplience manages site assets and content. Searchspring handles onsite search and merchandising. Emarsys drives personalization and customer data.

The systems integrator, Mira Commerce, built custom AWS-powered microservices to bridge Mizuno's existing backend ERP and inventory systems with the new commerce components, ensuring real-time data flow across the entire stack without forcing a rip-and-replace of legacy backend infrastructure. BigCommerce's open API architecture enabled Mizuno to connect both pre-built integrations and custom-built services without modifying the core platform.

The result is a platform where Mizuno can swap, add, or upgrade any component, whether checkout, search, content, or OMS, without rebuilding the system around it. When Mizuno needed 3D product customization, for example, it was addable without touching the rest of the system. The headless "Running Journey" UX/UI experience, built on a custom React/Next.js app with a headless CMS, demonstrates how the frontend and backend are fully decoupled: the shopper experience can be redesigned and redeployed independently of commerce logic.

Impact

The results from Mizuno North America's composable commerce transformation are both significant and multi-dimensional. Since the migration, Mizuno has delivered consecutive year-over-year revenue growth over 30%, a 20% increase in conversion rate, and a 17% increase in average order value. Sessions are up 55%, new users up 45%, first-time buyers grew 55%, and total purchasers are up 87%. Organic search traffic and direct traffic growth are both up 50%. Key holiday periods delivered consecutive 40% revenue growth compared to the previous platform.

Operationally, Mizuno achieved a 40% reduction in time to deploy site content and marketing campaigns. Real-time inventory sync across locations eliminated overselling risk during high-demand launches. 

The customer experience has been transformed. Checkout completion time dropped 90%, from approximately three minutes to a near-instant one-click experience via Bolt. Order cancellations fell 50% due to real-time product availability updates. A 3D product configurator now enables customers to visualize custom products before purchasing.

The composable stack also allowed Mizuno to scale infrastructure for the holiday season without performance degradation, supporting a near-2x increase in volume. New capabilities are now addable through the app marketplace with minimal development effort.

As Casey Rodriguez, Digital and Consumer Experience Director at Mizuno USA, noted, the streamlined checkout process and implementing Bolt to offer a seamless checkout experience has been a game changer.

Composable architecture in action

Mizuno's platform is a textbook example of composable commerce: a deliberate assembly of best-in-class, independently deployable components, integrated through APIs and orchestrated by a modern architecture. Separation of concerns is clearly demonstrated across the stack. Each system does one thing exceptionally well, and none are tightly coupled to one another.

API-first interoperability is the connective tissue. Custom AWS-powered microservices bridge Mizuno's existing backend ERP and inventory systems with the new commerce components, ensuring real-time data flow without forcing a rip-and-replace. BigCommerce's open API architecture was instrumental, enabling both pre-built integrations and custom-built services without modifying the core platform.

The headless "Running Journey" experience, combining a custom React/Next.js app, headless CMS, and tight BigCommerce API integration, demonstrates mature separation of frontend experience from backend commerce logic.

The phased, API-first migration approach meant Mizuno didn't rip out their entire backend. By building microservices to connect new components to existing systems, they preserved stability while adding capability incrementally, a model other brands with legacy infrastructure can replicate.