Marketplace Liquidity Management

Scope

Covers

• Defining liquidity as reliability: how often a user can complete the marketplace’s core action (find → match → transact) within an acceptable time and quality threshold
• Measuring liquidity where it actually happens (by “local markets” like geo × category × time window), not just in global averages
• Diagnosing liquidity failure modes: fragmentation, supply–demand imbalance (“flip-flop”), matching/mechanics issues, and quality/trust breakdowns
• Designing a practical liquidity operating system: scorecards, weekly review cadence, and a “whac-a-mole” rebalancing plan (move attention/inventory/incentives)
• Producing an actionable experiment backlog to improve liquidity (supply, demand, matching, pricing/incentives, trust & safety)

When to use

• “We need to improve marketplace liquidity / match rate / fill rate”
• “Time-to-match is too slow” / “buyers can’t find availability”
• “Supply and demand are imbalanced across cities/categories”
• “Our marketplace feels unreliable” / “conversion drops due to no availability”
• “We need a liquidity dashboard + operating cadence + experiments”

When NOT to use