How a Single Database Column Quietly Sold Paid Listings for Free

A US directory platform for special needs schools and ABA therapy providers discovered that a single integer column controlling featured rankings was costing them revenue. Because the priority flag lived on the listing row itself, paying to promote a provider in one city automatically boosted them across every other city they served, giving away inventory the company could have sold separately. The flawed schema also made market-based pricing impossible and tied cancellations to all locations at once. The team replaced the column with a dedicated market_coverage table, linking each listing to a specific market with its own plan tier, rank, and placement source. The fix made previously unanswerable business questions — such as when a placement started or why a provider appeared in a given market — straightforward database queries.