Coverage

The honest boundary of what a webhook subscription covers on its own.

The honest boundary of what a webhook subscription covers on its own. Read this before you assume webhooks alone keep your catalog fully in sync.


Coverage: what notifies and what does not

Every event is scoped to your visible catalog. Visibility means both halves of a rule: the product is in a collection shared with you, and it is priced in a price type attached to you.

ChangeNotified?
Product content: core fields, SKUs, prices, images, categories, badges, tags, materials, delivery windows, color exclusionsYes
A product deleted at JOOR, hard or softYes
A collection shared or unshared with youYes
A brand connected or disconnected; a price type granted or revokedYes
Collection metadata: name, season, delivery window, cutoff date, can_buyNo

Note the distinction in the two delivery window rows: a SKU delivery window is product content and notifies, a collection delivery window is collection metadata and does not.

Every way a product can vanish mid seed, becoming invisible, being deleted, or leaving the collection, is a row in this table marked Yes, so the transition reaches you as an event regardless.

A daily re walk is part of a correct integration

Because collection metadata does not notify, re walk GET /v4/connections and GET /v4/retailers/brands/{id}/collections on a schedule. Daily is enough.

This is cheap: a couple of thousand summary requests, minutes of wall clock. It is also your safety net for anything else, so keep running it even after metadata events exist.

One honest limit on deletions

There is a third way a product leaves your catalog: it keeps its collection but loses the last price you can see. We detect that from the fact that we previously told you about the product, and our delivery history is kept for 90 days.

A product you have not received any notification about for longer than that, which then loses its price, may not be announced. The daily re walk plus a periodic full reconciliation is what covers the tail. We would rather write this down than imply coverage we do not have.

Practically: a quiet product, one nobody edits and nobody reprices, is exactly the product this affects, and a seasonal catalog is full of them. Plan a full product level reconciliation on a cadence shorter than 90 days, not only the daily header re walk.