Merchant Center & Feed Rebuild
Disapprovals cleared at source, GTIN, MPN and attribute gaps closed, and titles rewritten to lead with searched terms. Custom labels for margin, stock cover and seasonality.
Capturing demand that already exists — across a Swiss feed in francs, a German-language feed in euros, and a French one that most accounts never build.
Delivered remotely for brands across Zurich and Switzerland.
Swiss search demand arrives unusually well-formed. Someone searching for a specific reference number, a technical outdoor product or a named chocolate house has already decided; the only question is who supplies it and at what landed cost. So the account is really a distribution question, and on a Shopify store the answer is written in Merchant Center rather than in campaign settings.
The Swiss complication is that you do not have one feed, you have several. A Swiss feed in francs with domestic delivery, a euro feed for Germany and Austria, often a French one, each needing its own prices, shipping settings and language. Feeds break in market-specific ways: prices that do not match the landing page after Markets rounding, shipping settings that promise a domestic timeframe to a cross-border buyer, missing GTINs on assortment lines, and the tax and shipping configuration that Merchant Center wants stated per country. Most of the wasted spend we find in Zurich accounts traces back to a feed problem, not a bidding one.
Then structure. Brand gets separated from non-brand immediately, because a respected Swiss name generates a lot of navigational search and letting it sit inside a blended campaign hides whether the non-brand side works at all. Shopping and Performance Max carry the catalogue, split by margin band and market rather than one asset group for everything. Search covers the queries a feed cannot reach — servicing, spare parts, comparison and repair terms that a watch or equipment brand owns and rarely bids on. Query mining runs weekly, with a maintained negative library that keeps budget out of research, careers and used-market queries.
The number that decides whether a Zurich account is profitable is not CPC, it is landed cost per market. A campaign into Germany can look efficient on click cost and lose money once duty handling, higher return rates on cross-border orders and the euro price you set rather than converted are counted. So targets are set per market from contribution margin, not from a single account-level tROAS, and custom labels carry margin band, stock cover and export complexity so the bidding actually respects it. Language targeting matters as much as country: Swiss search in German uses different vocabulary and different product naming than German search in Germany, and an account running one German ad group across both is being read as slightly foreign in each. We also keep a separate eye on the domestic-versus-export split in the search term data, because Swiss buyers cross-shopping German shops and EU buyers cross-shopping Swiss ones show up as very different query patterns that deserve very different bids.
The same standard of work we run for every client — applied to a Zurich brand’s realities.
Full service detailDisapprovals cleared at source, GTIN, MPN and attribute gaps closed, and titles rewritten to lead with searched terms. Custom labels for margin, stock cover and seasonality.
Branded demand isolated into its own campaign, budget and target so non-brand performance becomes visible. Competitor conquesting runs as a separate line, judged separately.
Asset groups split by margin band and product type instead of one catch-all, with listing-group bids, product exclusions and brand-term controls applied wherever PMax still allows them.
A weekly pass over search terms and PMax category reports, with a maintained shared negative library so budget stops leaking into research, DIY and job-seeker queries.
Merchant promotions, sale price annotations, shipping and returns policy setup, product ratings, and local inventory ads where you have stores worth feeding.
Targets set from margin per product group rather than a platform default, moved in controlled increments, with a written reason attached to every bid and budget change.
We do not work off a rate card. Every Zurich engagement starts with a fixed statement of work — named deliverables, named dates, one number — written after we have looked at your store, not before. If a smaller first step would serve you better, we will say so.
Get this scopedMerchant Center diagnostics, attribute coverage, campaign overlap and wasted spend scored against ninety days of search terms. You get the findings whether you hire us or not.
Titles, attributes, product types and custom labels rebuilt before any campaign work. A perfectly structured account on a bad feed still shows the wrong products to the wrong queries.
Brand, non-brand, Shopping, PMax and Search rebuilt with hard budget boundaries and a shared negative library, so each line answers a different commercial question.
tROAS targets derived from contribution margin by product group and applied gradually, so the account keeps its learning instead of resetting it every Monday.
Weekly query mining, monthly feed reviews, then expansion into the categories the search data says you can profitably win. Nothing scales before the query set is clean.
Anonymised under NDA. Figures pulled from the client’s own analytics.
~$6M/yr DTC, 900+ SKUs across size and colour variants, US · Shopify Plus
Returns ran at 31% and refund cost consumed the entire paid media margin. One size chart image served 40 different fits, and 62% of add-to-carts started on a collection page that never showed variant availability. The named constraint: no new product photography budget, so every fix had to come out of the existing asset library and the review corpus.
~$9M/yr, 210 SKUs, US + AU · Shopify Plus (migrated from BigCommerce)
Meta ROAS had slid from 3.6x to 1.9x in a year and the team had spent twelve months buying new creative to fix it. The real cause was measurement: the BigCommerce checkout dropped 22% of purchase events and the Conversions API had never been installed, so both ad platforms were optimising on incomplete data. The named constraint: peak season was 14 weeks out, and the replatform had to be live and stable well before Black Friday traffic arrived.
“Six thousand products and a Shopping feed nobody had touched since it was first generated — a third of it was disapproved and we had no idea. They rebuilt the feed off our real product data, fixed the GTIN and size attributes, and split brand off from non-brand so I could finally see what we were actually paying to acquire. They also cut the broad 'baby clothes' terms that were eating a quarter of the budget on people who were nowhere near buying. Spend is roughly flat and non-brand search revenue has close to doubled.”
Thirty minutes with the strategist who would actually run your account. We screen-share your store, read your data live, and tell you the three highest-value things we can see from the outside.
Prefer to write it out? [email protected] gets a real reply the same business day, Mon-Fri, 9am-6pm MT.