The Order You Haven’t Seen Yet
Your second largest account stopped emailing purchase orders in March. They went live on a procurement platform and sent a note about it, which somebody read and filed as an IT thing.
Now a person on your desk logs in every morning, clicks through to the open orders view, opens each PO, and retypes it into your ERP.
That was one account. There are five more now, and each one has its own login, its own layout, its own quirk about where the ship-to actually lives. Nobody decided to take this on. It arrived one account at a time, and every time it arrived it was small enough that absorbing it was easier than raising it.
So it never got assigned. It never got counted. And it never got a backup.
THE SAME PO, TWO WAYS IN
By email: it lands in a shared inbox. Timestamped, searchable, forwardable. Three people can see it. If the person who normally handles it is out, somebody else finds it.
By portal: it sits behind a login. No thread, no timestamp on your side, no search, no record on any system you own that the document exists at all. If the person who normally handles it is out sick, it stays there.
The order is identical. Everything around it is gone.
Here is the arithmetic, and it is the only arithmetic in this issue. September 3 to December 31 is 119 days. Seventeen weeks. Today is day 246 of the year, so 67 percent of the year is gone. That is your benchmark and it costs nothing to compute.
Put every account with a commitment on one chart against that line and the whole year resolves in about four seconds.
Here is the part worth saying plainly, because it is not anybody’s fault and treating it as a failure gets you nowhere. The portal was a good decision for your customer. Their procurement team got one system of record and cut their own keying to almost nothing.
That work did not evaporate. It changed hands. And it changed hands to the party with the least standing to object, without anyone on either side ever writing it down as a term of business.
Portals also carry more than orders. Change notices, forecast updates, requests for quote, shipping requirements, sometimes a supplier scorecard nobody on your side has ever opened. Some of them put a response window on the document, which means a PO nobody pulls down in time becomes a scorecard problem you hear about at the QBR, six months later, from a buyer who is reading it off a screen.
And I have never once seen a customer go back to email. This only moves one direction, and the next large account you win will have a portal too.
This Week, Try This: Watch the Notifications, Not the Portals
First, the thing you are already thinking, and the answer is no.
Do not point automation at the portal login. Most of them sit behind multi-factor authentication. A fair number have terms of use that restrict automated access. And the practical reason is the one that should settle it: a locked supplier account is a phone call to your buyer explaining why a robot was in their system. Nobody wants to make that call in September, let alone December.
The portal is closed to you. But every portal in the world sends you email.
1. Log the notifications
New PO available for review.” “PO 4500123 has been issued.” “Response required by 09/12.”
That message is machine generated, templated, and it lands in a mailbox you already control. It carries the portal, the account, the document number, usually a date, and a link. Nobody treats it as data. Somebody reads it once, acts on it or doesn’t, and it becomes another email.
Machine-generated mail is also the easiest thing a classifier will ever be handed. It’s templated, it says the same thing every time, and it doesn’t need interpreting.
Set it up as a scheduled task in Claude Cowork, pointed at whatever mailbox this arrives in. Gmail and Microsoft 365 both connect, so Outlook is covered, and on the Microsoft side it reaches shared mailboxes you already have access to. Which is usually where portal mail actually lands, since these notifications tend to go to orders@ rather than to a person.
And none of it depends on reading attachments. The document number, the account and the link are sitting in the body of the message in plain text. Worth knowing, because the attachment is where most inbox automation stalls, and there isn’t one here to open.
Every weekday morning, do this.
1. Search the mailbox for messages received since your
last run. If you have no record of a last run, use
the past 24 hours.
2. Identify every message that is an automated
notification from a customer's procurement or
supplier portal. These announce that a document is
available, that a document has changed, or that a
response is required. They are machine generated and
usually arrive from a no-reply address.
3. Open the Portal Log sheet in the working folder and
read it so you know what is already logged. Never log
the same notification twice. Match on the document
number.
4. For each new notification, append one row:
- date_received
- portal: the platform or system that sent it
- account: the customer, if the message names one
- document_type: purchase order, change order, RFQ,
forecast, scorecard, other
- document_number
- response_due: any deadline stated in the message,
else blank
- link
- source_quote: the exact sentence you took
response_due from, blank if there is none
Rules:
- Quote, do not paraphrase, in source_quote. Never infer
a deadline from context.
- Over-include. If you cannot tell whether a message is
a portal notification, log it and set document_type to
unclear. A wrong row costs ten seconds to delete. A
missing row is the entire subject of this newsletter.
- Do not open the link. Do not attempt to log in to
anything.
- Append only. Never modify a row that already exists.
2. Reconcile it against the ERP
Part one gives you a list. This is the part that turns the list into a finding.
Take the log and set it against your open order export, matching on the customer’s PO number. Anything notified more than two days ago with no matching order on your side is a purchase order sitting on a customer’s system that nobody has pulled down.
Not a metric. A short list of specific document numbers you can go check before lunch.
Three more things fall out of the same run, and they are the reason to keep it going after the first week:
The portal count, actually counted. Distinct portals in the log. Ask around the desk first and write down the guess, then compare. The guess is usually low by two.
Every response deadline in one place. Including the ones attached to documents that are not orders, which are the ones that get missed.
Your real channel mix. What share of inbound documents came through a portal rather than the inbox. Nobody in your building has this number either.
Every Monday, do this.
1. Read the Portal Log sheet in the working folder.
2. Open the newest open-order export from the ERP in the
same folder. If there is nothing newer than your last
run, say so in one line and stop.
3. Match log rows with document_type "purchase order"
against the export on document number. Where a match
exists, set Status to Entered and record the date you
found it.
4. Post a summary with four lists and nothing else:
- Purchase orders notified more than 2 days ago with
no match in the ERP, by account and days open
- Any response_due inside the next 7 days
- Distinct portals seen in the last 30 days, with a
document count for each
- Documents of a type other than purchase order
received in the last 7 days
5. If a list is empty, write one line saying so. Do not
pad it.
3. Map the logins, which takes ten minutes and no software
On paper, from memory, in whatever meeting you are already sitting in. One line per portal:
Portal. Account. What comes through it. Who has the credentials. Who else has them. What breaks if that person is out for a week.
Everyone expects the time column to be the alarming one. It usually isn’t. Six or seven hours a week spread across a desk is annoying, not frightening.
The credential column is the one that stops the room. Most operations find that every portal has exactly one person, that it is frequently the same person, and that at least one login is registered to an email address belonging to somebody who left in 2024. Password resets on a customer’s portal often route through their admin for approval, so a routine reset turns into an email to your buyer.
Which means, and I would put this in front of whoever owns the P&L: you are one resignation away from not being able to receive orders from your largest accounts.
That sentence is worth the ten minutes even if you never build parts one and two.
An Honest Take
When somebody finally lays all this out in a meeting, the first instinct in the room is to go back to the customer and ask whether you could just get the POs by email again.
Don’t. You will lose that conversation, and you will lose it while looking like the supplier who can’t keep up. The portal is not a preference on their side. It’s a control their finance and audit people asked for, and you are not going to win it by explaining that it’s inconvenient for you. You have no real standing there, and pretending otherwise wastes a call you could have spent on something that moves.
So stop trying to close the channel and start treating it like one.
Here is what I actually think, and it’s a management point more than a technology one. Portal duty is the last unassigned job on most order desks. No owner, no coverage, no volume number, no place in anybody’s review. That is the exact profile of every job that eventually fails at the worst possible moment. Everything else on that desk got a system as it grew. This one grew past the point where informal handling works and nobody noticed, because it never generated a complaint. Portals are quiet. That is the whole problem with them.
One smaller thing, and it points at what we sell, so weigh it accordingly. The reason nobody has counted this is not that counting is hard. It’s that the count has never existed anywhere, in any system, in any form. Orders in the ERP get counted. Emails in an inbox can be counted. A purchase order that a human read off a screen and retyped leaves no evidence of ever having arrived. That is what we sell against, and the logic holds regardless of who you buy it from.
The Bottom Line
There is a channel bringing orders into your business that has no owner, no volume report, no coverage plan, and one set of credentials per account sitting in one person’s password manager.
It is not going away. It grows every time you win a large customer. And the only part of it you actually control is your own inbox, which is also the only part you need.
Somewhere in the mail from the last two weeks are notifications about documents nobody has opened. The question isn’t what you missed last quarter. It’s whether anything is watching this morning.