Guide
A supplier portal is a door. The question is what is behind it.
Portals are easy to justify and easy to under-specify. The ones that work are the ones where publishing into the portal actually changes what buyers see downstream.
Evaluation guide
What a supplier portal is for.
A supplier portal is a place where suppliers do work on your behalf: maintain their details, publish product data, see orders, respond to requests. Its promise is that supplier data stops being something your team retypes from emails.
That promise only holds if publishing in the portal has consequences elsewhere. A portal that stores a catalog nobody consumes has moved the filing cabinet, not fixed the process.
02Behind the door
What a portal has to do after someone logs in.
Access is the easy half. A portal earns its place only if each of these steps produces something on the buying side.
- 01Kelqio
Identify who is on the other side
A supplier user, acting for one supplier, on the relationships that supplier actually has.
The supplier’s half
Their own users, managed by them, without a ticket for every arrival and departure.
The buying organization’s half
A supplier sees the customers it is connected to and nothing beyond them.
- 02Supplier
Give them something to maintain
Products, conditions, availability and documents — with the same fields the buyer will consume.
The supplier’s half
One place to update rather than a mailbox per customer contact.
The buying organization’s half
Data maintained by the party that knows it is right, at its source.
- 03◇ DecisionKelqio
Validate before publication
Missing fields, inconsistent units and expired conditions are caught at submission.
The supplier’s half
A rejection with a reason and a line number, fixable in one pass.
The buying organization’s half
Errors stop at the door instead of arriving in a requisition.
↳ Fails a rule · Supplier
It stays in draft
The supplier keeps working on it. Nothing half-valid crosses to the buyers on the other side.
- 04Kelqio
Close the commercial loop
Orders, confirmations and order documents travel back through the same relationship.
The supplier’s half
Orders arrive as data instead of as a PDF attached to an email.
The buying organization’s half
Fewer disputes, because both sides are reading the same record.
- 05Kelqio
Make the state visible
When the last exchange happened, and what is currently published, for each relationship.
The supplier’s half
The supplier can see it is live without asking anyone.
The buying organization’s half
A portal nobody is using is visible as such, rather than assumed to be working.
03Evaluation
Six questions worth asking before choosing one.
Where does published data go?
If a supplier updates a price, which downstream systems see the change, and how quickly?
Is the catalog customer-specific?
A supplier serving twelve customers needs twelve assortments and price structures, not one public list.
Do conditions have validity dates?
Price lists without an explicit lifespan get applied long after they expired.
Can orders come back through it?
A portal that publishes catalogs but returns orders by email has only fixed half the loop.
What does it ask of a small supplier?
If the smallest suppliers cannot realistically use it, the portal will not reach the long tail.
Is connection state visible?
You should be able to see which suppliers are publishing, which have stalled, and when each last did.
04How Kelqio approaches it
A workspace, not a filing cabinet.
Kelqio Supplier is the supplier-facing half of a connectivity layer. What a supplier publishes there is what connected buyers see — that is the whole point of it existing.
- Nordwerk Industrie
- Customers
- Groupe Vallis
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
| 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 |
- 01
Publishing has downstream effect
A published catalog is delivered into the customer environments that supplier is connected to.
- 02
Per-customer assortments and conditions
Each customer relationship carries its own assortment, pricing and validity.
- 03
Orders return through the same channel
Structured orders arrive in the workspace instead of a shared mailbox.
- 04
Usable without an IT project
A supplier with no systems to connect can still participate fully.
Supplier portal questions.
- Is a supplier portal the same as a supplier catalog?
- No. The portal is where a supplier does the work; the catalog is one of the things they publish through it. A portal without catalog distribution behind it does not keep buyer-facing data current.
- Will suppliers actually use it?
- They use it when it reduces their total work rather than adding an eleventh format to maintain. That is why per-customer publishing from a single product set matters more than the portal interface itself.
- Do suppliers need their own systems to connect?
- No. Suppliers with capable systems can connect them; suppliers without can maintain everything in the workspace directly.
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.