All case studies

Commerce Engineering Above the Kubernetes Platform

Strengthening the application layer that connects commerce features to a modern cloud foundation

Engagement model · Managed Services

01

The client is the second-largest global sportswear manufacturer and the company behind the "their digital transformation strategy" strategy that committed over a billion euros to digital transformation through 2025. The 2025 results land at tens of billions in net sales, billions in direct-to-consumer revenue, and multi-billion operating profit with strong e-commerce growth. Their loyalty program with over 300M members operates across roughly fifty countries; e-commerce runs in sixty-five. Taller's engagement at this client has run continuously since September 2021, sourced through a staffing partner. The dominant workstream is the North America intelligent process automation program on UiPath — captured in Volume II under the RPA Automation Anywhere case with $2M+ annual cost savings. Adjacent workstreams cover Power BI analytics for the client's tech delivery hub (also captured in Volume II), an eCommerce/B2B/Retail platform-engineering pod under the client's tech delivery hub, Databricks data engineering, SAP integration and functional business-analysis capability, EDI engineering for B2B trading, and the Latin America tech infrastructure team service-management team in Brazil and Mexico. The three validated use cases below land in three of these adjacent surfaces.

02

The global sportswear manufacturer's commerce strategy depends on operating a multi-platform application portfolio across consumer e-commerce (sixty-five countries, billions in 2025 DTC revenue), the wholesale B2B portal for trading partners, and owned retail in-store technology. Each surface has its own application portfolio (legacy and modern), its own integration boundaries (SAP, Tibco, third-party EDI), and its own service-quality expectations. Maintaining and evolving this application portfolio at this client's scale requires multi-skill engineering capacity that operates alongside the platform engineering work without compromising release cadence or operational stability.

03

Taller operates the multi-skill platform-engineering pod for the client's tech delivery hub, in place continuously since 2023. The pod sits at the application and integration layer above the Kubernetes substrate: Database Administration, Full-Stack development across the eCommerce and B2B application surfaces, DevOps engineering on the deployment pipelines, Backend application development, EDI engineering for B2B retail trading partners (ANSI X12), SAP/Tibco integration for the retail POS platform (with Kafka noted as future-state capability), Application Support, Scrum Master coordination, and Service Management at Mid and Senior levels. Taller does not operate the Kubernetes substrate, their Kafka observability platform, the SwaggerHub API design surface, or their internal paved-road platform engineering; those are engineered by the global sportswear manufacturer's internal platform organization. The application-layer disciplines that Taller operates compound with the platform investment by keeping the application portfolio maintainable and releasable as the platform substrate evolves underneath it.

04

Continuous engagement since 2023 with sustained multi-role pod operation. Workshop participation by Taller's service manager at the global sportswear manufacturer offices in São Paulo alongside the client's project director and manager. Ongoing project-level coordination with the client's project manager across multiple Power BI and Tech Delivery Hub workstreams.

05

The dossier's strategic frame on UC1 is the commerce control plane as the operational lever behind the global sportswear manufacturer's revenue capacity (the 2025 DTC revenue figure, sixteen percent e-commerce growth, peak traffic at hundreds of thousands of requests per second). Taller's contribution is at the application layer that runs on that lever: the engineering capacity that keeps the application portfolio maintainable through the platform's release cadence. The neighboring layer is the kind that makes the operational picture work; it is not Taller building the Kubernetes substrate the dossier UC describes.

The next proof point can be yours.