Exclusion of underperforming products: how to cut waste and grow profitable traffic

Excluding underperforming products removes wasted spend and frees budget for items that win. With NetAmplify you can set clear rules that pause low-quality traffic on Google Shopping, Meta and other channels, then allow products back in when performance improves. This page explains the signals to use, practical thresholds, re-entry rules, and a simple 7-day clean-up plan.

What counts as an underperformer?

It depends on your margin and goals, but most teams use a mix of volume and efficiency signals:

No conversions: high spend or clicks without orders in a fair time window.
Weak contribution margin: orders that lose money after fees, shipping and returns.
Low intent traffic: search terms or placements that bring clicks but no add-to-basket.
Stock or price issues: poor availability or uncompetitive price driving waste.

Suggested thresholds to start with

Pick one efficiency metric and one volume gate so you do not exclude products on tiny samples. Adjust for your margin and seasonality.

Signal	Threshold (starter)	Window	Action
No conversions after spend	Spend ≥ 1.5× target CPA	Last 14 days	Exclude product from paid feed or pause in campaigns
Low conversion rate	CVR below 1/3 of category average	Last 14–28 days	Exclude or down-bid; review title, image and price
Profit efficiency (POAS)	POAS < 1.2 (or ROAS < target)	Last 14–28 days	Exclude or switch to value bundle; fix margin inputs
Low intent clicks	>50 clicks, 0 add-to-basket	Last 14 days	Exclude and add query negatives or refine title
Price index	Price > 10% above main competitors	Rolling	Exclude until price is competitive or justify premium
Stock risk	<3 units or long lead time	Current	Exclude until stock stabilises; avoid wasted clicks

Notes:

POAS = Profit on Ad Spend = profit ÷ ad spend. Use contribution margin after fees, shipping and returns.

Re-entry rules so exclusions are not permanent

Fresh test: re-include after significant change (price cut, new image, new title) and set a small budget cap.
Performance gate: allow back in when CVR ≥ 50% of category average or POAS ≥ 1.2 over 7 days.
Seasonality: re-enable automatically when the category is in season (for example winter sports in Q4/Q1).
Stock recovery: re-include when stock ≥ 10 units and handling time is normal.

How to build exclusion logic in practice

Segment first: split by margin bands, price points and categories so rules reflect reality.
Add a sample gate: do not exclude until a product has at least 40–60 clicks or has spent ≥ target CPA.
Stage the action: down-bid or lower priority before full exclusion if you are cautious.
Log the reason: store the exclusion reason and date for audit and re-entry checks.

Examples

Category	Issue	Rule	Result
Trainers	High clicks on generic queries, no baskets	Exclude after 60 clicks with 0 add-to-basket; refine titles and add negatives	Spend down, CTR steady, CVR up after re-entry
Robot vacuums	ROAS below target due to fees and returns	Exclude until POAS ≥ 1.2; test bundle and price point	POAS recovered; product reinstated with cap
Garden furniture	Out of season	Exclude May–Jan; re-enable with cap in Feb–Apr	Budget shifted to in-season categories

7-day clean-up plan

Day 1: define targets: CPA or ROAS/POAS by category and margin band.
Day 2: map data fields: price, stock, margin, conversions, add-to-basket, search term signals.
Day 3: create segments (high, medium, low margin) and apply thresholds from the table.
Day 4: run a dry-run to list products that would be excluded; review edge cases.
Day 5: activate exclusions with audit notes; set re-entry rules and budget caps.
Day 6: monitor diagnostics and search terms; fix obvious content issues on top excluded SKUs.
Day 7: review spend, CVR and POAS. Keep the rules and scale to more categories.

What to watch after launch

Spend shift: budget should move to best sellers within the same category.
Click quality: add-to-basket rate should improve within a week.
Profitability: POAS and contribution margin should trend upwards.
Coverage risk: ensure you are not excluding all variants in a key range.

Common pitfalls to avoid

Excluding on tiny samples: always use a click or spend gate.
Ignoring margin: ROAS can look fine while profit is negative. Track POAS.
One-way doors: set re-entry criteria so good products return after fixes.
Seasonality blindness: keep calendars for peak and off-peak periods.

Next steps

👉 Learn more about feed optimisation

👉 Automate exclusions with ad automation

👉 Improve ad ROI with POAS-aware rules