Emailing POs and keeping vendor replies on the PO

The vendor's email about the backordered walnut legs is in the buyer's personal inbox. The buyer is on vacation. The customer is on the phone. Somewhere, an out-of-office reply is enjoying a more restful week than the showroom.

OrderPilot keeps vendor correspondence with the PO when reply capture is configured. Staff send the purchase with its PDF, review the communication activity, and find the vendor's replies and attachments beside the purchase. The next person can answer from the record instead of searching for the person who placed it.

Compose the message around the purchase

The PO email should tell the vendor what the store is asking it to do and include the document that defines the purchase. Start from the PO record, review the recipient, and inspect the attached PDF. The configuration, quantity, destination, and instructions should agree with the message. A useful message can be brief: identify the purchase, request acknowledgment, and draw attention to a detail that needs confirmation. Avoid rebuilding the entire specification in the email body. Two separately typed versions give the vendor two opportunities to find a difference.

For the full preparation stage, use purchase orders from the sold specification. The email is the handoff of that reviewed purchase, so an unresolved destination or fabric question should be settled before a routine order message goes out.

Read the sending state before assuming the vendor has it

The PO's sending state shows whether the outgoing step is still in progress or has completed. OrderPilot also records delivery and open activity in the email log. Read those signals for what they establish: a message was sent or delivered, or an open was recorded. None is the vendor's acceptance of the purchase. If delivery fails, resolve the contact or sending problem before treating a resend as useful. If the message is delivered but the acknowledgment does not arrive, follow the vendor's agreed response arrangement. A phone call can clarify whether the right person has the PO; the resulting answer should still be captured in the purchasing record.

Do not use the absence of an open event as proof that nobody read the email. Likewise, a recorded open does not prove the maker checked the leg finish. The acknowledgment guide explains the separate comparison that follows.

Turn on the reply route for the sending domain

Receive replies is the setup that brings incoming responses back into OrderPilot. It requires an MX record on the replies subdomain of the sending domain. The person managing the domain adds the record shown by the app, then the setup is checked before your team relies on it.

That setup is separate from writing a polished outgoing message. A branded sender can be working while incoming replies still need configuration. The sending-domain setup guide covers the domain work and the checks the store needs.

Test the complete exchange with sample data: send a PO, reply to that message, attach a harmless sample document, and open the PO conversation. The team should see the response and attachment on the correct record. That proves more than looking at a settings switch alone.

The vendor uses ordinary email. It does not need an OrderPilot account or a portal login to receive the PO and reply to the conversation. Give vendors the correct reply path, and make it part of the way your buyers communicate.

Keep the acknowledgment and supporting files together

The reply thread can hold the vendor's acknowledgment, revised information, and supporting attachments. Buyers can attach their own files as well, such as a drawing, finish photograph, or customer-owned-material instructions. Use clear filenames and explain which purchase and item each attachment concerns. A drawing is most useful when the vendor knows what it approves or clarifies. Identify the item, the version, and the question it answers. If a finish photograph is only a reference rather than an agreed substitute, say so. An image can make a detail clearer without replacing a written specification.

When an acknowledgment differs from the purchase, record the difference and ask for a response. Do not simply attach the document and move the conversation to Waiting. The next colleague should be able to see what is unresolved without comparing every attachment from the beginning.

Bring personal-inbox replies back into the record

A reply sent to an individual's address will not automatically become part of the PO merely because it mentions the same sofa. If the vendor bypasses the captured reply route, bring the relevant confirmation or attachment into the PO record and continue through the PO conversation.

Keep the original wording available when it affects a commitment. A summary that says “vendor confirmed” can lose the sentence that limits the confirmation to the frame while the fabric remains outstanding. Use an internal note for the team's interpretation, with the supporting vendor document attached where possible.

Ask the vendor to reply to the PO email on the next exchange. The aim is to make the useful route the ordinary habit. There is little value in a well-connected system if the decisive answer lives elsewhere every time.

Give the shared Inbox an owner for each conversation

The shared Inbox on Growth and Professional helps the team assign vendor conversations and work through views such as Needs reply and Waiting. Use assignment to make responsibility visible, particularly when purchasing work moves between shifts or someone is away. An internal note should explain the next action, not merely repeat the last email. “Awaiting confirmation that the darker legs are available; buyer to follow up before release” is more useful than “see below.” The shared Inbox guide develops that team routine.

Vendor conversations stay with their PO and are not customer conversations. If a vendor message affects the customer, send a separate customer-facing explanation from the order. Keep supplier costs and internal purchasing discussion out of that message, while preserving the facts the customer needs to decide what happens next.

Identify revisions so the vendor knows which PO to follow

Changing a PO after sending requires another communication. OrderPilot supports editing permitted unreceived lines and resending the updated purchase. Identify what changed, attach the current PDF, and ask the vendor to confirm the revision. The earlier message remains part of the history rather than silently becoming a different instruction.

Say a sample sofa's agreed legs change from walnut to oak before production. The buyer confirms feasibility with the vendor, the customer agreement is revised through the appropriate process, and the PO is updated. The resend message should make the changed leg finish explicit. A vendor reading quickly should not mistake it for another order for a second sofa.

If goods have already been received, the available edits are restricted by those records. Use the edit and resend guide for that boundary and for cancellation. A system change should describe the real purchasing event, not attempt to erase it.

Try a week of purchasing from the record

For a one-week trial, route vendor purchase emails through their POs and keep acknowledgments with the same records. This is a suggested team exercise, not a promised implementation time. At the end, ask a colleague who did not place an order to explain its latest vendor answer and next action.

The exercise exposes the missing pieces quickly: a private reply, an attachment without an explanation, an unassigned question, or a revision the vendor has not accepted. Fix the handoff that caused each gap. Then use the acknowledgment checklist to make the vendor's answer as dependable as the outgoing purchase.