headless-caching-strategy

To configure caching for a headless VTEX storefront, apply TTL recommendations and cache invalidation patterns to public APIs like Intelligent Search and Catalog, while keeping Checkout and Profile APIs uncached.

Non-cacheable VTEX APIs include Checkout, Profile, and OMS endpoints. These APIs handle sensitive user-specific data and dynamic state, requiring requests to bypass CDN and BFF-level caching layers entirely.

CDN cache invalidation for VTEX Catalog APIs uses specific patterns to clear stale data when product information changes. This ensures users receive updated catalog data without waiting for TTL expiration.

The best way to cache VTEX Intelligent Search responses is utilizing CDN edge caching for public queries and BFF-level in-memory or Redis caching for frequently requested search data.

Yes, you can use Redis for BFF-level caching in VTEX headless commerce. It stores frequently requested data from public APIs, reducing direct API load and improving storefront performance.

High API latency in a headless VTEX storefront often occurs when public APIs like Intelligent Search lack CDN caching, or when non-cacheable APIs are incorrectly routed through edge caches.