Sourcing Auditability Overview
Essential knowledge
Intended Audience:
Business User
Author:
Kirill Gaiduk
Changed on:
1 Sept 2026
Overview
Sourcing Auditability records why the Responsive Sourcing Framework made each sourcing decision. For each Sourcing Request, it records the inputs evaluated and the outcome reached, so you can review the decision later.It helps teams understand:- Which Strategies and Conditions were evaluated
- Which Locations were considered and how they scored against their Criteria
- The Location(s) selected, and why
- What Sourcing Auditability captures and why it matters
- What you can see and answer with it
- Where audit data appears, and where to find interface and API detail
Key points
- Prerequisites: You should have knowledge of the Responsive Sourcing Framework and How Sourcing Utilities work
- A Sourcing Audit is an immutable record of a single Sourcing Request, created at the end of each completed sourcing attempt
- Recording an audit never changes the sourcing outcome - if an audit cannot be recorded, the sourcing result still proceeds
- Audit records are shown only to users who hold the appropriate permissions
- Sourcing Auditability keeps the detailed Location scoring for the Sourcing Strategy that produced the Fulfillments
What Is Sourcing Auditability?
Responsive Sourcing lets you build advanced, dynamic sourcing logic. Before Sourcing Auditability, teams had limited visibility into why the Framework made a given decision, what influenced it, and how a change to the logic affected outcomes.Sourcing Auditability closes that gap. It makes sourcing decisions transparent, traceable, and easy to explain, in four parts:- Capture - the Framework collects the key inputs, evaluation results, and outcome of each Sourcing Request as it runs
- Retain - it keeps each Sourcing Request as an audit record
- Access - audit records are available through the Sourcing Auditability GraphQL API
- Review - audit records appear in the Fluent Order Management System (OMS) Web App, in a new Sourcing tab
Value Proposition
Sourcing Auditability addresses operational and governance needs that grow with sourcing complexity:- Explain any decision. See:
- Which Strategies were evaluated or skipped
- Which Conditions passed or failed
- Which Locations were considered
- How each Location scored against each Criterion
- The Location(s) selected, and why
- What each considered Location could not fulfill
- Reduce time to resolution. Operations and customer service teams can investigate an unexpected sourcing outcome directly, instead of piecing it together by hand
- Validate change. Product and engineering teams can confirm how a change to Sourcing Profiles, Strategies, Conditions, or Criteria affected real outcomes
- Support governance and analytics. Immutable, access-controlled records support compliance requirements and provide detailed data for downstream analytics
How It Works
The following diagram shows where Sourcing Auditability fits and how audit data reaches the people who review it:- The Responsive Sourcing Framework generates an audit as each Sourcing Request completes, from within the Sourcing Utilities
- Recording the audit never affects the sourcing outcome
- You review audits in the OMS Web App Sourcing tab, or retrieve them through the Sourcing Auditability GraphQL API
What Gets Captured
Each audit describes one Sourcing Request. It records:- The Sourcing Request and its overall outcome - Fully Sourced, Partially Sourced, or Not Sourced
- The Sourcing Profile and version used for the decision
- The items the request was sourcing
- Each Strategy considered, in priority order, and whether it was:
- Skipped - a Condition on the Strategy failed, so the Strategy did not run
- Evaluated - the Strategy's Conditions passed and it was evaluated
- Not Considered - an earlier Strategy already produced the required Fulfillments, so this Strategy was not reached
- For the Strategy that produced the Fulfillments - the Locations considered, how each scored against the Criteria, the Location(s) selected, and what each considered Location could not fulfill
Reviewing Audits in the OMS Web App
Audit data appears in a new Sourcing tab on the Order Detail screen of the Fluent OMS Web App. The tab is read-only and appears only for users with the required permissions.For each Sourcing Request, you can review the request summary, the items sourced, how each Strategy was evaluated, the Locations considered and how they scored, and the Location(s) selected. Location Comparison lets you compare the selected Location against another candidate the same Strategy evaluated.For the full walkthrough of the tab, see Sourcing Audits in Fluent OMS Web App.
Explanation Through an Example
Consider a Sourcing Request for an order with two items, using a Sourcing Profile that has two Primary Strategies:- The first Strategy - Skipped. The Strategy has a Condition requiring the delivery state to be one of a configured set. The order's delivery state is not in that set, so the Condition fails and the Strategy is skipped. No Location detail is recorded for it.
- The second Strategy - Evaluated. The Strategy's Conditions pass, so it is evaluated. The Framework scores the candidate Locations against the Strategy's Criteria and selects the best-ranked Location that can fulfill the items.
- Outcome. One Location fulfills both items, so the Sourcing Request is Fully Sourced. Because the second Strategy produced the Fulfillment, the audit records its full Location detail - the considered Locations, their Criteria scores, and what each could not fulfill.
- Review. In the Sourcing tab, an operations user opens the order, sees that the first Strategy was skipped because the delivery-state Condition failed, sees the second Strategy's ranked Locations and scores, and uses Location Comparison to confirm why the selected Location was chosen over the others.
