Luxury waitlist allocation: building a defensible scarcity model

September 13, 2026 · 5 min · Free, with full transcript

Who decides that a Hermes Birkin buyer waits six years? The position here is blunt: scarcity is an asset a data team manages, and every "nothing available" is an allocation decision someone modeled. The episode separates manufactured scarcity from the allocation logic that ranks clients by lifetime spend, purchase breadth and loyalty, and looks at the US class action arguing that tying Birkin access to other purchases is illegal bundling. You come away with a three-layer design, scarcity forecast, eligibility stripped of protected proxies, and allocation ranking, plus why transformation tools like dbt give you lineage as a legal shield. Also covered: the Patek Philippe Nautilus 5711 discontinuation and reading waitlists as intent data for product planning.

Listen to the podcast

5 min

Chapters

Key takeaways

  • Keep the scarcity forecast, the eligibility layer and the allocation ranking as three separate layers so any single decision can be audited.
  • Strip proximity variables such as postcode from eligibility rules, since they can smuggle protected characteristics into the model.
  • Document transformations so every allocation traces back to the rule that produced it, and treat vendor claims like dbt Labs' incident reduction figure as marketing to cross-check.
  • Feed waitlist data into product planning as a demand sensor by model, region and client tier instead of treating it as an apology backlog.
  • On Monday, test whether you can explain in writing why the last person got an offer and the person behind them did not.
Read the full transcript

Welcome to the Leaders Insights Podcast.

Today's episode, scarcity modeling and waitlist allocation for hero luxury products.

A CDO playbook.

A Birkin waitlist can stretch six years.

That's not customer service failing.

That's a design choice.

Who's actually making it?

The data team, whether they admit it or not, every sorry nothing available is an allocation

decision dressed up as bad luck.

Hermes doesn't have a shortage problem, it has a scarcity model, and someone built that

model with rules and thresholds.

Come on, are you telling me there's a spreadsheet deciding who deserves a 12,000 euros bag?

More sophisticated than a spreadsheet, but yes, essentially.

The durable principle here, the one the best operators internalized years ago, is that scarcity

is an asset you manage, not a limitation you apologize for.

The moment you can make everyone a Birkin, the Birkin is worth nothing.

So the model exists to keep supply below demand on purpose.

That sounds like a polite word for manipulation.

It's manufacturing, and it's legal, up to a point.

Where it gets interesting is the allocation layer, deciding who gets offered the scarce

thing.

That's where firms quietly build a customer scoring system, ranking clients by lifetime

spend, purchase breadth, how long they've been loyal, buy the scarves, the shoes, the

homeware, and your Birkin odds climb.

It's a relationship ledger.

And the legal line?

In the US, there's an active class action against Hermes, arguing that tying Birkin

access to other purchases is illegal bundling.

Whether it wins or not, the lesson stands.

Your allocation logic has to survive a courtroom.

If your model discriminates on anything protected, and proximity variables like postcode can smuggle

that in, you've built a lawsuit, not a strategy.

So what does a defensible model actually look like?

Give me the architecture.

Three layers.

One, the scarcity forecast rounds.

How much to make and hold back per region.

Two, the eligibility layer, who legally qualifies stripped of any protected proxy.

Three, the allocation ranking.

Being the eligible, who gets first offer?

Keep those separate when they blur, you can't audit why any single person was chosen.

And that's exactly the question a regulator asks.

You mentioned data tooling earlier.

What are these firms running under the hood?

A lot of them are moving allocation logic into transformation layers.

Tools like DBT, which basically turn raw sales data into governed, documented tables.

DBT Labs claims teams cut their data incidents significantly after adopting it.

But they sell that software, so treat the number as marketing and cross-check it.

What's genuinely useful, and O'Reilly Radar has written on this, is that documented transformations

give you lineage.

You can trace every allocation decision back to the rule that produced it.

That's your legal shield.

Patek Philippe does this with watches too.

Same playbook?

Same principle, different knob.

The Nautilus 5711 was discontinued in 2021, specifically to reset scarcity.

And the waitlist became legend.

But here's what the amateurs miss.

A waitlist is a data goldmine most brands waste.

It tells you unmet demand by model, by region, by client tier, in real time.

MIT Sloan Management Review has made the point that intent data—signals of what

people want before they buy—is often more valuable than transaction data, because it

predicts the next collection.

So the waitlist isn't a cue, it's a forecast.

Exactly.

If 10,000 people are waiting for a specific dial, you've just been told what to produce

next and at what price.

Most luxury houses treat that list as an apology backlog.

The smart ones treat it as a demand sensor and feed it straight into product planning.

Isn't there a risk you optimize so hard you strangle the mystique?

Turn romance into a scoring engine?

That's the real trap.

If clients feel graded, they resent it.

And resentment kills desirability faster than availability does.

So the model runs in the back office and the front of house stays human.

The data decides the offer.

The salesperson delivers the story.

The second the customer sees the algorithm, you've lost.

Give me the one thing a CDO should do Monday morning.

Pull your waitlist and check one thing.

Can you explain in writing why the last person got an offer and the one behind them didn't?

If you can't, you don't have a strategy.

You have a liability.

Sources for today's episode.

Cade Nuggets, The New Stack, O'Reilly Radar, Towards Data Science, MIT Sloan Management

Review, DBT Labs, vendor, Waymez Data Tooling.

That's your five.

The full CDO track, structured, no fluff, is at MBA-training.com.

Read and go deeper