FULFILLMENT_NOT_REQUIRED to every mapping of OrderDisplayFulfillmentStatus before upgrading Admin GraphQL to 2026-10. This is an order with nothing left to fulfill, not a new warehouse queue. Never turn an unknown fulfillment enum into an automatic pick ticket.On this page
Why the status changed
Shopify announced the enum change July 3, 2026. Fully cancelled orders, fully refunded orders without fulfilled items, and orders whose fulfillable quantities were removed could previously report UNFULFILLED. API 2026-10 can return FULFILLMENT_NOT_REQUIRED for these cases. Older API versions continue returning the older value. This is an additive GraphQL enum, but it is operationally breaking for integrations with exhaustive switch statements or hard-coded allowed statuses.
Fix the state mapping, not the order data
Search your code for displayFulfillmentStatus, OrderDisplayFulfillmentStatus, UNFULFILLED and any BI report or ERP transformation that assumes the enum list is closed. Introduce a dedicated terminal/no-work state for FULFILLMENT_NOT_REQUIRED. Keep order cancellation, payment/refund status and fulfillment status as separate dimensions; they answer different questions. Do not mark the order fulfilled merely to make the dashboard green.
A defensive JavaScript mapping
function fulfillmentQueueState(status) {
switch (status) {
case 'UNFULFILLED': return 'review_for_fulfillment';
case 'PARTIALLY_FULFILLED': return 'review_remaining';
case 'FULFILLED': return 'complete';
case 'FULFILLMENT_NOT_REQUIRED': return 'no_fulfillment_work';
default: return 'manual_review';
}
}
The default is deliberately non-destructive. Adjust these states to your actual ERP contract; this example is a routing safeguard, not a complete enumeration of every Shopify status. Read the order’s current line items and fulfillment orders before generating shipping work.
Review historical reconciliation
If you compare records fetched under different API versions, a changed display status does not prove a new fulfillment event occurred. Record the API version in exports and reconcile against fulfillable quantities, cancellations and fulfillment-order state. Update filters and reporting queries so zero-work orders don’t inflate the unfulfilled backlog.
How to test this
- Create a test order with a physical item and verify its initial fulfillment state.
- Fully cancel an unfulfilled test order, then read
displayFulfillmentStatuson API 2026-07 and 2026-10. - Test a fully refunded/unfulfilled scenario and an order with remaining fulfillable items.
- Confirm ERP routing creates no pick task for
FULFILLMENT_NOT_REQUIRED. - Inject an unknown enum in unit tests; verify safe manual review and no destructive default action.

