Enhanced Fulfillment Queries and Responsive Sourcing Platform Improvements
Release
Author:
Kirill Gaiduk
Changed on:
17 July 2026
| Target release date: | 2026-07-23 |
|---|---|
| Release status: | Development |
Description
This feature is rolling out gradually. Some components may not yet be available in all environments. Thank you for your patience.This release extends the Fulfillment GraphQL API with enhanced query capabilities and introduces platform improvements for Responsive Sourcing:
- The release enhances the Fulfillment GraphQL API by adding support for querying fulfillments by destination location (
`toLocation`), making it easier to retrieve inbound fulfillments for click & collect and store replenishment scenarios - It also lays the foundation for upcoming Responsive Sourcing enhancements by introducing platform changes that support:
- 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`)
- 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
Limitations
- RejectedLocationExclusionCriterion can be configured with this release and becomes effective after upgrading to Order Module v2.2.0+
- 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 |
