Skip to main content
Galantis registers webhooks across every major Shopify data domain at installation time. These webhooks are the primary mechanism for keeping Galantis data current — when something changes in Shopify, the corresponding webhook fires and Galantis processes the update asynchronously. Webhook handling is resilient to temporary failures — a transient error does not cause a webhook to be permanently lost. Failed processing is retried automatically until it succeeds or exhausts the retry limit. All incoming webhooks are validated via signature verification before processing.

​
What this covers

  • Every registered webhook topic
  • What each webhook powers in Galantis
  • Security validation and retry behavior
  • What happens when a webhook is missed

​
Customer webhooks

​
Order webhooks

The orders/updated webhook covers all order update events in Shopify, not only shipping. Galantis specifically detects whether the update contains fulfillment data and only fires the ORDER_SHIPPED automation trigger when it does.

​
Product and collection webhooks

​
Billing and app lifecycle webhooks

The app/uninstalled webhook triggers immediate workspace deactivation. If the app is reinstalled, a new OAuth token exchange occurs and data may need to be re-synced. Active automations and campaign schedules from before uninstallation are not automatically re-activated.

​
GDPR compliance webhooks

These webhooks are sent by Shopify in response to GDPR data subject requests and merchant data deletion requests. See Compliance — GDPR & Data Privacy for the full context.

​
What happens when a webhook is missed

Webhook delivery is not guaranteed — Shopify will retry failed deliveries, but a sustained outage or network issue can result in missed webhooks. When this happens, the Galantis record for affected entities will be stale until a corrective sync occurs. Recovery options:
  • For product data — trigger a manual full sync from Catalog → Shopify Sync → Sync Now
  • For abandoned checkouts — the polling mechanism runs every 10 minutes and self-heals; no manual recovery is needed