Ask a supplier how many customer portals they log in to and watch their face. Spend Matters found that 60% of suppliers have to log in to at least ten different portals every month. Ten passwords. Ten places where ‘confirmed’ is a different button. Ten dashboards that someone in a sales office has to remember to update after the real conversation already happened on the phone.
That’s portal fatigue. It isn’t laziness and it isn’t a training problem, whatever the launch deck said. It’s arithmetic, and the arithmetic runs against you every single week.
What portal fatigue actually looks like
Picture a packaging supplier with nine staff. One of them, call her the office junior because that’s what everyone in the building calls her, does the portals. It’s roughly forty minutes of her morning, every morning, and it goes like this.
Chrome opens with eleven pinned tabs. The first customer’s portal wants a password reset because the policy rotates every 90 days and nobody wrote the new one down. The second one works, and she pastes in three dispatch dates that the warehouse gave her on a scrap of paper at 7:40am. The third portal has a new interface since last month, and the button that used to say Acknowledge now says Respond to PO, which opens a form with a mandatory field for a commodity code she doesn’t have. She leaves that one. The fourth is fine. The fifth logged her out while she was in the fourth.
By the time she reaches the eighth tab, the orders she’s entering were confirmed by phone two days ago. The portal isn’t where the work happens. The portal is where the work gets retyped, later, by someone who wasn’t on the call.
That last sentence is the whole problem in one line, and it’s why portals feel fine to the buyer and awful to the supplier. The supplier isn’t using your system to run their business. They’re using it to file a copy of a decision already made somewhere else.
Why the cost is invisible to the buyer
You see one portal. You paid for it, you configured it, you probably like it. The login takes you four seconds and everything you need is on one screen, so when a supplier doesn’t keep it updated the obvious conclusion is that the supplier is disorganised.
Your supplier sees the sum. The Leverage blog put it about as bluntly as anyone has: “a supplier serving 60 customers cannot log into 60 portals”, and “the cost does not sit with you, it sits with the supplier, and it recurs forever”. Forever is the part that gets missed. A portal isn’t a one-off onboarding cost you can amortise over a relationship. It’s a tax charged per order, per week, per staff change, per password rotation, for as long as you trade together.
And the tax isn’t split evenly across your supply base. Your biggest supplier, the one doing £40k a month with you, will absorb it. The small fabricator who does two jobs a quarter won’t, because forty minutes a week of admin against a two-job-a-quarter account is an obviously bad trade and they can do that maths in their head.
So the portal quietly sorts your suppliers into ones that comply and ones that don’t, by account size, which is almost never the order of how much you actually need them. The specialist who makes the one part nobody else makes is usually a small account.
The three responses suppliers have
Suppliers are polite people. Nobody replies to a portal launch email saying no. What they do instead falls into three patterns, and you’ll recognise all of them.
Ignore
They register, because the email asked them to, and then never log in again. Orders get confirmed the way they were always confirmed: a call, a WhatsApp reply, an email to the buyer who placed it. Your portal shows a supplier who exists and has never acknowledged anything. Blue Meteor, a vendor in this space and worth reading with that in mind, reckons more than 60% of supplier portal implementations fail to hit their adoption goals. This is the shape most of that failure takes.
Delegate, late
Someone junior updates the portal in a batch on Friday, from notes. The data arrives, so the dashboard looks healthy, but it’s a transcription of last week rather than a live state. Anyone in your team who makes a decision off that screen on a Wednesday is working from fiction. This is worse than ignoring, honestly, because ignoring at least looks like what it is.
Price it in
The quiet one. The supplier adds two or three percent to your rates to cover the administrative load of being your supplier, or they stop quoting on your smaller jobs, or they put your work behind a customer who’s easier to serve when the shop floor is full. You never see this happen. You see a price that drifted and a lead time that got worse, and you put it down to the market.
Why WhatsApp wins by default
Nobody chose WhatsApp as the order system. It won because of where the phone is.
The person who knows whether the goods went out today is standing at the loading dock, not at a desk. Their phone is in their pocket. WhatsApp is already open, already logged in, already the app they used to tell their brother-in-law about the football. Answering “dispatched, on the 4 o’clock van” takes about four seconds and requires deciding nothing.
Compare that with the portal: find a computer, find the password, find the order, find the right status value from a dropdown of nine that includes “In Process” and “Processing” as separate options, save, wait for the page. Two minutes if everything works. The four-second path wins every time, and it will keep winning, because the four-second path is where the information actually lives at the moment it becomes true.
The catch, and it’s a real one, is that WhatsApp is a terrible record. Nothing’s structured, nothing’s filterable, and three months later you’re scrolling a thread trying to work out which of four similar messages was the order that got short-delivered. That’s a genuine problem and it doesn’t go away by pretending chat is enough.
What to ask of a supplier instead
Split the two things the portal was trying to do at once. One is getting information out of the supplier. The other is keeping a structured record. The mistake is making the supplier responsible for both.
Ask the supplier for three events, and nothing else:
- An acknowledgement when the order lands, with quantity, price and date repeated back.
- A note when it leaves, with what actually went on the van.
- The invoice.
That’s it. No commodity codes, no weekly status refresh, no mandatory fields they have to invent a value for. And every one of those three should be answerable on the channel they already use, in seconds, from a phone, without a login.
The record is your job. When the acknowledgement comes back it should land against the order in your system automatically, not get retyped by your buyer at 5pm. This is the thing OrderBookApp is built to do: the order goes out to the vendor as a WhatsApp message with a link, acknowledging is one tap, and your board updates itself whether or not they ever create an account. If they do want the full board later, the history is already sitting there.
You can run the same pattern without buying anything, incidentally. A spreadsheet plus a disciplined habit of pasting the reply into a row will get you most of the way, and the alternatives article walks through five versions of that. The principle holds either way: the supplier’s effort should be one reply, and the structure should be yours to maintain.
If you’re the supplier reading this
You’re allowed to say no. Not rudely, and not to Walmart, but to the mid-sized customer whose new portal arrived last Tuesday with a training webinar attached.
Something like this works: “Happy to keep you updated on every order. Our team works off the shop floor so we confirm and send dispatch notes by WhatsApp or email within the hour, which is faster than we can manage through a browser. If your system needs a weekly export we can send one.” Most buyers take it. The ones who don’t will tell you how much the account is worth, and then you can do the sum.
The bit you can’t skip is keeping your own order record. If you know, for every live order, who it’s for, what’s in it, what’s been dispatched and what’s been invoiced, then answering any customer’s portal or any customer’s phone call takes a minute. If you don’t, you’re doing forty minutes a morning of archaeology and blaming the portals for it. Some of that forty minutes is yours to fix.
Portal fatigue doesn’t get solved by a better portal. It gets solved by asking for less, in the place they already are, and doing the filing yourself.
Keep reading
- Why vendor portals fail (and what your suppliers do instead) is the buyer-side version of this argument, with the adoption numbers.
- Supplier portal alternatives: 5 ways to get order confirmations without one covers email, EDI, spreadsheets and chat, and when each is the right call.
- How to get suppliers to confirm orders is the practical follow-on: what to send, when to chase, how to make the reply one tap.