Multi-CSS Strategy: Benefits and How to Set It Up

Most merchants treat their CSS like an electricity contract: switch once, pay less, never touch it again. Understandable, but it leaves options unused. Nothing in Google's rules says your products may only enter the Shopping auction through a single CSS.

In practice you see multi-CSS setups mainly with merchants selling in several countries or running very different parts of a catalogue. One area runs smoothly with one provider; in another, support, a feed feature or a market is missing. Instead of migrating everything, a second CSS gets added.

This article covers what a multi-CSS strategy actually gains you, when it makes no sense, what a clean test looks like, and which mistakes come up most often.

How many CSS may a merchant use?

As many as you like. A CSS is the interface through which your products enter the Shopping auction. Each provider works with its own Merchant Center context and its own connection. Several providers in parallel is technically foreseen and has long been normal in larger accounts.

The only thing that matters is separation: a product runs through one route per campaign structure. So you do not duplicate the same campaign and hope both win. You decide which part of the business runs through which partner — by country, by catalogue area, or by account structure.

Short version: do not push the same product through the same campaign twice. Assign different areas to different partners. Then there are no auction conflicts, just a structure you can actually compare.

What a second CSS really gains you

A fallback when something breaks

This is the argument nobody debates after the first incident. If a Merchant Center context gets suspended, a feed import stalls, or a provider goes quiet for days, a single-CSS setup means your entire Shopping business is down. With a second partner already connected, you move campaigns in hours instead of weeks.

Provider performance becomes measurable

Every CSS provider promises savings and support. You can only compare that once both run on similar catalogue areas at the same time. After four to six weeks you see more than CPC and impression share: how fast does an answer arrive, is a feed problem explained or just forwarded, and who brings a suggestion before you ask?

Specialisation by market and catalogue

No provider is equally strong everywhere. Some are rooted in one country and have the best contacts there. Others are good with huge feeds, with local inventory, or with prices that change several times a day. A multi-CSS structure lets each area sit where it is best supported — sportswear with one partner, the 200,000-SKU spare parts business with the other.

A better negotiating position

Nobody says this out loud, but it is true. Once a second CSS is live, conversations change. Not as a threat, but because switching stops being a decision of principle and becomes a shift of budget. Revenue-share models are usually the first to stand out here: as sales grow the invoice grows too, while the service stays the same.

Reach. More combinations of feed, account and support instead of one structure for everything.
Safety. One blocked context no longer freezes the whole Shopping business.
Clarity. Provider performance shows up in your own numbers, not in slide decks.
Flexibility. New markets can be tested without rebuilding the running setup.

When a multi-CSS strategy is not worth it

The honest part: in many accounts a second CSS is effort without return. Two providers mean two contacts, two feed responsibilities, and a structure someone has to be able to explain — including six months from now.

Small catalogue, one market. 300 products in one country need a good feed, not a second channel.
Small budget. Below roughly €2,000 of monthly Shopping spend there is not enough data to see a difference at all.
Feed not clean yet. With disapprovals and missing attributes still open, you only duplicate the problem.
Nobody watching day to day. Multi-CSS assumes someone looks at the numbers regularly. Otherwise one half quietly underperforms and no one notices.

Rule of thumb from practice: get one setup genuinely stable, then extend. A second CSS is a scaling tool, not a repair.

One, two or several CSS — what fits whom?

Setup	Fits	Effort	What you get
One CSS	One market, manageable catalogue, small to mid budget	Low	20% CPC advantage, one contact, little admin
Two CSS	Several countries or clearly separated catalogue areas from around €5,000 spend	Medium	Comparability, a fallback, a real basis for negotiation
Several CSS	Large accounts, many markets, multiple brands or agency operations	High	Specialisation per market, maximum flexibility when scaling

The effort here is organisational rather than financial. With a fixed-price CSS the second channel costs £17 per month. The real work is deciding who owns which feed and where the campaigns live.

CSS Flat rate

£17/ month

Get started

Free Google CSS migration
Full visibility in Google Shopping
20% lower click prices
21 EU markets included
Premium email support
No minimum term

How to add a second CSS

1Define the base. Decide which partner stays your main structure. Everything else builds on it, not beside it.
2Scope the test. One country or one product category with stable volume. Not your top-revenue segment and not peak season.
3Connect the second partner. Merchant Center access, CSS connection, feed check. Usually a matter of days, not weeks.
4Separate campaigns properly. Dedicated campaigns for the test area, clear naming, no mixing inside one structure.
5Set a measurement window. Four to six weeks, no verdict before that. Shorter periods only tell you what the weather did.
6Review. CPC, impression share, conversion value and margin per channel. Note the support experience while it is still fresh.
7Decide. Expand, keep, or roll back. All three outcomes are fine — running on undecided is not.

Quick check before you start: feed errors cleared, test area defined, measurement window in the calendar, ownership per channel agreed. Answer those four and most of the work is done.

The most common mistakes

Duplicating the same campaign. Identical products in identical campaigns across two CSS adds no reach, only messy reporting.
Judging too early. After ten days a new channel almost always looks worse. That is the ramp-up curve, not a result.
Watching CPC only. A low click price with falling revenue is not a win. Margin and conversion value decide.
Leaving feed ownership open. If two parties may change feed rules, you get errors nobody can trace.
Not telling the providers. A partner who knows which area they own works far more purposefully than one who guesses.

What this means for your setup

Multi-CSS is not a matter of belief, it is a matter of size. With one market and a clean feed, one good partner at a fixed price is entirely enough. From several countries, several brands, or a catalogue that is already managed in separate teams, a second channel is often the cheapest insurance you can buy.

The pricing model is what decides. A revenue-share CSS automatically gets more expensive as you scale; a fixed price does not. That is why growing merchants in a multi-CSS structure usually keep at least one fixed-price channel as their base and use the second provider for what it genuinely does better.

Multi-CSS strategy: common questions

Does Google allow several CSS per merchant?

Yes. There is no limit of one Comparison Shopping Service. What matters is that campaign structures are separated and the same products do not run twice in the same build.

Do I compete against myself with two CSS?

Only if you push identical products through identical campaigns on both routes. Split by country, category or account and that does not happen.

Do I then pay twice?

You pay per provider. On a fixed-price model that is £17 per month for the additional channel, with no revenue share. On percentage models the amount grows with your sales — which is often where multi-CSS starts paying for itself.

How much ongoing work is it?

After setup, usually about an hour a week to look at both channels. The setup itself takes a few days, provided the feed is clean.

From what budget is it worth it?

Roughly from €5,000 of monthly Shopping spend, or from your second sales country. Below that you gain more from feed and campaign work than from a second channel.

Is switching not easier than adding?

If you are unhappy with your provider, yes. Adding makes sense when the existing setup basically works and you want extra markets, more safety, or a genuine comparison.

How do I measure which provider is better?

Separate campaigns, four to six weeks of runtime, then CPC, impression share, conversion value and margin side by side. Support response times belong in the picture too; they explain half the differences later.

Can I go back to one CSS later?

Any time. The campaigns stay in your Google Ads account; you simply end the second provider's connection. That is exactly why a test without a minimum term carries so little risk.

To the Google CSS Partner