Enhanced Fulfillment Queries and Responsive Sourcing Platform Improvements
Release
Author:
Kirill Gaiduk
Changed on:
13 Aug 2026
| Target release date: | 2026-08-10 |
|---|---|
| Release status: | Released |
Description
This release extends the Fulfillment GraphQL API with enhanced query capabilities and introduces platform improvements for Responsive Sourcing:- Adds support for querying fulfillments by destination location, making it easier to retrieve inbound fulfillments for click & collect and store replenishment scenarios
- Introduces platform changes that enable future Responsive Sourcing enhancements:
- More reliable concurrent re-sourcing and additional fulfillment uniqueness options
- Explicit rejected location exclusion configuration
Changelog
Platform- Introduced a uniqueness constraint that supports more reliable concurrent re-sourcing and duplicate fulfillment prevention in upcoming Order Reference Module v2.2.0
- Added support for filtering Fulfillment GraphQL queries by destination location (
`toLocation`)
- You can now enable
`fc.api.fulfilment.uniqueness`without submitting a support request. Once configured, the setting takes effect according to its documented behavior - Added support for the
`REF_ONLY`mode of`fc.api.fulfilment.uniqueness`setting, allowing references to be used as fulfillment unique identifiers - Updated the reference sourcing criteria configuration (
`fc.rubix.order.sourcing.criteria`setting) to expose`RejectedLocationExclusionCriterion`as an explicit configurable criterion
- GraphQL queries that traverse nested related entities (for example,
`order.fulfilments.fromAddress.location`) now resolve reliably - Querying an article's items (for example,
`articleById(...).items`) now returns each item exactly once, with a unique ID per item. Previously, articles associated with more than one fulfillment could return duplicate items
Limitations
- You can configure rejected location exclusion criterion starting with this release. The configuration becomes effective after upgrading to Order Reference Module v2.2.0 or later
- The
`toLocation`field is populated only for fulfillments created after this release. Existing fulfillments continue to return`null`for this field
| Released capability depth: | Enhancement |
|---|---|
| Release bundle / Capability type: | Platform |
