GIPR Exchange · In build

A supplier claim should arrive with the document behind it.

Everything on this page is future tense.

GIPR Exchange is the governed network for verifiable supply. It is designed and it is being built. It has no users, and we are not going to describe it as though it does. This page exists so you can see where we are going and tell us if we have it wrong.

01 — The problem

Supplier data is a stack of assertions nobody checked.

A supplier tells you it carries the insurance, holds the certification, qualifies as a small business, and meets the standard. Each of those is a field in your vendor master. Almost none of them arrived with the document that proves it, and almost none of them are checked again after onboarding day.

So the certificate expires and nothing happens. The diversity classification lapses and the report still counts it. The insurance certificate on file was valid in 2023. The data did not become wrong — it became stale, silently, which is worse, because a stale field looks exactly like a current one.

02 — What we will say now

The same discipline as Core, applied to supplier data.

A claim is an assertion with a source, and an assertion without its evidence is not a fact. That is what GIPR Core does with your transactions, and it is what Exchange is being built to do with what your suppliers tell you.

It works with the supplier system you already have. Exchange is not a replacement for your supplier-management or vendor-master platform, and it does not ask a supplier to abandon the portal it already uses.

We are not publishing the design. Not because it is unsettled — it is specified and being built — but because a detailed roadmap for an unreleased product is a gift to anyone who would rather arrive there first. We will describe Exchange feature by feature when there is something running to describe, and design partners who sign an NDA can see it now.

03 — Status

Designed. Being built. No users.

We publish product pages for things that do not exist yet because the alternative — describing a roadmap in the present tense — is how a company loses the benefit of the doubt on everything else it says.

○ IN BUILD

What that means here

There is design work and there is code in progress. There is nothing you can log into, nothing running for a supplier or a buyer, and no client using any part of it. Nothing on this page is running for anyone today.

● WHAT IS REAL NOW

Two products in the meantime

GIPR Connect is in production with paying clients. GIPR Core is in beta. Both have their own pages, and our capability register states row by row what runs and what does not.

Next — Shape it

If you run supplier data, tell us where this is wrong.

The useful conversations about an unbuilt product happen before it is built. If you manage a vendor master, a supplier portal or a catalog programme, we would rather hear your objection now than ship past it.

Tell us where this is wrong