Procurement / AI use case
AI purchase requisitions: from request to review.
Turn an email or free-text request into a purchase requisition that procurement can review. NyxAI helps teams use generative AI to structure product details, quantity, cost centre and timing, ask for missing information and prepare the existing approval workflow.
No-obligation enquiry · “Purchase requisitions” is preselected in the form.
- 01
Business need
Purpose + quantity
Location + timing
Existing reference
- 02
Completion
Product match
Cost center
Responsible role
- 03
Purchase request
Structured draft
Focused questions
Routine approval
The business question
Procurement becomes the follow-up desk.
One message lacks a cost center; another omits the exact specification. The requester knows the purpose, purchasing knows the catalog, and the system defines the required fields. Questions accumulate between them.
A premature match moves the problem downstream. A similarly named item may be technically unsuitable or supplied in a different pack size. The request needs to preserve those distinctions.
From a message to a draft
Purchase requisition example: two monitors for new desks
A fictional worked example with fixed sample data. It illustrates a possible workflow, not live AI or a client project.
The original request
We need one 27-inch monitor for each of two new desks in Munich, product MON-27-QHD, by 15 November. Please charge cost centre IT-240.
In this example, MON-27-QHD is listed in the approved product catalogue. The approval rule names the IT team lead, followed by procurement.
The prepared requisition draft
- Product
- MON-27-QHD · 27-inch monitor
- Quantity and purpose
- 2 units · two new desks
- Cost centre
- IT-240
- Location
- Munich
- Required by
- 15 November (example date)
- Approval route
- IT team lead → procurement (example rule)
What if a required field is missing?
If the message omits the cost centre, the follow-up is: “Which cost centre should the two monitors be charged to?” The field stays open; a previous allocation is not reused without confirmation.
The draft connects information from the message with the confirmed product reference and approval rule. The responsible people then review and approve the budget and purchase order.
Your next step
Could your purchase requisition process be simpler?
Use the enquiry form to describe a typical request, your current system and the most common follow-up question. A brief, anonymised description is enough to start.
What we assess together
Together we assess missing information and data sources, and whether a better form, a fixed rule or an AI pilot makes sense. Any proposed pilot has a defined scope and measurable criteria: follow-up questions, handling time and correct drafts.
Discuss your requisition workflowNo-obligation enquiry · “Purchase requisitions” is preselected in the form.
From input to output
How the workflow can work.
The workflow can sit ahead of an existing procurement portal or use its draft capability. It needs only the data for the bounded request type. Prices and inventory carry timestamps; a write-enabled ERP connection is not required for the first test.
- Requirement with purpose, quantity, destination and requested date
- Approved product catalog and accessible inventory information
- Cost centers, purchasing rules and responsible approval roles
- 01
Clarify the need
Capture the purpose, quantity and timing in a structured form. Ask only for the information that is missing for this type of request.
- 02
Check existing records
Look up confirmed product references and available stock information. Similar products remain candidates until their suitability is established.
- 03
Prepare the requisition
The draft contains required fields, source references and the appropriate approval role. Unresolved details stay visible before procurement receives the case.
The key review boundary
Budget approval, technical suitability, supplier selection and ordering retain their existing owners. Displayed stock is not a reservation. A prepared requisition does not create a purchase commitment.
The resultA complete purchase requisition, or one clearly marked as incomplete, with a product reference, quantity, cost center and owner. Procurement starts with an actionable case instead of another search.
One workflow. Three situations.
What changes when …?
Choose a situation and follow the handover. An illustration using fixed sample data, not live AI or a client project.
The example requests two identical monitors with an existing product code, cost center and requested delivery date.
The reference matches the catalog; required fields and the approval role are identified.
A complete requisition draft enters routine budget and purchasing approval.
Ready for reviewStart focused. Compare fairly.
What the pilot should be measured against.
- Actionable first handoff
- Measure how many requests contain all professionally required information when first received.
- Questions per request
- Separate necessary clarification from avoidable follow-ups; not every question is a defect.
- Effort to approval readiness
- Include requester effort, procurement work and corrections rather than reducing entry time in isolation.
A practical initial scope
One purchasing category with known products, one site and its existing approval chain. No autonomous orders or automatic selection of technically different substitutes.
- Typical requirement messages and follow-ups
- Current required fields and approval rules
- Product examples including similarly named variants
Agree acceptance criteria first
Procurement confirms whether drafts are genuinely actionable. Missing required information, incorrect product matches and unnecessary questions are measured separately against the current process.
Discuss your requisition workflowThis use case will be selected in the enquiry form.Common questions
Does AI choose the supplier?
Not in this workflow. It prepares the requirement for procurement. Supplier comparison or award decisions would be separate steps with their own criteria and approvals.
Can existing inventory be considered?
Yes, where information is accessible and sufficiently current. Available, reserved and blocked stock must be distinguishable. Displaying inventory does not reserve it.
Is this worthwhile for a small catalog?
Effort and variation matter more than catalog size. A good form may be sufficient for a few fixed cases. The pilot tests whether varied descriptions and clarification work justify additional support.