What Nobody Tells You About Purchase Orders Until a Delivery Slips: Why POs Still Fall Through the Cracks in 2026
A fit-out contractor orders 40 door frames from a supplier on a Tuesday. The PO goes out by email. The supplier confirms on WhatsApp because that's where the sales rep actually replies. Three weeks later, on delivery day, only 22 frames show up. Nobody can find the confirmation message because it's buried in a thread that also has photos of someone's lunch and a location pin for a job site three projects ago.
This isn't a software gap. Every one of these companies already has email, WhatsApp and probably a spreadsheet tracking "open POs." The problem is that a purchase order today doesn't live in one place — it lives in three or four, and the version that matters is whichever one someone happens to scroll back to first. In 2026, most PO delays aren't caused by a missing tool. They're caused by a follow-up nobody owned.
"The PO you wrote isn't the PO the supplier is working from. It's whichever version survived the longest WhatsApp thread."
Background and Context
Procurement software has spent two decades optimizing the wrong layer of the problem. Enterprise platforms built dashboards, three-way match automation and approval workflows — genuinely useful if every party is logging into the same portal. But most suppliers, especially in construction, industrial and fit-out work, aren't logging into your portal. They're texting a driver, replying to whoever answers the phone, and updating quantities verbally on site.
The mid-market tools that noticed this tried to fix it by making the portal nicer. That doesn't solve it either. A supplier with six customers isn't going to learn six different portals. They're going to default to the channel that takes the least effort: email if they're old-school, WhatsApp if they're not. The PO gets issued in the system of record and then negotiated, confirmed and changed somewhere else entirely — a gap that never shows up until the delivery is short, late, or wrong.
The request never enters one system
A site lead texts a supplier directly, an ops manager emails another, and a project coordinator adds a line to a spreadsheet. Three POs exist in three formats before anyone sees the full picture.
Confirmations happen off the record
The supplier confirms quantity, price or a delivery window in a WhatsApp reply. That confirmation is the operative one, but it's invisible to anyone not on that thread.
Changes get made without a paper trail
A supplier swaps a part number, delays a ship date by a week, or splits a shipment. If it's said out loud on a call, it's gone the moment the call ends.
Nobody owns the follow-up
Every open PO needs someone to chase a status update two or three days before it matters. In practice, that chase only happens when someone remembers, which is inconsistent by definition.
The invoice arrives and matches nothing
By the time the invoice lands, it reflects the WhatsApp version of the order, not the original PO. Someone now has to reconstruct what actually happened, usually under time pressure.
| Failure Point | Where It Happens Today | Why It Gets Missed |
|---|---|---|
| PO issued | Email or ERP | Supplier confirms elsewhere, so the "official" version stops being current |
| Quantity or price change | WhatsApp voice note or call | No searchable record, relies on someone's memory |
| Delivery date slip | Text to site lead, not procurement | Office team finds out on delivery day, not before |
| Partial shipment | Driver note or verbal handover | Nobody updates the original PO line items |
| Invoice mismatch | Email attachment, days later | Reconciliation happens against a PO that's already stale |
A Closer Look: Why "Just Use the Portal" Doesn't Work
Every enterprise procurement vendor eventually pitches the same fix: get your suppliers onto our portal, and the visibility problem disappears. It sounds reasonable. It almost never survives contact with reality, especially with small and mid-size suppliers who make up most of the vendor base in construction, industrial equipment and manufacturing.
- Adoption cost sits with the wrong party: You're asking a supplier's sales rep, who might work with fifteen buyers, to learn your specific portal for the small percentage of their business that's you.
- Speed loses to habit: A WhatsApp reply takes ten seconds. Logging into a portal, finding the PO, and updating a status field takes minutes. Under time pressure, habit wins.
- Field reality doesn't match office process: A driver on delivery day isn't opening a laptop to log a partial shipment. He's telling the site foreman, who tells nobody in procurement until someone asks.
- Portals fix the system's view, not the supplier's behavior: The PO can look "confirmed" in your system while the actual conversation that changed it happened somewhere your system can't see.
The fix isn't forcing suppliers to change how they communicate. It's meeting them in the channel they already use and pulling that conversation back into one operational record, automatically, without anyone having to manually copy a WhatsApp message into a spreadsheet at 6pm.
How PashX Outperforms the Competition
- vs SAP Ariba / Coupa: These platforms assume suppliers will adopt a portal. PashX assumes they won't, and captures requests, confirmations and changes directly from the email and WhatsApp threads suppliers already use, no retraining required on their end.
- vs Procore / Kojo: Construction-specific PM tools are strong on the field-to-office gap for tasks and drawings, but supplier chasing is often a secondary feature bolted onto a broader platform. PashX is built around the PO-to-delivery-to-invoice chain as the core loop, not an add-on.
- vs spreadsheets and manual tracking: A spreadsheet only knows what someone remembered to type into it. PashX chases the follow-up itself — flagging a supplier who hasn't confirmed, a delivery that's overdue, or an invoice that doesn't match the PO — and brings it to a human for the judgement call instead of letting it sit unnoticed.
Key Details on Getting This Right
- Capture everything at the source: Requests and confirmations should be pulled in from wherever they actually happen — email, WhatsApp, a shared document, a project system — not re-entered by hand into a fourth place.
- One PO record, not four versions: The moment a supplier confirms a change over text or call, that update needs to land against the original PO, or you're reconciling against a document that's already wrong.
- Follow-ups need an owner that doesn't forget: Every open PO should have a scheduled chase point before the delivery date, not after something's already late.
- Exceptions should surface themselves: A short shipment, a price discrepancy, or a delayed confirmation should get flagged automatically and routed to a person to decide — not discovered three weeks later during invoice reconciliation.
- Humans stay in the loop on judgement calls: Automating the chasing doesn't mean automating the decision. Approving a substitution, accepting a delay, or disputing an invoice line still needs a person to say yes.
Availability and Next Steps
None of this requires ripping out your ERP or telling suppliers to change how they work. The fix is a layer that sits on top of the channels already in use — email, WhatsApp, whatever document or system a request came from — and turns scattered confirmations into one PO record that's actually current. That's a smaller lift than most teams expect, and it's the difference between finding out about a short shipment on delivery day versus three days before.
If you're running procurement across four inboxes, two WhatsApp numbers and a shared spreadsheet, the question isn't whether something will fall through the cracks. It's when, and whether anyone notices before the delivery truck shows up short.
About PashX
PashX is a procurement and project coordination autopilot. It captures requests from email, WhatsApp, documents and project systems, then coordinates suppliers, purchase orders, deliveries, invoices and exceptions in one operational workspace. It chases the follow-ups; you approve the judgement calls. Visit pashx.com.
Ready to get started?
See how PashX coordinates your suppliers, POs and deliveries in one workspace.
Open Admin Dashboard →