Case Study

Build On Trust

How Coca Cola EP is Making the Most of their Salesforce Investment


Company Name: Coca-Cola European Partners
Date: Aug 2020

Previously plagued with critical errors, frequent overwrites and merge conflicts that were having a negative business impact, Coca-Cola EP took their release process to the next level with Copado’s native DevOps CI/CD solution, increasing release velocity, stability, and visibility.

Achieving Digital Transformation with DevOps

Copado: The #1 Complete CI/CD DevOps Tool for Salesforce


Virtually Eliminated Critical Errors


Increased Release Velocity


Version Control


3rd Party Dev Tools Integration

“You know you have control, and in the past, we didn’t have any.”

Tejeiro Del Río

Salesforce Platform Architect, Coca-Cola EP

The Challenge

Two of the three bottlers that combined to form CocaCola European Partners had been using Salesforce for
several years by the time of the merger. The combined
company has 60 developers supporting three production
orgs — the two legacy environments, plus a new one to
manage human resources data.
When Manuel Tejeiro Del Río came aboard as Salesforce
Platform Architect in 2017, he knew the company
needed to improve its DevOps process for Salesforce.
The teams he managed were engaged in major
projects, including building a B2B portal for European
customers and developing a mobile app for field
service representatives. They also handled the routine
enhancements to legacy Salesforce applications that
kept the business running day to day.
“This was very annoying for the business,” says Tejeiro
Del Río. “When they requested a new enhancement —
say a new field or page layout — they had to wait maybe
a month for a feature. Then two weeks later, someone
overwrites the page layout and the field disappears.
This kind of issue happened many times.”

The Solution

While other tools that promised to streamline DevOps
for Salesforce had appeared on the scene since CocaCola Enterprises first adopted Copado, Tejeiro Del Río
decided that Copado was the best solution. “I know
the other tools and have tested some of them, but I
think they are not very user-friendly and far behind
Copado in terms of features and capabilities,” he says.
Building a DevOps solution in-house also didn’t make
sense for the company. “It requires a lot of money and
effort, and in the end, it would be more or less the
same thing,” Tejeiro Del Río says. “If there’s a product
on the market, to me it always makes more sense to
buy than to build.”
Employing Copado allowed the team to easily run
tests and static code analysis at every stage of the
release process and automatically resolve conflicts.
This prevented components from being overwritten
and virtually eliminated critical errors. When release
managers made small errors during the manual
approval process, fixing them was much easier thanks
to having built-in version control…

Read full story >>