Create Custom Sourcing Condition

Get Started
Functionality
Learning
Extension
Dev Tooling
APIs
Releases

How-to Guide

Authors:

Kirill Gaiduk, Alexey Kaminskiy

Changed on:

3 Mar 2026

Key Points

Outcome: After completing this guide, you will know how to extend the Responsive Sourcing Framework with a Custom Condition and apply it in real Strategies
Minimal essentials: The process has four parts - implement the Condition, register it, expose it in the Setting, and verify behavior
Application: You will be able to influence sourcing decisions with your own logic, tailored to specific business contexts

Prerequisites

Responsive Sourcing Framework Overview

Sourcing Utilities Overview

Sourcing Conditions Overview

Getting Started with Reference Sourcing Conditions

Steps

Preliminary Setup

Custom Sourcing Condition creation requires modifying the Sourcing Utilities bundle:1. Prepare your module that contains Order Reference Module assets.

Reminder

Check the Module Recipe - Plugin Setup and Installation Guide for details.

2. Download the Sourcing Utilities Package (Java source code).3. Add Sourcing Utilities as a dependency in your project's `pom.xml` file.

Reminder

General Utility Bundles guidelines also apply to Sourcing Utilities.

Implement a Custom Sourcing Condition Function

Create a Condition class that enforces your business logic:

Create your class, e.g., `MySourcingCondition`, implementing the `SourcingCondition` interface.
Add your evaluation logic in `evaluateWithContext` method.

Note

Return only a boolean decision
Validate required fields from `sourcingContext` and handle missing/invalid data defensively
Mirror conventions from `DefaultSourcingCondition` (naming, null handling, logging)

Introduce Custom Sourcing Rules

Introduce custom versions of the Sourcing Rules that will execute your sourcing logic inside your plugin.

Note

Custom type registration and Rule execution must be initialized within the same plugin module.Creating custom Rules ensures that your Sourcing Condition or Criterion type is available during runtime evaluation.

1. Copy the reference Sourcing Rule implementation:

2. Rename the class3. Register your custom Sourcing Condition or Criterion inside the Rule class

1@RuleInfo(
2        name = "SampleCreateFulfilmentWithSourcingProfile",
3        description = "Applies Sourcing Profile {" + "profileRef" + "} to a sourcing request (Order, Fulfilment Option, etc.) and produces Fulfilment(s)",
4        accepts = {@EventInfo(entityType = "ORDER"),
5                @EventInfo(entityType = "FULFILMENT_CHOICE")}
6)
7@ParamString(name = "profileRef", description = "Profile reference to apply.")
8@Slf4j
9public class SampleCreateFulfilmentWithSourcingProfile implements Rule {
10
11    static {
12        // register custom criteria
13        SourcingCriteriaTypeRegistry.register("fc.sourcing.criterion.customCriteria", CustomCriteria.class);
14        // register custom condition
15        SourcingConditionTypeRegistry.register("fc.sourcing.condition.customCondition", CustomCondition.class);
16    }
17
18    @Override
19    public void run(Context context) {
20        SourcingCriteriaTypeRegistry.getTypeNameToClassMap().forEach((key, value) -> log.info("registered: {}", key));
21        SourcingProfile sourcingProfile = loadSourcingProfile(context);
22        if (sourcingProfile.getSourcingStrategies() != null) {
23            SourcingContext sourcingContext = loadSourcingContext(context, SourcingUtils::getUnfulfilledItems);
24            SourcingUtils.SourcingPlan plan = findPlanBasedOnStrategies(context, sourcingContext, sourcingProfile,
25                    ImmutableList.of("ACTIVE", "AT_RISK"), null);
26            if (plan.getFulfilments() != null) {
27                fillFulfilmentType(sourcingContext, plan.getFulfilments());
28                createFulfilments(context, sourcingContext, plan.getFulfilments());
29            }
30        }
31    }
32}

4. Replace the reference Rule in your Workflow configuration with your custom Rule

Reminder

Each plugin initializes its own Sourcing registries.To ensure correct registration and runtime resolution of custom Sourcing Conditions or Criteria, your custom Rule must:

Include `util-sourcing` in the plugin’s `pom.xml`
Register custom types inside the same plugin where the Rule executes

Expose the Condition Schema via Setting

Create (or update the existing) the Setting `fc.rubix.order.sourcing.conditions.custom` with your new Condition schema.

1mutation createSetting ($input: CreateSettingInput) {
2    createSetting (input: $input) {
3        id
4        name
5        valueType
6        lobValue
7        value
8        context
9        contextId
10    }
11}

1{
2  "input": {
3    "name": "fc.rubix.order.sourcing.conditions.custom",
4    "valueType": "JSON",
5    "lobValue": [
6      {
7      "name": "mySourcingCondition",
8      "type": "company.sourcing.condition.my",
9      "tags": [
10        "Lorem ipsum"
11      ],
12      "params": [
13        {
14        "name": "parameter1",
15        "value": "Lorem ipsum"
16        },
17        {
18        "name": "parameterN",
19        "value": "Lorem ipsum"
20        }
21      ]
22      }
23    ],
24    "value": "",
25    "context": "RETAILER",
26    "contextId": 1
27  }
28}

1{
2    "data": {
3        "createSetting": {
4            "id": "13141",
5            "name": "fc.rubix.order.sourcing.conditions.custom",
6            "valueType": "JSON",
7            "lobValue": [
8                {
9                    "name": "mySourcingCondition",
10                    "type": "company.sourcing.condition.my",
11                    "tags": [
12                        "Lorem ipsum"
13                    ],
14                    "params": [
15                        {
16                            "name": "parameter1",
17                            "value": "Lorem ipsum"
18                        },
19                        {
20                            "name": "parameterN",
21                            "value": "Lorem ipsum"
22                        }
23                    ]
24                }
25            ],
26            "value": "",
27            "context": "RETAILER",
28            "contextId": 1
29        }
30    }
31}

Verify the Condition Behavior

Use the Sourcing Profile GraphQL API to add the new Condition to a Sourcing Strategy.
Test against different Sourcing Requests and confirm the expected outcomes.

Related artifacts

fc.rubix.order.sourcing.conditions

Related content

Kirill Gaiduk

Contributors:

1@RuleInfo(
2        name = "SampleCreateFulfilmentWithSourcingProfile",
3        description = "Applies Sourcing Profile {" + "profileRef" + "} to a sourcing request (Order, Fulfilment Option, etc.) and produces Fulfilment(s)",
4        accepts = {@EventInfo(entityType = "ORDER"),
5                @EventInfo(entityType = "FULFILMENT_CHOICE")}
6)
7@ParamString(name = "profileRef", description = "Profile reference to apply.")
8@Slf4j
9public class SampleCreateFulfilmentWithSourcingProfile implements Rule {
10
11    static {
12        // register custom criteria
13        SourcingCriteriaTypeRegistry.register("fc.sourcing.criterion.customCriteria", CustomCriteria.class);
14        // register custom condition
15        SourcingConditionTypeRegistry.register("fc.sourcing.condition.customCondition", CustomCondition.class);
16    }
17
18    @Override
19    public void run(Context context) {
20        SourcingCriteriaTypeRegistry.getTypeNameToClassMap().forEach((key, value) -> log.info("registered: {}", key));
21        SourcingProfile sourcingProfile = loadSourcingProfile(context);
22        if (sourcingProfile.getSourcingStrategies() != null) {
23            SourcingContext sourcingContext = loadSourcingContext(context, SourcingUtils::getUnfulfilledItems);
24            SourcingUtils.SourcingPlan plan = findPlanBasedOnStrategies(context, sourcingContext, sourcingProfile,
25                    ImmutableList.of("ACTIVE", "AT_RISK"), null);
26            if (plan.getFulfilments() != null) {
27                fillFulfilmentType(sourcingContext, plan.getFulfilments());
28                createFulfilments(context, sourcingContext, plan.getFulfilments());
29            }
30        }
31    }
32}

Create Custom Sourcing Condition

Key Points

Prerequisites

Responsive Sourcing Framework Overview

Sourcing Utilities Overview

Sourcing Conditions Overview

Getting Started with Reference Sourcing Conditions

Steps

Preliminary Setup

Implement a Custom Sourcing Condition Function

Introduce Custom Sourcing Rules

Expose the Condition Schema via Setting

Verify the Condition Behavior

Related artifacts

fc.rubix.order.sourcing.conditions

Related content

Responsive Sourcing Framework Overview

Getting Started with Reference Sourcing Conditions

Create Custom Sourcing Criterion

Kirill Gaiduk

Contributors:

Building Blocks

By Type

Helpful Resources

Quick Links