July 26, 2026
min read

How to Scale Google Shopping Without Adding Headcount


Alexander Perleman
, Head Of Product @ groas
Ex-Goldman Sachs and Stanford Computer Science

alex@groas.ai

LinkedIn
Illustration for: How to Scale Google Shopping Without Adding Headcount

Most people who ask how to scale Google Shopping without adding headcount have already done the math and don't like the answer. Spend is up 40% year over year. The SKU count doubled when the new category launched. And the person managing it all is the same one person who was managing it when the account was a third the size. The work didn't disappear. It got quietly absorbed by someone working later.

I spent years on the manual side of this. Shopping was always the campaign type that punished growth the hardest, and it took me a while to understand why. A Search account with 200 keywords is a fundamentally different animal at $5k/month and $50k/month, but the number of things you manage barely changes. You still have those 200 keywords. Shopping doesn't work like that. When your catalog grows, the number of objects you're responsible for grows with it, one for one. Every SKU is a line item that can go out of stock, get disapproved, drift into the wrong bid, or start eating budget on a search term that will never convert. Add 500 products and you've added 500 small ongoing obligations, not one big one.

That's the headcount trap, and it's why so many ecommerce teams end up hiring a second and third PPC person whose entire job is keeping the feed and the campaigns from rotting. The good news is that most of that work is mechanical, which means most of it is automatable. The catch is that not all four of the jobs that scale linearly are equally worth automating first, and a couple of them you should be careful about handing off at all. Let me walk through which is which, in the order I'd actually do it, and what a realistic before-and-after looks like at a few different spend levels.

The four jobs that grow with your SKU count

Before you automate anything, it helps to name the work honestly. In a growing Shopping account, four jobs scale roughly in line with your feed size and spend. Feed hygiene: keeping titles, attributes, prices, and availability accurate so products stay eligible and show for the right queries. Bid and budget management: making sure winners get funded and losers get throttled, across a catalog too big to eyeball. Search term and placement cleanup: mining the queries your products actually showed for and cutting the ones that spend without converting. And product segmentation: deciding how products get grouped into campaigns and priority tiers so the high-margin, high-intent stuff isn't competing for budget with clearance junk.

Every one of those gets heavier as you grow. What changes with scale isn't the difficulty of any single decision. It's the volume. Deciding to pause one bad search term takes ten seconds. Doing it across a 3,000-SKU catalog every week is a part-time job that produces nothing a client can see, which is exactly the kind of work that gets deferred until it becomes a problem. I've watched accounts where nobody had touched the search terms report in two months quietly hand 20% of their Shopping budget to queries like "free" and "repair" and competitor names. Nobody decided to do that. It happened because the maintenance didn't scale and the person responsible ran out of Tuesdays.

So the question isn't really "can I automate Shopping." It's "in what order do I automate it so I stop leaking money fastest and keep the judgment that actually needs a human." That order matters more than most tool comparisons will tell you.

What to automate first, in order

Start with feed hygiene, because everything downstream depends on it

Automate the feed first. Not because it's the flashiest, but because every other optimization is built on top of it and a broken feed silently caps everything above it. If a product's availability attribute is wrong, it gets disapproved and your bid strategy is optimizing around a hole in the catalog. If the title is generic ("Model 4482, Black") instead of descriptive ("Stainless Steel Insulated Water Bottle 32oz, Black"), it shows for worse queries and converts worse, and no amount of bid tuning fixes a title problem. The mechanism is simple: Shopping matches on your feed content, not on keywords you choose, so the feed is your targeting. Automating hygiene here means rules and supplemental feeds that fix titles at scale, flag price mismatches between feed and site, and pull out-of-stock items before they burn impressions. This is the highest-leverage thing you can hand off, and it's the least emotionally difficult, because nobody enjoys doing it manually anyway.

Then bidding, budgets, and dayparting

Bid and budget management is next, and it's where automation has been most mature the longest. If you're still setting manual CPCs across a large catalog, stop. Smart Bidding with a target ROAS or target CPA will beat manual bidding on any account with enough conversion volume to feed it, and the reason is unglamorous: it's making per-auction bid decisions using signals you can't see and couldn't act on fast enough if you could. Where humans still add value is in setting the targets and structuring campaigns so the algorithm has clean data to learn from. What you're automating away is the daily act of nudging bids and shuffling budget between campaigns at 11pm because one of them spent out by noon. Dayparting and budget pacing fall in here too. These are pattern-recognition jobs, and pattern recognition at volume is exactly what machines do better than a tired person with a spreadsheet.

Search term and placement cleanup, on a schedule

Third, search term and placement cleanup. This is the one that leaks the most money the fastest when it's neglected, but I put it third because it depends on the feed and bidding being sane first. Shopping doesn't let you add keywords, but it does let you add negatives, and the search terms report is where you find them. The work is repetitive and endless: review what queries triggered your products, exclude the irrelevant ones, and push the low-intent stuff down in priority. Done manually it's a weekly slog that everyone hates and therefore skips. Automated, it runs continuously, catching a spend leak on "how to fix" or a competitor's brand name within a day instead of at the end of the month when someone finally opens the report. If you want a head start on the manual version, our 201 negative keywords list covers the usual suspects, but the point of automating it is that you stop maintaining lists by hand entirely.

Product segmentation last, because it's judgment wearing a coat of data

Product segmentation goes last, and this is where I part ways with a lot of the "just automate everything" crowd. Grouping products into campaigns and priority tiers looks like a data problem, and parts of it are: splitting by performance, isolating your best sellers into their own campaigns so they don't share a budget with the long tail, using priority settings to control which campaign wins an auction. Automation handles that reallocation well once the strategy is set. But the strategy itself is entangled with margin, inventory position, and what you're actually trying to do this quarter. A product that converts at a mediocre ROAS might still be the one you want to push hard because it has the best margin, or because it's the entry point to a subscription, or because you're overstocked and need to move it. The algorithm doesn't know any of that unless you tell it, and encoding it correctly is a decision, not a task. Automate the execution of your segmentation. Keep your hands on the design of it.

What humans should keep owning

That last point generalizes. The rule I'd give anyone scaling Shopping: automate the work that's mechanical and repetitive, keep the work that requires knowing something the machine doesn't. Three things fall firmly in the human column. Merchandising and margin strategy, because your ad platform optimizes toward whatever conversion value you feed it, and if you feed it revenue when you should be feeding it profit, it will happily scale your least profitable products. Somebody has to decide what "good" means before automation can chase it. Creative and offer direction, because the reason a product converts is often the offer, the imagery, the bundle, and the price position, none of which a bid algorithm touches. And catalog strategy, the decision about which products deserve to be advertised at all. I've seen accounts get a 15% CPA improvement not from any clever bidding change but from cutting 300 SKUs that were never going to be profitable to advertise and letting the budget concentrate. That's a human call.

The honest version of "scale without headcount" isn't "fire the humans." It's "stop paying humans to do what a machine does better, and redirect them to the decisions only they can make." The person who was spending twelve hours a week on search term cleanup and feed fixes is far more valuable thinking about margin mix and offers. You're not removing the role. You're removing the part of it that produced nothing and calling it a promotion.

A realistic before-and-after: hours per week at three spend levels

Numbers make this concrete, so here's roughly what the maintenance load looks like before and after automating the four jobs, based on the accounts I've worked and watched. Treat these as ranges, not promises. Your catalog size matters more than your spend, so a $15k account with 5,000 SKUs can be heavier than a $40k account with 200.

  • Around $10k/month, a few hundred SKUs. Before: 6–8 hours a week of real maintenance, most of it feed fixes and a search terms pass that happens when someone remembers. After: 1–2 hours a week, mostly reviewing what the automation did and making the occasional strategic call. This is the level where most teams don't hire a second person; they just quietly overwork the first one. Automation here mostly buys back evenings.
  • Around $25k/month, a thousand-plus SKUs. Before: 12–15 hours a week, and this is usually the point where the maintenance stops fitting inside one job and starts getting deferred, which is when the leaks start. After: 3–4 hours, spent on segmentation strategy and margin decisions rather than execution. This is the level where teams are typically about to hire, and automation is the alternative to that hire.
  • Around $50k/month, several thousand SKUs. Before: this is a full role, 30+ hours a week, and often more than one person once you count feed management as its own job. After: closer to 6–8 hours of genuine strategic oversight. You don't eliminate the human at this scale, but you change what they do from data entry to direction, and you stop the headcount from scaling in lockstep with the catalog.

The pattern across all three: the busywork doesn't grow linearly anymore once it's automated, but the judgment work still needs a person, and it actually gets more valuable the bigger the account is. That's the whole argument in one line. Scale the mechanical part with software. Keep the thinking with people.

Choosing your tooling: scripts, rule-based platforms, or autonomous management

There are three broad ways to actually do this, and they sit on a spectrum of how much of the work stays on your desk. Scripts are the cheapest and the most brittle. If you or someone on your team can write Google Ads scripts, you can automate feed flagging, pause zero-conversion search terms, and send yourself alerts, all for free. The catch is that scripts are rules you wrote once, so they only catch what you anticipated, and they break silently when Google changes something. I ran plenty of scripts in my manual days. They're genuinely useful and they are also a second job to maintain. Fine at $10k. A liability at $50k.

Rule-based platforms are the next step up. Tools like Optmyzr and the older Shopping feed managers give you a library of pre-built rules and a nicer interface than a script editor. They're a real improvement, but notice what they still are: rules you configure and recommendations you approve. The software surfaces the search term to cut and the bid to change; you still click the button, or you set a rule and hope you set it right. That's less work than doing it by hand, but it's not zero work, and the review queue itself becomes a job once the account is big enough. This is the layer most "automation" tools live at, and it's why teams using them still find themselves hiring. The bottleneck moved from doing the work to approving the work, which at scale is the same bottleneck wearing a different hat.

Autonomous management is the third option, and it's the one that actually breaks the headcount link rather than stretching it. Instead of surfacing a recommendation for a human to approve, the engine executes the bid, budget, negative keyword, and segmentation changes itself, continuously, and a strategist oversees the direction rather than clicking through a queue. This is the category groas sits in, for full disclosure, since I write for them: an engine trained on a large volume of ad spend runs the mechanical four jobs around the clock while a human owns the strategy calls I flagged as human work above. Dynamic landing pages that adapt to each product's search intent are part of the same system, which matters for Shopping specifically because the click means nothing if the page it lands on doesn't match what the person searched for. Whether you use groas or something else, the test is the same: does the tool do the work, or does it just tell you about the work. The first one scales without headcount. The second one is a nicer-looking version of the problem you already have.

One last thing, because it's the objection I hear most and it's a fair one. "If I automate all of this, how do I know it's not quietly making things worse?" You don't take it on faith. You watch the same numbers you'd watch a new hire on: ROAS or CPA against your target, impression share on your priority products, the share of spend going to converting search terms versus junk, and whether disapprovals are trending toward zero. Give any automation a control period. Run it on part of the catalog first, or compare a month of autonomous management against your manual baseline. I tested tools this way for years and it never steered me wrong. If something can't show you what it changed and what happened as a result, that's not automation you can trust. It's a black box, and a black box is worse than the spreadsheet you at least understood.

So the answer to "how do we scale Google Shopping without adding headcount" isn't a single tool or a clever trick. It's a sequence. Fix the feed so your targeting is sound, hand the bidding to a system built for per-auction decisions, put search term cleanup on continuous autopilot, and automate the execution of a segmentation strategy you still design yourself. Keep margin, offers, and catalog decisions with a human, because those are the parts that were never mechanical in the first place. Do that and the account can triple while the team stays flat, not because you worked people harder, but because you stopped paying them to do the parts a machine does at three in the morning without complaining.

If you take one thing from this: count how many hours a week your team spends on feed fixes and search term cleanup right now, then ask whether any of those hours produce a decision. The ones that don't are the ones to automate first.