Skip to content

Procurement connectivity platform

Connect every supplier to your procurement stack.

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.

Nordwerk IndustrieCATALOGFerralux SASWEBSITEVantage LaboEXCELMeridian ToolsAPIKELQIOONE STANDARDIZED FLOWERPMASTER DATA, ORDERSProcurement platformCATALOGS, CARTSBuyersONE BUYING EXPERIENCEApproval workflowREQUISITIONS
Illustrative architecture

Trusted by procurement teams in industry, healthcare and professional services

  • CapgeminiConsulting & technology services
  • AirbusAerospace
  • PwCAudit & advisory
  • Ambroise ParéHospital group
  • ThalesAerospace & defence
  • SodexoFood services & facilities
  • Saint-GobainConstruction materials
  • VINCIConstruction & concessions

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

Procurement wasn’t designed to look like this. One clean flow.

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.

Before KelqioAfter Kelqio

End to end

One supplier, one purchase, from their system to yours.

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.

  1. 01Supplier

    The supplier connects as it is

    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.

  2. 02DecisionKelqio

    One flow is made out of many

    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.

  3. 03Kelqio

    Buyers get one place to look

    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.

  4. 04Your side

    Your process runs unchanged

    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.

  5. 05Kelqio

    The connection stays visible

    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.

Conceptual flow. Named systems and protocols are published per integration, once verified.

05Core platform

Four capabilities. One connectivity layer.

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.

06Catalog workflow

One supplier catalog experience. Whatever is behind it.

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.

  1. 01Your existing systems

    Procurement system

    A buyer starts a requisition in the system they already use.

  2. 02Inside Kelqio

    Supplier catalog

    A catalog session opens with that buyer’s contracted assortment and pricing.

  3. 03Inside Kelqio

    Shopping

    The buyer searches and compares across suppliers in one consistent interface.

  4. 04Inside Kelqio

    Cart returned

    The cart is handed back as structured lines — references, quantities, prices.

  5. 05Your existing systems

    Procurement workflow

    Approval and the purchase order run in your existing process.

A conceptual PunchOut round trip. Specific protocol support is published only once verified.
Kelqio Catalog
Demo data
  1. Workspace
  2. Catalog
  3. Search
nitrile gloves size L

Nitrile glove, powder-free, size L

Ref NW-GN-4412-LNordwerk IndustrieLead time 2d
Contract priceIn stock

18,40

24,90

/ box of 100

Add

Nitrile glove, textured grip, size L

Ref VL-2209-LVantage LaboLead time 3d
Contract priceIn stock

21,05

26,00

/ box of 100

Add

Nitrile glove, chemical resistant, size L

Ref FX-NC-880-LFerralux SASLead time 6d
In stock

31,50

/ box of 100

Add
  • 01

    Search across suppliers, not one at a time

    One query returns contracted items from every connected supplier, with the assortment that applies to that buyer and that site.

  • 02

    Contract pricing where the buyer can see it

    Negotiated prices sit next to list prices at the moment of choice, instead of being discovered at invoice reconciliation.

  • 03

    The cart returns as structured lines

    References, quantities and prices come back to your procurement workflow as data, not as a PDF someone has to re-key.

  • 04

    Catalog updates propagate

    When a supplier changes a reference or a price, connected buyers see the change instead of ordering from last quarter’s file.

  • Kelqio Catalog in detail

07Supplier experience

Stop maintaining the same supplier data in five different places.

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.

Kelqio Supplier
Demo data
  1. Nordwerk Industrie
  2. Customers
  3. Groupe Vallis
ProductsCustomer catalogsOrdersConditionsActivity

Groupe Vallis — MRO 2026

Published
items in catalog
1 284
Last update
14/04/2026 08:31
Price list
VALLIS-MRO-26
Validity
01/01/2026 → 31/12/2026

Delivered to

  • Groupe Vallis — ERP
  • Groupe Vallis — Procurement
  • Kelqio Catalog

Update once — every connected buyer sees it.

Incoming orders

OrderSiteLinesValueStatus
PO-88412Lyon 0345 782,50New
PO-88396Nantes 011112 044,00Acknowledged
PO-88361Lyon 032918,20Shipped
PO-88307Metz 0273 260,75Invoiced
  • 01

    Publish once

    Products, references and pricing are maintained in one workspace and delivered to every connected customer environment.

  • 02

    Customer-specific catalogs

    Each customer sees their negotiated assortment and their conditions — not a public price list.

  • 03

    Orders arrive as orders

    Incoming orders land in a structured queue that can be acknowledged and tracked, rather than in a shared mailbox.

  • 04

    Visible activity

    Suppliers see which customers are buying what, so commercial conversations start from data.

  • Kelqio Supplier in detail

08Procurement workflow

Approval that matches your rules, not the tool’s rules.

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.

Kelqio Approve
Demo data
  1. Requisitions
  2. REQ-2026-04188
In approval

Q2 maintenance consumables

Requester
C. Moreau
Delivery site
Lyon — Site 03
Cost centre
CC-4402
Budget line
MRO / 2026-Q2
Cart
LinesQty
Nitrile glove, powder-free, L40736,00
Industrial degreaser 5 L121 428,00
Safety goggles, anti-fog25612,50
Absorbent pads, 40×50183 006,00
Total excl. tax5 782,50

Approval

Rule: > €5,000 requires site manager + procurement

  1. M. Lefèvre

    Site manager

    14 Apr, 09:12

  2. A. Brandt

    Procurement

    Pending

  3. ERP

    Purchase order

    Automatic

ApproveReject

On approval, one purchase order per supplier is sent to your ERP.

  • 01

    Requisitions from a real cart

    The requisition carries the same structured lines the buyer selected in the catalog.

  • 02

    Multi-level and multi-rule

    Route by amount, category, cost centre, site or supplier — and combine those rules.

  • 03

    Multi-site delivery

    One requisition can serve several delivery sites without being split by hand.

  • 04

    Spend stays visible

    Monitoring and reporting on committed spend, not just on invoices after the fact.

  • Kelqio Approve in detail

09Integration architecture

Connect suppliers without rebuilding your procurement stack.

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.

  1. A

    Supplier side

    Supplier systems, product data, B2B commerce sites and catalog files are connected through whichever method the supplier can actually support.

  2. B

    Kelqio

    Catalog data, carts and orders are normalized into one model, with the mapping, enrichment and validation that makes them usable downstream.

  3. C

    Enterprise side

    The standardized flow is delivered into your ERP, your procurement platform and — optionally — Kelqio Approve.

Kelqio Connect
Demo data
  1. Admin
  2. Connections
SupplierMethodScopeLast exchangeStatus
Nordwerk IndustrieAPICatalogPricingAvailabilityOrders00:02Connected
Ferralux SASCatalog fileCatalogPricing06:14Syncing
Vantage LaboSupplier workspaceCatalogPricingOrders00:47Connected
Meridian ToolsWeb catalog sessionCatalogAvailability00:11Connected
Kessler TechnikCatalog fileCatalog31:22Needs attention
Aumont ÉquipementSupplier workspaceCatalogOnboarding

Downstream systems

Where the standardized flow is delivered

  • ERPPurchase orders, supplier master data
  • Procurement platformCatalogs, carts
  • Kelqio ApproveRequisitions, approvals

Connection methods shown are illustrative. Supported protocols are published only once verified.

  • Integrate once

    Adding the tenth supplier should not cost what the first one did.

  • Your systems stay authoritative

    Kelqio moves and standardizes data. It does not try to become your system of record.

  • Suppliers are met where they are

    A supplier with no IT team should be able to connect without an IT project.

  • Nothing silently drifts

    Connection state, last exchange and failures are visible rather than discovered at month end.

  • How integration works

11Outcomes

What we instrument — and what we refuse to invent.

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.

  • 01

    Time to connect a new supplier

    Measured from onboarding start to first catalog available to buyers.

    Baseline to be set

  • 02

    Share of spend through connected catalogs

    Connected catalog spend over total addressable indirect spend.

    Baseline to be set

  • 03

    Manual order handling

    Orders entered or re-keyed by hand as a share of total order lines.

    Baseline to be set

  • 04

    Catalog data freshness

    Age of the price and assortment data buyers actually see at order time.

    Baseline to be set

  • 05

    Off-contract purchasing

    Order lines placed outside the contracted assortment or price.

    Baseline to be set

  • 06

    Requisition cycle time

    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

Built to pass a procurement security review.

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 compliance
  • Access control

    Role-based access separating buyers, approvers, administrators and supplier users, with per-customer data isolation.

  • Data protection

    Encryption in transit and at rest, with a documented data model describing exactly what is stored and why.

  • Auditability

    Catalog changes, order events and approval decisions are recorded so a decision can be reconstructed later.

  • Hosting and residency

    Hosting regions and data residency options.

    [TO BE CONFIRMED]

  • Certifications

    Formal certification status.

    [TO BE CONFIRMED]

  • Availability commitments

    Service level commitments and continuity plan.

    [TO BE CONFIRMED]

13Use cases

Three situations we were built for.

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.

  1. 01

    Multi-site industrial group

    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.

  2. 02

    Distributed retail or services network

    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.

  3. 03

    B2B supplier or distributor

    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 references

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

Book a demo

Enterprise integration product. No credit card, no self-serve trial — a conversation with someone who knows procurement systems.