Styxis
Company
Knowledge

Shopify canceled receiving: reconciling the meaning of totalReceivedQuantity

When testing the new receiving state, separate status totals so received is not mistaken for the quantity that physically arrived.

Shopify canceled receiving: reconciling the meaning of totalReceivedQuantity

Assuming a received total means only physically arrived or sellable stock can mislead reconciliation when a new status is introduced. A contract recording cancellations separately must distinguish processed units from physical movement. Preserve API version and status-specific quantities to explain totals across the transition. [1, 2, 3]

What the primary source establishes

Shopify added CANCELED receiving and canceled-quantity fields to inventory shipments in API 2026-10. It states that received includes accepted, rejected, and canceled quantities. Earlier webhook versions do not deliver receives that change canceled quantities alone. [1]

The handover decision

Build a trial shipment containing accepted, rejected, and canceled units. Record both the received total and webhook-delivery scope by API version. Keep api_version, accepted, rejected, canceled, and total_received together rather than mapping every closed-out unit into sellable inventory. [1, 3]

A reference defined before the output

The illustrative shipment has 7 accepted units, 1 rejected unit, and 2 canceled units, giving a processed total of 10. Reporting 8 by omitting canceled units fails the new received definition. The normal total is 10, not an assertion that all those units physically arrived. [1, 3]

The scoped Truthound check

Truthound Core 3.3.2 can check the relationship between total_received and its status components with ExpressionValidator. Specify the business definition in filter_expr and retain the webhook subscription version. This is not a function that moves inventory or cancels receiving. [1, 2, 3]

Limits and alternative choices

Received does not necessarily mean physical arrival or sellable inventory, and missing delivery on an earlier webhook version is not automatically a collection failure. Preserve status quantities and separate webhook and query-reconciliation paths across the version transition. Do not impose the new state total on an integration using only earlier versions without the canceled action. [1, 3]

Application conditions

Prepare status-specific quantities and the received total under the same API version and shipment identity.

Alternatives

Preserve status quantities and separate webhook and query-reconciliation paths across the version transition.

Limitations

  • Received does not necessarily mean physical arrival or sellable inventory, and missing delivery on an earlier webhook version is not automatically a collection failure.

Evidence

Event checked
Subject checked
Modified