How Google Ads agencies build extra, stable revenue with White Label CSS

An outside service becomes your own agency product

CSS stands for Comparison Shopping Service. In the participating European markets, Shopping ads run through such a service. Google Shopping is one of them. The ads carry the CSS name in the "By …" link (Google: Advertising with comparison shopping services).

With a White Label CSS that line carries your own CSS name. The comparison shopping platform wears your branding while the infrastructure partner handles the technical operation. You are no longer referring clients to somebody else — you are selling a service under your own brand.

For clients who currently use Google Shopping as their CSS, the commercial starting point is that the Google Shopping margin no longer applies. Google describes how that margin is deducted from the merchant's bid before the auction (Google: Advertising with comparison shopping services).

If a client already uses an external CSS, your extra selling point is mainly single-source support: campaigns, feeds and CSS become part of one offering. Moving between two external CSS providers does not in itself create an additional bidding advantage.

What can your agency earn from it?

The business model is simple: you pay for the white label infrastructure and charge your clients a monthly usage fee.

At csspartner.io the White Label CSS costs £89 per month per agency, regardless of how many merchants you run on it, plus a one-off £449 setup fee. Your own selling price is entirely up to you.

As a worked example, take an end-client price of £35 per merchant per month:

A model calculation with £35 per merchant per month and £89 in monthly platform costs. All amounts are net. The annual figure assumes twelve fully paid months with an unchanged client count. The last column shows revenue minus platform costs, not net profit. Setup, staff, sales and your other costs still come off.

In this example three paying merchants already cover the ongoing platform fee. At 25 merchants you add £875 of monthly revenue. At 50 merchants it is £21,000 a year.

Your pricing should reflect more than the technical connection, though. A bare CSS offering deserves a different calculation from a package with regular feed optimisation, Merchant Center support and personal advice. Price extra service explicitly instead of folding an unlimited amount of it into a small CSS flat fee.

Why this income is easy to plan for

A monthly CSS fee follows a different logic from a one-off consulting project: you don't have to sell the same service again every month. As long as the client uses and pays for the agreed service, the revenue recurs.

With a fixed monthly price, your CSS income also doesn't drop automatically the moment a client cuts their ad budget. You are charging for the service, not for a percentage of the current media spend.

What makes the model stable is a clear scope of service, reliable billing and satisfied clients. Recurring income is not uncancellable income — but you can plan it from your active client base far more concretely than projects you haven't sold yet.

There is a further strategic advantage: CSS and campaign management can be offered as separate services. If a client later brings campaign work in-house, they can keep using your CSS. Technically, the CSS assignment in the Merchant Center and the management of the Google Ads account are two different things (Google: Move merchant accounts between CSSs).

So the end of a management mandate doesn't have to mean the end of all income from that client relationship.

How much work does it create?

The attractive maths works because your agency doesn't have to build and run the CSS infrastructure itself. At csspartner.io we set up the branded comparison shopping site, handle the technical configuration and the CSS application, support the merchant onboarding and run the platform day to day.

What stays with you is mainly the commercial and personal side. At the start you decide on the CSS name, the branding, the offering and your client prices. Then you present the service to your clients and coordinate the approvals it needs.

In day-to-day operation you handle billing, client communication and the questions that fall to your agency within the agreed scope. Technical edge cases go to the infrastructure partner.

A pure CSS switch does not require rebuilding the Google Ads accounts. Existing Merchant Center accounts can be assigned to a different CSS; the Google Ads accounts don't have to be migrated for it (Google: Move merchant accounts between CSSs).

You should still put a time allowance into your business case. An example: you reserve three hours a month for 25 merchants and cost your own time internally at £55 an hour.

The three hours are a planning assumption, not a guaranteed support allowance. What matters is recording your actual effort and drawing the boundaries of the service accordingly.

White Label CSS decouples extra revenue from building your own technology. It doesn't replace client service — but it does make an extra product possible without any extra platform development.

Client lock-in: your agency becomes harder to replace

A client who buys nothing but campaign management from you is judging that one service. With an integrated offering, the basis of the relationship changes.

You are no longer just looking after ads. You are connecting strategy, campaigns, product data, Merchant Center and CSS into one solution.

The strategic thought behind it: a competitor has to offer more than a lower management fee. They have to convince the client that their whole package improves a collaboration that already works.

Technically, a CSS switch stays possible at any time. It is initiated by the new CSS and has to be approved by an administrator of the Merchant Center account (Google: Move merchant accounts between CSSs). White Label CSS does not make clients immovably dependent.

Your aim should therefore be to make the benefit of the integration visible: clear responsibilities, short lines of communication and one contact who knows the entire Shopping setup. That gives clients additional reasons to stay.

Better protection against poaching

An external CSS provider doesn't have to supply infrastructure only. Google describes models in which CSS providers also optimise feeds, manage campaigns or advise (Google: Working with comparison shopping services). Their offering can therefore overlap with your agency services.

At the same time, the CSS in use gets a visible spot in the Shopping ads through the "By …" link, which leads to its own comparison shopping site. With a White Label CSS you use that spot for your own brand. It reduces the need to introduce another visible provider into your client relationship.

This does not replace a non-solicitation agreement. When you choose your infrastructure partner you should set out explicitly how client contacts are handled: no independent sales approaches to the clients you bring in, clear communication channels and technical support coordinated with your agency.

That is how you close off one concrete opening: you don't have to hand a potential competitor a visible place inside your own client offering.

Getting started with a CSS partner is manageable

You don't need a development project of your own to get going. The process breaks down into four steps:

1. 1Define the offering and the brand. You decide on the CSS name, the domain, the branding and your client prices. You also define which services are included in the monthly fee.
2. 2Have the infrastructure set up. The white label partner builds the comparison shopping site, configures the CSS account and supports the Google approval process. After that you get access and an introduction.
3. 3Bring your existing clients across. Migration works by changing the Merchant Center account's assignment. The client approves the request. A 14-day grace period then runs before the switch takes effect; the previous CSS can shorten it or waive it (Google: Move merchant accounts between CSSs).
4. 4Standardise billing and support. You add the monthly service to your billing, use a consistent onboarding process and decide which questions your team answers and which go to the infrastructure partner.

Before every migration, check the countries, ad surfaces and account permissions you need. Google points out that these can depend on the CSS you choose and on the specific setup (Google: Working with comparison shopping services).

Start with the clients you already look after

To build a CSS business you don't have to open up a new audience first. The obvious starting point is your existing Shopping clients.

Check which CSS they use, how the service is billed today and what your integrated offering gives them. Start with a small group, measure the support effort for real, and then roll the working process out to more merchants.

Make a deliberate choice between extra revenue and extra package value: sell CSS separately and you create a new monthly line item. Fold it into an existing retainer without adjusting the price and you strengthen your offering — but not automatically your revenue.

White Label CSS can do both: build a revenue stream of its own and strengthen your existing client relationships. csspartner.io gives you the infrastructure for it. You turn it into your offering, set the price and develop the client relationship from there.

Don't just sell Google Shopping management. Make the CSS service a product of your own agency — and earn from it month after month.