--- sourceDocument: Zurich Finance and Supply Chain sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/source-to-pay-operations Release : - zurich ft:locale : - en-US ft:publication_title : - Zurich Finance and Supply Chain ft:clusterId : - stpop bundleId : - stpop workflow : - Employee --- # Sourcing request # Sourcing request {#ariaid-title1} * Release version: Zurich * * Updated March 12, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 6 minutes to read A sourcing request is created for when an item that a shopper, employee, or requester needs, must be sourced. This record is created when an active contractual price for the product that the shopper intends to purchase doesn't exist. This includes items in both the product catalog and off-catalog. A purchase line is created, which is then grouped into a sourcing request. Sourcing requests are grouped by product models. As a procurement specialist or sourcing manager: * To view all sourcing requests from the Source-to-Pay Workspace, navigate to AllProcurement Case ManagementSource-to-Pay Workspace, and select the List icon (![]()), followed by All team workSourcing Requests. * To view all sourcing requests from the Platform, navigate to Sourcing and Purchasing AutomationAll Work, and select All Sourcing Requests. * To view sourcing requests assigned to you from the Platform, navigate to Sourcing and Purchasing AutomationMy Work, and select My Sourcing Requests. {#sourcing-request__ul_kdw_gdt_flb} After the shopper places a request for a catalog or non-catalog item from ShoppingHub, the information that the shopper provides is mapped to the fields of a sourcing request as follows: {#sourcing-request__table_x3l_cdt_flb__entry__2} | Field | Description | |-|-| | Number | System-generated unique identifier of the sourcing request. | | Assigned to | User who is responsible for the purchase. Determined using purchasing assignment rules. For details, see [Create a purchasing assignment rule](https://www.servicenow.com/docs/6MuP9_chsztaQJ0WqpDmNg "Automatically assign a sourcing request, negotiation, or purchase requisition to a procurement specialist user or a task fulfiller’s group based on pre-defined conditions by using a purchasing assignment rule."). | | Business owner | User who owns the sourcing request. | | Submitted by | User who has shopped and submitted the purchase. | | Status | Status of the sourcing request. Note: This is a read-only field. | | Purchase | Related purchase, if any. | | Sourcing event | Represents the type of sourcing activity needed to negotiate with each supplier, and tracks the individual negotiations with each supplier. | | Short description | Brief description of the sourcing request. | | Summary Details || | Product category | Product category that is sourced through this sourcing request. | | Product model | Product model that is sourced through this sourcing request. | | Product name | Product that is requested for. | | Product type | Indicates if the type of the product is a good or service. | | Supplier responses close | Date by which the suppliers must submit their responses to the sourcing activity. | | Benchmark price | Price point from which all starting unit costs for all the purchase lines of this sourcing requests are derived. | | Request type | Type of request that the shopper, employee, or requester is asking for. The options are request for quote, request for information, request for proposal, and proof of concept. | | Sourcing request details | Details of the sourcing request. | [Table 1. Sourcing request fields] {#sourcing-request__table_x3l_cdt_flb} The following are the related lists of a sourcing request record: {#sourcing-request__table_svr_qws_flb__entry__2} | Related list | Description | |-|-| | Purchase Lines | Provides information of the individual lines under a sourcing request for the referenced supplier. The number of purchase lines for a sourcing request depends on the number of products or services with the same product model. For more details, see [Purchase lines](https://www.servicenow.com/docs/SUn6WIlxwj_9OdhV6SvnOg "Purchase lines provide information of the individual lines under a purchase requisition or a sourcing request for the referenced supplier."). | | Purchasing Tasks | Provides information of all purchasing tasks that are related to the sourcing request​. The tasks on the associated negotiation aren't displayed. For more details, see [Purchasing tasks and procurement cases](https://www.servicenow.com/docs/rlhO4Dv5NrTBGhtWIhIYOA "All automated purchasing tasks and procurement cases are created using flow designer from the Service Delivery Common (SDC) application. The flow designer uses the underlying task and case generation decision tables. Purchasing tasks and procurement cases are created based on the conditions defined in the decision tables."). | | Cases | Displays all the cases associated with this sourcing request. | | Purchasing SLAs | Displays the SLAs associated to purchasing tasks against the sourcing request, along with tasks associated to the underlying purchase requisition line. | | Negotiations | Represents the task of obtaining the pricing of or negotiating the terms for the product or service requested by the shopper. For more details, see [Negotiations](https://www.servicenow.com/docs/UOeZNecbnK6WdBoZ4RVeDg "A negotiation represents individual supplier negotiations and tracks the items and activities according to supplier. These activities involve obtaining the price for the products or services requested by the shopper, or negotiating the terms."). | | Draft Contracts | Displays all the draft contracts associated with this sourcing request. For more details, see [Contracts](https://www.servicenow.com/docs/O6s6oGoJKww8U8gs0eXbvw "A contract defines the terms and conditions along with pricing agreed for a product with the supplier​. An active contractual price determines if the pricing of a product or service is displayed on ShoppingHub."). | | Signed Contracts | Displays all the signed contracts associated with this sourcing request. | | Other Legal Documents | Displays all the other legal documents associated with this sourcing request. | | Contract Requests | Displays all the associated contract requests against this sourcing request. Note: This field is displayed only if you have the Source-to-Pay Operations with Contract Management Pro plugin (sn_spend_clm) installed. | | Approval Plans | Displays all the approval plans created against this sourcing request. | | Draft Emails | Associated email communication that is saved as drafts. | | Sent Emails | Associated email communication that has been sent. | [Table 2. Sourcing request related lists] {#sourcing-request__table_svr_qws_flb} ## Sourcing and negotiation workflow {#sourcing-request__section_bkg_31x_y1c} After a sourcing request is created, the procurement specialist can create a purchasing task of the subtype Ask a question if more details are needed from the shopper. The procurement specialist can decide if a negotiation for this purchase can be created or not. If time doesn't permit for a negotiation, the supplier can be contacted directly for pricing details. After the suppliers respond with their quotes, a purchasing task is systematically created requesting the shopper to select a supplier to award. This is a sourcing task of the subtype Select a supplier. For an awarded supplier, the Awarded column value of a purchase line is automatically set to Yes, and this creates an associated purchase requisition. A shopper can select Cancel to update the status of the sourcing request and its associated purchase lines to Closed Canceled. ## Sourcing request state flows {#sourcing-request__section_pb4_rvt_c1c} Let's consider a simple scenario where qualification is needed. If a price is entered on a purchase line (PRL), the PRL indicates that the price has been added or updated, and moves to the Pricing Obtained state, where it remains in that state. All the other PRLs without price and the sourcing request (SR) continue to remain in the Qualification Needed state. Once qualified, the SR and other PRLs that are in the Qualification Needed state move to the Qualified state, while the PRL that had price remain in the Pricing Obtained state. Manually creating a new PRL re-triggers the qualification flow. If pricing has been added to this PRL, the PRL remains in the Pricing Obtained state while qualification work is being done. The SR also remains in the Qualification Needed state, as needed. When sourcing events (NEs) and negotiations (NEGs) are considered in the sourcing flow, consider the following scenarios: * Qualification is needed, where NE is in the Planned state, and NEG, SR, and PRL are all in the Qualification Needed state:If a price is entered on a PRL, the PRL indicates that the price has been added or updated, and moves to the Pricing Obtained state, where it remains in that state. All the other PRLs without price and the SR continue to remain in the Qualification Needed state. Once qualified, the SR and other PRLs that are in the Qualification Needed state move to the Qualified state, while the PRL that had price remain in the Pricing Obtained state. * NEG is in progress, where NE is in WIP, and NEG, SR, and PRL are all in the Negotiation in Progress state:If a price is entered on a PRL when NEG is in progress, the PRL indicates that the price has been added or updated, and moves to the Pricing Obtained state, where it remains in that state. All the other PRLs without price and the NEG and SR remain in the Negotiation in Progress state, while the NE remains in WIP. * New SRs or suppliers are added after Start negotiating is selected on the NE, where NE is in WIP, and NEG, SR, and PRL are all in the Negotiation in Progress state: This triggers qualification cases to be evaluated on the affected PRLs and move the NEG to Qualification Needed. If qualification isn't needed, both the NEGs and the newly created PRLs remain in the Negotiation in Progress state. If qualification is needed, NEs remain in WIP even when new SRs or existing suppliers are added. Once qualification cases are complete, Individual NEGs automatically move from Qualified to Negotiation in Progress, without the need to re-select Start negotiating on the NE. The newly evaluated PRLs also move to Negotiation in Progress. However, at any point, if a price is entered on any of the newly created PRLs, the PRL indicates that the price has been added or updated, and moves to the Pricing Obtained state, where it remains in that state. {#sourcing-request__ul_jym_y1w_c1c} The default states that are available for a sourcing request are listed. * Pending Approval * Pending Review * Information Needed * Qualification Needed * Qualified * Pending Negotiation * Negotiation in Progress * Pending Resubmission * Awaiting Supplier Response * Awaiting Task Completion * Requires Decision * Closed Complete * Closed No Decision * Closed Canceled * Closed Rejected {#sourcing-request__ul_o34_5pz_bcc} For more information on NEGs and NEs, see [Negotiations](https://www.servicenow.com/docs/UOeZNecbnK6WdBoZ4RVeDg "A negotiation represents individual supplier negotiations and tracks the items and activities according to supplier. These activities involve obtaining the price for the products or services requested by the shopper, or negotiating the terms.") and [Sourcing events](https://www.servicenow.com/docs/_XDInknu9jH~CokOd0ilXQ "Sourcing events represent the type of sourcing activity needed to negotiate with each supplier, and track the individual negotiations with each supplier. They help sourcing managers manage multi-supplier and multi-product negotiations.") respectively. For information on how a supplier tiering assessment task influences SR states, see [Sourcing and Procurement Operations integration with Third-party Risk Management](https://www.servicenow.com/docs/VPoNXytWZaCFfXsZ_lKcPg "Leverage relevant supplier risk assessment capabilities by integrating Sourcing and Procurement Operations with Third-party Risk Management."). *[\>]: and then