Until recently, this was not an issue with ExpertFlyer. In the example below, there are 7 or more J seats for sale, yet only 3 seats showing that are unassigned. This cannot be correct. But it would be correct to see 3 seats for sale, but showing 5 unassigned, which was common in the past.

My guess is there may be blocked seats. So either one of two things is happening:
1) Data sources (APIs, web scrapers, however EF gets its data) are no longer differentiating between blocked seats and occupied/assigned seats
2) Data sources are still differentiating, but EF logic/software is not differentiating and displaying properly