1. Supply Chain Analytics
  2. Features
  3. Purchase Demand
Feature · Purchase Demand

Purchase Demand

Raise purchase requests with lines, budget codes and required-by dates against eligible suppliers.

OverviewRequests Awaiting Approval
Supply Chain Analytics · Purchase Demand

Requests Awaiting Approval

Approval waits for the procurement approver

New
Record numberSubjectCounterpartyRequested amount USDRequired byRevision
PR-76506Submitted pr-745SPP-131032022 Oct550
PR-53853Submitted pr-677SPP-246050004 Oct570
PR-80702Submitted pr-474SPP-975080022 Oct660
PR-69728Submitted pr-441SPP-927631014 Oct490
PR-44026Submitted pr-918SPP-802035018 Oct320
6 of 6 records
Submitted pr-745Purchase requests · PR-76506
CounterpartySPP-1310
Requested amount USD320
Required by22 Oct
Revision550
Example screen with sample data

What you can do

Measure suppliers against what you actually asked for

Supplier performance only means something against a clear request. Each purchase request records a record number, subject, supplier, required-by date, budget code, the buyer who owns it and its version. Its lines carry the item description, requested quantity and unit price, and the requested amount is computed from those lines when the request is submitted.

A request moves from Draft to Submitted, then Approved or Rejected. Approved requests are issued to the supplier as Ordered and become Received once the goods or services are accepted. A request that will not go ahead is Cancelled.

How the work is organized

  • Lines carry the quantities. Requested quantity on each line is the baseline for fill rate later.
  • Eligible suppliers only. Submission checks that the supplier is active, and the eligibility note records what the supplier may supply.
  • Required-by dates matter. On-time performance is measured against the date on the request.

What to agree during setup

Load your supplier list with eligibility notes. Agree budget codes and how buyers choose them. Decide how required-by dates are set: the date needed at the dock, or the supplier’s promised date. Agree what evidence a request needs, such as a quote or a demand forecast.

Check the handoff on an actual case

A distribution center needs 2,400 cases of bottled water for a summer promotion. The Buyer raises a request to the regular beverage supplier with one line of 2,400 cases at $6.10, a required-by date of 1 June and the promotions budget code. The requested amount is computed as $14,640 on submission.

The approver approves it and the buyer issues it with an order reference. When the delivery arrives on 3 June with 2,250 cases, the receiving clerk records the accepted quantity and time. The request now shows a 94 percent line fill and a two-day late acceptance, which feed the supplier’s performance.

What your team sees

  • Draft Requests — Requests being prepared, with supplier, required-by date and budget code.
  • My Requests — The signed-in buyer’s requests and their status.
  • Request Board — Every request grouped by status.

The Operations Overview page shows approved commitment, accepted receipt value, pending reviews, failed operations and the exception queue.

Follow the work through

Review the implementation plan and the data model before importing open requests.

What it keeps track of

Data model
Purchase requests
Purchase demand records with lifecycle, owner, counterparty and approved commitment.
Purchase lines
Requested and accepted line detail for each purchase request.
Suppliers
Eligible supplier parties that receive purchase commitments.
Record attachments
Evidence files attached to a purchase request.

Who uses it

Permissions
Buyer
, Procurement Approver, Admin.
Buyer
S raise requests.
Approvers decide them.
Admin
Maintains suppliers.

Set up Supply Chain Analytics your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started