From 200 SKUs to Account-Wide Coverage — Seasonal Amazon PPC with Kalitec

Kalitec didn’t tiptoe into scaling Amazon Ads—they ripped the handbrake. In this candid session, AMALYZE’s Christian Kelm interviews Kai and Philipp (Kalitec) about moving from ~200 promoted SKUs to broad, account‑wide coverage across a 10k+ catalog, locking into fixed bids, and letting per‑target bidding do the work. The result: a verified 10x YoY and April as the second‑best month in company history, with ACOS segments landing under goal.

Why Kalitec changed course

Philipp recalls the pre‑AMALYZE era as a mix of hope marketing and whack‑a‑mole: lots of manual checks, some seasonal pushes that overheated while he was on vacation, and almost no scalable structure across more than 10,000 SKUs. Only a couple hundred SKUs were advertised.

Christian anchors the inflection point to two shifts:

• Amazon Marketing Stream (hourly signals) enabling faster, data‑driven bid changes.
• AMALYZE handling per‑target bids against explicit ACOS goals, reducing the need for daily micromanagement.

Kalitec’s internal trigger: they wanted to advertise the whole account, not just hand‑picked hero SKUs, without drowning in maintenance.

The structure that actually scaled 10k+ SKUs

Kalitec runs a hybrid of single‑ASIN and big umbrella campaigns:

• ~20 seasonal, business‑critical SKUs sit in single‑ASIN auto campaigns (one campaign, one ad group, one ASIN). Minimal clutter, clean signals.
• The rest of the catalog goes into large, loosely themed auto campaigns—e.g., “electric power tools,” “corrugated conduit,” brand buckets—so they can push breadth without a combinatorial explosion.

They did test splitting auto campaigns by match group (close match, loose match, substitutes, complements) into separate campaigns. Verdict: occasionally helped, mostly noise. They reverted to single autos per theme.

They also leaned hard into Amazon’s account‑wide ASIN search in the console to audit where a product is already advertised and to use cumulative data before adding it elsewhere.

Fixed bids only: kill the modifiers

Dynamic bidding and placement multipliers were the silent killers of target‑level control. Kalitec found this the hard way.

• Up/Down dynamic bidding at the campaign level + placement multipliers (Top of Search/Product Pages/Rest of Search) can go to +900% and create bid spirals.
• A single campaign‑level modifier applies unevenly across multiple keywords and products, muddling causality and blowing up ACOS math.

Christian lays out the math nobody wants to maintain by hand. If your target ACOS is 25% and you run a +60% modifier, your effective ACOS target must be 25 / 160% × 100 = 15.65%. If Amazon only applies +30% that day, it’s 25 / 130% × 100 ≈ 19%. You can’t set a stable goal like this—let alone per target.

Philipp’s practical verdict:

“Fixed bids were the key—once we killed up/down and placement modifiers, performance jumped.”

They now run fixed bids across the board. AMALYZE optimizes bids per target against the goal; no tool can responsibly chase moving modifiers while keeping clean control. Launches may still use modifiers in very narrow, single‑keyword setups, but for ongoing scale Kalitec keeps them off.

Dynamic ACOS segments routed by campaign names

This is the quiet killer feature. Kalitec encodes the ACOS goal directly in the campaign name—e.g., “... acos 10,” “... acos 15,” “... acos 20,” “... acos 30.” AMALYZE reads these dynamic filters and routes each campaign into the right control bucket automatically. No manual mapping in the tool UI.

• Anyone on the team can change a campaign’s goal by editing the title number. No one “breaks” the setup.
• AMALYZE keeps a change history, so if someone shifts a goal on Saturday, it’s traceable.
• For seasonality, raise/lower the goal by renaming (e.g., start a hot SKU at ACOS 30, lower to 20/15 as stock tightens).

Reported segment performance after the switch:

• ACOS 10 segment runs at 9.08%
• ACOS 15 at 13.86%
• ACOS 20 at 17.18%
• Fallback “Account” at 19.02% vs goal 20%

That predictability gave them the nerve to “not limit budgets” early in testing.

What still needs human hands

Kalitec made PPC lean on purpose—think 80/20—and reserves human time for the highest‑leverage moves:

• Monitoring top spenders: Sort by spend (even in Seller Central) and deep‑dive the top campaigns/ASINs first.
• Negatives: Today added manually in autos; AMALYZE Recommendations for search term negatives is rolling out to reduce this burden.
• Pruning losers: Kill SKUs that eat clicks and never convert (Philipp cites four‑figure workshop tool cabinets that hoovered spend with zero conversions across markets).
• Initial bid seeding: For new targets with no impressions, Philipp manually bumps starting bids to “wake up” the auctions. After that, AMALYZE’s per‑target control takes over.
• Budget guardrails: Hourly bids are automated, but budgets are still human decisions. They watch caps to avoid starving unexpected winners, especially when year‑over‑year behavior changes.

Time cost now averages under one workday per week for PPC—including strategy. Some weeks, it’s an hour. Manual bid management? Essentially zero after launch.

Per‑target bidding with hourly reactions (why it matters)

Two dynamics justify the whole setup:

• Hourly demand swings: Weather spikes drive conversion up on hot days; AMALYZE reacts via Amazon Marketing Stream data and adjusts bids per target accordingly. Cold/rainy days? Bids drift down automatically—no hand‑tuning possible at that cadence.
• Long‑tail starvation: Thousands of low‑traffic ASINs won’t signal daily. AMALYZE’s longer, backward‑looking windows consolidate sparse events to make saner bid decisions. Humans can’t do consistent math on 1 click / 1 sale edge cases.

Christian’s mantra: Control at the target level, never at a mixed campaign average. That’s how you get both speed and stability.

Seasonal playbook (and where DSP fits)

• February–May: Invest to regain rankings for seasonal ASINs ahead of the peak.
• May onward: Switch on Amazon DSP—but only for the seasonal B2C lines. The year‑round B2B tool business did not benefit; they cut it there.
• Throughout: Keep budgets elastic, watch for surprise winners/losers, and don’t be shy about pausing SKUs that can’t convert.

Christian notes they see segment‑level ramps in the data like clockwork—ACOS‑20 activity rising early March, cold‑season segments tailing off—without manual triggers. That’s the benefit of per‑target hourly reactions.

Content before expansion (and fixing translation mishaps)

Kalitec is expanding EU‑wide next, starting with France. Two realities shape the rollout:

• Content first: They only scale ads once translations and on‑page assets are clean. An earlier attempt using Amazon’s translation tooling conflicted with their JTL ERP sync, overwriting content and forcing rework.
• Ads second: With content fixed, they’ll clone the German playbook—autos + dynamic ACOS filters—then layer AMALYZE Recommendations for negatives so nobody needs to speak the language to keep query hygiene.

Philipp’s blunt reminder still applies:

“A bad product with ads is just a bad product with ads—only now it burns money.”

Ops: when PPC success hits the warehouse

The ad engine compounds operational stress. Kalitec prepared, but reality still bites:

• FBA push: They dramatically increased FBA over the past 12 months. Even then, spikes exposed staffing gaps (illness, vacations, holidays) and packing capacity limits.
• Lead times: ~6 weeks production time isn’t China‑long, but it’s still a season inside a season. They mitigate by pre‑booking manufacturing slots, deciding variants (size/color/length) later to stay flexible.
• Supply risk: Less China dependence helped during recent shipping disruptions, but containers still add some uncertainty.
• Planning cadence: Season planning starts in October for the following year. Even with planning, weather and school‑holiday calendars add variability. They err toward earlier purchasing and secured slots.

The upshot: Ads, inventory, and staffing have to mature together. You can’t out‑spend a bottleneck.

B2B + B2C in one account (and why that’s fine)

They run both the year‑round B2B tools and the spiky B2C seasonal lines in one Amazon account. They tested splitting accounts; consolidating won:

• Better overall account health and momentum.
• Seasonal spikes lift the baseline; B2B stability supports the troughs.
• Advertising tactics differ (e.g., DSP only for B2C), but the shared infrastructure and data help both.

Guardrails and gotchas

• Don’t fight the tool without adjusting the triad: bid, lookback window, and ACOS goal. If you only raise bids manually, AMALYZE will push them back down based on its window and goal.
• Modifiers create unknowable effective ACOS math and mislead optimization. If you insist on them for launches, keep the structure ultra‑narrow (one campaign/ad group, one SKU, one keyword) and monitor closely.
• Budget management remains human by design. Tools shouldn’t reallocate all spend; you need strategic control across lines and countries.
• Low‑data long tail will always be noisy; rely on longer lookbacks and be patient—or prune.

What changed in PPC (Philipp’s view)

Philipp has lived this from agency to in‑house. His diagnosis of the industry arc:

• Early days: Simple funnels (auto → broad → exact), lots of rules of thumb, fewer moving parts.
• Middle era: Complexity creep—modifiers, esoteric structures, conference decks full of hacks. Many small sellers got lost and defaulted to tools/agents.
• Now: Back to basics. A rudimentary, robust structure + per‑target bidding + explicit ACOS goals, powered by data freshness, beats Rube Goldberg setups. Small teams can win again.

Results snapshot (so far)

• 10x YoY growth reported; April became the second‑best month in company history.
• ACOS segments track under goal: 10→9.08, 15→13.86, 20→17.18, fallback 20→19.02.
• Manual PPC time: typically under one day per week; some weeks, an hour.
• DSP: seasonal only, for B2C; turned off for B2B after testing.
• Structure: single‑ASIN autos for ~20 seasonal SKUs; large, themed autos for the rest; no persistent modifier usage; fixed bids.

How to replicate Kalitec’s approach

1. Make fixed bids your default. Turn off campaign‑level up/down and placement multipliers unless you’re running a surgical launch with one SKU/one keyword.
2. Declare ACOS goals in campaign names (e.g., “... acos 15”) and let dynamic filters auto‑map control. Adjust seasonally by renaming.
3. Use autos for breadth. Keep single‑ASIN autos for heroes; group the long tail into large, loose themes. Don’t over‑split auto match types unless testing shows a clear win.
4. Seed bids for new targets to ensure initial delivery, then let per‑target automation take over.
5. Spend your human time where it pays: top spenders, negatives, content, and pruning obvious losers.
6. Plan seasonality months ahead; switch on DSP only where it proves ROI (for Kalitec: B2C seasonal). Watch budgets to avoid capping surprise winners.
7. Fix translations/content before scaling to new countries. Then roll the same structure, and lean on Recommendations to manage search terms without speaking the language.

Bottom line

Kalitec’s leap from a few hundred advertised SKUs to true account‑wide coverage didn’t require a labyrinth of campaigns. It required discipline: fixed bids, per‑target control, explicit ACOS goals baked into campaign names, and the willingness to let hourly data do the heavy lifting.

The payoff is real—10x YoY, segment ACOS under goal, and PPC hours slashed—while ops scaled via FBA and pre‑booked manufacturing. If your current setup depends on modifiers, averages, and wishful thinking, this episode is a case study in getting back to basics and winning with a small team.