AI and Automation

Shopify Events vs Webhooks for Odoo Sync: What Changed and Why It Matters

How Synco moved product, inventory, customer, order, and fulfillment updates from classic Shopify webhooks to Shopify Events, how Events take priority over pending webhook jobs, and what it means for how fast and how reliably changes reach Odoo.

The Quick Take

For years, a Shopify Odoo connector learned about changes one way: Shopify sent a webhook for the topic, the app verified it, queued a job, and the job fetched the record and wrote to Odoo. That still works. But classic webhooks fire on every save, carry a payload that may already be stale by the time the job runs, and for some topics do not fire at all for the field you care about.

Shopify Events are the newer delivery mechanism. Synco now uses them for product, inventory, customer, order, and fulfillment updates from Shopify to Odoo, with classic webhooks kept for creates and as a fallback. This guide explains the difference in practice, how the two are reconciled when both arrive, and what to expect in the sync logs.

Related reading: webhook sync guide, auto-sync webhook registration, idempotent sync jobs, inventory webhook payloads, features page.

Webhooks, Briefly

A classic webhook is a topic subscription: products/update, inventory_levels/update, orders/updated, and so on. Shopify POSTs a payload to the app on every matching change. The app must answer fast, so Synco verifies the signature, queues a job with a deterministic id built from the shop and the record id, and returns 200. The job runs a little later, fetches the current record, and syncs it.

Two properties matter for an ERP sync:

  • Volume. A product with 40 variants edited in bulk can fire dozens of updates in a second. Synco debounces them into one job per record, delayed slightly so the last edit wins.
  • Coverage. Some changes do not fire the topic you would expect. A metafield edit, a variant added through the admin, or a change made by another app may arrive late or under a different topic.

What Events Change

Shopify Events are triggered on the fields you subscribe to rather than on the save. Synco subscribes to exactly the fields the Odoo sync reads: the product and variant fields that are sent to Odoo, inventory levels at mapped locations, the customer and order fields that drive partner and sale order updates, and fulfillment creation and update.

The practical effects:

  • Fewer, more relevant deliveries. An edit to a field that does not sync does not trigger anything. An edit to one that does, triggers once.
  • Better coverage. Fields that classic topics missed now fire, because the subscription names the field.
  • Same job path. An Event is turned into the same queued job as a webhook would have been. Odoo sees no difference; the sync logic is identical.

Events are gated per shop by the sync settings you already have. Turn off automatic product sync and product Events are not acted on.

When Both Arrive

During the transition, a change can arrive twice: once as a classic webhook and once as an Event. Synco gives Events priority for the same shop and record.

  • Both share one debounced job id per record, so there is one job, not two.
  • An Event replaces a pending webhook job and restarts the short delay, keeping the Odoo protocol the earlier job had queued.
  • A webhook arriving behind a pending Event only adds its source label; the Event's delivery is used.
  • A second Event refreshes the pending Event job.
  • A job that is already running is left alone; the follow-up delivery becomes a timestamped successor job that waits a minute, so history is never overwritten.

The logs show the source as webhook, event, or both. If you see "both" on most jobs, the shop is in the transition window and that is expected.

What Does Not Use Events Yet

Creates. New products, orders, and customers still arrive through classic webhooks, because Events cover updates. Odoo to Shopify flows use Odoo's own webhooks (automated actions) and periodic sync, unchanged.

What You Should Notice

For most stores: nothing, which is the point. Products edited in Shopify reach Odoo with the same delay as before, and a few changes that used to need a manual sync now arrive on their own.

For high-volume stores: fewer queued jobs per bulk edit, and fewer "nothing changed" syncs, because the Event only fires for fields that matter.

For stores that watch the logs: a source label on each job, and a weekly count of Event-driven versus webhook-driven syncs on the dashboard.

Reliability Properties That Did Not Change

  • Every job is idempotent and retry-safe, with bounded retries and backoff.
  • Job ids are deterministic per shop and record, so a replayed delivery cannot create a duplicate.
  • Rate limits on either side pause and resume by themselves.
  • A failed job stays visible for 15 days with its log and can be retried from the dashboard.

Events change how Synco learns about a change. They do not change how carefully it is applied.

Frequently Asked Questions

Do I need to do anything to switch from webhooks to Events? No. Synco registers Events for the flows you have enabled and keeps classic webhooks as a fallback. Nothing changes in Odoo.

What happens if a webhook and an Event arrive for the same product? They share one debounced job. The Event replaces a pending webhook job. One sync runs with the latest data.

Which flows use Events today? Product, inventory, customer, order, and fulfillment updates from Shopify to Odoo. Creates still use classic webhooks.

FAQ

Common questions

Do I need to do anything to switch from webhooks to Events?

No. Synco registers Events for the flows you have enabled and keeps classic webhooks as a fallback. The switch is managed per shop from your sync settings; nothing changes in Odoo.

What happens if a webhook and an Event arrive for the same product?

They share one debounced job per record. An Event replaces a pending webhook job; a webhook arriving behind a pending Event only adds its source label. One sync runs with the latest data.

Which flows use Events today?

Product updates, inventory level changes, customer updates, order updates, and fulfillments from Shopify to Odoo. Creates still arrive through classic webhooks.

Keep reading

Related guides