Skip to content
James DarbyJames Darby
November 15, 2026
Last reviewed November 15, 2026
10 min read
Order Management

Order Acknowledgement: What to Include

What an order acknowledgement is, the fields it needs, a copy-ready email template, line statuses for backorders and changes, and how it differs from a 997.

An order acknowledgement tells the buyer, line by line, what will actually happen to their purchase order. The buyer sent a PO for 40 lines. Your acknowledgement says 37 ship as ordered on Thursday, two are backordered to the 24th, and one item is discontinued. Without it, the buyer finds out when the shipment arrives short, and the first conversation you have is about a chargeback.

The spelling varies. "Acknowledgement" is common in British English and in a lot of US business writing, "acknowledgment" is the US dictionary spelling, and EDI guides use both. They mean the same document.

This guide covers what to include, a template you can copy, the line statuses that matter, how the acknowledgement differs from a confirmation and a 997, and how to stop writing them by hand.

What Is an Order Acknowledgement?

An order acknowledgement is the supplier's written answer to a purchase order, and it turns the buyer's request into a shared plan. A purchase order is the buyer's offer. The acknowledgement is your answer to it, and it does three jobs:

  1. Confirms receipt: The buyer knows the PO reached someone who will act on it.
  2. Commits to what you will ship: Quantities, prices and dates, per line, with any differences from the PO spelled out.
  3. Sets your terms: If you sell under your own terms and conditions, the acknowledgement is where you state them. When buyer and seller terms conflict, UCC section 2-207 decides which ones survive between merchants, and a written acknowledgement puts your terms on the record. Check your own wording with a lawyer.

The most useful acknowledgement is the one that reports problems early. "All lines accepted" is easy to send. "Line 14 is short 18 units until the 24th, do you want a partial shipment or should we hold?" is what saves the order.

What to Include in an Order Acknowledgement

Every acknowledgement needs the buyer's PO number, your own order number, and a status for each line. The full set of fields:

FieldExampleNotes
Buyer's PO number4500087321Copy it exactly. A missing or mistyped PO number breaks the buyer's matching
PO date2026-11-10The date on the PO, not today's date
Your sales order numberSO-30418So the buyer can quote it back to you
Acknowledgement date2026-11-11When you sent it
Ship-toDC 7034, Joliet ILConfirms you read the right delivery location
Line number and itemLine 3, SKU 88-1204Use the buyer's line numbers and item numbers
Quantity ordered vs confirmed48 ordered, 30 confirmedShow both when they differ
Unit of measureCS (case of 12)Confirms what "48" means
Confirmed unit price$14.20Flag any difference from the PO price
Line statusAccepted, changed, backordered, rejectedThe core of the document
Expected ship or delivery dateShips 2026-11-13Per line if dates differ
TermsPayment, shipping, your T&CsOr a link to them

Order Acknowledgement Template

Here is a plain-text template that works for email. Replace the bracketed fields. Keep the line table even when every line is accepted, because buyers' teams scan it.

Subject: Order acknowledgement: PO [PO number] from [Your company]

Hello [Buyer name],

We have received purchase order [PO number] dated [PO date] and
entered it as our sales order [SO number].

Line  Item        Ordered  Confirmed  Price    Status       Ships
1     [SKU]       24 CS    24 CS      $14.20   Accepted     [date]
2     [SKU]       6 CS     6 CS       $31.00   Accepted     [date]
3     [SKU]       48 CS    30 CS      $9.75    Partial      [date]
3     [SKU]                18 CS               Backordered  [date]
4     [SKU]       10 CS    0          -        Rejected     Discontinued

Changes from your PO:
- Line 3: 30 cases ship [date]; the remaining 18 follow on [date].
  Reply by [date] if you would rather cancel the backorder.
- Line 4: item discontinued. Suggested replacement: [SKU].

Ship-to: [address]
Payment terms: [terms]
This order is accepted under our terms of sale: [link]

[Your name]
[Company] | [phone]

If nothing changed, delete the "Changes" block and say "All lines accepted as ordered."

Line Statuses: Accepted, Changed, Backordered, Rejected

The status on each line is what the buyer's planning team acts on. EDI formalizes these as codes. The plain-language versions map to them directly:

StatusWhat it meansEDI 855 code
AcceptedShips as orderedIA
Quantity changedShips, but a different quantityIQ
Price changedShips at a different priceIP
Date changedShips on a different dateDR
BackorderedWill ship later, when stock arrivesIB
SubstitutedA different item ships in its placeIS
RejectedWill not shipIR

A single line can carry more than one status. The template above splits line 3 into 30 cases shipping now and 18 backordered, which is exactly how the EDI version works: the acknowledgement repeats the status segment for that line. The full code list and segment layout are in our EDI 855 PO acknowledgment guide.

"Backordered" means the order is still open for that quantity and you will ship when stock returns. If you will not restock, use rejected or substituted instead. A backorder you never fill looks like a broken promise, which is worse than a clear "no." More on the difference in our glossary entry on the backorder.

Order Acknowledgement vs Order Confirmation vs 997

Three documents get called "acknowledgement," and they answer different questions.

DocumentWho sends itQuestion it answers
EDI 997 functional acknowledgmentReceiving system, automaticallyDid the file arrive and parse correctly?
Order acknowledgement (EDI 855)SupplierWhat will you ship, at what price, and when?
Order confirmationSeller, often a webshopWe got your order (usually no line-level changes)

The EDI 997 functional acknowledgment is purely technical. Your EDI system sends it within minutes to say "file received and readable." It says nothing about whether you can fill the order. Suppliers who send 997s and no 855 to a buyer who requires the 855 still fail compliance.

"Order confirmation" usually means the automatic "thanks for your order" message from an online store. In B2B the terms blur, and some buyers call the acknowledgement a confirmation. If their vendor guide says "confirmation," check whether they want line-level detail. They usually do.

If the buyer later changes the PO, the change gets its own acknowledgement. In EDI that pair is the EDI 860 PO change and the 865 change acknowledgment.

When to Send It

Send the acknowledgement after you have checked stock, price and items, and before you start picking. Acknowledging before you check makes it a receipt, not a commitment. Acknowledging after you ship makes it pointless.

The buyer's vendor guide sets the deadline, and many retail EDI programs track late or missing acknowledgements as compliance failures. Without a written deadline, same business day is a good standard. Fast acknowledgements give the buyer time to source a backordered item elsewhere, which is the difference between a minor change and a cancelled order.

How to Automate Order Acknowledgements

Acknowledgements are slow by hand because they need the order already entered and checked. Someone keys the PO into the ERP, checks stock and prices line by line, then types the acknowledgement. For a supplier receiving 100 POs a day, that is a full-time job.

Automating it means connecting the steps:

  1. Read the PO from whatever format it arrives in: EDI, PDF, email or spreadsheet.
  2. Validate each line against your item master, customer price list and available stock.
  3. Create the sales order in the ERP.
  4. Generate the acknowledgement from the validated order: an 855 for EDI buyers, an email or PDF for everyone else.
  5. Hold real exceptions (unknown item, price mismatch, stock short) for a person, and send everything else straight through.

OrderSync does this for multi-format orders: EDI 850s and emailed PDFs go through the same validation, and the acknowledgement goes back in the format each buyer expects. To check what your current 855s actually contain, paste one into the free EDI Inspector. The underlying standard is maintained by X12, which publishes the 855 transaction set alongside the 850, 856 and 810.

For the document the acknowledgement answers, see what is a purchase order.

Standards and References

  • X12 transaction sets: the 855 purchase order acknowledgment, 865 change acknowledgment and 997 functional acknowledgment are all X12 transaction sets.
  • 004010 855 structure: the segment order of the EDI acknowledgement, including the ACK loop under each line.
  • ACK01 line item status codes: the full list of line statuses used in the table above.
  • UCC section 2-207: how US law treats an acceptance that adds or changes terms between merchants.

Frequently Asked Questions

What is an order acknowledgement?

An order acknowledgement is a supplier's response to a purchase order. It confirms the order was received and states, for each line, what will ship, in what quantity, at what price and on what date. It flags anything that differs from the PO, such as backorders, price changes or rejected items.

Is it acknowledgement or acknowledgment?

Both spellings are correct. "Acknowledgment" is the standard US dictionary spelling, and "acknowledgement" is standard in British English and widely used in US business. EDI documentation uses both, for example "purchase order acknowledgment" for the 855 and "order acknowledgement" in many vendor guides.

What is the difference between an order acknowledgement and an order confirmation?

In B2B, an order acknowledgement gives line-level detail: what ships, what is backordered, what changed. An order confirmation is often just a notice that the order was received, typical of online stores. Some buyers use the terms interchangeably, so check their vendor guide for the detail they expect.

What is a purchase order acknowledgement in EDI?

In X12 EDI, the purchase order acknowledgement is the 855 transaction set. The supplier sends it in response to an 850 purchase order. It carries the PO number, an overall acknowledgement type, and a status code for each line, such as IA for accepted or IB for backordered.

Does a 997 count as an order acknowledgement?

No. A 997 functional acknowledgment only confirms that an EDI file arrived and was structurally valid. It says nothing about whether the supplier accepts the order. Buyers who require an 855 will treat a 997 alone as a missing acknowledgement.

Is an order acknowledgement legally binding?

An acknowledgement that accepts a purchase order generally forms the contract. If it adds or changes terms, US law under UCC section 2-207 decides which terms apply between merchants. Get legal advice on the terms you attach to acknowledgements.

James Darby

Related Articles

More from the Blog

Related Resources