Build a title-level eligibility register and a sequential catalogue filter. A headline count should never be the denominator until duplicates, relevance and permission uncertainty have been resolved.
Use the following proposed sequence:
| Stage | What to establish |
|---|---|
| Advertised records | What the supplier export actually contains |
| Distinct content | Which rows represent separate games or meaningful variants |
| Editorially relevant | Which games meet your audience and publishing priorities |
| Documented eligibility | Which uses, domains and territories are covered |
| Operationally accepted | Which eligible games passed the agreed test matrix |
Apply exclusions sequentially so a title rejected for several reasons is not subtracted several times. Keep the original record and all reasons for exclusion.
Use three eligibility states: confirmed, excluded and unresolved. An unresolved title should not enter the confirmed usable total, but should not be described as definitively unavailable either.
A useful complementary measure is:
Priority coverage = sum of weights for accepted required titles ÷ sum of weights for all required titles
Set weights before comparing suppliers, and use the same requirement list throughout.
The distinction matters even within a single supplier: First Look Games separately advertises its information library and Demo Game Server offering. Buyers should request the relevant playable subset rather than assume the two inventories are identical. (firstlookgames.com)