Opsynth Journal

Opinion3 min read

Your inbox is already the supplier portal

Supplier portals promise structured answers, but suppliers keep replying by email. Why procurement and supply chain teams should read supplier email better instead of trying to replace it.

Zhaire WelchCo-Founder and CEO, Opsynth
Two people working through something on a laptop
Photo: John on Unsplash

Every few years a procurement team rolls out a supplier portal. Suppliers are asked to log in to acknowledge purchase orders there, answer RFQs there, upload certificates there and confirm ship dates there. A handful do. Most keep replying to email, because email is where every one of their customers already is.

So the buyer ends up running two systems: the portal, which is tidy and half empty, and the inbox, which is where the procurement work actually arrives.

Procurement work hides in supplier replies

Think about what lands in a buyer’s inbox on an ordinary morning:

  • a purchase order acknowledgement with a ship date two weeks later than the PO asked for
  • an RFQ response that quotes three of the five lines
  • a price increase “effective next month”
  • a request for a drawing revision before the supplier can start
  • silence from the one supplier you needed to hear from

None of these is a message to file. Each one is a task: expedite, accept, push back, escalate, update the plan. The difference between a buyer who is on top of the day and one who is not is rarely effort. It is whether those tasks were noticed in time, before a late part became a line-down.

What to track in supplier email

If you manage suppliers by email, and almost every procurement team does, these are the things that decide whether the supply chain holds:

  • Order acknowledgements. Did the supplier confirm the PO, and does the confirmed date, quantity and price match what you ordered? A confirmation with changes is a new negotiation, not a confirmation.
  • RFQ responses. Which suppliers have quoted, which lines are missing, and how do the price breaks and lead times compare?
  • Changes to price and lead time. Price increases, longer lead times, allocation and end-of-life notices all arrive as ordinary email, often in the second paragraph.
  • Quality and compliance documents. Certificates of conformance, first article reports and expiring certifications that have to be chased before a part can ship.
  • Unanswered requests. Every question you sent that has not been answered, and how long it has been waiting. This is the one no inbox will ever show you on its own.

Reading is the bottleneck

Most supplier email is read once, quickly, on a phone between meetings. The change buried in an acknowledgement gets missed. The supplier who has not answered in nine days does not send an email to say so. Nothing in the inbox tells you who you are waiting on, or who is waiting on you.

That is the gap we built Opsynth Desk for. It reads the supplier mail in your Outlook, works out what each message asks of you, and turns it into a task: the PO, the supplier, what changed, and how late it is. It keeps count of every request still waiting for an answer, on both sides, and flags anything that has waited three days. Suppliers sign up for nothing. They keep replying to email, the way they always have.

What changes when supplier email is read for you

The morning stops starting with a search. You open one list of procurement tasks, ordered by what is most urgent, and work it down. A supplier who moved a date shows up as a task, not as a line you might have skimmed past. An RFQ response that came back incomplete is visible as incomplete. The supplier who has gone quiet for three days is flagged before it turns into an expediting emergency.

And because it is the whole team’s mail, not one person’s, cover works too. When a buyer is out, a colleague can open their desk and see exactly what is open, without forwarding rules or a handover document written at 6pm the night before.

Why supplier portals fail

Supplier portals are an attempt to make suppliers structure their answers for you. It is a reasonable wish, and it mostly fails, because each supplier has a hundred customers and a hundred portals, and only one inbox.

The structure can come from the other side instead. Let suppliers write the way they write, and do the reading properly. That is the idea Desk is built on, and it is what we will be writing about here: supplier follow-up, purchase orders and quotes, BOM risk, supplier response times, and the projects that hold them together.

If you want to see it on real-looking supplier mail, try Desk in the sandbox. It takes two minutes.

Keep reading