· ai-devtools
Tesco Cloud-to-Edge Platform: Jayesh Bhayani shares decade-long enterprise transformation lessons
The move toward a unified cloud-edge platform, enabling a global enterprise to scale its retail operations for millions of customers, is the core of the transformation discussed by Jayesh Bhayani…
The move toward a unified cloud-edge platform, enabling a global enterprise to scale its retail operations for millions of customers, is the core of the transformation discussed by Jayesh Bhayani regarding Tesco. He details a decade-long overhaul that successfully aligned changes in systems, personnel, and processes, while also offering insights on managing cloud expenditures, the build versus buy decision, and preparing for the advent of agentic commerce. As Senior Engineering Director at Tesco, Bhayani plays a pivotal role in steering the company's technology strategy and shaping its business trajectory, focusing on achieving the necessary organizational alignment, architectural direction, and strategic clarity to compete effectively in the rapidly changing retail sector and support agentic commerce readiness.
Software continues to reshape the world, and gatherings like QCon London help foster this evolution by circulating knowledge and sparking innovation among the developer community. This practitioner-focused conference is specifically tailored for architects, engineering directors, project managers, and technical team leads who guide innovation within their respective teams. Bhayani stated, "I'm going to spend some time in sharing our learnings of transformation at scale at Tesco. That's why modernizing technology at Tesco. How it has changed the culture, not just within the company, along with systems, but enabled the growth for the company. From that perspective, after 10 years being at Tesco, I thought it would be good to share the learnings we had from here and how we are looking at the future."
His journey into this massive undertaking began when Tesco reached out to him after he had spent approximately 25 years in Silicon Valley, California. At the time, he had little familiarity with Tesco, having never visited London previously. Initial views of the company's website suggested a lack of technological sophistication for a major grocery chain. This perception persisted for several months until he was persuaded to meet with members of the technology department. The details he learned about the current state of the technology and the requirements for large-scale growth and transformation were what motivated both him and his wife to accept the offer. They were empty nesters at the time, prompting them to decide to join.
The scale of Tesco itself is immense: it operates about 5,000 stores, ranging from small to medium and superstores, across five different nations. When Bhayani began ten years prior, the company was also operating in Asia, specifically Thailand and Malaysia, though those operations have since been divested, leaving the current five countries. Furthermore, Tesco manages 20 distribution centers and serves 25 million customers—nearly a third of the entire UK population, which is a significant figure. The workforce comprises 350,000 colleagues across its stores, with roughly 15,000 situated in head office, and among those, about 6,000 working in technology. The operational volume is staggering, involving around 50 million baskets processed, referring to orders across the entire estate, alongside 1.3 million online orders each week.
The COVID-19 pandemic presented a massive test of scale; when the entire business pivoted online, the immediate hurdle was doubling the number of available online slots for shoppers. By that point, the e-commerce platform was already operational. Doubling this capacity in a single month was equivalent to bringing almost three competing companies online simultaneously, a feat when many businesses were halting order acceptance or customer acquisition. This demonstrated the sheer scale, alongside the massive supply chain movement of 50 million cases, not even accounting for the miles driven by trucks or internal distribution center logistics. The company handles 4.5 billion calls daily and possesses 98% coverage within the UK, meaning home grocery delivery is feasible across 98% of the nation's geography for its 25 million customers. The physical infrastructure includes nearly 50,000 till points, or POS devices, which is just a fraction of the thousands of other handheld devices utilizing the same underlying platform. This context underscores how mission-critical the technology has become.
Driving transformation within such an environment is inherently difficult. Having worked in startups, mid-sized firms, and running his own venture, Bhayani noted that Tesco represents another level of scale. He felt it was important to reflect on this because the decision-making process for technology and transformation choices involves numerous complexities that extend beyond the retail industry. Any business possessing physical locations, digital components, and real-time operations will encounter these same challenges. The key learning derived was the necessity of being both effective and efficient; efficiency means executing tasks well and quickly, whereas effectiveness involves pursuing the right objectives. One can move fast, but if the goals are incorrect, the effort is misplaced. Therefore, achieving both efficiency and effectiveness requires doing the correct things in the correct manner. This principle applies broadly to industries operating with comparable scale and complexity.
The impetus for change ten years ago stemmed from the poor state of the technology infrastructure. When he initially perceived a lack of technology, it was actually a situation where technology existed but was severely fragmented. Numerous technology stacks were tethered to outdated business structures. The term "siloed" here means more than just a store having a POS system while e-commerce used something else; it referred to multiple stacks even within the e-commerce business itself. The entire grocery stack, plus the marketplace, and the clothing division (F&F) each ran on different systems—one using Microsoft .NET and another Oracle. Customers faced a lack of unified identity; for example, "Jayesh@groceryhomeshopping is different than Jayesh@marketplace, is different than Jayesh@f&f." The organization lacked a unified view of the customer, data platforms, or product management capabilities; the fragmentation was absolute. Furthermore, there was no single source of truth for pricing or inventory.
In that era, with multiple monolithic systems housed in private data centers, the company was far from the public cloud; it was merely a collection of machines. Obtaining a server could take two months. The POS systems in stores utilized decades-old hardware, running software that was 20 years old and entirely batch-oriented, making connectivity impossible. Deployments were archaic, requiring engineers to travel with floppy disks to install software in retail locations. Third-party solutions were not merely external additions; they were heavily customized. Given Tesco's scale, the demand for minor deviations in vendor software seemed reasonable initially, but this quickly led to long-term dependency on highly customized vendor solutions. The company utilized vendor software that was at least a decade old and could not be upgraded. Compounding this were heavily outsourced resources from consulting firms, which often resulted in poor quality and a deficient culture.
Navigating this landscape was daunting. The necessity for change became clear because customer expectations were advancing rapidly, demanding an omnichannel experience that the old operational model could not support; technology was failing to aid the business, which possessed the motivation to change, yet technology remained stagnant. They had reached a literal impasse. Achieving coherence across both the physical and digital domains, coupled with the need for rapid change cycles, was the core problem. Previously, requesting minor modifications to the POS systems from a vendor could take six months, and these changes often introduced regressions, leading to bug fixes that incurred additional charges. It could take six to nine months just to implement anything on the store tills. This was before even considering e-commerce needs, all while requiring higher security, greater capability, and increased capacity.
This situation spurred the shift from fragmented stacks toward unified platforms capable of serving all channels across every market, leading to the development of a multi-tenant platform, which they termed "only platform." Bhayani cautioned that platform terminology can be ambiguous, clarifying that he refers not just to the technical layer, but to the encompassing retail platform that operates the business. He noted that the technical platform's importance cannot be overstated if development does not begin early. Currently, the entire UK and Republic of Ireland operations run entirely on this platform, and they are beginning to implement it within their Central European businesses, which possess their own unique regional variations.
A significant outcome of this evolution is the vastly improved trust in technology, as the technology strategy is now deeply interwoven with the overall business strategy. This contrasts sharply with the former service-oriented mindset, where the approach was simply, "We need three things; go ahead and build it," which contributed to the prior siloed environment. The platform is now both more capable and significantly more scalable, and this is where they are currently focusing on the future of agentic commerce. Technology has evolved from being an isolated department receiving ad-hoc requests into an integral component of the entire business ecosystem. Bhayani further elaborated on the transformation journey, noting that while many assume transformation means only system development—building platforms—that is insufficient. Equally crucial was the talent transformation; given the previous reliance on outsourced development and the service-oriented mindset, the company had to completely redefine job definitions, career paths, and transform its talent structure.
Why it matters
This presentation offers practical lessons for developers and architects tackling enterprise-level modernization. Readers interested in large-scale systems will find insights on balancing build vs. buy decisions and cloud cost management in complex environments.





