These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- SCM with Vendor Scorecard
- Features
- Demand and Suppliers
Demand and Suppliers
Prepare an owned purchase request for an eligible supplier with a clear required date and line scope.
OverviewRequest Review Queue×
SCM with Vendor Scorecard · Demand and Suppliers
New
Request Review Queue
Approval waits for the procurement reviewer
| Record number | Counterparty | Owner | Required by | Requested amount USD | Budget code | |
|---|---|---|---|---|---|---|
| PR-81821 | SPP-4008 | 20 Oct | 550 | BC-604 | ||
| PR-14243 | SPP-6281 | 19 Oct | 270 | BC-768 | ||
| PR-46744 | SPP-7881 | 11 Oct | 640 | BC-441 | ||
| PR-65873 | SPP-6192 | 03 Oct | 350 | BC-347 | ||
| PR-22645 | SPP-2605 | 08 Oct | 950 | BC-251 |
6 of 6 records
BC-604Purchase requests · PR-81821
SubmittedCounterpartySPP-4008
Required by20 Oct
Requested amount USD550
Revision60
What you can do
Establish what the organization is asking to buy
Procurement Specialist prepares the purchase request with its subject, required date and requested USD amount. The assigned owner gives the team someone to contact when a line changes or the supplier needs clarification. Purchase lines retain the item description, requested quantity and USD unit price under the same parent request.
The supplier relationship belongs to an operating organization. Admin maintains the supplier code, contact details and eligibility note, along with the active state. Procurement Specialist selects the intended supplier before submitting demand so the later commitment and scorecard evidence concern the correct party.
Submission freezes an eligible draft revision for review. The action checks the caller’s expected revision and retains an operation receipt. This gives Procurement Reviewer a stable commercial scope to decide, while a request based on an older draft cannot silently replace a newer version of the demand.
How the work is organized
- Supplier context. Admin maintains the eligible supplier and organization records. Procurement Specialist checks the code and eligibility note rather than choosing a party by a familiar name alone.
- Owned demand. The request identifies its owner and required date. Lines explain the requested items and quantities, while the budget code gives the reviewer the recorded spending context.
- Controlled submission. Procurement Specialist submits the current draft through the guarded action. The submitted revision and its receipt remain available for independent review and later investigation.
What to agree during setup
Agree how supplier codes distinguish similarly named businesses and how eligibility information is maintained. Name the person responsible for keeping organization membership and supplier active states current. A supplier used on an older order still needs to be eligible for the new commitment.
Define what each line quantity represents and how the team records that meaning in the item description and supporting evidence. Agree the requested-amount convention and the budget-code vocabulary used by the organization. The reviewer should be able to compare the requested scope with the supporting quotation without inferring a unit or commercial basis from an unexplained number.
Check the handoff on an actual case
Prepare a hypothetical request for a batch of replacement components. Procurement Specialist selects the eligible supplier, enters the required date and records the item quantities. Attach the supplier quotation with the appropriate visibility, then submit the current revision for review.
Before submission, retain an older request and change a line in the rehearsal. The old request must not freeze the revised demand or move it forward. Inspect the recorded result so the preparer can distinguish a rejected command from a successful submission. Also try a supplier from another organization and confirm that the authorized scope remains intact.
Procurement Reviewer should receive the exact submitted request with its supplier, lines and evidence. The handoff is ready when the reviewer can explain what is being requested without searching a separate conversation for the intended supplier or quantity basis.
What your team sees
- Draft Requests — Demand being prepared with supplier, required date and current revision.
- My Requests — Requests assigned to the signed-in procurement owner.
- Active Suppliers — Eligible supplier details within the authorized organization scope.
Follow the work through
Continue with request to supplier commitment and agree the pilot scope during implementation.
What it keeps track of
Data model- Purchase requests
- Demand records carrying requested amount, lifecycle status and supplier counterparty.
- Purchase lines
- Line items under a purchase request with requested and accepted quantities.
- Suppliers
- Approved supplier parties eligible for purchase commitments.
- Organizations
- Operating organizations that own procurement records and supplier relationships.
- Team members
- Authenticated platform users mapped to an organization with a business role.
- Users
- Users
- Record attachments
- Evidence files attached to a purchase request with visibility scope.
- Operation receipts
- Idempotent receipts for guarded operations and their downstream effects.
Who uses it
Permissions- Procurement Specialist
- Prepares and submits demand.
- Admin
- Maintains suppliers and memberships.
- Procurement Reviewer
- Receives the submitted scope, and Auditor reads authorized evidence.
Set up SCM with Vendor Scorecard your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.