Rakuten
Unifying a Global Ecosystem: How Motomtech Helped Rakuten Modernize Across E-Commerce and FinTech
About Rakuten
Rakuten is one of the world's largest internet services companies, headquartered in Tokyo, Japan. Founded in 1997, Rakuten has grown into a global ecosystem of more than 70 services spanning e-commerce, fintech, digital content, communications, and mobile — serving 1.9 billion members worldwide with an annual gross transaction volume exceeding 44 trillion yen. The company's portfolio includes Rakuten Ichiba (Japan's leading e-commerce marketplace), Rakuten Travel, Rakuten Card (one of Japan's most widely used credit cards), Rakuten Bank and Rakuten Securities (leading digital financial services), the messaging platform Rakuten Viber, ebook platform Rakuten Kobo, and Rakuten Mobile — Japan's fourth mobile network operator, launched in 2020. What ties these services together is the Rakuten Ecosystem model: a unified membership and loyalty program where points earned across any service can be used across all others, creating deep cross-platform engagement. The scale and breadth of this ecosystem create unique engineering challenges. Each service has its own product team, technical stack, and delivery cadence, yet users expect a seamless experience as they move between shopping, banking, reading, and communicating. Rakuten needed a development partner capable of working across this complexity — one that could embed deeply within its engineering organization and contribute at the level of quality that a platform serving nearly two billion users demands.
Industry
E-commerce and Financial Services
Service
Dedicated Engineering Team
What We Did
Product Conceptualization, Software Prototype, Web & Mobile Application Development, Maintenance & Enhancement
Custom Team
11 people (6-in-1 Business Analyst, UX/UI Designer, DevOps, Quality Assurance, Project Manager, Software Architect, plus 5 Developers)
Results
Since its launch, Rakuten's platforms have delivered tangible benefits like
seamless integration of services,
The fragmented experience that had resulted from decades of independent service development was replaced with a cohesive cross-platform journey. Users moving between Rakuten's e-commerce, financial, and communication services now encountered consistent design patterns, shared navigation conventions, and unified account experiences — reducing confusion and increasing the cross-service engagement that drives the Rakuten Ecosystem model.
enhanced user experience,
The redesigned interfaces delivered smoother navigation and more intuitive interaction patterns for Rakuten's global user base. Prototype testing during Phase 2 validated design decisions before they reached production, resulting in interfaces that tested well across demographics and reduced support requests related to usability issues.
streamlined operational workflows,
By rationalizing cross-service workflows and eliminating manual handoffs between departments, the project significantly reduced task completion times and minimized service delays. Internal teams that had previously spent time coordinating across disconnected systems could now focus on delivery, with the integrated pipeline handling the coordination that had previously been manual.
scalable platform growth rate,
The architectural improvements and DevOps infrastructure established during the engagement enabled Rakuten to expand services and onboard new capabilities without the performance degradation that had previously accompanied growth. The platform was built to scale — and the monitoring and deployment tools in place gave the internal team confidence to push that scale further as business needs evolved.
Challenge
Rakuten's greatest strength — the breadth of its ecosystem — was also the source of its most pressing engineering challenges. With more than 70 services built and maintained by different teams over nearly three decades, fragmentation had become a structural problem. Various teams managed disconnected systems across e-commerce, fintech, and digital communication, making it difficult to deliver a unified experience for users who moved fluidly between services. These silos created cascading issues. Inconsistent interfaces across platforms confused users who expected the Rakuten brand to feel the same whether they were buying on Ichiba, checking their Rakuten Card balance, or booking travel. Operational inefficiencies multiplied as teams duplicated infrastructure and made integration decisions in isolation. Manual handoffs between departments slowed delivery timelines, and a lack of cohesive UX standards made it difficult to maintain product consistency as new features were shipped across the ecosystem. The challenge went beyond surface-level design alignment. At the systems level, data flows between services needed to be rationalized — user identity, loyalty points, transaction history, and preferences all needed to be accessible and consistent across platforms. On the engineering side, the combination of C# backend services and React frontend applications required a team comfortable operating across the full stack, with the discipline to write code that would be maintained by Rakuten's own engineers long after the engagement. The company needed more than a software update. They needed structural, cross-functional alignment that would enable their internal teams to deliver more effectively — and their existing internal resources could not support that effort at the required scale and speed.
Solution
Motomtech embedded a dedicated engineering team of 11 specialists — including a combined business analyst, UX/UI designer, DevOps engineer, QA specialist, project manager, and software architect, plus 5 developers — directly within Rakuten's engineering organization. The team was structured to operate as a self-contained delivery unit while integrating fully with Rakuten's internal processes, tools, and standards. This model gave Rakuten immediate access to a cross-functional team that could own end-to-end delivery: from discovery and architecture design through implementation, testing, and production support. The team's multi-disciplinary composition meant that design, engineering, quality, and operations were synchronized from day one — eliminating the handoff delays that had been slowing Rakuten's internal delivery. The engagement focused on Rakuten's e-commerce platform — modernizing core systems and shipping new capabilities across one of the company's most heavily-trafficked service categories.
Phase 1
Conceptualization
The engagement began with deep discovery work across Rakuten's business and engineering teams to identify the delivery obstacles and system fragmentation that were limiting velocity. A full-stack team was embedded within Rakuten, bringing together the necessary expertise to understand and address the root causes — not just the symptoms — of the cross-platform inconsistencies. Motomtech mapped out the existing architecture across the relevant services, documenting API contracts, data flows, integration points, and areas where systems had diverged. The team then designed a centralized architecture tailored to Rakuten's business goals, creating a blueprint that integrated design, engineering, DevOps, QA, and project management functions into one synchronized delivery pipeline. This architecture was designed to be adoptable by Rakuten's internal teams after the engagement — not a proprietary system that would create dependency, but a structural improvement that would outlast the partnership.
Phase 2
Software Prototype
With the architectural foundation in place, the UX/UI team developed user-centered design flows that reflected the needs of multiple user groups across the ecosystem. These designs were tested and validated early through prototyping and stakeholder review, ensuring that the final product would deliver consistency and intuitive functionality before a single line of production code was committed. The prototype phase was critical for alignment. Rakuten's ecosystem serves users with vastly different contexts — a consumer shopping on Ichiba has different needs than a small business managing their Rakuten Card account or a user booking domestic travel. The design system needed to accommodate these contexts while maintaining the visual and interaction consistency that makes the Rakuten ecosystem feel unified. The team iterated rapidly based on feedback from product owners across service lines, converging on patterns that could scale across the platform.
Phase 3
Implementation
On the engineering side, Motomtech leveraged C# and React to build a robust, scalable platform capable of handling millions of users across Rakuten's various services. The backend services were designed for high throughput and reliability — essential for a platform where transactions, data lookups, and real-time updates happen at massive scale throughout the day across global time zones. A strong DevOps foundation enabled smooth deployments and long-term maintainability. The team established CI/CD pipelines, automated testing suites, and monitoring infrastructure that gave both Motomtech and Rakuten's internal teams confidence to ship frequently without fear of regression. The implementation phase focused on translating the architecture and designs from earlier phases into production-grade code, with particular attention to the integration points between services where the previous fragmentation had been most acute. Each release was staged and monitored, with rollback procedures in place to protect the live user experience.
Phase 4
Maintenance & Enhancement
Once the core changes launched, Motomtech continued to support them through active iteration. The team implemented roadmap features, gathered user feedback from multiple channels, and deployed improvements on a rapid cadence. This agile approach allowed Rakuten to keep pace with evolving market needs — including the accelerating demand for mobile-first experiences, AI-powered personalization, and real-time analytics — without disrupting live operations or compromising product quality. The maintenance and enhancement phase also included knowledge transfer to Rakuten's internal teams. Motomtech documented architectural decisions, established coding standards for the new components, and conducted technical walkthroughs to ensure that Rakuten's engineers could maintain and extend the work independently. The goal was to leave Rakuten in a stronger position than before — not just with better software, but with a more effective development process and a proven architectural pattern for future cross-ecosystem work.
Technology Stack
To ensure a high-performance, scalable, and secure solution, Rakuten's updates were built using:
Backend
C#
Frontend
React
Testimonial
"Motomtech's expertise in developing our unified platform has transformed the way we deliver services. Their dedication to understanding our needs and delivering a tailored solution has significantly enhanced our user experience and operational efficiency."
Nick Golden,
Project Manager, Rakuten
