Product · Supplier Portal
Supplier portal software for your whole supply base
Your suppliers see their orders, send a shipping notice, submit an invoice and watch it match — and answer a corrective action in the same place they do all of it.
Two ways in, deliberately. Onboarded suppliers work signed in. Anyone you invite to a sourcing event answers on a secure link, with no account to create and nothing to install.
- Lines and dates
- As you issued them
- A printable copy
- Theirs to take, not yours to send
- Acknowledgement
- Accept, reject, or accept with changes
- A short line
- Marked backordered with a confirmed quantity
With its lines and dates, and an acknowledgement recorded against it.
The same supplier work. An inbox, or a portal.
Most supplier interaction is still a mailbox: an order as an attachment, an invoice as a reply, a corrective action as a document someone fills in.
What they do here
Eight things. All behind one sign-in.
Not a document library with a login on it. These are the areas a supplier actually works in, and what each one lets them do.
The orders raised against them, each with its own PDF, and an acknowledgement they record against it — accepted, rejected, or accepted with changes, line by line where a line is going on backorder.
A notice against the order with its lines and quantities, capped at what is still outstanding, optionally tied to a lot, and a printable version with a code on it for the receiving dock.
Submitted against a purchase order — uploaded, or built from the order itself — with milestone, advance and credit-note variants, and a duplicate number refused rather than quietly accepted.
Where the invoice has got to in your matching process: pending, matched, under review, a quantity dispute, a price variance, approved, rejected or paid. The supplier reads it instead of asking.
Contact details, address, website and phone updated directly. Banking and tax details proposed as a change for your team to approve, with the reason shown to them if you turn it down.
Certificates against the types you require, with issue and expiry dates and a clear state — missing, current, expiring soon or expired. A replacement keeps the previous one rather than overwriting it.
The eight steps as sections they complete and submit for your review, in two submissions: containment first, then root cause, corrective action, implementation and prevention.
Sourcing events and auctions they have been invited to, questionnaires you have sent, part-approval status, and contracts to read and sign.
Where this already runs
In operations like yours. Not vendor scenarios.
An oil and gas producer brings 4,000 suppliers onto one record
A supplier base above 4,000, with 50–80 onboardings a month 4,000+suppliers on one governed record50–80onboardings a month through one process3 → 1systems holding the supplier view Read the story
A chemicals manufacturer takes the spreadsheet out of the award
Raw materials, packaging and engineering goods across several business units 1supplier record behind every award0Oracle modules replaced3kinds of evidence in the decision: price, quality, contract Read the storyAn order, from their side
Six steps. None of them is an email.
The sequence a supplier actually works through, and where it hands back to your team.
-
01
System
The order appears
Once you approve and issue it, the order is in their portal with its lines, dates and its own PDF. They do not wait for someone to forward it.
-
02
Human
They acknowledge it
Accepted, rejected, or accepted with changes — recorded against the order, with a confirmed quantity where a line is going short or on backorder.
-
03
Human
They send a shipping notice
A notice against the order with its lines and quantities, limited to what is still outstanding, and tied to a lot where you track them. It prints with a code for the dock.
-
04
Human
They submit the invoice
Against the order, uploaded or built from the order itself. A number you have already seen is refused at submission rather than found later.
-
05
Rule
Matching runs and they watch it
The match runs when the invoice is submitted, and its status is visible to them — matched, a quantity dispute, a price variance, under review. No status call required.
-
06
Human
Your team decides, and they see the date
Approval stays with your people. Once an invoice is approved the supplier sees the date it is due to be paid by, and a rejected invoice can be corrected and resubmitted where you send it back.
Core capabilities
What supplier portal software has to get right.
Two ways in, on purpose
A login for the suppliers you work with, a secure link for everyone else
- Onboarded suppliers sign in and reach orders, invoices, certificates and quality in one place
- Anyone invited to a sourcing event answers on a link — no account, no password, nothing installed
- The link route captures the most on a bid: price tiers, minimum order quantities, alternates and deviations
Orders they can act on
The order, the acknowledgement and the shipping notice, in one sequence
- Every order with its lines, dates and its own printable copy
- Accepted, rejected or accepted with changes — recorded line by line, including backorders
- A shipping notice capped at the outstanding quantity, tied to a lot, printable for the dock
Invoices with their status attached
Submitted against the order, and visible all the way to a payment date
- Uploaded or built from the order; milestone, advance and credit-note variants included
- A duplicate invoice number is refused at submission rather than discovered in a reconciliation
- Matching status visible to the supplier — matched, quantity dispute, price variance, under review
Changes that go through you
Bank and tax details proposed by the supplier, approved by your team
- Account, payment terms, tax identifiers and legal entity details all sit behind approval
- The supplier sees the pending state, and the reason if you turn it down
- Contact details, address and phone update directly, because they do not need a gate
Certificates with a state you can read
What they hold, what expires when, and what is still missing
- Certificates against the types your organisation requires, with issue and expiry dates
- A clear state on each — missing, current, expiring soon or expired
- A renewal keeps the previous certificate rather than overwriting the history
Corrective action answered in a form
Eight steps as sections, not a document attached to a reply
- Containment submitted first, then root cause, corrective action, implementation and prevention
- Each section saves as they work, so a long investigation survives a closed laptop
- Returned with notes they can read, and your team is notified when a submission arrives
Sourcing and auctions in the same place
Events, questionnaires, part approvals and contracts, beside the day-to-day
- Open events and auction invitations surface on their landing page with what is awaiting them
- Live auctions require your bidding terms to be accepted before a bid is taken
- Contracts to read and sign, and part-approval progress where you run it
Notifications you control
In-app and email, switched per event type by you rather than by us
- A bell in the portal, plus email where you have it configured for that event
- Your team chooses which events notify, on which channel, with your own wording
- Questions are answered privately, or broadcast to every invitee without naming who asked
Features
Supplier portal software that holds its own rules.
Five groups of features, and not one of them depends on someone remembering the policy.
What it refuses, and what it holds for approval
Self-service with the decisions that matter still on your side.
- Banking and tax changes are proposed by the supplier and approved by your reviewer roles
- A supplier cannot approve any step of their own onboarding or corrective-action review
- A duplicate invoice number is refused at submission rather than found in a reconciliation
- A shipping notice is capped at the quantity still outstanding on the order
- Submission deadlines are checked on the server, so a late bid is refused rather than discouraged
Orders, and what is actually shipping
The order, the answer to it, and the notice that something has left.
- Every order with its lines and dates, and its own printable copy
- Accepted, rejected or accepted with changes — recorded line by line
- A line going short is marked as backordered with a confirmed quantity
- A shipping notice with its lines, tied to a lot where you track them
- The notice prints with a code on it for your receiving dock
Invoices, and where they got to
Submitted against the order, and visible all the way to a payment date.
- Uploaded, or built from the purchase order so nothing is retyped
- Milestone invoices, advance invoices and credit notes all supported
- Matching runs on submission and its status is visible to the supplier
- Matched, quantity dispute, price variance, under review, approved or paid
- An approved invoice shows the date it is due to be paid by
The details they keep current
What they can change directly, and what waits for you.
- Contact details, address, phone and website updated directly
- Banking and tax details proposed as a change, with the reason shown if declined
- Certificates against the types your organisation requires, with issue and expiry dates
- A clear state on each one — missing, current, expiring soon or expired
- A renewal keeps the previous certificate rather than overwriting it
Events, auctions and quality actions
The rest of the relationship, in the same place as the orders.
- Open events, auction invitations and awaiting quality actions on their landing page
- Invited suppliers without an account answer a sourcing event on a secure link
- That link route captures price tiers, minimum order quantities, alternates and deviations
- Live auctions take no bid until your bidding terms have been accepted
- Corrective actions answered as eight sections, submitted in two stages for your review
Where your team still decides
Self-service. Not self-approval.
- A supplier can propose a change to banking or tax details. They cannot approve one. That decision belongs to the reviewer roles your organisation sets.
- A supplier cannot approve any step of their own onboarding review, or any step of a corrective action review. Those sit with your team.
- Contact details, address and phone update directly, because an address does not need an approval queue. Banking and tax do, and are gated accordingly.
- Submission deadlines on sourcing events and auctions are checked on the server, not in the browser, so a late submission is refused rather than politely discouraged.
- On a live auction, your bidding terms have to be accepted before a bid is taken, and the wording accepted is kept.
- A question from one supplier is private until you choose to broadcast the answer, and a broadcast answer does not carry the name of whoever asked.
- Invoice approval and payment stay entirely on your side. The portal shows a supplier where their invoice has got to; it does not move it along.
Two suppliers. Two different weeks.
A supplier you order from every month
They sign in, open the order you issued this morning and record an acknowledgement — accepting most lines and marking one as going on backorder with a confirmed quantity. A fortnight later they raise a shipping notice against it for what is actually leaving, which prints with a code for your receiving dock. When they invoice, they build it from the order rather than retyping it, and they watch the matching status move rather than emailing to ask. Once it is approved, they see the date it is due to be paid by.
A supplier you have never bought from
You invite them to a sourcing event and they get a secure link. There is no account to create and nothing to install. They enter their price, lead time, minimum order quantity, price tiers and any deviation from your terms, attach what they need to, and submit — or decline, with a reason, if the work is not for them. If you later put them through onboarding and activate them, their contacts get portal logins and the rest of this page applies to them too.
Where it fits
The supplier side. Of things your team owns elsewhere.
The supplier record lives in supplier management
Identity, onboarding and the hold or block your team applies are held there. The portal is where the supplier maintains their own part of that record and uploads what you ask for.
Orders, receipts and invoices come from procure-to-pay
The orders a supplier sees, the shipping notices they send and the invoices they submit all belong to that module. The portal is the supplier-facing side of it.
Corrective actions and part approvals come from supplier quality
The eight-step form a supplier fills in, and the part-approval progress they see, are that module’s records. Your quality team reviews them from their own screens.
Sourcing events arrive from sourcing and auctions
An invited supplier responds either signed in or on a secure link, depending on whether they are onboarded with you yet.
Connects to Supplier management · Procure-to-pay · Supplier quality management
Bring us one supplier who lives in your inbox.
We will set them up with their own orders and invoices, and you can watch a shipping notice arrive without anybody sending an email about it.
Security, compliance and recognition
Checked by auditors. Judged by the industry.
Where each compliance programme stands, and what the procurement industry has given us so far.
Security and compliance
Awards
Five, presented on stage at three industry events.
- Autonomous Procurement Platform of the Year
- Procurement Technology Innovation Award
- Unified Procurement and Supplier Management Platform
- Procurement Startup of the Year
- AI in Procurement or Supply Chain Award — Solution Provider
Before you book anything. Answered honestly.
What is supplier portal software?
Supplier portal software gives the companies you buy from a place to do their side of the work — read the order, say whether they can meet it, tell you what has shipped, submit the invoice, keep their certificates current and answer a quality issue. The test of a useful one is whether it removes an email rather than adding a login: whether a supplier can find out where their invoice has got to without asking anybody.
Do suppliers need an account?
It depends which job they are doing, and that is deliberate. A supplier you have onboarded gets a login and works signed in — orders, shipping notices, invoices, certificates, quality actions, contracts. A supplier you are inviting to a sourcing event responds on a secure link instead, with no account to create and nothing to install, which matters when you are inviting companies you have never bought from.
What can a supplier do with a purchase order?
Read it with all its lines and dates, take a printable copy, and record an acknowledgement against it — accepted, rejected, or accepted with changes, including marking a line as going on backorder with a confirmed quantity. They cannot change the order’s dates or quantities themselves; that stays a conversation with your buyer, because a supplier editing a purchase order is not something most procurement teams want available.
How do invoices work in the portal?
A supplier submits an invoice against a purchase order, either by uploading their own or by building it from the order so nothing is retyped. Milestone invoices, advance invoices and credit notes are all supported. An invoice number you have already received is refused at the point of submission. After that the supplier can see the matching status — matched, a quantity dispute, a price variance, under review, approved or paid — and once it is approved, the date it is due to be paid by.
What happens when a supplier changes their bank details?
They propose it; your team approves it. Banking and tax details — account, payment terms, tax identifiers, legal entity and signatory — all sit behind approval by the reviewer roles your organisation sets. A supplier can never approve their own change. Contact details, address and phone update directly, because those do not warrant a queue.
What do suppliers see about their own certificates?
What your organisation requires of them, what they currently hold, the issue and expiry dates on each, and a clear state against every one: missing, current, expiring soon or expired. When they upload a renewal, the previous certificate is kept rather than overwritten, so the history is still there when someone asks what was valid in a given month.
Can suppliers answer a quality issue in the portal?
Yes. A corrective action appears as the eight steps in sections they complete, saving as they go, and they submit in two stages — containment first, then root cause, corrective action, implementation and prevention. Your quality team reviews each submission and either accepts it or returns it with notes the supplier can read, and the product records who made that decision.
Who controls what suppliers are notified about?
You do. Notifications reach a supplier in the portal itself and, where your team has configured it for that event type, by email. Which events notify, on which channel, and in what wording are your settings rather than ours. Questions a supplier asks are private until you choose to broadcast the answer, and a broadcast answer does not carry the name of whoever asked it.
One supplier. One sign-in.
No slides. Their orders, their invoice status, and a sourcing event answered on a link with no account at all.
Someone from client success replies, not a sales sequence. If we are not a fit we will say so on the first call.
Not ready to talk to anyone?
Fair enough. Both of these work without giving us your email.
Explore the next step