---
title: "Storefront revalidate in Admin"
description: Configure revalidation endpoints and check sync status from the Enad dashboard.
---

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](/storefront/revalidate/revalidate) and [Payload](/storefront/revalidate/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:

| Field | What it does |
| --- | --- |
| **URL** | HTTPS endpoint that receives a `POST` with a JSON body when content changes. |
| **Channel** | Optional. Limits product payloads to one channel's name, slug, and translations. |
| **Interval** | How often Enad tries to deliver pending updates (1 minute to 24 hours; default 15 minutes). |
| **Auth header** | Optional. A custom header name and value sent on every request. |

Saved endpoints appear in a table with URL, interval, auth status, and next scheduled sync. The row menu supports **edit** and **delete** actions.

:::tip
  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:

:::note
  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

{/* ## Permissions

| Permission | Allows |
| --- | --- |
| `integrations.view` | View endpoints and open the status popover |
| `integrations.edit` | Create, edit, delete endpoints and run revalidation | */}

## How it fits together

```mermaid
flowchart LR
    A[Catalog change] --> B[Enad marks item dirty]
    B --> C{Scheduled interval}
    B --> D[Manual Run revalidation]
    C --> E[POST to registered URL]
    D --> E
    E --> F[Storefront refreshes cache]
```

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

- [Revalidate overview](/storefront/revalidate/revalidate): scheduling, retries, and URL requirements
- [Payload reference](/storefront/revalidate/payload): JSON fields per content type