Nitrile glove, powder-free, size L
18,40 €
24,90 €
/ box of 100
AddProcurement connectivity platform
Catalogs, carts and orders move through one standardized flow between suppliers, procurement teams and ERP systems.
Your ERP stays. Your procurement stack stays. The friction disappears.
Trusted by procurement teams in industry, healthcare and professional services
Named references are published only with written consent from each organisation. [TO BE CONFIRMED]
Connect what exists
No rip-and-replace of your ERP or procurement platform
One supplier onboarding path
The same route whether a supplier has an API or a spreadsheet
Catalog data stays current
Suppliers publish once instead of mailing files
Buyers see one experience
Whatever system sits behind each catalog
Before: every supplier is wired to every part of the procurement stack, over fifteen uncoordinated channels — Email, Excel, Telephone, Fax, Postal mail, SMS, WhatsApp, Supplier sites, Custom portals, ERP interfaces, EDI, PDF quotes, Paper catalogs, Re-keying, Chasing. After: suppliers publish once into Kelqio, which sends one structured flow to every destination.
Before Kelqio
Procurement wasn’t designed to look like this.
Every supplier arrives on its own channel. Every channel needs its own owner, its own file, its own follow-up. Nobody designed this — it accumulated.
After Kelqio
One clean flow.
Suppliers publish once. Kelqio standardizes catalogs, carts and orders. Your ERP and procurement platform receive the same structured flow from every supplier.
End to end
The diagram above shows the shape of the problem. This one shows the path a single purchase takes through it — with what each step asks of the supplier, and what it gives your side.
Catalog file, API, B2B site or the supplier workspace — whichever it can genuinely operate.
Supplier side
No migration, no new format to learn, no IT project imposed from outside.
Your side
Suppliers that were unreachable by integration become reachable anyway.
References, units, packaging, prices and availability are normalized into a single structure.
Supplier side
The supplier keeps its own references; the translation lives on the connection.
Your side
Your ERP mapping is written once, not once per supplier.
↳ Fails validation · Supplier
It goes back to the supplier
Named field by field. Your buyers never see the line that did not pass.
One search across every connected supplier, showing that entity’s contracted assortment and prices.
Supplier side
The supplier appears at the moment of the requisition, not on a website nobody visits.
Your side
Off-contract buying gets harder than on-contract buying, which is the only control that holds.
The cart returns as structured lines and follows your existing approval and ordering path.
Supplier side
The resulting order arrives as data the supplier can process directly.
Your side
No migration: your ERP and procurement platform keep their process and their authority.
Method, scope and last successful exchange are shown per supplier, continuously.
Supplier side
A supplier that stopped publishing is named, with a date.
Your side
Failures surface as status rather than as a wrong price in a cart.
05Core platform
Kelqio is not another procurement suite competing with your ERP. It is the layer that makes the systems you already own talk to the suppliers you already buy from.
Connect supplier systems and enterprise procurement environments.
One integration point instead of one project per supplier. Connect supplier systems on one side and your procurement and ERP environment on the other, then add suppliers without reopening the integration.
One supplier catalog experience. Whatever is behind it.
Buyers search across every connected supplier in one consistent interface, with the assortment and contract pricing that applies to them. Catalog data stays synchronized instead of arriving as an emailed file that was already out of date.
Let suppliers update once. Let every buyer see the right information.
A workspace where suppliers manage products, build customer-specific catalogs, receive and monitor orders, maintain commercial conditions and see what their connected customers are actually buying.
A lightweight workflow — only if you need one.
Optional requisition and approval workflow for organizations without one, or for the spend categories that never made it into the main system. Multi-level and multi-rule approval, spend monitoring, multi-site delivery and order tracking.
06Catalog workflow
A buyer should not need to know whether a supplier maintains a modern product API or a spreadsheet updated once a quarter. Kelqio normalizes both into the same catalog session.
A buyer starts a requisition in the system they already use.
A catalog session opens with that buyer’s contracted assortment and pricing.
The buyer searches and compares across suppliers in one consistent interface.
The cart is handed back as structured lines — references, quantities, prices.
Approval and the purchase order run in your existing process.
18,40 €
24,90 €
/ box of 100
Add21,05 €
26,00 €
/ box of 100
Add31,50 €
/ box of 100
AddOne query returns contracted items from every connected supplier, with the assortment that applies to that buyer and that site.
Negotiated prices sit next to list prices at the moment of choice, instead of being discovered at invoice reconciliation.
References, quantities and prices come back to your procurement workflow as data, not as a PDF someone has to re-key.
When a supplier changes a reference or a price, connected buyers see the change instead of ordering from last quarter’s file.
07Supplier experience
Supplier onboarding usually fails on effort, not intent. Kelqio Supplier gives suppliers one place to publish, and one place to see what their customers ordered.
Delivered to
Update once — every connected buyer sees it.
Incoming orders
| Order | Site | Lines | Value | Status |
|---|---|---|---|---|
| PO-88412 | Lyon 03 | 4 | 5 782,50 € | New |
| PO-88396 | Nantes 01 | 11 | 12 044,00 € | Acknowledged |
| PO-88361 | Lyon 03 | 2 | 918,20 € | Shipped |
| PO-88307 | Metz 02 | 7 | 3 260,75 € | Invoiced |
Products, references and pricing are maintained in one workspace and delivered to every connected customer environment.
Each customer sees their negotiated assortment and their conditions — not a public price list.
Incoming orders land in a structured queue that can be acknowledged and tracked, rather than in a shared mailbox.
Suppliers see which customers are buying what, so commercial conversations start from data.
08Procurement workflow
Many organizations run a capable ERP and still approve half their indirect spend over email. Kelqio Approve covers that gap without becoming a second system of record.
| Lines | Supplier | Qty | € |
|---|---|---|---|
| Nitrile glove, powder-free, L | Nordwerk Industrie | 40 | 736,00 |
| Industrial degreaser 5 L | Ferralux SAS | 12 | 1 428,00 |
| Safety goggles, anti-fog | Meridian Tools | 25 | 612,50 |
| Absorbent pads, 40×50 | Nordwerk Industrie | 18 | 3 006,00 |
| Total excl. tax | 5 782,50 | ||
Approval
Rule: > €5,000 requires site manager + procurement
M. Lefèvre
Site manager
14 Apr, 09:12
A. Brandt
Procurement
Pending
ERP
Purchase order
Automatic
On approval, one purchase order per supplier is sent to your ERP.
The requisition carries the same structured lines the buyer selected in the catalog.
Route by amount, category, cost centre, site or supplier — and combine those rules.
One requisition can serve several delivery sites without being split by hand.
Monitoring and reporting on committed spend, not just on invoices after the fact.
09Integration architecture
Kelqio sits between two worlds that change at different speeds. Suppliers move at their own pace; your ERP moves on a release calendar. The connectivity layer absorbs that difference.
Supplier systems, product data, B2B commerce sites and catalog files are connected through whichever method the supplier can actually support.
Catalog data, carts and orders are normalized into one model, with the mapping, enrichment and validation that makes them usable downstream.
The standardized flow is delivered into your ERP, your procurement platform and — optionally — Kelqio Approve.
| Supplier | Method | Scope | Last exchange | Status |
|---|---|---|---|---|
| Nordwerk Industrie | API | CatalogPricingAvailabilityOrders | 00:02 | Connected |
| Ferralux SAS | Catalog file | CatalogPricing | 06:14 | Syncing |
| Vantage Labo | Supplier workspace | CatalogPricingOrders | 00:47 | Connected |
| Meridian Tools | Web catalog session | CatalogAvailability | 00:11 | Connected |
| Kessler Technik | Catalog file | Catalog | 31:22 | Needs attention |
| Aumont Équipement | Supplier workspace | Catalog | — | Onboarding |
Downstream systems
Where the standardized flow is delivered
Connection methods shown are illustrative. Supported protocols are published only once verified.
Adding the tenth supplier should not cost what the first one did.
Kelqio moves and standardizes data. It does not try to become your system of record.
A supplier with no IT team should be able to connect without an IT project.
Connection state, last exchange and failures are visible rather than discovered at month end.
10Who this is for
Kelqio is built for organizations that already run an ERP or a procurement platform and are held back by the number of suppliers they cannot connect to it.
11Outcomes
We do not publish an ROI number we have not measured with you. These are the metrics Kelqio is designed to move, and how each one is captured. Baselines and targets are set during the evaluation.
Measured from onboarding start to first catalog available to buyers.
Baseline to be set
Connected catalog spend over total addressable indirect spend.
Baseline to be set
Orders entered or re-keyed by hand as a share of total order lines.
Baseline to be set
Age of the price and assortment data buyers actually see at order time.
Baseline to be set
Order lines placed outside the contracted assortment or price.
Baseline to be set
From requisition submitted to purchase order issued.
Baseline to be set
No benchmark figures are shown on this site until they come from a real deployment with the customer’s agreement. [TO BE CONFIRMED]
12Enterprise readiness
Kelqio sits in the path of supplier pricing and order data. That places it inside the scope of your security, data protection and continuity requirements — and we document it accordingly.
Security and complianceRole-based access separating buyers, approvers, administrators and supplier users, with per-customer data isolation.
Encryption in transit and at rest, with a documented data model describing exactly what is stored and why.
Catalog changes, order events and approval decisions are recorded so a decision can be reconstructed later.
Hosting regions and data residency options.
[TO BE CONFIRMED]
Formal certification status.
[TO BE CONFIRMED]
Service level commitments and continuity plan.
[TO BE CONFIRMED]
13Use cases
Named customer stories are published only once the customer agrees to be named. Until then, these are the patterns we see, written as scenarios rather than dressed up as references.
A capable ERP, a procurement platform, and roughly two hundred indirect suppliers — of which a few dozen were ever connected to either.
Suppliers connect through Kelqio rather than through individual interface projects, so catalog coverage grows without the IT backlog growing with it.
Watch: share of indirect spend flowing through connected catalogs.
Dozens of sites ordering locally by phone, email and supplier websites, with contract compliance discovered only at invoice reconciliation.
Site managers buy from one catalog carrying the negotiated assortment, and approval rules follow the amount and the site rather than the habit.
Watch: off-contract order lines and requisition cycle time.
A strong B2B commerce site that large customers cannot use, because those customers buy through their own procurement systems.
The supplier publishes customer-specific catalogs once and reaches those buyers inside the systems they are required to use.
Watch: order volume arriving structured instead of by email.
Illustrative scenarios. Not customer references. [TO BE CONFIRMED]
Customers and references14Resources
Plain explanations of the mechanisms behind supplier connectivity — written for the people who have to specify, approve and operate them.
Next step
A working session with our team, using your systems and your supplier mix — not a generic slide deck.
Where your suppliers sit today: connected, semi-connected, or not at all
How each channel would route through Kelqio into your ERP and procurement platform
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.