White Label CSS: how to operate as a Google CSS under your own name

Your clients save 20% CPC or bid with 25% more bidding power

Without their own CSS, Google Shopping keeps a markup on every click. Of a £1 bid, only 80p reaches the auction.

Through your White Label CSS, the full pound goes into the auction. For the same position, your clients save 20% CPC; on the same budget, they bid with 25% more bidding power.

The online shop shop4runners saves around 20% CPC after switching to our CSS.

You decide what your clients pay for CSS access

We charge you £89 a month per agency and a one-off £449 for setup. With annual billing, you only pay for ten months.

You decide what price you quote your clients, and whether to include access in your retainer. You pay the fee once for your agency, and every client with CSS access increases your margin.

The client relationship, campaigns and margin stay with you

The client relationship and the margin belong to you. Your clients' campaigns, bid strategies and conversion data keep running unchanged through the switch.

If you don't offer CSS, your client books it elsewhere

Any merchant can book a CSS themselves today. If your client does that without you, another provider's name appears under their ads.

If you set up the CSS under your brand, the advantage becomes part of your service.

White Label CSS costs you £89 a month per agency plus a one-off £449

Building your own CSS involves software development, a price comparison page, merchant processes and programme participation. With white label you launch the offer faster and only need to define the pricing model, client communication and onboarding.

If you pay annually, you pay for ten months instead of twelve. We handle approval, the price comparison page and Google's requirements; the client relationship and client pricing stay with you.

Building your own CSS only pays off once you have several hundred Shopping clients

For the CSS programme, Google requires a company registered in the target country and a working price comparison website with merchant search, which Google reviews regularly.

On top of that come a stable product data infrastructure, Merchant Center integration, data protection and contract processes, plus ongoing adjustments to Google's requirements.

For most agencies, white label is the quicker, lower-risk route: you focus on winning clients and optimising campaigns, while the partner runs the infrastructure.

You build a complete Shopping package around the CSS

Combine White Label CSS with further services and you get one connected offer:

1. Define first what you offer your clients

With a White Label CSS, a provider supplies the agreed technical infrastructure while you market the service under your brand. Which tasks the partner takes on depends on the contract: comparison shopping website, set-up, hosting, merchant onboarding, support and reporting can be split in different ways.

So before you look for a provider, decide how CSS fits into your business model.

This decision shapes your workload. If you sell only a CSS connection, decide whether fixing product errors is included. Otherwise a small monthly fee quickly turns into extensive account management.

2. Assess the partner against your operating model

A low purchase price is of little use if every client onboarding needs several rounds of coordination. Before signing, ask the provider to show you how a new client is added, how you check the status and how a problem is escalated.

In particular, clarify:

• Brand and domain: Which of your own domains and which CSS display name will be used? Where does the technical provider still appear?
• Scope of services: Who runs the website, updates product data and handles technical faults?
• Client management: Do you work in CSS Center or through support?
• Costs: Is billing per merchant account, MCA, shop or domain? Are there minimum volumes and extra costs?
• Support: Who can be reached, how quickly do they respond and who communicates with Google?
• Exit: What happens to the domain, data and merchant connections when the contract ends?

Ask for a billing calculation based on your actual client base. Ten shops with one account each may be treated differently from one merchant with several sub-accounts.

3. Set up your own CSS brand

Prepare a complete set-up package: preferred name, domain, logo, company details, contact person, support address and planned target countries. Agree with the provider which DNS records are needed and who sets them.

Your own domain should ideally sit in a domain account controlled by your agency. For support and system notifications, a central address such as css@deine-agentur.de works well, with an inbox that several responsible people can handle.

The set-up includes a working comparison shopping website. Among other things, Google requires product search, comparison options and sorting or filtering functions. For every participating country, there must be offers from at least 50 different merchant domains whose merchants deliver to that country. This does not mean your agency already needs 50 paying CSS clients. What counts are the merchant offers available on the website. Clarify with the partner how they will meet these requirements on an ongoing basis. Google: Comparison Shopping Service requirements

Don't confuse technical completion with Google approval. Just because the website is live doesn't mean you can manage clients through it yet.

For a new CSS set-up, Google describes a registration process with a new Merchant Center account, domain verification and a subsequent application to convert it into a CSS multi-client account. With White Label, decide beforehand which steps your provider takes on and which details or approvals they need from you. Only create additional accounts once this has been agreed. Google: Get started as a CSS

4. Define the account structure and access rights

Three systems have different jobs:

A CSS group can include several CSS domains. Several merchant accounts can in turn be assigned to one CSS domain. Alongside the primary CSS multi-client account, standalone merchant accounts and further MCA structures are also possible. So not every client has to move into a newly created agency sub-account. Google: Account types in CSS Center

Agree the desired structure for each client before the switch. With existing multi-client accounts in particular, be clear whether only the CSS assignment changes or the account hierarchy as well.

The client should keep their own admin access. Grant personal user access instead of shared passwords and document who takes on which tasks. Approving a CSS switch and granting additional access for feed management or campaign management should be handled separately.

5. Standardise client onboarding

Create a short form that your team uses for every onboarding. It should contain at least the following details:

• Shop name, domain and contact person
• Merchant Center ID and previous CSS
• Existing MCA membership
• Responsible Merchant Center administrator
• Target countries and surfaces used
• Product data source and technical contact
• Preferred start date and booked scope of services

Take a closer look at international accounts in particular. The new CSS must support the placements required, for example outside general Google Search and outside the CSS programme countries. Free product listings also belong in this check. Google: Working with Comparison Shopping Services

Before the switch, record the state of the account: active products, existing disapprovals, feed issues and current campaign performance. That way, your team can tell later which issues already existed.

6. Carry out the CSS switch in a controlled way

If you keep the existing Merchant Center, the switch generally works like this:

1. The merchant confirms that they want to work with the new CSS.
2. An administrator of the new CSS starts the switch request with the Merchant Center ID.
3. An administrator of the merchant account approves the request in Merchant Center.
4. After the scheduled transition period, the new assignment takes effect.

Google states a transition period of up to 14 days after approval. The previous CSS can shorten or waive it. So plan the start date based on the actual switch status. In CSS Center, you can follow the process via the switch history. Google: Move merchant accounts between CSSs

The Google Ads account does not need to be transferred for a CSS switch. What matters is the Merchant Center assignment. A Merchant Center account can be assigned to one CSS at a time. Google: Working with Comparison Shopping Services

Avoid rebuilding the feed and changing the bidding strategy at the same time. A clearly scoped switch makes monitoring and troubleshooting easier.

7. Close every onboarding with a sign-off

A confirmed switch request doesn't mean the client job is done. Once the switch has taken effect, check whether:

• the intended CSS assignment is in place,
• product data is still being updated,
• the required products are approved,
• campaigns are still serving,
• countries and surfaces work as intended,
• client and agency have the agreed access.

Then send the client a short update covering completion, check results and their contact person. Document open points with an owner and a deadline.

Do not promise a blanket improvement in campaign results. Assess performance over comparable periods and take budget changes, promotions, product range and seasonality into account.

8. Manage clients from one shared overview

To start with, a well-maintained spreadsheet or a CRM is enough. What matters is that client status, technical assignment and billing match.

For each client, record the Merchant Center ID, CSS domain, contact person, responsible Account Manager, switch status, activation date, purchase price, selling price and next review date.

A consistent status flow works well:

For open cases, always add the next concrete action. “Approval missing – Account Manager reminds client on Thursday” is more helpful than a generic “in progress” status.

Schedule a weekly review of open onboardings and technical issues. Each month, reconcile active accounts with supplier and client billing. That way, you spot forgotten cancellations and uninvoiced activations early.

9. Factor account management effort into your pricing

The difference between purchase and selling price isn't your profit yet. Factor in set-up, client queries, invoicing and technical support.

A simplified calculation example with freely chosen net amounts: you charge £49 a month and pay the partner £19 per client account. With 20 accounts, that initially leaves £600 a month. If each account needs an average of 15 minutes of management, that adds up to five hours of work. At an internal rate of £60 per hour, £300 remains before other costs.

So define which support is included and when additional services are charged. An economically viable service needs a clear scope.

10. Plan for client departures too

Decide during onboarding how a cancellation will be handled. Document the contract end, the desired target CSS, the contact person and the date on which additional agency access will be removed.

A CSS service can be ended without deleting the Merchant Center. Google describes both switching to another CSS and returning to Google Shopping after consent from a Merchant Center administrator. Google: Move merchant accounts between CSSs

Start with a few pilot clients and document every step. Once set-up, approvals, sign-off and billing work reliably, you can onboard more clients using the same process. That way your White Label CSS becomes a predictable agency offering that you can manage and grow with reasonable effort.