What the Other Side Can Actually Do
Your suppliers can have logins here — with multi-factor authentication, a forced first password change, and rate limits on every action. From that login they answer quotations, accept or reject your orders, and set a shipping status. Very few systems in this bracket do the second half at all.
Most procurement software is written entirely from the buyer's chair. The supplier is a row in a table, an email address, and a name on a document. Whatever they think about your order arrives by phone.
The position, up front
There is a real supplier portal here and it is worth using. A vendor logs in, sees the requests for quotation they were invited to, submits and edits their own quotations, sees the resulting orders, and can accept, reject, close or update the shipping status of each one — all rate-limited, behind an account with multi-factor authentication. Where it stops is invoices and payment: the supplier cannot submit an invoice or see what they are owed.
What a supplier account is
A real account, not a magic link. It has a password with a forced change on first use, optional multi-factor authentication with recovery codes, and a record of when the password was last set. It even carries its own appearance preference, which tells you it was built as a place somebody works rather than a page they visit once.
Every action a supplier can take is rate-limited separately from the rest of the application. That is a small detail with a specific meaning: the people who built it assumed the accounts would be used by people outside the organisation, and treated them accordingly.
What they can do with it
The supplier's side of the chain
See the requests they were invited to
A list of open requests for quotation, and each one in detail.
Respond with a quotation
Submit a quote against a request, then view and edit their own quotations afterwards.
See the resulting purchase orders
A list and a detail view of every order raised against them.
Accept or reject an order
A recorded decision from the supplier rather than a phone call, with the acknowledgement time measurable from the order date.
Update the shipping status and tracking
The supplier tells you where the goods are, rather than your buyer chasing them.
Close an order
A supplier-initiated close on their side of the document.
Submit an invoice
No. There is no invoice capture anywhere in the product, and the portal is no exception.
See what they are owed, or when they will be paid
No. There is no remittance view and no payment status exposed to the supplier.
Update their own bank details or documents
Not from the portal. Prequalification is the route in, and changes after that are yours to make.
Read the shape: everything up to and including delivery is collaborative, and everything about money is one-way. That boundary is deliberate in effect even if it was not designed as one, and it is worth knowing which side of it your supplier relationships live on.
The acknowledgement is the underrated one. A recorded yes, with a time on it, is the difference between a supplier who is late and a supplier who never agreed.
Why the acknowledgement matters more than it sounds
Because the most common dispute in purchasing is not about price or quality. It is about whether an order was ever accepted.
A buyer sends an order. Three weeks later nothing has arrived. The supplier says they never confirmed it; the buyer says they sent it. Both are telling the truth as they understand it, and there is no record of the moment in between.
An acknowledgement with a timestamp closes that argument permanently, and the product goes one step further: it can express the time between the order being raised and the supplier acknowledging it, in hours. That is a measure of responsiveness that costs nothing to collect once the portal is in use — and it is one of the very few supplier-performance figures in this product that comes from data rather than from a field somebody types.
Why a Jordanian buyer should push suppliers onto it
Because a large share of supply here is regional rather than domestic, which means the practical distance between buyer and supplier is a time zone, a border, and often a different working week.
A working week that does not overlap is the specific problem. A buyer chasing an acknowledgement by phone has a narrow window; a supplier answering a portal has all of theirs. Asynchronous is not a convenience here, it is the only mode that works, and a portal is asynchronous by construction where a phone call is not.
The half that is missing is the money half
The collaboration side is built. What a supplier cannot do is anything to do with being paid, and that is one project rather than three — it needs somewhere to put an invoice before anything downstream of it makes sense.
Supplier invoice submission
The foundation. It is also the missing third document in receipt matching, so the same build closes two gaps we publish about.
A remittance and payment status view
What is owed, what is scheduled, what has been paid. Cheap once the invoice exists, and the single most requested thing by suppliers on any portal.
Self-service document renewal
A supplier updating their own expiring certificates before the qualification lapses, which would close the silence described in A Qualification That Expires in Silence.
No dates on a public page. If supplier self-service on invoices is a requirement rather than a nicety, describe the volume and we will come back with a written scope, timeline and cost.
Scope the portalThree questions about any supplier portal
Can a supplier reject an order, and is the rejection recorded?
A good answer sounds like
Yes, with a timestamp.
What it actually means
Many portals are read-only for orders. A portal a supplier can only look at does not resolve the dispute this exists to resolve.
What authentication does a supplier account have?
A good answer sounds like
A password with a forced change, and multi-factor available.
What it actually means
External accounts are the softest part of most systems. Ours are treated as external and rate-limited separately, which is the right instinct.
Can a supplier see what they are owed?
A good answer sounds like
Yes or no, plainly.
What it actually means
Ours is no. It is the first thing suppliers ask for and the answer determines whether they will actually log in.
What AWRA OpsHub does today
- Supplier accounts with a password, a forced first change, optional multi-factor authentication with recovery codes, and rate limiting on every write action.
- A supplier dashboard, a list of requests for quotation they were invited to, and a detail view of each.
- Quotation submission, and viewing and editing of their own quotations afterwards.
- A list and detail view of purchase orders raised against them.
- Accept, reject and close actions on an order, and an update to shipping status and tracking number.
- An acknowledgement timestamp on the order, and the elapsed time between raising and acknowledgement expressed in hours.
- Secure attachment access scoped to the supplier's own quotations.
What it does not do
- Supplier invoice submission of any kind.
- Any view of what a supplier is owed, when it is scheduled, or what has been paid.
- Self-service updates to bank details, contact details or compliance documents.
- Any notification to a supplier when their qualification is about to lapse or has lapsed.
- A supplier-facing message or query thread against an order.
Not ours, by choice
- This is one of the more complete pieces of the product and it is under-used, largely because nobody thinks to ask whether their suppliers can have logins.
- The acknowledgement figure is one of the few genuine supplier-performance measures available here, because it is derived rather than typed.
- Nothing here is Jordanian. It is what asynchronous collaboration is worth; a regional supply base with a different working week is where it is worth the most.
Put your five largest suppliers on it first
A portal is worth nothing at ten per cent adoption and a great deal at eighty. Start with the suppliers whose orders you chase most, and the acknowledgement figure will tell you within a month whether it is working.
Roll it outFrequently asked questions
Do suppliers need to pay for an account?
Supplier accounts belong to your organisation rather than to the supplier, and how many vendors you can keep active is governed by your plan. That is worth checking against the size of your supply base before you plan a rollout.
What stops a supplier seeing another supplier's quotation?
Every portal route is scoped to the signed-in vendor, including the secure attachment route, and cross-access between the internal application and the portal is prevented at the routing layer. Treat it the way you would any external access: give accounts to named people, not to a shared mailbox.
If a supplier rejects an order, what happens?
The rejection is recorded against the order from their side. What happens next is a commercial decision rather than an automatic one — nothing re-sources it, and nothing notifies your buyer to go back to the second-placed quotation, so build that step into your process.
