Aestiva Wiki
Back to Search >

Purchase Request Software

A Purchase Request, also known as a requisition (Req), is a document used internally in an organization to request the purchase of goods and services.

Generally speaking their are two kinds of Purchase requests (PRs), single and multi-supplier requests. Single supplier requests assume the request of goods and services are for a subsequent purchase from a single supplier whereas mutli-supplier requests are designed for subsequent purchases from multiple suppliers.

Purchase Requests can be simple. In these cases only essential information is placed on the PR. And they can be more complex, requiring the user fill out purchase order coding information, project management tracking information, and other kinds of data on the Purchase Request itself.

The Purchase Request is part of a purchasing process. On-line purchase requests, upon approval, are typically used to create Purchase Orders and, in some cases, they are used to create request for quotations also known as Sourcing RFQs.

In many government and large corporations, after the approval of a Purchase Request, information is manually typed into a separate government or corporate purchasing system. This is because, frankly speaking, integration with the other system can be impractical in large corporations where resource scarcity is commonplace.

In organizations with centralized purchasing departments (buyer groups), multi-supplier requests are set up to collect requests. The buyers use create POs and RFQs from those requests. The best systems provide easy-to-use tools to move lines from PRs to POs and from PRs to RFQs.

Example Usage

"I agree. Let's fill out the Aestiva Purchase Request now so purchasing can combine it with their other requests tomorrow."

See Also

Purchase Request Software, Aestiva Purchase Order, Requisition, Purchase Order Process, Purchase Order Workflow Software

Purchasing Note

The best purchase order systems, like those from Aestiva, can easily create POs and RFQs in both a one-to-many and many-to-one manner. This means POs and RFQs can be built from items selected from multiple PRs and, alternatively, the buyer can easily create many POs and RFQs from a single PR.