Your suppliers will not use your portal
Procurement software assumes the other side plays along. In the mid-market it rarely does. Why email is the only channel that works without your supplier's consent.
Every piece of procurement software we have looked at contains a supplier portal somewhere. The supplier creates an account, maintains prices, confirms orders and reports dates. On paper it is the clean solution: structured data on both sides, no misunderstandings.
In practice it fails on a question that never comes up in the product demo. Why would the supplier do this?
The supplier’s arithmetic
Your supplier has a system of their own. They also have thirty, a hundred or five hundred other customers, and some of those have portals too. Each of those portals means another login, another interface, another place where data is maintained twice.
For their largest customer they will do it. For the customer who orders standard parts twice a quarter they will not. Not out of ill will, but because the effort does not pay for them.
So the mid-sized company is left with a tool whose usefulness depends on the other side playing along. And the other side has no reason to.
What actually works instead
There is exactly one channel every supplier already uses without you having to ask them for anything: email.
The supplier receives an order as an email with a PDF attached, the way they have been used to for years. They reply in their own style, from their own system, in free text. They install nothing, register for nothing, learn nothing. From their side, nothing has changed.
The effort therefore shifts entirely to your side, which is exactly where it belongs. The supplier should not have to deliver structured data; your system should read the fields out of what arrives anyway.
The hard part is the reply, not the order
Sending an order is easy. Understanding a reply is the actual work.
Order confirmations look different at every supplier. Sometimes the order number is in the subject, sometimes in the PDF, sometimes nowhere. Sometimes the full quantity is confirmed, sometimes a partial quantity with a second date for the rest. Sometimes instead of a confirmation there is a question, or a quiet change of date buried in the running text.
This is precisely where the value sits. The agent reads the reply, matches it to the open order, recognises the confirmed quantity and the promised date, and moves the order from “sent” to “confirmed”. When the promised date differs from the one that was planned against, that is not a silent event but a notification.
Every one of those matches lands in the log: which mail belongs to which order, and what was read out of it. That is the precondition for anyone being able to disagree.
What we are not claiming
Not every reply is unambiguous. When a mail could refer to two open orders with the same supplier, or when a partial quantity is confirmed without a date, the honest response is not a guessed result but a hand-off to a person.
We think that is the right boundary. A system that guesses when in doubt saves you time once and costs you considerably more at the first wrong goods receipt.
The point is not that email is elegant. The point is that it is the only channel that works without your suppliers’ consent. Everything else is a project you cannot decide on your own.