The questions that come up before the first call.

Product and scope

Does Kelqio replace our ERP or our procurement platform?

No. Kelqio is a connectivity layer that sits between supplier systems and the procurement and ERP systems you already run. Catalogs, carts and orders pass through it and arrive in your existing tools in a standardized shape. If replacing your procurement suite is the goal, Kelqio is the wrong product.

We have no e-procurement platform, only an ERP. Does that work?

Yes — that is a common starting point. Kelqio can carry the catalog and cart experience itself and hand structured order lines to the ERP, which means buyers get a single place to search across suppliers without you first buying a procurement suite. The approval workflow module is optional and only relevant if your ERP does not already handle it.

What actually happens to a supplier once they are connected?

Their assortment and contracted pricing become reachable from inside your buying flow, and the cart a buyer builds comes back as structured lines — references, quantities, prices — rather than as an email or a spreadsheet. What changes for the supplier depends on the connection method: a catalog file means they publish updates, an API or PunchOut connection means their own system answers in real time.

Do our suppliers need an IT team to connect?

Not all of them. Connection methods exist at several levels of supplier maturity, from a supplier uploading and maintaining a catalog file in a workspace, through to a full system-to-system connection. A supplier without technical capability is connected at the level they can sustain, because a connection nobody maintains is worse than no connection.

Integration and technical

Which ERPs and procurement platforms do you integrate with?

The architecture is designed to interface with the major ERP and procurement systems, using the integration method that suits each environment. We publish a named system as supported only once we have verified it in a real deployment, so the integrations page lists methods and protocols rather than a logo wall. Ask about your specific system and you will get a direct answer, including if that answer is that it has not been done yet.

Which protocols are involved?

The exchange patterns are the standard ones in this field: PunchOut sessions for live supplier catalogs, cXML and OCI for the catalog and cart round trip, EDI for order and document exchange where a supplier already runs it, plus HTTP APIs and structured file import and export. Which of these applies depends on what each side of a given connection already speaks.

How long does an integration take?

This depends on the systems involved, the connection method and how clean the supplier data is, so any single number quoted on a website would be marketing rather than information. What we can do in a first session is walk through your actual supplier list and say which ones are straightforward, which need work, and where the work sits.

What happens when a supplier changes their catalog or their prices?

That depends on the connection method. A live connection reflects the change when the supplier system answers; a published catalog reflects it when the supplier publishes a new version. In both cases the point of routing catalogs through one layer is that a stale or failing supplier surfaces as a visible status rather than as a wrong price inside a cart.

Security, data and commercials

Where is the data hosted, and are you certified?

Hosting location and any certification status are published on the security page only once confirmed, and are currently marked as unconfirmed rather than omitted or implied. If your procurement process requires a certification we do not hold, we would rather you learn that from this page than from a security questionnaire three months in.

What data does Kelqio hold?

Supplier catalog and pricing data, the carts and orders that pass through, and the user accounts needed to operate that. Because Kelqio sits in the path of contracted pricing, it falls inside the scope of your own security and data protection requirements — which is why the security page documents the model rather than offering reassurance about it.

How is it priced?

Pricing is not published on this site. It depends on the number of connected suppliers and the connection methods involved, which vary widely between a company connecting twenty catalog suppliers and one connecting several hundred systems. We would rather quote against your actual supplier list than publish a number that would be wrong for most readers.

Is there a free trial?

No. Kelqio connects supplier systems to enterprise procurement environments, so a self-serve trial would show an empty shell — nothing meaningful appears until something real is connected. The first step is a working session against your own systems and supplier mix instead.

Continue reading

• Platform
• Integrations
• Security
• Contact