Skip to main content
When products, categories, or collections change in Enad, storefront caches may still serve stale pages. Storefront revalidate delivers updates to registered URLs, enabling Next.js ISR, CDN purges, or custom cache logic on a schedule or on demand. This page covers the Admin UI. For the HTTP contract and JSON payload, see Revalidate and Payload.

​
Location in Admin

  1. In Enad Admin, open the target app.
  2. Navigate to System → Storefront revalidate (Beta).
This page lists and manages all revalidation endpoints for the app. The same view is available from the status popover on individual catalog items (see below).

​
Endpoint configuration

Select Create endpoint and configure: Saved endpoints appear in a table with URL, interval, auth status, and next scheduled sync. The row menu supports edit and delete actions.
In edit mode, leave the auth header value blank to retain the existing secret.

​
Status on products, categories, and collections

When editing a product, category, or collection, a refresh icon appears in the header actions. The Storefront revalidation popover shows status across all configured endpoints for that item:
Endpoint status appears only after at least one revalidation event has been recorded for the item. Before that, the list is empty and a notice indicates that no revalidation has run yet.
  • Each endpoint URL and when revalidation last ran
  • Run revalidation for on-demand sync outside the scheduled interval, for example during troubleshooting or when an update must reach the storefront before the next endpoint sync
  • A link to Configure here when no endpoints are configured

​
How it fits together

Enad handles change detection and delivery. The endpoint handler determines what to invalidate: a page path, a CDN tag, or a full rebuild.

​
Next steps