---
title: "Commerce order updated event"
method: POST
path: "commerce.order.updated"
tags: ["Webhook Events"]
---

# Commerce order updated event

`POST commerce.order.updated` (webhook)

Fired when an order on a connected store changes: payment, fulfilment, cancellation, edits, and refunds too. The payload carries identifiers only; read the order with
`GET /v1/commerce/orders/{orderId}?accountId=...`. Fired once per
Zernio account connected to the store.

## Payload

- WebhookPayloadCommerceOrder
  - `test` boolean: Always true when present: only a sample sent by POST /v1/webhooks/test with an event carries it. Real deliveries never do.
  - `id` string
  - `event` 'commerce.order.created' | 'commerce.order.updated' | 'commerce.order.refunded'
  - `timestamp` string, date-time: UTC time at which Zernio generated this event (set once when the event payload is built, before delivery is queued). Retries and redeliveries keep the original value, so it reflects the event, not the delivery attempt.
  - `store` object
    - `accountId` string: Zernio SocialAccount id of the store.
    - `platform` 'shopify' | 'woocommerce'
    - `shopId` string, nullable: The platform id of the shop.
  - `resource` object: Identifiers only, never buyer data: read the order with GET /v1/commerce/orders/{orderId}.
    - `type` 'order'
    - `id` string: Platform-native order id.
    - `status` 'pending_payment' | 'on_hold' | 'awaiting_fulfillment' | 'partially_fulfilled' | 'in_transit' | 'delivered' | 'completed' | 'cancelled': Where the order stands. The raw platform value is returned next to it as platformStatus.
    - `platformStatus` string, nullable: Raw platform status, e.g. UNFULFILLED on Shopify or processing on WooCommerce.

## Acknowledgement `200`

Webhook received successfully

---

[API](https://skmtc.dev/zernio/apis/zernio-api.md) · [All operations](https://skmtc.dev/zernio/apis/zernio-api/llms.txt) · [OpenAPI document](https://skmtc.dev/zernio/apis/zernio-api/revisions/4e74db179e73?raw)