The order object and the allowed CRUD operations on the related resource endpoint
Orders get created in
draftstatus and become
pendingwhen they have a customer and some line items.
pendingorders can be recovered when abandoned. The status of an order is strictly dependent on the related payment and fulfillment statuses. When an order is
placed, it can either get
cancelled. An approved order becomes
fulfilledwhen paid and shipped. Cancelling an order automatically voids its payment source's authorization. Captured payments can be refunded, either fully or partially.
This can be useful to force a payment status (e.g.
paid), in case the payment gateway has recorded the capture, but for some reason (typically the gateway's timeout) the order kept an inconsistent payment status (e.g.
authorized). Webhooks's events, stock item updates, and other status-related actions are granted to be executed only once.