A purchase order acknowledgement is a supplier saying, in writing, ‘yes, we’ll fulfil this, on these terms, by this date’. Large buyers want it as an EDI 855 message. If you’re a supplier with twelve staff and no IT department, you’re not sending an 855, and your customer’s procurement team knows it. What you can do is send an acknowledgement that has every piece of information the 855 carries, on a channel that costs you nothing.
That’s the whole argument of this article. The 855 is a format. The acknowledgement is the promise inside it. Buyers chase you for the second one and ask for it in the shape of the first, and if you send the promise clearly enough, in writing, with the PO number on it, almost every buying team will take it.
What a PO acknowledgement contains
Strip away the syntax and an 855 answers six questions. Your acknowledgement has to answer the same six, whatever it’s written on.
- Which PO. The buyer’s PO number, exactly as they wrote it, plus the date they issued it. This is the single field that makes the rest usable, because it’s how their system finds your reply.
- A decision per line. Accepted, rejected, or changed. Not an overall “yes” for an order where line 3 is discontinued.
- Confirmed quantity for each accepted or changed line.
- Price you’ll actually bill, per line. If it matches the PO, say so. If it doesn’t, this is where you say it, not on the invoice five weeks later.
- A promised ship or delivery date. One real date. “ASAP” isn’t an acknowledgement, and the buyer’s planner can’t do anything with it.
- Your own reference: your sales order number, so both sides can quote it afterwards.
Two more things are worth adding even though the 855 handles them differently: who acknowledged it, and when. A name and a timestamp turn your reply into evidence. When somebody argues in February about a February delivery date you promised in November, the name and the time do more work than the format ever would.
Notice what isn’t on the list. Nothing about a portal login, nothing about a mapped document, nothing about a translation layer. The information is small. It fits in a WhatsApp message.
Why EDI doesn’t fit small suppliers
EDI works, and at volume it works brilliantly. If you ship a thousand order lines a week to Walmart, the 850 in and the 855 back out are cheaper than any human process could be. The problem is that the cost of getting there doesn’t scale down.
You need a translator or a web-EDI service, a connection (a VAN or AS2), and a mapping exercise per customer, because their 855 spec is not the same as the next customer’s 855 spec even though both are called an 855. Somebody has to test it with their team, in their test environment, on their schedule. Then it needs maintaining forever. Pricing for all of this is quote-based and varies enormously by provider and volume, so treat anyone quoting you a flat figure with some suspicion.
Then multiply. The Leverage blog made the point about portals and it lands just as hard here: a supplier serving 60 customers cannot log into 60 portals, and the cost doesn’t sit with the buyer, it sits with the supplier, and it recurs forever. Swap “portals” for “EDI connections” and nothing changes. Your biggest customer’s integration is a cost you might justify. Your fortieth customer’s isn’t, and your fortieth customer still expects an acknowledgement.
There’s a quieter reason too. EDI rewards whoever has staff to maintain it. A ten-person fabrication shop with one office manager doesn’t have a spare person for document mapping, and the acknowledgement doesn’t get sent at all. Not because the shop is disorganised. It just never had the hands.
The plain flow
Here’s the version that works with a phone, an email account and whatever you already use to record orders.
- Take the PO on whatever channel it arrives. Email attachment, portal download, a photo of a printed PO, a WhatsApp message from the buyer’s storeman. Don’t fight the channel.
- Enter it into your own order record first, before replying. You need your reference number and your stock check to exist before you promise anything, and that ordering matters more than it sounds.
- Reply on the same channel the PO arrived on, within one working day, with the six fields above. Same channel, because that’s where their team is looking for you.
- Keep a copy against the order in your record: the text you sent and the date you sent it. If your acknowledgement only exists in a sent-items folder, it’ll be gone by the time it matters.
- Ask for a reply on any line you changed. A change nobody agreed to is not an acknowledgement. It’s a disagreement with a polite tone.
Copy this and edit it. It’s deliberately boring.
That message has everything an 855 carries and one thing it doesn’t: a human name at the bottom. Send it as the body of the email rather than an attachment. Attachments get filed unread, and the buyer’s expediter is scanning for a PO number in a preview pane.
Keep the punctuation plain, by the way. Some buyers run order-entry screens old enough to mangle anything that isn’t ASCII, and curly quotes arrive at the other end as black diamonds. Nobody rejects an acknowledgement over it. They do reply asking what the symbols mean, and that’s a day gone.
Handling changes
This is the part most small suppliers get wrong, and it isn’t a rare edge case. Gartner has found that about half of purchase order lines change after issue, a figure the Leverage blog quotes in its argument about portals. Half. So the acknowledgement isn’t a single event at the start of an order, it’s the first of several.
Keep two ideas apart. Acknowledging the original PO means you’re agreeing to what they asked. Acknowledging a change means you’re proposing something different and waiting to hear back. Same message format, completely different status in your own head and in your order record.
A few rules that save arguments later:
- Always quote the buyer’s PO number and their line number when you change something. Their planner is looking at a line, not at your message.
- Change one thing at a time where you can. A message that moves a date and a price and a quantity gets half-answered.
- Say what happens if they don’t reply. “If I don’t hear back by Wednesday I’ll ship the 30 and hold the balance” is a fair default, and it stops a silent thread from stalling your production.
- Re-acknowledge when they revise the PO. A revised PO is a new promise, and the old one shouldn’t be sitting in your record as though it still stands.
Price changes deserve their own sentence. If your cost went up between quoting and receiving, the acknowledgement is the last comfortable moment to say so. After that you’re raising it on an invoice, which is where relationships actually break, because their accounts team finds it and yours didn’t warn them.
When the buyer is on a shared order book
There’s a third option between EDI and a message you type out each time, and it’s the one worth knowing about because it costs the supplier nothing to join.
If the buyer places their order in a system that shows both sides the same record, their placed order simply arrives as your received order. You don’t rekey it. The PO number, the lines, the quantities, the requested date are already there, because they’re the buyer’s own entry rather than a document you’ve had to interpret. Acknowledging is a tap, per line if you need it, and the buyer’s board updates the moment you do. That’s the model OrderBookApp is built on: one order record that the buyer sees as an order placed and you see as an order received, with WhatsApp carrying the message when the other side isn’t on the app yet.
The honest limit: this only helps for customers who use it. You’ll still have the big national account that runs Ariba and wants an 855, and the builder who sends POs as photos of a printed pad. Your acknowledgement habit has to work across all three, which is why the template above matters more than any tool.
What to say to a buyer who insists on EDI
Sometimes it’s a genuine requirement written into a supply agreement, and sometimes it’s a procurement analyst repeating what the onboarding form says. Find out which before you spend money.
Ask three questions, in this order:
- What do you do today with suppliers our size? Most large buying teams already have a manual lane, and the person you’re talking to may not be the one who runs it.
- Which documents do you actually need from us? Often it’s the 856 advance ship notice and the label that matter operationally, and the 855 is on the list because it was on the template.
- Will you accept an emailed acknowledgement with the PO number, line status, confirmed quantities, price and ship date? Put the sample in the email when you ask. Showing them the message is more persuasive than describing it.
If the account is big enough to justify it, a web-EDI provider is the sensible answer: you log into their web form, fill in the acknowledgement, and they turn it into a compliant 855 on your behalf. No translator to run, no VAN to manage. Pricing is quote-based and usually tied to document volume, and some buyers subsidise it for suppliers they care about, so ask the buyer before you sign anything.
And if the account isn’t big enough? Then the acknowledgement above is what they’ll get, and you say that plainly rather than going quiet. Most buyers accept it. The ones who don’t tend to be the ones whose chargeback schedule you should have read before quoting.
One last thing, because it’s the habit rather than the format that decides this. Set yourself a rule: every PO gets an acknowledgement the same working day, even when the answer is “received, checking stock, full confirmation tomorrow morning”. That holding reply takes eleven seconds and it stops the expediting call. Suppliers who do it get treated as reliable by buying teams who’ve never once asked what system they run it on.
Keep reading
- Supplier portal alternatives compares EDI, email and PDF, spreadsheets and chat, and says when each one is the right call.
- Customer order portal for wholesalers is the wider vendor-side view if your customers order by voice note.
- How to get suppliers to confirm orders shows the same problem from your buyer’s side, which is useful when you’re the one chasing.