Purchase order acknowledgments: check what the vendor actually accepted

The PO asks for walnut legs. The acknowledgment says oak. The PO requests an early ship week. The acknowledgment puts it later. Both documents reach the same inbox, but only the first gets a careful read.

A purchase order acknowledgment records what the vendor says it has accepted, including any differences from your request. Compare it with the PO before treating the purchase as settled. The vendor's accepted ship estimate is more useful than the date you asked for, but it still needs to remain distinct from shipment and customer delivery.

Read the acknowledgment as an answer

The acknowledgment should identify the purchase and confirm its items, specifications, quantities, prices, destination, and shipment arrangements. A formal PDF is useful, but the purpose is the vendor's clear written answer. A small workshop can supply that answer in an email if it addresses the same details.

Shipment-schedule templates commonly separate dates and quantities by item; the Business in a Box acknowledgment template is one example of that document structure. The practical lesson is to ask what each line is waiting for, rather than accepting one unexplained date for a roomful of furniture.

The acknowledgment explainer covers the definition. In the buying routine, make the distinction visible: PO sent, acknowledgment received, acknowledgment checked, and differences resolved are different events. A document sitting in a folder has completed only the filing part.

Compare the details that can change the purchase

Use the same review every time so a familiar vendor does not receive a lighter inspection than a new one. Start with the PO number and the vendor's reference, then compare the individual lines.

The material details deserve more than a glance. A maker's shorthand can be harmless, or it can conceal a different finish. Ask what an unfamiliar code means instead of assuming it is the vendor's charming way of spelling walnut.

Keep ship estimates tied to the actual order

A catalog lead time is a planning input; the acknowledgment is the vendor's answer for this purchase. Record when that answer was given and what it depends on. A production estimate contingent on fabric arrival should not become an unconditional delivery promise in the showroom.

The pandemic backlog showed how far a maker's timing could move. In August 2022, Business of Home reported one upholstery maker at 34 weeks after a peak of 51, compared with six to eight before 2020. That is a historical account of one maker, not an industry average or a current expectation. Business of Home's reporting also identified fabric availability as a constraint.

For your own orders, preserve the original requested date, the vendor's accepted estimate, and later changes. Recording the latest date without its history makes it difficult to see whether the purchase is progressing or merely being rescheduled.

Give purchasing ownership and sales the customer decision

The buyer should own the acknowledgment comparison because purchasing understands the vendor commitment. The salesperson should be brought in when a difference affects the customer's choices, price, or expectations. Assigning both people without naming an owner tends to leave each waiting for the other.

Agree a response window with each vendor and set the next follow-up when the PO is sent. You might ask a small workshop to confirm by the next business day, but that is an arrangement to agree, not an industry rule. Chase the unanswered purchase when the agreed window passes.

If a vendor never sends formal acknowledgments, request a written confirmation of the key details. Summarize a phone conversation back to the vendor and ask it to confirm the summary. Keep any uncertainty visible until the answer arrives; a successful phone call is not a reason to invent a confirmed ship date.

Resolve a higher acknowledgment price before proceeding

A higher vendor price is a difference to investigate, not an automatic instruction to charge the customer more. Ask whether the cause is a different fabric grade, a missed option cost, freight, a changed price list, or an error. Compare the vendor's explanation with the quote or terms on which the purchase was based.

Say an illustrative pair of chairs was ordered at $600 each, but the acknowledgment shows $650 each. The difference is $100 for the pair. Purchasing identifies the reason and the store decides whether to accept it, negotiate, or pursue another permitted option. Any customer-price change needs its own customer agreement; the maker's document does not provide that approval.

Update the purchasing record to reflect the accepted result. If the quoted customer price stays unchanged, the vendor increase affects the store's margin. Hiding it by leaving the old PO cost makes the buying record less useful precisely when the cost deserves attention.

Keep the acknowledgment beside the PO in OrderPilot

With Receive replies configured, a vendor acknowledgment sent in reply to the PO email lands on the PO conversation with its attachment. Your team can review the response beside the purchase rather than searching a personal inbox. The vendor-email guide covers the setup and team habits. Email activity shows the outgoing communication's delivery and recorded opens. Use it to guide follow-up, then obtain the actual acknowledgment. On Growth and Professional, shared Inbox views and assignments help the team manage conversations that need a reply or are waiting on the vendor.

OrderPilot has no dedicated confirmed-ship-date field for each PO line, so keep the vendor's dated confirmation in the PO conversation. Identify the line and date clearly in the message. That gives the next colleague a usable answer without implying that an option lead time is a confirmed manufacturing commitment.

Correct the mismatch on the right side of the agreement

An acknowledgment that says oak when the approved purchase says walnut should first be corrected by the vendor. Do not edit the PO to oak merely to make the documents agree. Matching documents are useful only when they describe the piece the customer actually approved.

If the store and customer accept a genuine change, revise the customer-facing agreement and obtain the required new signature. Then update the permitted unreceived PO line and resend it with a clear explanation. Keep the vendor's acceptance of the revised purchase with the conversation. An internal custom order status such as Vendor confirmed can help the team distinguish a checked purchase from an unanswered one. Use Next status for that staff step and keep its meaning consistent. It is an order status you configure, not a dedicated PO acknowledgment state.

Tell the customer the delivery estimate you can support

The customer's delivery estimate should account for the vendor's ship estimate plus the route home: transport, receiving, inspection, and appointment arrangements. Explain the milestone you are reporting. “The maker expects to ship” is different from “we will deliver.”

If only one piece is late, name it and explain what happens to the others. The vendor-delay guide covers that conversation. Do not let one aggregate date conceal a chair that will hold up the whole room.

Print a short acknowledgment checklist

Use this card at the buying desk:

- Match the PO and vendor reference. - Compare every line's cost, quantity, specification, ship estimate, and destination. - Identify each difference and the person resolving it. - Preserve the vendor's written confirmation and any revisions. - Update the customer when the agreed sale or delivery expectation changes. - Record the next follow-up for anything still unanswered.

Repeated late or inaccurate acknowledgments belong in the vendor scorecard. For the complete buying sequence, return to purchase orders from the sold specification.

Sources

1. Shipment schedule acknowledgment of purchase order template — Business in a Box; document structure only.
2. Is the lead time crisis almost over? — Business of Home, August 17, 2022; original reporting from an upholstery maker.