In a perfect cloud world, you would host all your applications in containers running on Kubernetes and Istio, benefitting from the portability and improved resource utilization of containers, plus a robust orchestration platform with advanced application management, networking, and security functionality. This is easy to do if you’re developing a new application, but it can be hard for existing applications to take advantage of those capabilities.

Many of the applications that you may want to move to the cloud have been around a long time, and you may not have the application-specific knowledge that would be required to rewrite them to be more cloud-native—or it would be incredibly time-consuming to do so.

Another option is to lift-and-shift to a virtual machine (VM) hosting platform like Compute Engine, but that means you still need to maintain the VMs. Even if you’re not able to fully modernize an existing app, it would still be great to get some of the benefits of containers and Kubernetes.

What is Migrate for Anthos?

Enter Migrate for Anthos, a fast and easy way to modernize your existing applications with a service that encapsulates them in a container. Moving your physical servers or existing VMs into Kubernetes containers gives you crucial portability and resource utilization benefits without having to rewrite the underlying application.

Since Migrate for Anthos is built for Google Kubernetes Engine (GKE), you also automatically capture the scaling and flexibility benefits of a managed Kubernetes environment in the cloud. Migrate for Anthos recently became generally available.

Converting an application with Migrate for Anthos happens in two phases. First, it creates a generic container wrapper around your application that makes it seem like it is still running in a full VM environment. Then, you launch Migrate for Anthos software on your Kubernetes cluster that runs the containerized application.

You can find more details about this in the documentation and in our blog post: Migrating from Compute Engine to Kubernetes Engine with Migrate for Anthos.

As the name suggests, Migrate for Anthos works with Anthos GKE. However, you can also use Migrate for Anthos with only GKE—all it requires is your application and a GKE cluster running the Migrate for Anthos software. 

Getting started with Migrate for Anthos

Migrate for Anthos works with a variety of workloads, but not all. It’s particularly adept at migrating legacy applications, stand-alone applications, and monolithic applications. As you start the modernization process, here are some questions to ask to determine whether to use Migrate for Anthos with your applications:

1. Should this app be in the cloud?
By its nature, the cloud may not be able to support some characteristics of your on-prem environment, such as geography and legal compliance. The best way to find out whether the cloud will work for each of your applications is to plan out a full migration. That will allow you to identify groups of applications that can benefit from cloud offerings such as a global network and ease of resizing resources. After that, try out a proof of concept by testing the apps in the cloud to see if it fits your business needs.

2. Should this app be in Kubernetes?
Containerizing an application simplifies workload administration, improves scalability (both up and down), and increases host utilization. Kubernetes orchestrates the containers and GKE handles node upgrades, while add-ons like Istio let you manage network and security policies independently of your application.

With those advantages, it’s easy to think that containers are always the right way to go, but there are some cases where it may make sense to stick with VMs. Strict hardware requirements, specialized kernel modules, and license constraints may be harder to run with containers, negating their advantages.

3. Should this app migration use Migrate for Anthos?
Migrating your apps or workloads to the cloud isn’t just about shifting where the compute resources run; it’s also an opportunity to modernize them with containers. Using Migrate for Anthos (or Migrate for Compute Engine) gives you the ability to get your workloads in the cloud quickly, with minimal upfront downtime that’s easy to plan for. 

However, even if you use the Migrate for Anthos wrapper, your application is still the same application. The benefits of the modern platform may not outweigh a legacy application and a rewrite may be the only way to meet your business needs. There are also some specific services from your VM that may not work with Migrate for Anthos, for example licensing requirements.

Migrate for Anthos can also be the first step in a larger migration effort. Once you’ve migrated the application to GKE, you can gradually break up a monolithic app into microservices by manually rewriting parts. Spreading out the migration effort gets you in the cloud sooner, giving you more time to modernize.

Next steps

A successful modernization starts with creating a full migration plan, testing the workloads, and monitoring them. You can experience the benefits of modernization with Migrate for Anthos by picking a small workload and trying it out for yourself!

A subsidiary of United States-headquartered corporation Yum! Brands, Pizza Hut prides itself on serving more pizzas than any other pizza business. Founded in 1958, Pizza Hut operates 18,000 restaurants in over 100 countries. In the Indian subcontinent, Pizza Hut and franchise partners Devyani International and Sapphire Foods India operate more than 500 pizza restaurants, including 430 in India itself.

Yum! Brands aims to increase the number of Pizza Hut restaurants in India to 700 by 2022 and has nominated the country as one of the keys to its future growth. The business also operates the KFC and Taco Bell brands in India.

“Globally we are the number one pizza chain in the world based on store count and we aim to be the single biggest pizza brand in India,” says Prashant Gaur, Chief Brand and Customer Officer, Pizza Hut India Subcontinent.

Google Cloud Results

• Maximizes customer coverage and helps ensure riders deliver pizzas to customers within required timeframes
• Onboards new stores to delivery in half a day, rather than the one month required previously
• Meets tech-savvy customer demands to interact across new social media messaging channels
• Launch of live tracking delivers superior customer experience, driving positive word of mouth and repeat business

Pizza Hut launched initially in the country in the late 1990s as a dine-in restaurant brand. However, with changing customer needs, Pizza Hut soon included delivery and takeaway to provide customers with the best tasting pizzas whenever and wherever they wanted them. “Pizza is always at the center of the experience, whether through delivery, dine-in, or takeaway,” says Gaur. “Convenience is key in allowing people to access our products.”

Manual processes

While the business had long shifted into a model that featured delivery and takeaway options, it still used some manual processes. For example, some restaurants used manual listings of customer addresses to manage delivery, which ended up excluding some customers and compromising the brand. In other cases it could take the business up to a week to create a trade zone – a delivery zone assigned to a restaurant – for each new outlet, delaying the commencement of delivery services and costing the business money.

In addition, Pizza Hut India identified an opportunity to more closely track whether pizzas were being delivered within targeted timeframes.

“In some cases, we were using a manual, self-reporting mechanism that provided information about the number of orders that reached consumers less than 30 minutes after an order was placed,” explains Ashish Agarwal, Director, Technology and eCommerce, Pizza Hut India Subcontinent. “We wanted to objectively track and verify delivery times.”

Manual order tracking and execution also limited the number of orders that could be processed effectively during demand peaks. Further, customers could not monitor the status of their pizza orders, including estimated time of arrival.

“Millennial consumers expect products and services to be available when and where they want them. Our focus is to retain the heritage of the brand, which is the dine-in environment, legendary service, and great assets in terms of our stores, while responding to this demand,” adds Gaur.

Pizza Hut India also needed improved analytics in order to identify where the best returns could be achieved by opening new restaurants; how to improve the customer experience; and operate more efficiently.

The business decided to implement a transformation program underpinned by two imperatives: the need to deliver operational efficiencies and scale faster by accelerating the opening of new stores, and the need to give consumers the option of connecting with the brand using the most convenient channel.

A ground-breaking initiative

Pizza Hut India evaluated potential technology partners that could help deliver the program and decided to partner with digital consulting services company MediaAgility, and use Google Maps Platform and Google Cloud Platform services.

“Our journey with MediaAgility and Google incorporated two key initiatives that had a specific impact on our brand and consumers,” says Gaur. “The first of these initiatives was the launch of a feature that enabled consumers and our business to track delivery riders in real time.”

This initiative was ground-breaking for a business that had, until recent years, focused on establishing itself as a restaurant brand. However, with delivery an increasingly important part of its revenue mix, Pizza Hut India decided to build customer engagement through the channel. “By allowing customers to track delivery riders in real time, we could improve engagement – but more importantly give them control,” says Gaur.

During the evaluation, MediaAgility demonstrated Google Maps Platform to Pizza Hut India. “We loved Google Maps Platform as its accuracy and value was proven by consumers using Google Maps for their day-to-day needs,” says Agarwal.

Pizza Hut India conducted brainstorming sessions with MediaAgility and its franchise partners to develop its strategy and complete the implementation. The business then completed several proofs of concept to determine how best to deploy and adapt the technology to some operational processes. “We submitted some data points to our franchise partners and our Pizza Hut brand operations team, and they determined which option to adopt,” says Agarwal.

Google Maps Platform powers delivery

MediaAgility, Pizza Hut India, and the franchise partners then completed a three-month implementation that included onboarding all existing restaurants and new restaurants to the delivery platform based on Google Maps Platform and on Google Cloud Platform.

Pizza Hut India now uses Distance Matrix API through Google Maps Platform to provide travel time and distance based on recommended routes between origins and destinations. This service helps provide delivery riders’ estimated time of arrival to customers.

Directions Service calculates directions by communicating with the Google Maps API Directions Service, which receives direction requests and returns efficient paths based on travel time and factors such as distance and number of turns. This service provides a view of the delivery rider’s position relative to the customer’s location.

Through the Nearest Roads service included in Roads API, Pizza Hut India obtains individual road segments for given GPS coordinates, while Snap to Roads provides the best-fit road geometry for given GPS coordinates.

The business employs Maps Javascript API to customize maps with dedicated content and imagery for websites and mobile devices – showing a map view to store managers and customers – and uses Maps SDK for Android to add maps based on Google Maps to its applications.

Google Cloud Platform runs the delivery platform

Pizza Hut India is running its delivery platform on a Google Cloud Platform architecture that comprises App Engine to run its web applications; virtual machine instances provided through Compute Engine; Cloud Datastore to run a NoSQL document database; Firebase to develop and run its mobile applications; Cloud Storage to store data; and a BigQuery analytics data warehouse.

Realizing goals

With Google Maps Platform and Google Cloud Platform, Pizza Hut India and its franchise partners are realizing the goals of the transformation program.

Rather than take up to seven days to manually map trade zones for stores, Pizza Hut India uses Google Maps Platform to create and update them as required. “After we started working with MediaAgility and Google, we digitized those maps and created trade zones – zones within which Pizza Hut India restaurants will deliver – based on estimated travel times during the busiest time of the week,” says Gaur. “This minimizes the risk of late deliveries.

“The other benefit was reduced time to activate new stores,” he adds. “If you are launching 100 stores per year, this becomes a big, big task. Now we can bring new stores into the market much more quickly.”

With MediaAgility and Google Maps Platform, the business can also help ensure newly built establishments – such as blocks of flats – are captured within trade zones, allowing stores to deliver to residents.

Delivery accounts for increased transactions

Pizza Hut India now automatically allocate orders to delivery riders using a rider tracking application on their mobile phones. When a rider starts his or her journey, Google Maps Platform enables point-by-point tracking by consumers and store managers. The Pizza Hut India delivery operations team monitors delivery performance through a real-time dashboard.

Pizza Hut India is meeting customer expectations of live, map-based streaming of delivery status on their devices – enhancing customer experience and loyalty, and adding accountability to the process. The business is reaping the rewards of its investment, with delivery now a large slice of its overall offering. “We have taken significant strides in the past three to four years to change our customers’ online ordering experience, and the last-mile delivery experience to the customers’ homes,” says Gaur.

Launching delivery tracking has also had a dramatic impact on Pizza Hut India’s internal key performance indicators. “The proportion of calls to our call center that are following up on an order, as opposed to placing an order, has fallen dramatically,” says Gaur.

Advanced analytics

Further, Pizza Hut India is running advanced analysis of data in the BigQuery data warehouse, enabling the business to determine which restaurants are doing well, which deliveries may be delayed, and what locations are most promising to open a new store. These insights enable the business to boost productivity, expand effectively, and operate more efficiently.

The business can now onboard new stores to delivery in half a day, rather than the month required previously. “The process enabled by Google Cloud and MediaAgility is also delivering significant operational cost savings as well as helping us open and grow new stores quickly,” says Agarwal.

“MediaAgility acted as our development partner across the project, helping us deploy everything from zones to rider tracking,” he says. “It’s been with us from the strategy discussion through the implementation and stabilization phases.”

Chatbot in development

MediaAgility has also helped Pizza Hut India create a chatbot using the Dialogflow development suite for creating conversational interfaces. “This project is about giving millennials and other customers one more channel to reach out and connect to the brand,” explains Agarwal.

Pizza Hut India is now ideally placed to continue growing and position itself as a brand of choice for tech-savvy consumers. “We’re extremely pleased with the contribution of all the parties involved in this project and look forward to continue transforming our business to meet the demands of the digital age,” says Agarwal.

While Gaur acknowledges it is difficult to predict change over the next two to five years, he believes delivery is likely to become more prominent in Pizza Hut India’s combination of offerings. “When we began our online journey in 2016, we predicted delivery would be about 25 percent of the mix by 2020,” he says. “With Google and MediaAgility, I think it will keep growing.”

Hi there! I’m David Challoner from Access Site Reliability Engineering (SRE), here with Anthony Bushong from Developer Relations to talk about how Corp Eng is adopting Anthos Service Mesh internally at Google.

Corp Eng is Google’s take on “Enterprise IT”. A big part of the Corp Eng mission is running the first and third party software that powers internal business processes – from legal and finance to floor planning and even the app hosting our cafe menus – all with the same security or production standards as any of Google’s first party applications.

Googlers need to access these applications, which sometimes then need to access other applications or other Google Cloud services. This traffic can cross different trust boundaries which can trigger different policies.

Access SRE runs the systems that mediate this access, and we implemented Anthos Service Mesh as part of our solution to secure the way Googlers access these applications.

But why?

You can probably tell, but the applications Corp Eng is responsible for have disparate requirements. This often means that certain applications are tied to disparate infrastructure due to legal, business or technical reasons – which can be challenging when those infrastructures work and operate differently.

Enter Anthos. Google Cloud built Anthos to provide a consistent platform interface unifying the experience of working with apps on these varying underlying infrastructures, with the Kubernetes API at its foundation.

So when searching for the right tool to build a common authorization framework to mediate access to CorpEng services, we turned to Anthos – specifically Anthos Service Mesh, powered by the open-source project, Istio. Whether these services were deployed in Google Cloud, in Corp Eng data centers, or at the edge onsite at actual Google campuses, Anthos Service Mesh delivered a consistent means for us to program secure connectivity.

To frame the impact ASM had on our organization, it’s helpful to introduce the roles of the folks who manage and use it:

For security stakeholders, ASM provides an extensible policy enforcement point running next to each application capable of provisioning a certificate based on the identity of the workload and enforcing mandatory fine-grained application-aware access controls.

For platform operators, ASM is delivered as a managed product, which reduces operational overhead by providing out-of-the-box release channels, maintenance windows, and a published Service Level Objective(SLO).

For service owners, ASM enables the decoupling of their applications from networking concerns, while also providing features like rate limiting, load shedding, request tracing, monitoring, and more. Features like these were typically only available for applications that ran on Borg, Google’s first-party cluster manager that ultimately inspired the creation of Kubernetes.

In sum, we were able to secure access to a plethora of different services with minimal operational overhead, all while providing service owners granular traffic control.

Let’s see what this looks like in practice!

The architecture

In this flow, user access first reaches the Google Cloud Global Load Balancer [1], configured with Identity Aware Proxy (IAP) and Cloud Armor. IAP is the publicly available implementation of Google’s internal philosophy of BeyondCorp, providing an authentication layer that works from untrusted networks without the need for a VPN.

Once a user is authenticated, their request then flows to the Ingress Gateway provided by Anthos Service Mesh [2]. This provides additional checks that traffic flows to services only when the request has come through IAP, while also enforcing mutual TLS (mTLS) between the Anthos Service Mesh Gateway to the Corp services owned by various teams.

Finally, additional policies are enforced by the sidecar running in every single service Pod [3]. Policies are pulled from source control using Anthos Config Management[4], and are propagated to all sidecars by the managed control plane provided by Anthos Service Mesh[5].

Managing the mesh

If you’re not familiar with how Istio works, it follows the pattern of a control plane and a data plane. We talked a little bit about the data plane – it is made up of the sidecar containers running alongside all of our service Pods. The control plane, however, is what’s responsible for updating these sidecars with the policies we want to enforce:

Thus, it is critical for us to ensure that the control plane is healthy. This is where Anthos Service Mesh gives our platform owners a huge advantage with its support for a fully-managed control plane. To provision cloud resources, like many other companies, our organization uses Terraform, the popular open-source infrastructure as code project. This gave us a declarative and familiar means for provisioning the Anthos Service Mesh control plane.

First, you enable the managed control plane feature for GKE by creating the google_gke_hub_feature resource below using Terraform.

resource "google_gke_hub_feature" "feature_asm" {
name = "servicemesh"
location = "global"
provider = google-beta
}

Keep in mind that at publication time, this is only available via the google-bet provider in Terraform.

Once created, we then provision a ControlPlaneRevision custom resource in a GKE cluster to spin up a managed control plane for ASM in that cluster:

apiVersion: mesh.cloud.google.com/v1alpha1
kind: ControlPlaneRevision
metadata:
  
name: asm-managed
  
namespace: istio-system
spec:
  
type: managed_service
  
channel: regular

Using this custom resource, we are able to set the release channel for the ASM managed control plane. This allows for our platform team to define the pace of upgrades in accordance with our team’s needs.

In addition to managing the control plane, ASM also provides management functionality around the data plane to ensure each sidecar Envoy is kept up to date with the latest security updates and is compatible with the control plane – one less thing for service operators to worry about. It does this using Kubernetes Mutating Admission Webhooks and Namespace labels to modify our Pod workload definitions to inject the appropriate sidecar proxy version.

Syncing mandatory access policies

With the core Anthos Service Mesh components in place, our security practitioners can define consistent, mandatory security policies for every single GKE cluster, using Istio APIs.

For example, one policy is enforcing strict mTLS between Pods using automatically provisioned workload identity certificates. Earlier, we talked about how this is enforced between the Istio Gateway; that same policy enforces mTLS between all Pods in our cluster.

Another policy we implement is denying all egress traffic by default, requiring service teams to explicitly declare their outbound dependencies. The following is an example of using an Istio Service Entry to allow granular access to a specific external service – in this case, Google. This helps prevent unintended access to external services.

apiVersion: networking.istio.io/v1alpha3

kind: ServiceEntry
metadata:
  
name: google
spec:
  
hosts:
  - www.google.com
  
ports:
  - number: 443
    
name: https
    
protocol: HTTPS
  
resolution: DNS
  
location: MESH_EXTERNAL
EOF

These policies are automatically synced to all service mesh namespaces in each cluster using Anthos Config Management. By using our internal source control system as a source of truth, Anthos Config Management can sync and reconcile policies across all of our GKE clusters, ensuring that these policies are in place for every single one of our services. You can find more details about our implementation of Anthos Config Management here.

With this in place, our team plans on eventually migrating away from security automation that operates solely based on explicit IP, port and protocol policies.

Integration with Identity-aware Proxy

The publicly available version of the BeyondCorp proxy used by CorpEng is called Identity-aware Proxy (IAP), which offers an integration with Anthos Service Mesh. IAP allows you to authenticate users trying to access your services and apply Context-Aware-Access policies. This integration comes with two main benefits:

• Ensuring that user traffic to services in the service mesh only come through Identity-aware Proxy
• Enforcing Context-aware access (CAA) trust levels for devices, defined by multiple device signals we collect

Identity-aware Proxy allows us to capture this information in a Request Context Token (RCToken), which is a JSON Web Token (JWT) created by Identity-aware Proxy that can be verified by ASM. IAP inserts this JWT into the Ingress-Authorization header. Using Istio Authorization Policies similar to the following policy, any requests without this JWT are denied:

apiVersion: security.istio.io/v1beta1
kind: AuthorizationPolicy
metadata:
name: iap-gateway-require-jwt
namespace: istio-system
spec:
selector:
matchLabels:
app: istio-iap-ingressgateway
action: DENY
rules:
- from:
- source:
notRequestPrincipals: ["*"]

Here is an example policy that requires a fullyTrustedDevice access level – this might be a device in your organization that is known to be corporate-owned, fully-updated, and running an IT-approved configuration :

apiVersion: security.istio.io/v1beta1
kind: AuthorizationPolicy
metadata:
  name: require-fully-trusted-device
  namespace: fooService
spec:
  selector:
    matchLabels:
      app: fooService
  action: ALLOW
  rules:
  - from:
    - source:
       requestPrincipals: ["*"]
    when:
    - key: request.auth.claims[google.access_levels]
      values: ["accessPolicies/$orgId/accessLevels/fullyTrustedDevice"]

This allows our security team to not only secure service to service communications, or outbound calls from services, but also specifically require incoming requests come from trusted devices and authenticated users using a trusted device.

Enabling service teams

As an SRE, one of our priorities is ensuring Service-level indicators (SLIs), SLOs, and Service-level agreements (SLAs) exist for services. Anthos Service Mesh helps us empower service owners to do this for their services, as it exposes horizontal request metrics like latency and availability to all services in the mesh.

Before Anthos Service Mesh, each application had to export these separately (if at all). With ASM service owners can easily define their Service’s SLOs in the cloud console or via terraform using these horizontally exported metrics. This then allows us to integrate SLOs into our higher-level service definitions so we can enable SLO monitoring and alerting by default. You can see the SRE book for more details on SLOs and Error budgets.

The takeaway

ASM is a powerful tool that enterprises can use to modernize their IT infrastructure. It provides:

• A shared environment-agnostic enforcement point to manage security policy
• A unified way to provision identities, describe application dependencies

This also enables previously unheard of operational capabilities such as distributed tracing or incremental canary rollouts – which were difficult to find in the typical enterprise application landscape.

Because it can be incrementally adopted and composed with existing authorization systems to close gaps – barriers to adoption are low and we recommend you start evaluating it today!

Today we’re hosting our Retail & Consumer Goods Summit, a digital event dedicated to helping leading retailers and brands digitally transform their business. For me, this is a personally exciting moment, as I see tremendous opportunities for those companies that choose to focus on their customers and leverage technology to elevate experiences.

Our event includes breakout sessions to help retailers and brands become customer centric, embrace the digital moment and transform their operations. Some of my favorite sessions include: 

• Why Search Abandonment is the metric that matters, highlighting Retail Search, and featuring a conversation with Macy’s
• Driving Consumer Closeness in a Privacy-Centric World, discussing how retailers and brands can create a successful first party data strategy, featuring a conversation with P&G
• The Modern Store: 7 Innovation Hotspots, sharing how retailers and brands can approach store transformation to unlock the most value from technology, featuring a conversation with The Home Depot.   

I’ll be speaking in our Retail Spotlight session, discussing the current retail landscape and our industry approach, followed by conversations with Albert Bertilsson, Head of Engineering – Edge at IKEA Retail (Indga Group) and Neelima Sharma, Senior Vice President, Technology Ecommerce, Marketing and Merchandising at Lowe’s. 

Let me share a bit more about the topics we’ll discuss in that session.

In retail specifically, digital-first shopping journeys are blurring the lines between the physical and digital brand experience. Shoppers want to know what’s available before they visit your stores, and they expect fulfillment options like curbside pickup. We see this when tracking trends for interest in curbside pickup or in-stock items.

This has left many retailers asking how they can get smarter with their data, tackle the $300 billion dollar problem of “search abandonment,” move faster to create new customer experiences, and do a better job of connecting their employees and customers – with confidence.

Our team has been spending time thinking about how we can rise and succeed in this new era together. We continue to focus on areas where we can bring the best of our capabilities to our retail customers around the world. And we’re focused on ways we can bring the best of what Google has to offer through cloud integrations.

Our goal is to help retailers become customer-centric and data-driven, capture digital and omni-channel revenue growth, create the modern store and drive operational improvement.

Let’s dig into each of these strategic pillars in a bit more detail. 

Become customer centric and data driven

Customers today expect experiences that are timely, targeted, and tailored for them and their needs, and reject experiences that can’t deliver these features. Data modeling, legacy technology, and siloed systems often prevent retailers from providing that level of personalized experience. 

At Google Cloud, we work with global retailers and our ecosystem partners to activate and bring value from first-party data, particularly in the field of customer data platforms (CDPs). This includes integrations from Google Cloud, such as our business intelligence platform Looker and other popular platforms to power one source of customer data through the organization. We also help retailers modernize their data warehouse with Looker for gathering business intelligence across their organization. This is important not just for consumer data, but inventory, supply chain, and store operations as well. 

Capture Digital and Omnichannel Growth 

We power some of the largest e-commerce sites in the world, helping them scale for Black Friday, Cyber Monday, and other holiday events. While scale is critically important, it’s also important to consider the quality of the online experience. How do your customers find products? How can you help deliver seamless online and omnichannel experiences? 

To help, we’re building product discovery solutions that bring together the best of our technologies that help retailers drive engagement with their consumers. Retail Search, for example, gives retailers the ability to provide Google-quality search on their own digital properties – search that is customizable for their unique business needs and built upon Google’s advanced understanding of user intent & context. 

The imperative is clear. Recent research found that retailers lose more than $300 billion to search abandonment — when purchase intent is not converted into a sale due to bad search results — every year in the US alone. 

Today, we announced that Retail Search is available to a larger set of retailers. If you are interested in learning more about Retail Search you can contact your sales representative for additional details.

Create the modern store  

With the rise of buying trends like curbside pickup and proximity-based search, our Google Maps Platform team is working on new products and features to help raise inventory awareness for your shoppers. We want to help you make it easier for them to understand what’s available to purchase in their channel of choice.

With Product Locator, each product page connects customers with information they need for local pickup and delivery options. This ensures customers are aware of pickup and delivery options throughout the buying journey—not just checkout. 

Awareness of local inventory can boost a wide range of key metrics for your business. Shopify recently shared that shoppers who opt for local pickup over delivery had a +13% higher conversion rate and that 45% of local pickup customers make an additional purchase upon arrival.

This is just one quick example of how our Google Maps Platform team can improve experiences for your shoppers.

Operational improvement

It can be challenging to operate in a world and at a time when consumer behavior and supply chains are so disrupted and volatile, and where entire retail teams had to go remote during the pandemic and beyond. 

We’re working with retailers to leverage artificial intelligence (AI) to improve consumer experience through chat bots or conversational commerce that solves problems for customers from anywhere. You can learn more about these offerings in our Conversational Commerce with Google breakout session, featuring Albertsons.

As the need for digital transformation continues to accelerate, Google Cloud is helping retailers stay ahead of the curve with solutions for digital and omnichannel growth, data-driven and customer-focused experiences, and operational improvement. For every era of cloud technologies, from the past into the future, Google Cloud is committed to providing solutions to retailers.

Read more about our solutions for retail, and check out additional sessions, including the CPG Industry Spotlight Session How To Grow Brands in Times of Rapid Change – Featuring L’Oréal at our Retail & Consumer Goods Summit.