Most marketplace ad accounts do not run out of ideas. They run out of commercial attention.
There is always another Amazon keyword to test, another bol Sponsored Products campaign to split, another MediaMarkt retail media placement to negotiate, another competitor ASIN to target, another budget request to defend. On paper that looks like healthy optimisation. In practice, the account often lets the campaigns choose which products get attention: the SKU with the loudest spend, the SKU with the cleanest ROAS, the SKU the marketplace manager mentioned last, or the SKU the agency already knows how to fix.
The named mistake is campaign-first optimisation. The team opens the advertising interface, sorts by spend or ACOS, and starts improving what the platform makes visible. That is efficient if the campaign is the business. It is dangerous when the business is a portfolio of products with different margins, stock risks, return behaviour, price positions and channel roles.
My stance: every Advertentie Service managing more than roughly €5K per month across Amazon, bol and MediaMarkt needs a SKU priority queue. Not another dashboard. A weekly list of products ranked by whether the next euro of ad spend can still create profitable progress. Campaigns then serve that queue. They do not define it.
This is especially important in the Netherlands and Belgium, where a brand might use Amazon for scale, bol for local conversion strength and MediaMarkt for electronics-intent moments. The right question is rarely “which campaign has the best ROAS?” The better question is: which SKU deserves scarce advertising attention this week, and what must be true before we move more budget toward it?
What competitor advice explains well
The useful public advice on marketplace advertising tends to focus on campaign mechanics. BidX’s budget automation article explains how monthly campaign budgets can be distributed by cost or ACOS, with an emergency stop when budget is used up. It also gives a helpful warning: if budget is distributed by cost, high-cost unprofitable campaigns can still receive too much money. That is a real operational risk.
BidX’s article on common Amazon advertising mistakes covers the basics sellers must not skip: optimise listings, set campaign goals, use relevant keywords, avoid irrelevant broad spend and analyse performance. For a newer Amazon operator, that is good advice. It prevents the obvious leakage.
Podean’s Amazon DSP article adds a more strategic point: retail media should not be managed as a silo. DSP only works well when it is connected to Sponsored Ads, inventory data, pricing strategy and merchandising execution. I like that point because it moves the conversation beyond the ad console.
ATTN’s Amazon Ads versus retail media comparison looks at the channel-choice question. It compares reach, CPC, conversion rates, attribution windows and strategic trade-offs across Amazon and other retail media networks. For budget holders, that is helpful context.
The bol Partnerplatform explains Sponsored Products clearly: CPC bidding, campaign setup, daily budget, automatic campaigns and target ACOS. It is practical platform documentation. It helps sellers start correctly.
Real sellers on Reddit add the messy truth. One Amazon seller says software can move budget between campaigns that are not spending full budget. Another describes spending around $3K to make $6K per month and struggling to scale because 80% of orders come from 20% of keywords. A newer seller asks how long to keep spending after “an obscene amount of money” produces only about one order a day. Those comments are not polished strategy decks. They are what the work feels like when money is moving and confidence is thin.
The gap is clear: most advice tells you how to allocate campaign budget, automate bid movement or choose a channel. Much less advice starts one level earlier: which products should be allowed to compete for budget in the first place?
The SKU queue changes the operating question
A campaign-first account asks: “What should we do with this campaign?”
A SKU-first account asks: “Does this product deserve ad pressure, ad protection, ad learning or ad silence this week?”
That small change matters. A low-ACOS campaign can be attached to a SKU with weak contribution margin. A high-ACOS launch can be exactly right if the product has strong stock, strong margin and a realistic ranking upside. A MediaMarkt placement can look expensive in-platform but still make sense if it defends a premium electronics bundle during a short promotional window. A bol Sponsored Products campaign can look efficient while it accelerates a SKU that will stock out before the next inbound shipment.
The SKU priority queue is the place where those trade-offs are made before the ad interface starts shouting.
The five fields every SKU needs before it enters the queue
You do not need a 40-column spreadsheet. You need five fields that stop ad spend from pretending every product has the same commercial permission.
1. Contribution margin after marketplace reality
Use contribution margin after purchase cost, marketplace commission, fulfilment, expected returns, payment costs, VAT handling where relevant, coupons and agency or tool costs if you allocate them. Do not use gross margin from the product sheet. Advertising spends real money against realised unit economics, not against a tidy catalog number.
FiveX’s profitability dashboards are useful here because the ad operator can see SKU-level margin next to ad performance instead of waiting for finance to translate it later.
2. Stock cover and replenishment confidence
A product with 14 days of stock and a supplier delay should not receive the same ad permission as a product with 62 days of clean stock and confirmed inbound. Stock cover turns “scale” into “wait”, “protect” into “cap” and “launch” into “collect evidence carefully”.
FiveX inventory insights help make this visible before the marketplace ad service raises bids on a product operations is trying to slow down.
3. Offer strength by marketplace
Amazon Buy Box, bol price position, delivery promise, reviews, content quality and MediaMarkt listing readiness all change ad permission. A SKU can be ready on bol and not ready on Amazon. It can be attractive on MediaMarkt only during a promotion. The queue should store marketplace-specific permission, not one generic product score.
4. Campaign role
Every SKU should have one main ad role for the week: defend, harvest, learn, launch, clear, recover or wait. Without a role, the operator ends up judging every product by the same metric. That is how launch campaigns get cut too early and mature defensive campaigns receive endless budget because their ACOS looks polite.
5. Evidence maturity
A SKU with 320 recent clicks, stable conversion and three weeks of margin history deserves different treatment from a SKU with 34 clicks and two orders. Evidence maturity decides whether the correct action is bid change, budget move, wait, or test design. FiveX’s ad logs and recommendation history are handy here because they show what has already changed, not just what the current report says.
A simple scoring model for a €5K+ account
For a managed account spending €5K to €25K per month, I would start with a 100-point queue. Keep it boring. Boring systems get used.
- Margin permission: 30 points. Can the SKU absorb advertising after all marketplace costs?
- Stock permission: 20 points. Is there enough stock and replenishment certainty to justify demand creation?
- Offer readiness: 20 points. Is the price, delivery, content, review and marketplace position strong enough?
- Learning value: 15 points. Will spend answer a useful question, or only create more noise?
- Strategic role: 15 points. Does the SKU matter for category defence, launch sequencing, bundle strategy or channel growth?
Then assign a weekly label:
- 80-100: Scale or defend. The SKU can receive budget if campaign evidence supports it.
- 60-79: Controlled test. Spend can move, but with a ceiling and a review date.
- 40-59: Repair before scaling. Fix margin, stock, listing or offer first.
- 0-39: Hold. Do not let campaign optimism spend ahead of business permission.
This model is deliberately not a black box. A marketplace ad service should be able to explain why a SKU scored 74 instead of 91. If the explanation needs a machine-learning monologue, the operating team will not trust it when the auction gets expensive.
Example 1: NorthPeak Home should scale bol, not Amazon
NorthPeak Home sells a compact air fryer accessory set for €39.95. On Amazon, the SKU has 24% contribution margin after FBA fees, a 29% return-adjusted break-even ACOS and 19 days of stock. Sponsored Products shows a pleasant 22% ACOS over the last 14 days. Campaign-first thinking says: raise budget.
The SKU queue says wait. Stock permission is weak. Amazon scores 58: decent margin, weak stock, enough evidence, but no room to create extra demand. On bol, the same SKU sells at €41.50 through LVB, has 31% contribution margin, 46 days of stock and a stronger review position. bol Sponsored Products currently spends only €38 per day with a 17% ACOS. bol scores 87.
The decision is not “Amazon good, bol good.” It is sharper: cap Amazon at €60 per day until inbound lands, move €40 per day into bol scale campaigns, and review after seven days. The next euro follows profit capacity, not platform habit.
Example 2: LumaPet needs learning budget, not an ACOS punishment
LumaPet launches a dental chew multipack on Amazon and bol. The first week looks ugly: €312 ad spend, €690 attributed revenue and 45% ACOS. A normal optimisation pass would cut bids. The SKU queue asks what the spend is buying.
Contribution margin is 42% after marketplace and fulfilment costs. Stock cover is 78 days. The listing has 22 reviews at 4.7 stars. Search-term evidence shows three converting non-brand terms with low volume but high repeat-order potential. Evidence maturity is still low: only 148 clicks across both marketplaces.
The queue score is 76: controlled test. The decision is to keep €45 per day in learning budget for another ten days, isolate the three promising search terms into manual campaigns, and block two irrelevant terms that spent €37 without cart adds. FiveX Ads AI recommendations can support the bid review, but the operator should not let an ACOS rule kill a product that is still buying useful evidence.
Example 3: VoltEdge should hold MediaMarkt until the offer is fixed
VoltEdge sells a USB-C hub for laptops. MediaMarkt proposes a retail media push around a back-to-work page. The placement cost is €1,200 for the week. The in-platform forecast looks attractive: high electronics intent, strong category traffic and a predicted ROAS of 4.5x.
The SKU queue blocks it. The hub’s contribution margin fell from 28% to 19% after a supplier price increase. Amazon has already started discounting comparable hubs. MediaMarkt content is missing two compatibility images. Stock cover is 24 days, but the next shipment is not confirmed. The score is 43: repair before scaling.
The decision is to hold the placement, fix the content, reset the price or bundle economics, and reopen the question next week. That sounds slower. It is actually faster than spending €1,200 to discover that the product page was not ready to convert profitably.
How the weekly queue runs
The operating rhythm is simple.
- Monday: rank the top 20 SKUs by spend potential. Include current spend, lost opportunity, margin, stock and strategic role.
- Tuesday: assign permissions. Scale, controlled test, repair or hold.
- Wednesday to Friday: let campaigns serve the queue. Bid changes, search-term moves and budget reallocations must tie back to the SKU label.
- Friday: review queue movement. Which SKUs graduated? Which lost permission? Which stayed stuck because the same data was missing again?
FiveX fits naturally into this cadence because marketplace analytics, advertising performance, product profitability, inventory risk and AI recommendations sit in one operating layer. The point is not that software replaces the operator. The point is that the operator stops making ad decisions with half the business context missing.
The trade-off: fewer optimisations, better decisions
A SKU priority queue will make the team do fewer random optimisations. Good.
It may mean you do not touch a campaign with a noisy ACOS because the SKU is waiting for stock. It may mean you leave a launch campaign alive even though the first week looks inefficient. It may mean you decline a retail media opportunity because the product page is not ready. That can feel uncomfortable to a team used to proving activity.
But managed marketplace advertising should not be measured by how many switches were flipped. It should be measured by whether ad spend moved toward products with the strongest profit permission.
If your Advertentie Service can show that every Amazon, bol and MediaMarkt budget move came from a SKU priority queue, the client conversation changes. You are no longer defending isolated bid edits. You are explaining capital allocation.
That is the work. The campaign is not the customer. The SKU portfolio is.