Running Amazon Ads Across Hundreds of SKUs: Structure, Rules and Exceptions

A catalog of twenty products can be run by feel. A catalog of three hundred cannot. At that size there are hundreds of campaigns, thousands of targets and no way to open each one every week. The old habits of checking everything and nudging bids by hand either swallow the whole week or quietly stop happening. What works instead is a structure that makes the account readable, budget rules that follow product value, bulk tools that make changes safe, and a review that looks only at the campaigns needing a decision. This guide takes those four in turn.

Why checking every campaign stops working

Suppose you have 400 campaigns and spend two minutes on each during a weekly check. That is more than 13 hours before you have changed anything, and most of those campaigns will be fine. The cost is not only time. When everything looks equally urgent, the campaign that is wasting money gets the same two minutes as one that is performing, and review fatigue means the check gets shorter or skipped.

The fix is to separate three jobs. Structure is designed once, so the account can be read at a glance. Rules are decided once and applied to many campaigns. Exceptions are the few places where a rule says something is off, and those are the only places you look. The rest of this guide builds them in that order.

Names you can filter

A naming convention is the cheapest control you can add. Names appear in the console, in bulk sheets and in every report, so a consistent pattern lets you sort, filter and total campaigns without opening them. Choose the fields, fix their order and use one separator between them.

A campaign named T1 | Mugs | SP | Auto | Core tells you its tier, family, format, targeting and job before you open it. Write the pattern and its allowed values in a shared document, and apply it to portfolios and ad groups as well. Check the console's current limits on name length and characters before you settle on it, and avoid renaming campaigns in bulk partway through a quarter, because it makes comparisons across time harder.

Portfolios as a control layer

Portfolios group campaigns inside Amazon Ads so you can report on them together and, where the feature allows, set a budget cap for the whole group. Build them around one axis of the same grouping you use in names. A portfolio per product family answers how a family is doing in a single view. A portfolio per tier answers whether your top products are staying inside their budget.

Pick one axis for portfolios and let the other live in the name. Mixing both in the portfolio list produces overlaps and orphans, and nobody can tell where a new campaign belongs. Treat a portfolio cap as a safety ceiling against a runaway campaign, not as a plan for how to spend.

Budget rules by product tier

Not every product deserves the same treatment. Sort your products into tiers using two numbers you already have: profit per sale and sales volume. Then give each tier a rule instead of making a custom decision for every product.

Within a tier, size budgets from arithmetic rather than habit. A daily budget can be set as target orders per day, divided by conversion rate, multiplied by expected cost per click. For example, 10 orders a day at a 10% conversion rate needs 100 clicks, and at $0.80 a click that is $80 a day. Then confirm the product stays profitable at the bids you would need to win those clicks.

Three more rules save a lot of effort. Tie budgets to inventory, so a product running low on stock stops buying clicks it cannot fulfill. Give every test budget an end date and a review. And for known sales events, use the console's budget rules to raise budgets on a schedule or when a performance condition is met, after checking what each rule type does for your ad type.

Bulk sheets and rules

Amazon Ads lets you download campaign settings as a spreadsheet, edit them and upload them again, which is how one person changes hundreds of bids in an afternoon. It is also how one mistake reaches hundreds of campaigns at once, so the discipline matters more than the speed.

Rules do the same job without you. The console offers rule features, such as budget rules and some automation for bids and campaign settings. Which ones exist, and which ad types they cover, changes over time, so check what is available. Whatever applies the rule, write it in plain words first: if a Tier 1 campaign runs above its break-even ACoS for a set number of days, lower its bids by a set step. A rule you cannot state in one sentence is a rule you cannot audit. At larger scale, some teams move to the Amazon Ads API or third-party tools, and the same discipline applies.

Review by exception

With structure and rules in place, the weekly review becomes a list. Each rule flags the campaigns that cross a line, and you review only the flagged ones. Useful lines include:

• Spend with no orders, over a window long enough to judge, after a meaningful number of clicks.
• ACoS above the product's break-even ACoS for a sustained period.
• Campaigns that run out of budget while staying profitable, since they may be leaving sales behind.
• A sudden drop in impressions or spend, which often points to a stockout, a lost Buy Box or a listing problem rather than a campaign problem.
• Spend running well ahead of its normal daily pace.

Give each line a number, and make it tighter for top tiers than for the long tail. In a hypothetical week, 400 campaigns might produce about 60 flags. Of those, about 15 turn out to have a real cause behind them, and about 5 lead to a change. At three minutes per flag, the review takes about three hours instead of 13.

Audit the audit. Once a month, open a handful of campaigns that were not flagged and check whether any should have been. If you find one, tighten the line that missed it. Exceptions also tell you about the account itself: a rule that flags the same campaigns every week is usually pointing at a structural problem, not a bid problem.

Where to start

• Write the naming pattern and apply it to new campaigns, then backfill the old ones.
• Sort your products into four tiers by profit per sale and sales volume.
• Group campaigns into portfolios along one axis, and keep the other axis in the name.
• Set one budget rule per tier, and put an end date on every test budget.
• Adopt the bulk-edit habits: a fresh download, one change per upload and a log.
• Define four or five exception lines with numbers, and review only what they flag.