Guide
E-procurement software: three categories sold with the same words.
Most disappointing procurement software purchases are category errors, not product errors. The tool worked; it just was not the kind of tool the problem needed.
Category guide
Start from the gap, not the category.
Ask what specifically fails today. Is there no process — requisitions agreed by email, no approval trail? Is there a process, but buyers cannot find contracted items because catalogs are missing or stale? Or is the process fine and the pain is entirely in the plumbing between suppliers and systems?
Those three gaps map to three different categories of product. Buying the wrong one is expensive not because the software is bad but because it will solve a problem you did not have while leaving yours untouched.
02Category map
The same chain, read by two different categories.
Suites and connectivity layers are sold with the same vocabulary because they touch the same chain. They cover different links of it.
- 01Your organization
A need becomes a requisition
Someone asks for something, in a form, with a budget line behind it.
A procurement suite covers
This is a suite’s home ground: forms, roles, budgets and policy.
A connectivity layer covers
Nothing. A layer does not want to own your requisition screen.
- 02Your organization
Approval and policy
Rules decide who has to see the request before it becomes an order.
A procurement suite covers
Rules engines, delegation, thresholds and audit — the reason suites are bought.
A connectivity layer covers
Only where a suite is absent for part of the spend, and only as an option.
- 03The catalog layer
Where the products come from
A requisition is only as good as the catalog data available to it.
A procurement suite covers
A catalog module exists, and it has to be loaded by someone.
A connectivity layer covers
This is the point of a layer: supplier data, normalized, kept current at source.
- 04The catalog layer
Connecting the suppliers themselves
Every supplier is a different technical and organizational situation.
A procurement suite covers
Usually priced as an integration project, per supplier, per format.
A connectivity layer covers
The long tail, met at each supplier’s real capability, on one enterprise integration.
- 05Your systems
The order and the record
The purchase order, the accounting and the master data.
A procurement suite covers
Suites integrate with the ERP; they rarely replace it.
A connectivity layer covers
Delivers to it, and claims no authority over it.
03Categories
What each category is actually good at.
Procurement suite
- Provides the process: sourcing, contracts, requisitions, approvals, invoicing
- Right when there is no process, or the process is fragmented across tools
- Substantial change programme; touches finance, IT and every buyer
- Still needs suppliers connected to it — that problem does not disappear
Marketplace
- Provides assortment and a transactional relationship
- Right for tail spend where you do not want to manage the supplier relationship
- Takes a position between you and the supplier
- Less suited where negotiated contracts and specific suppliers matter
Connectivity layer
- Provides the connection between suppliers and the systems you already run
- Right when the process exists but supplier coverage is the constraint
- Leaves the ERP and procurement platform in place
- Does not attempt to become the system of record
04Diagnosis
Five questions that identify your category in an afternoon.
- 01
What share of indirect spend can a buyer transact through a catalog today?
If it is low, coverage is the constraint — that is a connectivity problem, not a process problem.
- 02
When a buyer needs something, where do they go first?
If the answer is a supplier website or the phone, the contracted route is losing on convenience.
- 03
How long does connecting one new supplier take?
If the answer is measured in months, the cost per supplier will cap your coverage regardless of tooling.
- 04
Is there an approval trail for indirect spend?
If most of it is agreed by email, you have a process gap as well as a connectivity gap.
- 05
How old is the price data buyers see?
If nobody can answer, catalog freshness is not being managed — and that is measurable.
05Where Kelqio fits
Kelqio is the third category, deliberately.
We would rather be clear about what we are not than win an evaluation we are wrong for.
If you have no process at all
A suite may serve you better. Kelqio Approve covers a workflow gap, but it is not a source-to-pay programme.
If you want to outsource the supplier relationship
A marketplace fits that intent. Kelqio assumes you want to keep your suppliers and your contracts.
If your systems are fine and coverage is the problem
That is exactly the gap Kelqio is built for, and the one where a suite would be an expensive detour.
If you are mid-transformation
Connectivity is often the dependency that the target operating model quietly assumes. It can be solved before, during or after.
Common questions.
- Is Kelqio an e-procurement software?
- It belongs to the e-procurement field but not to the suite category. Kelqio is a connectivity layer between suppliers and the procurement systems you already run, with an optional lightweight approval workflow.
- Do we still need our procurement platform?
- Yes, if it is doing its job. Kelqio supplies it with connected supplier catalogs and structured carts rather than replacing it.
- Can Kelqio be a first procurement tool?
- It can, for organizations whose main gap is supplier connectivity and who need a light requisition and approval flow. It is not a substitute for a full source-to-pay programme.
Next step
Bring your supplier list. We’ll show you the flow.
A working session with our team, using your systems and your supplier mix — not a generic slide deck.
- 01
Where your suppliers sit today: connected, semi-connected, or not at all
- 02
How each channel would route through Kelqio into your ERP and procurement platform
- 03
What connecting the next twenty suppliers would actually involve
Enterprise integration product. No credit card, no self-serve trial — a conversation with someone who knows procurement systems.