Money for nothing: is anyone checking your affiliate commission?

A program nobody was actually running

The brand wasn't proactively managing affiliate marketing — no planned campaigns, no active recruitment, no outreach. It had simply been running on its own for years, the way affiliate programs quietly do. But there was one person keeping an eye on the money: checking every commission claim, and specifically, whether the discount code used in the sale was one the brand's own site had generated. If it was, no commission was paid — the sale wasn't the affiliate's to claim.

That single check was doing more work than it looked like it was doing.

Why that specific check mattered so much

The affiliate program had a long tail of old, inactive "discount code" sites still registered — the kind that exist purely to catch people searching "[brand] discount code." Many of them had nothing real to offer. A visitor would click through looking for a code, find nothing live, and simply use the brand's own legitimate code instead — the one from a newsletter signup, say, not from the affiliate at all.

This is the same pattern that shows up when a brand's own discount code gets published somewhere it was never meant to be found — a code being searched for and found in the wrong place, quietly undermining whatever it was supposed to be gating.

Affiliate tracking typically runs on a 30-day attribution window. Clicking through the old coupon site — even to find nothing — was often enough to plant that window. If the sale happened within it, using any code at all, the affiliate network would credit the coupon site by default. The verification check existed for exactly this reason: to catch it and void it before it became a real cost.

What happened when the check stopped

The person doing that verification left the business. The head of department who inherited it didn't fully understand what the task was actually for — from the outside, it looked like small, quiet admin, not something with a real number attached to it. An assumption was made about how much the role was worth. It was never replaced.

The mistake wasn't carelessness

Nobody decided the checking didn't matter. The role simply looked like nothing was happening, right up until two months of evidence arrived that something very much had been. That's the trap with this kind of task — the value is entirely in what doesn't happen, and nothing that doesn't happen shows up on anyone's radar until it's expensive.

How this fits the framework

A departing hire's job should be re-evaluated, not automatically dropped or automatically re-bought — the same principle either way. Usually that means asking whether a role is still needed at full cost. Here it cuts the other direction: a role that looked administrative and easy to skip was actually a live Defend job, protecting real margin every single month it ran. The mistake wasn't hiring too much. It was assuming a quiet task had no real job attached to it.