Styxis
Company
Knowledge

Shopify FULFILLMENT_NOT_REQUIRED: distinguish unfulfilled from nothing left to fulfill

Mapping the new status to a generic unfulfilled queue can leave orders with no remaining work in the dispatch backlog.

No shipment does not always mean pending work

Unfulfilled and no remaining fulfillment obligation are different states. Collapsing the new status into pending orders hands impossible work to the operations team. An order with nothing left after cancellation or refund can trigger another investigation if it still appears unprocessed. The queue should communicate remaining work rather than merely copy a status label. [1, 2, 3]

The version and conditions for the new state

Shopify's 2026-07-03 announcement says that OrderDisplayFulfillmentStatus may return FULFILLMENT_NOT_REQUIRED from 2026-10. It covers orders not fulfilled but with no remaining fulfillable quantity, including cases previously shown as UNFULFILLED. Earlier API versions remain unchanged. The announcement also advises treating enums as open to future additions and handling unrecognized values gracefully. [1]

Retain the source state before applying queue policy

The dispatch-list owner should inspect display branches for orders with nothing remaining after cancellation or refund. Support the new state, then recheck queue inclusion. Preserve the source state and API version so the new branch is not incorrectly required of older responses. Keeping unrecognized states in an investigation path, rather than converting them immediately to unfulfilled, protects handoff meaning when another enum value arrives. [1, 3]

Passing and failing cases with 0 remaining items

Define an illustrative order with no fulfilled goods that has been fully cancelled, leaving fulfillable quantity 0. Expected queue inclusion is false. An actual false result separates an order with no executable shipment work. A true result places an order with no remaining obligation into the dispatch queue and calls for a mapping correction. This is a conditional example, not a classifier for every possible state. [1, 3]

Truthound checks contradictions in the handoff table

RowLevelValidator in Truthound Core 3.3.2 takes a row_validator callback that can check the relation between prepared source status, remaining quantity and queue classification. The dispatch owner defines the business rule; the validator does not cancel or refund an order. Investigate records lacking a confirmed version, status or quantity first. Test both support for the new type and the fallback for unknown values, so passing this case is not mistaken for complete correctness across all states. [1, 2, 3]

Application conditions

For 2026-10 or later, retain actual source status and remaining fulfillable quantity, and have the dispatch owner approve the queue definition. Keep unknown enum values in a separate hold path.

Alternatives

Update mapping tables and generated types, and implement a default hold branch for unrecognized enum values.

Limitations

  • Truthound does not perform cancellation or refunds, and this rule does not classify other fulfillment states. Do not require the new enum from older API responses.

Evidence

Event checked
Subject checked
Modified