Product · Intake & Orchestration

Procurement intake software for global enterprises

Every request enters one front door. Your rules decide where it goes next.

Procurement intake software captures a purchasing need once, routes it through the approvals you configure, and lets routine catalogue buys reach the supplier without a buyer re-keying them.

Intake · one entry point Illustrative
Agent actionPlain language becomes a structured, classified request
Request REQ-88214 · what was captured Illustrative
Category
Drives
Entity
Plant 2
Value band
Band B
Required by
Week 34
Still to confirmOnly the two fields this category needs and the request did not stateAsked
Agent actionThe system asks only for what it still has to know
Matched against what you already buy Illustrative
Catalogue lineDrives · Plant 2 · contracted price appliedCatalogue
Punchout lineReturned as a structured line, not a screenshot of a cartPunchout
Service lineScope and milestone captured — routed for a service entry sheet laterService
Nothing matchedGoes to sourcing rather than being guessed atRoute
Rule appliedEach line tagged with its category, plant and date
Before the requester submits Illustrative
GL code
6410 · maintenance
Cost centre
B4-MNT-02
Fulfilment route
Contracted purchase
Approval chain
2 steps · shown in full
SubmitThe requester takes this action themselves — the front door never does it for themHuman
Human decisionNothing is hidden until after it has been committed
REQ-88214 · where it is now Illustrative
Plant maintenance leadApproved · Tuesday 09:14Approved
Category managerSitting with them for 2 daysWith them
FinanceNot reached yet — steps run in the order you configuredQueued
Requester viewCan see the step it is on, and send a nudgeVisible
RecordedNo one has to ask procurement where a request has got to

Every request starts in the same place, whatever is being bought.

Same request. Two different weeks.

Too much buying starts with an email. Too much time goes into chasing it.

The problem
With Proconomy
The problemA request arrives as an email, and someone decides what it is
With ProconomyIt arrives as a structured requisition, classified against your own category tree
The problemThe specification, quantity or date is missing, and a buyer chases it
With ProconomyThe category knows what it needs, and the requester is asked once before it moves
The problemApproval sits in an inbox until somebody follows up
With ProconomyThe configured chain routes it, and escalates a step left unactioned past its limit
The problemA buyer re-keys the approved request into a purchase order
With ProconomyEligible catalogue, punchout and MRO-stock lines raise the PO and reach the supplier on their own
The problem“Who approved this?” means searching email
With ProconomyEvery approval step is recorded in the workflow as it happens

How it works

From purchasing need to an approved next step.

Six stages. The one in the middle waits for a named person, and that is not a setting.

  1. 01 Human

    Raise a request

    A guided form, or conversational intake where your organisation has it switched on. Either way the requester describes what they need in their own terms, and what arrives is a structured requisition classified against your own category tree.

  2. 02 Rule

    Validate

    The request is checked server-side before it is allowed to exist as a record, independently of whatever the browser sent.

  3. 03 Human

    Review and submit

    The requester reviews what was captured and takes the submit action. The front door never submits on their behalf.

  4. 04 Rule

    Route

    The configured approval chain runs — in sequence or in parallel waves, with any-one-of-a-group approval where you want it, escalating a step that goes unactioned past its limit.

  5. 05 Human

    Decide

    Required approvers approve or reject. A wave only completes when a real person signals it; there is no configuration that lets a step auto-complete.

  6. 06 System

    Fulfil

    Eligible catalogue, punchout and MRO-stock lines raise a purchase order and dispatch it to the supplier. Anything needing supplier judgement goes to a buyer.

Core capabilities

What procurement intake software has to get right.

Guided request forms

Capture purchasing needs as structured, trackable requisitions against your own category tree rather than as free text in an inbox.

Conversational intake

A requester describes the need in plain language and the system asks only for what it still has to know. They review what was captured before submitting. A guided form captures the same request against the same category rules for anyone who would rather use one.

Configurable approval workflows

Set who approves and in what order, run steps in parallel waves, allow any one member of a group to approve, and escalate a step that goes unactioned past its limit.

Eligible catalogue PO automation

Approved catalogue, punchout and MRO-stock lines raise a purchase order and reach the supplier without a buyer re-keying anything.

One workflow engine, three surfaces

The same approval engine runs requisitions, contract approvals and auction go-live gates, so your administrators learn one builder rather than three.

Features

Procurement intake software that holds its own rules.

Five groups of features, and not one of them depends on someone remembering the policy.

Approvals that cannot be skipped

Every configured step waits for a real person, and no setting changes that.

  • A request is validated on the server before it is allowed to exist as a record
  • A wave completes only when a named person approves or rejects it
  • There is no configuration that lets an approval step silently auto-complete
  • Conversational intake drafts; the requester reviews and submits, in that order
  • An AI-drafted RFQ, RFP or RFI stays a draft until a person publishes it

Governed AI

AI assists. People approve.

  • AI helps capture request detail where conversational intake is enabled.
  • Conversational intake is one way in, not the only one. A guided form captures the same request against the same rules.
  • The requester reviews the draft and takes the submit action themselves.
  • Required approval steps wait for a person to approve or reject.
  • Approval actions are recorded in the workflow as signals, not as side conversations.

What it will not do

The limits are the product.

A procurement platform that will not tell you where it stops is not one you can put in front of an auditor.

It never skips a configured approval step

Every wave requires a real human action to advance. There is no setting that lets one silently auto-complete.

The front door never submits for anyone

Conversational intake drafts. The requester reviews and submits. That order does not change.

A drafted RFx stays a draft

Where a request needs sourcing, an AI-drafted RFQ, RFP or RFI is never published automatically. A person takes that action.

Automatic PO creation is scope-limited

Pre-vetted catalogue, punchout and MRO-stock lines only. A line that needs supplier judgement is left for a buyer, by design.

Two purchasing needs. Two clear paths.

1

Repeat catalogue MRO purchase

A plant team requests an approved catalogue item. The request runs the approval chain, then the purchase order is raised and dispatched to the supplier without a buyer touching it. One entry point instead of four systems, and nothing re-keyed between them.

2

Non-catalogue component request

An engineering team records its requirements and submits for approval. A buyer then handles sourcing and supplier selection — starting from a structured, approved request with the specification already attached, rather than from an email thread.

Bring us a real intake problem.

Give us one category where requests arrive badly today. We will run it against your policy and show you exactly where a person still decides.

Request a demonstration

Platform fit

Keep your ERP. Bring structure to the requests in front of it.

Proconomy owns the request-to-PO process

Capturing the need, routing approval and raising the purchase order against your policy.

Connected ERP data supports the decisions

Purchase order, receipt and invoice data flows in from your connected systems to support sourcing and matching.

Inventory stays where it is

On-hand quantities, availability and replenishment remain your ERP’s job.

The approved order reaches your supplier

An approved order becomes a PDF and is emailed straight to the supplier. On by default for every organisation, with nobody re-keying or re-sending it by hand.

Security, compliance and recognition

Checked by auditors. Judged by the industry.

Where each compliance programme stands, and what the procurement industry has given us so far.

Security and compliance

Awards

Five, presented on stage at three industry events.

  • Autonomous Procurement Platform of the Year
  • Procurement Technology Innovation Award
  • Unified Procurement and Supplier Management Platform
  • Procurement Startup of the Year
  • AI in Procurement or Supply Chain Award — Solution Provider

See the events and the trophies

Before you book anything. Answered honestly.

What is procurement intake software?

Procurement intake software gives every purchase request a single entry point, whatever form the need arrives in. Instead of requests reaching procurement as emails, spreadsheets and corridor conversations, one front door captures the need, works out what is being bought, collects the information that category requires, and routes the request into the buying process your policy specifies — so the same request gets the same treatment regardless of who received it.

What happens if the AI gets something wrong?

Nothing it drafts is final. The AI turns what a requester wrote into a structured draft — the category, the fields, the route it should take — and the requester reviews that draft and takes the submit action themselves. A mistake therefore shows up as a draft to correct, never as a submitted or approved transaction, and the approval chain sits downstream of that review regardless. Conversational intake is also one entry point among several: a guided form captures the same request against the same category rules.

Does this replace our ERP?

No. Intake & Orchestration owns the request-to-PO process — capturing the need, routing approval, generating the purchase order and getting it to the supplier. It is not an inventory or stock system: on-hand quantities, availability and replenishment stay in your ERP by design. Data moves from connected ERPs into Proconomy to support sourcing and matching decisions; newly created POs still hand off manually or by file.

Can someone approve their own request?

Your approval chain decides that, and the chain is configured to your organisation’s policy rather than fixed by us. Steps can run in sequence or as parallel waves, any one member of a named group can be allowed to clear a step, and the route can differ by category, value, plant or entity. A configured chain always has to be actioned before anything is approved. We set that chain up with you during implementation — so if your policy requires that a requester is never an approver on their own request, tell us and we will configure the routing that way.

Can we customise the approval chain per department or spend threshold?

Yes. The approval workflow is a configurable graph, not hardcoded logic. An administrator builds the chain visually: who approves, in what order or in parallel, and what happens if someone does not act in time. The same engine underneath runs contract approvals and auction go-live gates, so chains behave consistently across the platform.

What do we get automatically once something is approved?

For items fulfilled from your catalogue, punchout channels or MRO stock, the purchase order is generated and sent to the supplier automatically — no buyer re-keys an approved request into a PO. Items that require supplier judgement or are not catalogue-sourced are deliberately left for a buyer rather than auto-generated.

Is there an audit trail of who approved what?

Yes for the approval chain itself: every step action is a recorded signal in the workflow rather than a side conversation. We do not characterise every adjacent action across the platform as equally audited today — that varies by area, so ask us about the specific transaction type you care about before relying on it for a compliance claim.

Bring one workflow. We will run it.

No slides. You will see where it stops for a person.

Someone from client success replies, not a sales sequence. If we are not a fit we will say so on the first call.