This article discusses the importance of managing time-gated product launches in a GraphQL API. It highlights two approaches to filtering: implicit and explicit, where the logic is handled by the domain service or within the field resolver, respectively. The article also touches on displaying unavailable products, error handling, connecting entity types across subgraphs, and paginating lists when gating products. Additionally, it emphasizes the need for predictable responses from the client application, particularly when dealing with time-gated results that may be filtered from the list within the data source or in the field resolver. The article concludes by encouraging readers to explore a retail supergraph schema and run real queries against it to see the possibilities of Apollo GraphOS in powering modern retail applications.