The purchase order stretch, after the customer has decided to buy and before the work starts, is where a lot of avoidable B2B frustration lives. The customer has to raise a PO, route it through their own approval chain, and send it to you, while your team receives, matches, and processes it. The customer cannot tell whose delay is whose. If the PO takes two weeks, you feel slow, regardless of which side caused it.
Last updated: July 2026.
For most B2B customers, deciding to buy is the easy part. Then comes the purchase order. The customer has to raise a PO, route it through their own internal approvals, and get it issued before any money can move. And on your side, that PO has to be received, matched, and processed before fulfillment begins.
This middle stretch, after the decision and before the work, is invisible in most experience programs. But it is where a surprising amount of customer frustration lives. The customer has decided to spend money with you and is now stuck in process, often on both sides of the table at once.
The purchase order experience, from the customer's side
Put yourself in the customer's seat. They have championed your product internally, gotten budget approved, and committed. Now they have to:
- Raise a purchase order in their procurement system, often with details they have to chase you for.
- Route it through their own approval chain, which may involve managers, finance, and procurement.
- Send it to you and confirm you received it.
- Wait while your team matches it against the order and the eventual invoice.
Every step is a place to stall. And from the customer's perspective, the distinction between their delay and your delay is meaningless. If the PO process feels slow, you feel slow.
The customer does not see your approval workflow or theirs. They see how long it takes to go from yes to delivered.
Where PO friction comes from
PO friction is usually a combination of manual handling and poor visibility. POs arrive by email as PDFs and get re-keyed into your system by hand, which is slow and introduces mismatches. Nobody can see where a given PO is in the approval chain, so it gets chased by email. Matching the PO to the order and the invoice is a manual three-way reconciliation that finance does under deadline pressure. Each of these adds days, and days right after the decision are the most damaging kind. In organizations that buy through formal procurement, the PO is only the last leg of a longer chain that began with the RFP process, so a customer who already spent months evaluating you feels every extra approval day acutely.
Smoothing this out is mostly about removing manual steps and adding visibility. Dedicated purchase order management software handles the intake, approval routing, and matching as a structured workflow instead of an email chain, so a PO moves through approvals predictably and everyone can see where it is. The result the customer feels is simple: less waiting between commitment and delivery, and fewer "where are we on the PO" emails.
Why do B2B customers need a purchase order?
A purchase order is the customer's internal authorization to spend, issued before the money leaves. It commits budget, records who approved the expense, and gives their accounts payable team something to match your invoice against. Without a PO number on your invoice, many companies' AP systems will not pay it, no matter how valid the charge is.
That last point is the one vendors underestimate. A missing PO reference is not a formality, it is a hard stop in the customer's payment process, and the invoice will sit unpaid without anyone telling you why. Capturing whether an account requires a PO, and what that number is, belongs in onboarding rather than in a collections call sixty days later, which is one more reason a written client onboarding checklist pays for itself in cash collection alone. Left uncaptured, it shows up later as a line on your accounts receivable aging report that nobody can explain. On the receiving side the same document drives your own matching, which is why the accounts payable process is built around the purchase order, the receipt, and the invoice agreeing with each other.
How long does purchase order approval take?
In most mid-sized companies a routine PO clears in two to five business days, and anything above a departmental spend threshold takes longer because it picks up finance and sometimes executive approval. The variable is almost never the reviewing, it is the waiting: each approver's queue adds a day whether the decision takes ten seconds or ten minutes.
| Where the time goes | Typical cost | What removes it |
|---|---|---|
| Customer chases you for details to raise the PO | 1 to 3 days | Send a quote with every field their system needs, unprompted |
| Sequential approval chain | 1 day per approver | Parallel approvals for anything under a threshold |
| PO emailed as a PDF and re-keyed on your side | Hours to a day, plus mismatches | Structured intake instead of manual entry |
| Mismatch between PO, order, and invoice | Days, sometimes a full billing cycle | Match at receipt, not at invoice time |
The first row is the one entirely within your control and the one most often ignored. If the customer has to email you twice to find out your legal entity name, remit-to address, or line item descriptions, you have added days to your own cash collection for no reason.
Designing a PO process customers do not dread
You cannot control the customer's internal approval chain. You can control everything on your side and make their side easier. A few practices:
- Give them what they need to raise the PO. Clear line items, your billing details, and the right reference numbers, up front, so they are not chasing you to fill in their own form.
- Confirm receipt and status. The moment a PO arrives, confirm it and tell the customer what happens next. Visibility kills anxiety.
- Automate the matching. Three-way matching of PO, order, and invoice should not be a manual invoice reconciliation done at month end. It should be routine and fast, which is why it pays to formalize the invoice approval workflow the PO eventually feeds into.
- Connect approval to fulfillment. An approved PO should trigger the next step automatically, so the customer never sits in the gap between approved and started.
The purchase order is the most procedural moment in a B2B relationship, which is exactly why it is so easy to neglect and so powerful to get right. A customer who experiences a fast, visible, painless PO process learns that you are easy to do business with, in the most literal sense. The same procedural friction shows up on the supplier side too, where vendor and partner onboarding paperwork stalls relationships in exactly the same way. For the broader pattern, see our piece on why customer experience is won in the back office, and how the whole discipline of customer experience operations treats moments like this as the place the experience is actually delivered.