iSeller — order_status_update

Part of the iSeller adapter guide — see it for authentication, endpoints, pagination, rate limits and shared quirks.

Contract: status update or skip sentinel.

iSeller pushes inbound webhooks (separate "Webhook Notification" mechanism — set up in-store under Apps → Webhook, per-type Notification URLs, retries on failure). Relevant events: Order and Fulfillment (also Refund, Member, Payout, Online Ordering Notification).

Signature verification (do in Go, not JS):

• Header Timestamp — e.g. 2019-11-29T06:06:40.0476436Z.
• Header Signature = SHA256( APIKey + rawJsonBody + Timestamp ), hex (uppercase), where APIKey is the store's API key (the shared secret). Verify before processing.

Order event body (key fields):

iSeller field	Use
order_id (GUID)	POS order reference → posOrderId
order_reference (#3340-10001)	human ref
channel (pos / online)	filter/route
status (e.g. completed)	order lifecycle
payment_status (e.g. paid)	payment
fulfillment_status (e.g. fulfilled)	fulfillment
cancel_reason	present when cancelled

Status mapping (examples — full enums [verify]):

iSeller	Cata status
fulfillment_status: fulfilled	COMPLETED (or READY)
status: completed + payment_status: paid	COMPLETED
cancel_reason present / cancelled	CANCELLED

Reconciliation: match the webhook's order_id to the external id captured when the order was dispatched (order_dispatch) to update the right Cata order. iSeller also emits webhooks for orders created directly in iSeller (pos/web); filter to Cata-dispatched orders (by stored external id, or by channel).

// @provider iseller  @topic order_status_update — TO BE GENERATED