Frequently asked questions

What did Motomtech build for Rakuten’s e-commerce ecosystem?

Motomtech modernized Rakuten’s e-commerce platform by embedding an 11-person dedicated engineering team within Rakuten’s organization. The team rationalized cross-service workflows, redesigned UX patterns across more than 70 services, and built unified architecture in C# and React so users moving between Rakuten Ichiba, Rakuten Card, Rakuten Travel, and other services encountered consistent design and shared navigation.

How big was the Motomtech team embedded inside Rakuten’s engineering organization?

Motomtech embedded 11 specialists directly within Rakuten’s engineering organization, including a combined Business Analyst, UX/UI Designer, DevOps Engineer, QA Specialist, Project Manager, and Software Architect, plus 5 Developers. The team operated as a self-contained delivery unit while integrating with Rakuten’s internal processes, tools, and standards.

What technology stack did Motomtech use to modernize Rakuten’s platform?

Motomtech leveraged C# for the backend services that powered Rakuten’s core workflows and React for the frontend across the e-commerce platform. The team also established CI/CD pipelines, automated testing suites, and monitoring infrastructure that gave both Motomtech and Rakuten’s internal teams confidence to ship frequently without regression risk.

What results did Rakuten see from Motomtech’s modernization engagement?

Rakuten saw 95% integration of services across its ecosystem with shared navigation and consistent design patterns, 92% enhanced user experience with smoother navigation, 45% streamlined operational workflows by eliminating manual handoffs, and a 3x scalable platform growth rate enabled by the new architecture and DevOps infrastructure. Project Manager Nick Golden said the work changed how Rakuten delivers services to its 1.9 billion members.

How did Motomtech enable Rakuten’s internal teams to maintain the work independently?

Motomtech documented architectural decisions, established coding standards for the new components, and conducted technical walkthroughs so Rakuten’s engineers could maintain and extend the work after the engagement. The architecture was designed to be adoptable by Rakuten’s internal teams, not a proprietary system that would create dependency, leaving Rakuten with a proven architectural pattern for future cross-ecosystem work.