Goods and services
Separate line structures and RFQ options collect the commercial detail appropriate to each request, including budgeted GL validation where required.
← Client work · Mining & resources
One procurement front door for very different requests.
The Metro Mining workspace organises goods, services, IT, recurring, warehouse inventory, projects and work orders while preserving the different data and approval paths each request needs.
Power AppsApproval workflowsProcurement dashboardDev · UAT · Production
PROCUREMENT DASHBOARDRequests requiring action
Illustrative data onlyTriageQuote sourcingApprovalERP handover
REQUEST TYPEWarehouse goodsLine details and stock context
SUPPLIER CONTEXTQuote reviewSupplier and quote actions
APPROVAL CONTEXTProject + GLAccount-code and work-order detail
NEXT STEPProcurement reviewStatus-based queue ownership
Requestor→Approval chain→Procurement→Handover
Seven pathsGoods, services, IT, recurring, warehouse, projects and work orders.
Shared queueProcurement sees status and missing information in one workspace.
Reference dataSuppliers, currencies, account codes and approver limits stay governed.
Release-awareFeedback is tracked against specific screens and states.
Request design
The form changes with the thing being purchased.
The strength of the app is not one universal form. It is a common entry point with different paths where the business rules genuinely differ.
IT and recurring
Specialist and repeat-purchase requests have their own context instead of forcing unrelated fields into every procurement form.
Warehouse inventory
New-inventory and min/max-stock paths handle stock review, justification and approval as a distinct operational decision.
Project and work order
Project, account-code, work-order, supplier and currency reference tables support governed selection and downstream handover.
Approval context
Approval chains, approver limits and request context travel with the requisition before procurement action is authorised.
Procurement review
Quote actions, inventory decisions, request edits and ERP/PO handover are grouped around workflow status.
The procurement desk view
From triage to handover, the next action is visible.
Each stage answers a different question: is the request complete, does it need quotes, who can approve it and what must move into the next system?
Triage the request
Dashboard queues expose request type, status and missing information before procurement commits to the next action.
Source and compare
Quote screens and supplier context stay linked to the requisition and its individual lines.
Route and hand over
Approval chains and limits govern progression before purchase-order or ERP handover.
Illustrative interface: the hero visual contains no live request, employee, supplier or financial data.
Delivery detail
Feedback was treated as workflow evidence.
The project records specific edge cases rather than relying on a generic “governance” claim.
| Area reviewed | Observed concern | Why it matters |
|---|---|---|
| New Goods submission | Draft status, attachments, totals and final submit behaviour needed explicit validation. | A completed-looking screen is not the same as a persisted requisition. |
| Edit rollback | Exit Edit needed to restore snapshots and avoid unintended side effects. | Requestors must be able to cancel changes without silently rewriting a request. |
| Dashboard status | Triage and stock-review labels needed to agree across actions and queues. | Status is the handover contract between requestors and procurement. |
| Quote popup | Save and close behaviour needed a clear escape path. | Users should not feel trapped while adding quote or GL information. |
Release boundary: the phase-two tracker documents Dev, UAT and Production as separate stages. This public page describes the workflow and review evidence without claiming a measured procurement saving.
Talk through procurement complexity
Need one front door without flattening the rules?
Tell us which request types, approval decisions and handovers need to coexist. We can help shape a practical workflow around your existing Microsoft estate.
Discuss a similar project
Share the request paths and handover points that matter.