| Class(Criterion Utilities) | Type(Sourcing Criteria Schema) | Description(UI) | Notes |
`LocationDistanceCriterion` | `fc.sourcing.criterion.locationDistance` | Prioritizes locations that are geographically closer to the delivery address | - Calculates raw distance (in km) between delivery address and Location
- The raw distance is captured as the Criterion's actual value in the Sourcing Audit
- Then normalized (closer = higher rating)
|
`LocationDistanceBandedCriterion` | `fc.sourcing.criterion.locationDistanceBanded` | Ranks locations by distance bands {{value}}, prioritizing bands that are closer | - Groups Locations into configurable distance “bands” (in km or miles)
- Scores based on which band they fall into (closer = higher rating)
|
`LocationDistanceExclusionCriterion` | `fc.sourcing.criterion.locationDistanceExclusion` | Excludes locations that are farther than {{value}}{{value}} | Excludes (-1) Locations beyond a specified maximum distance threshold (in km or miles) |
`LocationDailyCapacityCriterion` | `fc.sourcing.criterion.locationDailyCapacity` | Prioritizes locations with the highest daily fulfillment capacity | Rates Locations based on their `DAILY_MAX_ORDER_CAPACITY` attribute value (higher capacity = higher rating) |
`NetworkPriorityCriterion` | `fc.sourcing.criterion.networkPriority` | Prioritzes locations by the specified network ranking {{value}} | - Assigns scores by matching each Location to an ordered list of preferred Networks
- If a Location belongs to multiple Networks, it inherits the score of the highest-ranked Network it belongs to
Example:- Network priority value = [Network1, Network2]
- Scores:
- Location1 (Network1) → 1
- Location2 (Network2) → 0
- Location3 (Network1 and Network2) → 1
|
`InventoryAvailabilityCriterion` | `fc.sourcing.criterion.inventoryAvailability` | Prioritizes locations based on total units of inventory requested in the order that can be fulfilled | - Calculates a "raw" availability for each Location = total available Items / total requested Items (can be > 1 if there is surplus Inventory)
- All scores normalized to the 0-1 range: normalized = raw / max(raw)
- If total requested Items = 0, returns 1
Example:- Sourcing Request:
- Product1 (P1): 5
- Product2 (P2): 3
- Total requested Items = 8
- Scores:
- Location 1 (P1: 5, P2: 3) → raw = 8 / 8 = 1 → normalized = 0.625
- Location 2 (P1: 4, P2: 1) → raw = 5 / 8 = 0.625 → normalized = 0.39
- Location 3 (P1: 10, P2: 6) → raw = 16 / 8 = 2 → normalized = 1
Note:A Location with surplus Inventory that does not fulfill the entire Sourcing Request may still receive a higher score than a Location that fully satisfies the Request. However, the framework prioritizes the Fulfillment Plan with the fewest Fulfillments overall |
`InventoryAvailabilityBandedCriterion` | `fc.sourcing.criterion.inventoryAvailabilityBanded` | Ranks locations by fulfillment percentage bands {{value}}, prioritizing bands with higher availability | - Converts fulfillment percentage into configured “bands”
- Assigns corresponding scores
|
`InventoryAvailabilityExclusionCriterion` | `fc.sourcing.criterion.inventoryAvailabilityExclusion` | Excludes locations where inventory availability for a given order, is less than {{value}}% | Excludes (-1) Locations that do not meet the configured minimum fulfillment threshold (in %) |
`LocationTypeExclusionCriterion` | `fc.sourcing.criterion.locationTypeExclusion` | Excludes locations of type {{value}} | Excludes (-1) Locations whose type matches a configured value(s) (e.g., store vs. warehouse) |
`LocationNetworkExclusionCriterion` | `fc.sourcing.criterion.locationNetworkExclusion` | Excludes locations that are members of one of the following networks {{value}} | - Excludes (-1) Locations that belong to disallowed Networks
- If a Location belongs to multiple Networks, and any of them matches a disallowed Network from the list, that Location will be excluded
|
`RejectedLocationExclusionCriterion` | `fc.sourcing.criterion.rejectedLocationExclusion` | Excludes locations that previously rejected items | Must be added explicitly to each Sourcing Strategy that requires it. Not injected automatically as of Order Reference Module v2.2.0 |
`OrderValueCriterion` | `fc.sourcing.criterion.orderValue` | Prioritizes locations that fulfill a higher monetary portion of the order | - Calculates a score for each Location based on the monetary value of fulfillable Items
- For each Item: value = (paidPrice + taxPrice) * quantity
- filled = sum of monetary value that the Location can fulfill (capped at the requested quantity)
- total = sum of monetary value of all requested Items
- Score = filled / total (always in the 0–1 range)
- If total = 0, returns 0
Example:- Sourcing Request:
- Product1 (P1): 5 units @ $10 each
- Product2 (P2): 3 units @ $20 each
- Total value = (5 × $10) + (3 × $20) = $110
- Scores:
- Location 1 (P1: 5, P2: 3) → fulfills full $110 → 1
- Location 2 (P1: 4, P2: 1) → fulfills (4 × $10) + (1 × $20) = $60 → 0.545
- Location 3 (P1: 2, P2: 2) → fulfills (2 × $10) + (2 × $20) = $60 → 0.545
Note:Unlike `InventoryAvailabilityCriterion`, surplus Inventory does not increase the score above 1 because the calculation caps the fulfilled value at the requested quantity of each Item |