Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Falabella’s reported cloud commerce rebuild was a redesign, not a straight move of its legacy Oracle ATG system. In 2021, the retailer described a custom, open-source platform built from homegrown microservices: shared capabilities such as search and orders sit alongside a flexible layer for the distinct needs of its businesses. The architecture details below are historical reporting, not confirmation of Falabella’s current production stack.

Why Falabella replaced the old approach

Falabella operates a group of retail and related businesses, including brands such as Sodimac, Tottus and Mallplaza. CIO reported in October 2021 that the group then had 25 brand websites and had used Oracle ATG for ecommerce for more than 12 years. The account described the operating burden of a large monolithic system and the challenge of serving an omnichannel business across multiple brands. Those website and system figures describe the situation reported in 2021, not Falabella today. CIO’s 2021 account

Instead of simply moving ATG into a public cloud, Falabella chose a custom platform based on open-source software and internally developed microservices. Vinayak Raichur, identified by CIO as a Falabella engineering leader, said the goal was “not to just shift from ATG to the cloud” but to build a custom solution. The choice prioritized a platform designed around the group’s needs rather than a like-for-like relocation of the existing system.

How the platform was designed

Shared capabilities, with room for each business

CIO described a two-layer design: a centralized technology platform for capabilities used across the group, and a flexible business layer to accommodate differences among business units. The reported multi-tenant capabilities included search, orders, customer service, catalogue, pricing, inventory and shipping. In practical terms, this model aims to avoid rebuilding common commerce functions separately for each brand while allowing brand-specific workflows and experiences.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Cloud-native services and storefronts

The 2021 CIO report said Falabella’s ecosystem was hosted on Google Cloud and described a headless microservices platform built on Kubernetes. It reported React server-side rendering for the front end and a polyglot backend spanning Java, Node.js and Go. More than 150 IT team members were reported to have worked on the project; Falabella retained decisions about the architecture blueprint and selected Thoughtworks as its implementation partner. These are details from the project-era account, not a verified inventory of today’s systems. CIO’s 2021 account

Thoughtworks characterizes its work as beginning with a three-month discovery phase and an ecommerce product blueprint that developed into a digital retail backbone. Its account describes the platform as cloud-native, multi-tenant, API-driven, headless and based on domain-driven design, with Kubernetes and an event-driven architecture. It also connects the digital platform to store modernization, including handheld devices, self-checkout, mobile point-of-sale and scan-and-go. The discovery duration and architecture descriptions come from Thoughtworks’ case study. Thoughtworks’ Falabella case study

How the cloud data work fits in—and what it does not prove

Falabella’s commerce platform should not be conflated with the separate data and analytics work described by Google Cloud. The vendor’s case study says Grupo Falabella decided in 2019 to consolidate its data ecosystem on Google Cloud and began a data lake for the ecommerce platform in January 2021. It names BigQuery for analytical databases, Looker for reporting, Google Kubernetes Engine for deploying and scaling website applications, Cloud Storage for unstructured data, Cloud Run to reduce service operations and Pub/Sub for messaging. This account shows services used in the broader cloud and data environment; it does not establish that every listed service formed part of the core commerce platform architecture. Google Cloud’s falabella.com case study

Google Cloud also reports that Looker reporting output rose from five to 25 reports per sprint and that users of Google Cloud tools grew by 300%. The page does not clearly date the measurement period, and these are vendor-reported results about analytics and tool use—not independent measures of overall commerce-platform productivity, customer growth or seller growth. Google Cloud’s falabella.com case study

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

How the platform story connects to omnichannel retail

Falabella’s 2022 annual report describes a wider platform strategy spanning ecommerce, payments, digital banking, loyalty and delivery, using microservices and API connections. It says components of a modern cloud-based Home Delivery platform launched in 2022 to manage inventory, availability and order orchestration, with logistics services for IKEA and marketplace sellers. This is dated company context that illustrates the group’s platform ambitions; it does not verify the current deployment details of the original commerce rebuild. Falabella 2022 Annual Report

Business updates show that digital commerce and seller activity remain important, but do not settle the architecture question. In a June 2025 Seller Day announcement, Falabella said online gross merchandise value (GMV) grew 17% in the first quarter of 2025 and that sellers contributed 74% of that growth. The company also reported that more than 450 brands attended the event. These are company-reported business and event figures, not technical performance measurements. Falabella’s 2025 Seller Day announcement

Falabella’s 2026 Seller Day announcement discusses omnichannel strategy and a new business-to-business unit, but does not publish a current technical architecture. The available dated accounts therefore support a clear history of the rebuild and its design goals, not a claim that the 2021 stack remains unchanged. Falabella’s 2026 Seller Day announcement

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

What Falabella’s approach demonstrates

The reported design addresses a common trade-off in large retail groups: shared platform capabilities can reduce duplication, while business-specific flexibility is needed for different brands and operations. Microservices and APIs can support modular development and integrations, but they also require coordination across services and teams. The case accounts describe Falabella’s intended model and implementation; they do not provide an independent cost comparison, performance benchmark or quantified proof that this design is superior to alternatives.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.