Integrations
Two sides, connected differently on purpose.
Supplier systems and enterprise systems fail in different ways and change at different speeds. Kelqio connects each side with the method that suits it, and absorbs the difference in between.
Named protocol and vendor support published only once verified
01Supplier side
Suppliers are met at their real capability level.
The single biggest reason supplier connectivity programmes stall is that they assume a capability the supplier does not have. These are the routes in.
Supplier API
For suppliers with a maintained product or commerce API, connected directly so catalog and availability stay current.
Catalog file exchange
For suppliers who can produce a structured export on a schedule, mapped once and validated on each delivery.
Web catalog session
For suppliers whose own catalog experience is richer than any export they could produce.
Kelqio Supplier workspace
For suppliers with nothing to integrate. They maintain products, catalogs and conditions directly and still reach connected buyers.
02How a connection is made
What each side has to provide for a connection to exist.
The two halves are connected differently on purpose, so it is worth reading the sequence as two lists of obligations rather than one diagram.
- 01Supplier side
Establish what the supplier can actually operate
Not what it says on a capability questionnaire — what it can maintain every month.
Supplier side
An honest answer about files, APIs, or nothing at all. All three are workable.
Enterprise side
A supplier list, ranked by spend or by manual handling rather than by technical maturity.
- 02Supplier side
Agree the method and the access
Catalog file, supplier API, hosted assortment or the supplier workspace, plus the credentials that go with it.
Supplier side
One contact who owns the data, and access for their own users.
Enterprise side
One integration to Kelqio, specified once and reused by every later supplier.
- 03◇ DecisionKelqio
Exchange, validate, normalize
The first real exchange is checked field by field before anything is published downstream.
Supplier side
Rejections come back with a reason, so the supplier can fix them without a meeting.
Enterprise side
Your systems never see the first draft of a supplier’s data.
↳ Fails validation · Supplier side
Held, with the reason
The supplier is told what to fix. Nothing partial is delivered into your systems in the meantime.
- 04Enterprise side
Deliver into your systems
Catalogs, carts and orders are exchanged with the ERP and the procurement platform.
Supplier side
Orders return on the same connection the supplier already publishes on.
Enterprise side
Your process, your users and your master data authority are unchanged.
- 05Kelqio
Publish the state, not the promise
Method, scope and last successful exchange stay visible for every connection.
Supplier side
A supplier can see whether its data is live without asking your team.
Enterprise side
A connection that has stopped is visible as stopped, by name and by date.
03Enterprise side
Your side is integrated once.
This is the half that must stay stable while suppliers come and go.
ERP connectors
Standardized delivery of catalog, order and supplier data into the ERP in the shape it expects.
Procurement platform integration
Catalog sessions and structured carts delivered into the platform your buyers already use.
API access
Direct programmatic access for the parts of your landscape that need to read or write themselves.
Kelqio Approve
Optional delivery into the built-in requisition and approval workflow where you do not have one.
04Operations
Every connection has a visible state.
An integration nobody can inspect is an integration nobody trusts. Method, scope, last exchange and onboarding progress are part of the product surface.
- Admin
- Connections
| 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
- ERPPurchase orders, supplier master data
- Procurement platformCatalogs, carts
- Kelqio ApproveRequisitions, approvals
Connection methods shown are illustrative. Supported protocols are published only once verified.
- 01
Method and scope per supplier
Different suppliers connected differently is normal; not knowing which is which is not.
- 02
Last successful exchange
Surfaced per supplier so a stalled feed is caught before a buyer notices.
- 03
Onboarding pipeline
Suppliers being connected appear alongside those already live.
- 04
Downstream delivery
Where the standardized flow lands, so change impact is knowable.
05Our rule
Why you will not find a logo wall of supported systems here.
In procurement software, a named protocol or a vendor logo on an integrations page is read as a commitment. Teams plan around it, and discovering later that support was aspirational costs months.
So we publish named support for a specific standard, protocol or vendor product only once it is verified and we can demonstrate it. Where this site shows a to-be-confirmed marker, it means exactly that.
What we will say generally: Kelqio is designed to connect through APIs, ERP connectors and procurement platform integrations, and to accept supplier catalog data through several methods so that suppliers without an IT team can participate. For the confirmed list as it stands today, ask us — the answer will be specific.
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.