Somewhere in your inbox is an email from a customer with the subject line “Action required: register on our new supplier portal”. You opened it, saw a 14-step onboarding guide as a PDF, and closed it. Three weeks later they emailed the purchase order anyway.
That’s the whole story of vendor portals, told from the supplier’s chair. And once you’ve sat in that chair, you’ll understand why the portal you’re thinking of building for your own vendors is going to meet the same fate.
What a vendor portal is supposed to do
The pitch is reasonable. Instead of purchase orders going out by email and confirmations coming back by phone, both sides log in to one website. The buyer posts the order. The vendor clicks “accept”, uploads the delivery note, submits the invoice. Everyone can see the status. Nobody has to ask “did you get my PO?” again.
Big companies have run these for decades. Walmart’s Retail Link, Amazon Vendor Central, SAP Ariba. And in the last few years the idea has drifted down-market: no-code tools like Stacker, Knack and Zoho Creator will let a ten-person business spin up a “vendor portal” in an afternoon, for $12 a seat.
So people do. And then nobody logs in.
The number that explains everything
Spend Matters surveyed suppliers and found that 60% of them have to log in to at least ten different customer portals every month. Ten. Each with its own password, its own idea of what a “confirmed” order looks like, its own place to hide the invoice upload button.
Now put yourself in the shoes of a packaging supplier with 80 active customers. Customer number 41 sends the “please register” email. What’s the rational response? The supplier’s blog at Leverage put it bluntly: a supplier serving 60 customers cannot log into 60 portals. When you mandate one, they either ignore it, delegate it to someone junior who updates it late, or absorb the cost and pass it back to you in pricing.
That third option is the one nobody talks about. You built a portal to save money and your vendor quietly added 2% to the quote to cover the admin.
Why the economics never work
I think most portal failures get misdiagnosed as a training problem or a UX problem. “The interface was clunky.” “We didn’t do enough onboarding webinars.” Sometimes true. Usually not the real reason.
The real reason is who pays. The buyer pays once, to build the portal. The supplier pays every single week, forever, in the form of one more place to check, one more set of data to retype from their own system, one more login to reset. The same Leverage piece has the line that should be printed on the wall of every procurement office: the cost does not sit with you, it sits with the supplier, and it recurs forever.
And it gets worse after the order is placed. Gartner has found that about half of all purchase order lines change after they’ve been issued. Quantity goes up, delivery date slips, one item gets swapped. Every one of those changes is a portal update the supplier has to remember to make, on top of the WhatsApp message they already sent you about it.
Because that’s what actually happens. The vendor tells you on WhatsApp. The portal still says “confirmed, 500 units, Tuesday”. The portal is now wrong, and everyone knows it’s wrong, and within a month it’s just a place you go to download PDFs.
Portals are built for the person who isn’t using them
Open any supplier portal and ask: who was this designed for?
The answer is nearly always the buyer’s finance team. The screens are about approvals, compliance documents, tax forms, three-way matching. All useful things. None of them are why a supplier gets up in the morning.
What the supplier wants from you is embarrassingly simple. Tell me what you want and when. Tell me it’s confirmed. Tell me when you’ve received it. Pay me. That’s four messages. A portal turns those four messages into a registration flow, a profile to maintain, a document library, and a dashboard nobody asked for.
There’s a related trap that’s easy to fall into if you’re the buyer: assuming your vendors think about your orders as much as you do. For a small bakery ordering flour, the flour mill is the most important vendor in the world. For the mill, the bakery is order line 3,412 this month. Any system that requires the mill to care more than that is a system the mill will not use.
The portal that gets used is the one that isn’t a portal
Here is what your suppliers do instead of logging in, right now, today.
They reply on WhatsApp. They call. They send a photo of the delivery challan. They email a PDF invoice with “as discussed” in the body and nothing else. And to be fair to them, all of that works. Orders get delivered. Invoices get paid. It’s messy, but it’s messy in a way that costs the supplier nothing extra.
So the question isn’t “how do I force my vendors onto a portal”. It’s “how do I get a structured record out of the channel they already use”.
That reframes the problem completely. A vendor who won’t register on your portal will absolutely tap “Acknowledge” on a WhatsApp message that took them to a page with one button on it. A vendor who won’t upload a delivery note to a document library will reply “dispatched, reaching tomorrow” in chat. If the order record can capture that, you’ve got everything the portal promised without asking the vendor to change a single habit.
And when a vendor does decide to come on board properly, because you’re a big enough customer or because three of their other customers use the same thing, the structured version should just be there waiting. Same order, now with a status they can move themselves.
What “both sides” actually means
Most portal thinking has a hidden assumption: there is a buyer, there is a supplier, and the software belongs to the buyer. The supplier is a guest.
But almost every business is both. The furniture workshop buys timber and hardware from six vendors, and sells finished pieces to forty shops. The restaurant buys from a dozen suppliers and caters corporate lunches for twenty offices. Each of those businesses is a supplier in the morning and a buyer in the afternoon. Each of them is being asked to register on other people’s portals while wishing their own customers would confirm orders faster.
A portal makes that worse. Two businesses that trade with each other now have two portals pointing at each other, each with a partial copy of the same order.
What works instead is one record. The buyer sees it as an order they placed, sitting in a column called “placed” until the vendor acknowledges. The vendor sees the very same order as something they received, sitting in their inbox until they accept it. When the vendor marks it dispatched, the buyer’s board updates. Nobody retyped anything. The record is shared, the views are different.
That’s the model we built OrderBookApp around, and honestly the reason was selfish: we were tired of being a guest on other people’s portals. One board for every order you place and every order you receive. WhatsApp when the other party isn’t on the app, a structured workflow when they are.
If you still want to build a portal
Fine. Some situations do call for one: you’re a large buyer with real leverage, your top vendors ship to you daily, and you’re doing serious compliance work. Ariba exists for a reason.
Before you do, though, write down the answers to these, and be honest:
- How many of your vendors will use it in month six, not month one? If the answer is “the big three”, build for the big three and leave everyone else on chat.
- What does the vendor get out of it that they don’t get from replying to a WhatsApp message? If you can’t name something they’d notice, they won’t notice.
- What happens to the order record when a vendor sends a change by phone? If the answer is “someone updates the portal”, that someone will stop doing it by week four.
- Can a vendor confirm an order in under ten seconds, on a phone, without logging in? If not, you’ll be chasing confirmations by hand anyway.
One more, which is the one people skip. Are you also a supplier to someone? Then ask yourself how you feel about their portal. That’s how your vendors feel about yours.
Keep reading
- How to track vendor orders on WhatsApp is the practical system behind the “keep the channel, fix the record” idea.
- The vendor order lifecycle: 7 stages from placed to paid sets out the statuses a portal is trying to track in the first place.
- 5 signs your business is losing orders in WhatsApp chats is the self-test for what chat alone costs you.