Send a purchase order through the channel the supplier has agreed to accept, then distinguish successful delivery of the message from acceptance of the order. A sent email, read receipt or technical acknowledgement does not by itself confirm quantity, price and delivery date.
Create a supplier-channel register before automating dispatch. For each supplier, record the authorized contact or account, required format, cutoff, expected confirmation, escalation contact and fallback method.
Four common routes
| Route | Good starting point | Verify before relying on it |
|---|---|---|
| Supplier accepts a structured message or PDF PO | Monitored address, reply route, attachment format and confirmation process | |
| WhatsApp Business | Supplier agrees to this business messaging route | Authorized number, supported integration, platform policy and message restrictions |
| EDI | Trading partner specifies electronic documents | Partner mapping, version, test certification, acknowledgements and change handling |
| Supplier portal | Supplier account requires or supports online checkout | Whether submission, confirmation and changes return to your order record |
A supplier can use more than one route, but identify which one creates the order. Sending the same PO through a portal and email without that agreement can create duplicates.
Email: make the request explicit
Include the supplier account, PO number, item identifiers, pack sizes, quantities, agreed price reference, delivery address and requested date. Give the supplier a monitored reply address and ask it to call out substitutions, shortages, price changes and revised dates.
Use this illustrative email as a starting point. Replace the bracketed fields and attach the reviewed PO; the quantities are an example, not a customer order.
Subject: PO [number] — [location] — requested delivery [date]
Hi [supplier contact],
Please find PO [number] attached for account [account number], delivering to [address]. The order includes 10 cases of [item/SKU], 12 units per case, at the agreed $30 per case: $300 before the separately stated tax and delivery charges.
Please confirm the items, pack sizes, quantities, prices and delivery date by [confirmation deadline]. If anything is unavailable, list the quantity available now, the balance due and its expected date.
Please propose substitutions or price changes for our approval before shipping. Reply to [monitored purchasing address] with your order reference and any differences from the attached PO.
Thank you, [buyer name and contact number]
Preserve the sent version. When the reply changes the order, record the proposal and buyer's decision alongside it. A manually maintained history can work; automation is useful when it reduces repetitive capture without hiding uncertainty.
See how to write a purchase order for the document fields and how supplier emails are read for LineNow's supported processing.
WhatsApp: verify the business connection
A supplier's preferred messaging channel may be convenient, but connecting purchasing software requires a supported business setup. Do not assume access to personal chats, group history or every attachment type.
The WhatsApp supplier-ordering guide explains setup, confirmation and duplicate prevention. Check the current WhatsApp business policy, especially when the business handles regulated products or the workflow sends proactive messages.
EDI: test the trading-partner agreement
X12 identifies the 850 as a purchase order, 855 as a purchase-order acknowledgement, 856 as a ship notice/manifest and 810 as an invoice. Its ordering flow also includes change messages. These are related documents with different purposes, not interchangeable confirmations of physical delivery. X12 supply-chain transaction flow.
The partner's implementation guide determines required fields, version and permitted values. Test item and unit mapping, acknowledgement handling, changes, duplicates and errors. An ASN tells the receiver what is expected; it does not prove the cartons arrived as described.
Confirm the actual EDI service and integration rather than assuming a product that mentions EDI supports every trading partner. Include setup and ongoing exception work in the evaluation.
Portals: preserve the external order reference
A portal may provide catalog browsing, account pricing, order submission, shipment status and invoice access. Coverage varies. Check what it knows about your other suppliers, inventory and expected demand instead of assuming those records are connected.
If checkout remains manual, use the purchasing system's reviewed list to place the order and record the supplier's confirmation number. Reconcile changed prices or unavailable items before marking the order confirmed. Do not assume that every portal can be automated or scraped by a procurement app.
For a connected portal route, demonstrate a submission and returned confirmation in the actual supplier account, plus a failed request and retry.
Check the handoff after sending
For any route, the buyer should be able to answer:
- Was this order submitted once to the right account?
- Did the supplier confirm the items, units, price and delivery date?
- Which changes remain unapproved?
- What does the receiving shift expect, and what is still due?
- Which invoice or credit belongs to the order?
LineNow can keep supported supplier communication and receiving context with a living purchase order. Confirm each route and its setup; “multi-channel” is not a promise of universal connectivity.
Before rollout, assign the person who checks unacknowledged orders and resolves failed sends. Use PO status tracking to evaluate one real order, one changed reply and one fallback-channel resend without creating a duplicate commitment.