Use webhooks to keep static storefronts fresh.

Why This Matters

Astro and Netlify storefronts are fast because they serve static HTML. Product state such as price, inventory, and availability can become stale unless the site hydrates live offers or rebuilds after catalog changes.

Distribution Webhooks give each storefront a place to store deploy hooks and future webhook destinations. The first supported use case is a Netlify build hook.

Netlify Build Hook Setup

1. Open the Netlify site settings for the storefront.
2. Create a build hook for the production branch.
3. Copy the hook URL.
4. In BMOS, open the storefront and go to Distribution → Webhooks.
5. Add the hook as a Netlify build hook destination.
6. Use the Test button to trigger a rebuild.

Recommended Triggers

• manual_rebuild for support and merchant-triggered rebuilds.
• product_changed when catalog product content changes.
• price_changed when BMOS pricing overrides change.
• availability_changed when source inventory or BMOS offer availability changes.

Long-Term Webhook Uses

The Webhooks area is intentionally general. BMOS can later support custom merchant automations, Zapier/Make, deploy hooks, catalog sync hooks, and notification destinations from the same storefront-level model.