White Label CSS: How Agencies Expand Their Google Shopping Offering Without Their Own CSS Infrastructure

What is a Comparison Shopping Service?

A Comparison Shopping Service, or CSS for short, is a price comparison service that gathers product offers from various merchants and allows users to compare products, prices, and providers.

In countries participating in the European CSS programme, Shopping ads and free product listings are displayed via a CSS. Merchants can use either Google Shopping or another Comparison Shopping Service for this. The programme applies in countries including Germany, Austria, Switzerland, France, Netherlands, Spain, Italy, and the United Kingdom.

The CSS takes on the formal role of the comparison service through which the merchant's products are submitted for Shopping ads on Google. The actual campaigns can still be managed by the agency or the merchant themselves.

Google fundamentally distinguishes between different forms of collaboration:

• With a Managed Service, the CSS manages product data and campaigns.
• In the Self-Service model, the merchant or their agency gains access to Merchant Center and Google Ads and manages everything themselves.
• In hybrid models, feed management, campaign control, and billing are divided between the CSS, agency, and merchant.

White Label CSS is not an official Google programme type in itself. Rather, it is a sales and service model built on one of these technical configurations.

What Exactly Does White Label CSS Mean?

In a White Label model, it's not the technical CSS provider that takes centre stage, but the managing agency.

To the merchant, the CSS service appears to be an integral part of the agency's offering. Communication, onboarding, support, reporting, and billing can be entirely under the agency's brand. The underlying CSS infrastructure is provided by a specialised vendor.

The distribution of roles could, for example, look like this:

The exact division depends on the White Label provider. Some solutions merely provide the necessary CSS assignment. Others additionally offer APIs, merchant management, automated onboarding, feed technology, support, or a fully customisable client portal.

Why an Agency Doesn't Simply Become a CSS Itself

At first glance, an agency could also build its own Comparison Shopping Service. Technically, this is generally possible, but in practice, it is significantly more complex than setting up another Google Ads offering.

For participation in the CSS programme, Google requires, among other things, a registered company in a supported country and a functional price comparison website where users can search for and compare products from different merchants. Participating CSS websites are regularly reviewed.

But that's not all. A proprietary CSS also requires:

• a stable product data infrastructure
• scalable merchant management
• processes for Merchant Center linking
• a functional price comparison platform
• data protection and contractual processes
• technical monitoring
• support and escalation processes
• ongoing adaptations to Google guidelines

For a large platform or an agency with several hundred Shopping clients, this investment can be worthwhile in the long run. For most agencies, however, a White Label solution is the faster and economically less risky path.

The agency can focus on its core strengths: acquiring clients, optimising campaigns, and delivering measurable e-commerce results.

The Service Offering Remains Under Your Own Brand

If a merchant uses an external CSS provider directly, an additional visible client relationship arises alongside the agency. The merchant receives invoices, emails, access, or support from an additional company.

In a White Label model, the agency remains the central point of contact. The CSS service is not perceived as an outsourced service, but as part of its own Shopping offering.

This strengthens the agency's position with the client. It not only manages campaigns but also provides the entire operational Shopping structure.

The Agency Retains Control Over the Client Relationship

Especially for large online shops, access to Merchant Center, product feeds, and Shopping campaigns is strategically relevant. An external provider who communicates directly with the merchant can eventually become a service provider or competitor themselves.

A well-structured White Label model reduces this risk. The infrastructure partner works in the background, while consulting, strategy, and operational support remain with the agency.

However, this requires clear contractual agreements. These include, in particular, client protection, data protection, support responsibilities, data access, and the terms of termination of collaboration.

Faster Market Entry and Recurring Revenue

Building a proprietary CSS involves more than just software development. The price comparison site, merchant processes, account management, and programme participation must also be prepared.

With an existing White Label infrastructure, an agency can introduce the offering much faster. Often, only its own pricing model, client communication, and onboarding process need to be defined. This transforms a technically complex infrastructure service into a standardised agency product.

White Label CSS is particularly well-suited for monthly recurring revenue. The agency can, for example, offer the service as a fixed component of a Shopping package:

• CSS Basic for smaller merchants
• CSS Professional including feed monitoring
• CSS Managed including campaign control
• Enterprise CSS with API, individual reporting, and support

In addition to a fixed monthly fee, volume-based models are also conceivable, such as by number of Merchant Center accounts, countries, products, or managed ad budget.

It's important that the agency doesn't just sell a technical account switch. The lasting value comes from combining it with other services like feed optimisation, Merchant Center support, product data analysis, and campaign management.

How Merchant Onboarding Works

An existing Merchant Center account can generally switch from one CSS to another. The new CSS initiates the switch, after which a Merchant Center account administrator can approve or reject the request. The Google Ads account itself usually does not need to be changed.

A typical White Label onboarding process consists of five steps.

1. Technical and commercial review: First, it is checked in which countries the merchant is active, which Merchant Center accounts exist, and which CSS is currently assigned. Additionally, it should be clarified who manages the Merchant Center, who has administrator rights, which Google Ads accounts are linked, whether free product listings are used, whether dynamic remarketing or other product-based campaigns are running, and whether products are also displayed outside Europe.

2. Merchant's consent: The agency transparently explains to the merchant which CSS will formally represent them in the future and which tasks the agency and infrastructure partner will each undertake. White Label should not mean obscuring the actual provider. At the latest, in contracts, data protection notices, and account assignments, the involved companies must be clearly named.

3. Initiating the CSS change: The new CSS or the White Label infrastructure partner initiates the transfer of the Merchant Center account. The merchant then receives a request that must be approved by an administrator. Only then can the account be assigned to the new CSS. A Merchant Center account can only be assigned to one CSS at a time. However, a merchant can work with multiple CSSs if different Merchant Center structures or campaign constellations are used for this purpose.

4. Review of display surfaces: Not every CSS automatically supports all product-based display surfaces. By default, a CSS can place products in the Shopping units of general Google search results. For other surfaces like the Shopping tab, YouTube, the Display Network, or certain remarketing applications, the CSS must be appropriately set up or approved. This point is particularly important if the merchant uses Performance Max, dynamic remarketing, or international Shopping campaigns.

5. Control after the switch: After the switch, the agency and provider should jointly check whether all products are still active, whether the existing Google Ads links remain, whether conversion tracking works, whether free product listings are displayed, whether all required countries are available, whether new rejections or policy issues arise, and whether the delivery on individual Google surfaces changes. Only after this check should onboarding be considered complete.

Do Smart Bidding and Conversion Tracking Remain Usable?

Yes. According to Google, all participating CSSs generally have access to the same relevant campaign features, including conversion reporting and automated bidding strategies.

Conversions can be provided via Google Ads tracking, a shared Google Ads manager account, or Google Analytics, among other methods. Compatible external bidding systems can also continue to be used.

For agencies, this means: Switching to a White Label CSS does not automatically require a new campaign strategy. Existing Shopping or Performance Max structures can often be continued, provided Merchant Center, Google Ads, and conversion data remain correctly connected.

Caution with Blanket CPC Promises

CSS offers are often advertised with a blanket promise of cost-per-click savings. Agencies should not accept such claims unchecked.

Google calculates the actual ad price based on the auction. Additionally, CSS providers' business models differ: some charge a fixed monthly fee, others a CPC surcharge, a commission, or a combination of several components.

A reputable agency should therefore not promise a guaranteed percentage CPC reduction. The overall economic efficiency is crucial:

• How high are the CSS fees?
• What additional services are included?
• How does campaign performance change?
• What time does the agency save?
• What additional revenues can be generated?
• What technical or operational risks are assumed?

White Label CSS should not be positioned solely as a discount model. The greater strategic value lies in controlling one's own service offering and the ability to provide scalable Shopping services under one's own brand.

What Agencies Should Look for in a White Label Provider

The cheapest provider is not automatically the best infrastructure partner. A switch affects central merchant accounts and can have immediate consequences for product display. Therefore, at least the following points should be checked before collaboration.

Supported display surfaces: Can the CSS only place Shopping ads in general search or does it also support other Google surfaces? This question is particularly relevant for Performance Max campaigns and dynamic remarketing.

Ownership and access to accounts: The agency should clarify who owns the Merchant Center and Google Ads accounts and who has administrator rights. Ideally, merchants and agencies retain permanent access. A change of provider should not lead to the loss of important accounts, data, or historical campaign values.

Automation and API: For a small number of merchants, onboarding can be done manually. However, for a larger number of clients, automation becomes crucial. A good White Label solution should at least offer structured processes for creating and assigning new merchants, monitoring switch status, managing multiple Merchant Center accounts, retrieving account status and errors, mapping different pricing tiers, generating billing data, and managing roles and permissions.

Branding: White Label means more than a logo in the client portal. Brand capability also includes custom sender addresses, individual domains or subdomains, customisable reports, proprietary contract and proposal documents, branded onboarding communication, and consistent support processes. The less visible the technical provider is to the merchant, the more consistent the agency's offering appears. Nevertheless, the legally required transparency about involved companies must be maintained.

Support and escalation: Merchant Center issues can cause direct revenue losses. Therefore, a general email inbox often isn't sufficient as a support model. The agency should know what response times apply, who assists with account suspensions, who reviews rejected products, who communicates with Google, whether there's an emergency contact, and whether support is available in the relevant languages.

Exit process: Even before the contract begins, it should be clear how merchant accounts will be returned or transferred to another CSS upon termination. Google provides processes for migrating merchant accounts between CSS providers or back to Google Shopping CSS. However, the specific implementation, deadlines, and responsibilities should still be clearly defined contractually.

For Which Agencies is White Label CSS Worthwhile?

This model is particularly suitable for agencies that already manage several online shops and want to professionalise their Shopping offering. It is especially useful if the agency:

• regularly acquires new Shopping clients
• manages many Merchant Center accounts
• offers feed optimisation
• manages Performance Max campaigns
• wants to build recurring software or service revenues
• wants to control the entire client relationship itself
• wants to develop a standardised e-commerce package

The model is less suitable for agencies that only occasionally manage Shopping campaigns or lack resources for Merchant Center support and product data issues.

White Label relieves the agency of the technical CSS infrastructure. However, it does not replace the professional support of the merchant.

From Supplementary Service to Proprietary Product

The biggest mistake would be to treat White Label CSS merely as a small additional item on the invoice. The stronger offering is created by combining several services:

Thus, the agency doesn't just sell access to a CSS. It offers a complete Shopping infrastructure that is closely linked to campaign management.

Conclusion: More Control, More Client Loyalty, More Recurring Revenue

White Label CSS enables Google Ads agencies to offer a technically sophisticated service under their own brand, without having to develop and operate a complete Comparison Shopping Service themselves.

The agency remains the central point of contact, expands its value creation, and can transform a previously externally sourced service into its own recurring product.

The decisive advantage here is not a blanket promise of lower click costs. White Label CSS primarily creates control: over the client relationship, the service offering, pricing, and the entire Shopping infrastructure.

For agencies that already manage multiple e-commerce clients, this can lead to a scalable new business area – closely linked to Feed Management, Merchant Center, Performance Max, and Google Shopping.