From signed sale to vendor PO to arrival

Monday morning brings the weekend's signed orders to the buying desk. The salesperson remembers the sofa as “the one with the beautiful linen.” The vendor will need a little more to go on.

Follow Priya at the invented Linden & Oak showroom as she buys Jordan's Madison sofa and dining chairs. This illustrative order shows the chain from the signed specification to the PO, acknowledgment, and partial arrival. OrderPilot carries the configured sale into purchasing, while Priya owns the decisions that make the purchase ready to send.

1. Review the sale before buying from it

Priya starts with the approved product lines, required signature, and payment position. A signature confirms an agreement; it does not prove that every purchasing question is settled. The buyer resolves any held fabric, destination, or release decision before creating the vendor commitment.

The PO workbench groups sold lines by vendor into draft purchases. Jordan's configured sofa appears with the selected fabric, size, and finish. The buyer does not need to reconstruct those choices from the salesperson's recollection. The sold-spec purchasing guide explains that connection. The starting point is the sale the customer approved, with the buyer checking the actual outstanding demand rather than ordering the same units again.

2. Shape the purchases around the supply arrangement

Priya chooses the destination for each PO. Goods intended for consolidation go to the warehouse; a supported direct shipment uses the customer or dropship destination. The receiving contact and instructions should match the location that will actually accept the goods.

A line can be split across purchases when the arrangement requires it. In this sample, four dining chairs are divided into purchases of two and two for separate shipments. The buyer reviews the remaining demand after the first split so the second purchase covers the balance. Tracked options can appear as component items under a configured piece. Review the parent and its components together. A separately tracked component is part of the buying structure, not an invitation to create another whole sofa.

Add the requested delivery date and review the vendor's SKU-display setting. A requested date is the store's instruction, not the vendor's promise. The workbench and split-line guide covers the shaping of the purchase in more detail.

3. Resolve minimums before sending

Vendor minimums can stop a PO from being sent while still allowing Priya to save it as a draft. That is useful when the buyer is gathering demand across the store. An unfinished purchase can remain visible without being mistaken for an order the vendor has accepted. If the store decides to add stock to meet a minimum, make that a real buying decision. Identify the stock configuration, quantity, destination, and expected use. The extra units are store stock, not additional goods silently attached to Jordan's sale.

Priya checks that the combined purchase makes sense before sending. Meeting a minimum by buying unwanted goods may solve the warning on screen while creating a problem in the warehouse. The owner still decides what stock the business should commit to.

4. Send the document the vendor can act on

Priya reviews the email and attached PO PDF before sending. The outward document needs the correct item, specification, quantity, cost, destination, and instructions. A special project reference goes in Vendor notes when it needs to reach the vendor; the internal Side Label does not automatically print. The PO's sending state distinguishes Draft, Sending, and Sent, while the email log records delivery and opens. Read those as communication evidence. An open event does not establish that the vendor agreed to the fabric, price, or requested date. If the vendor accepts orders through a portal or by phone instead of email, Priya places it through that channel, retains the confirmation, and records the PO as sent through the supported process. She does not send a second ordinary order email merely to make the status look right.

The PO email and reply guide explains the conversation setup. The record should say what actually happened, whichever channel the vendor requires.

5. Tell the customer what the event really means

On Professional, a configured connection can move the customer's progress when a PO is sent. Build the condition around the whole purchase state. An order with goods still waiting for a second vendor should not be presented as completely sent merely because the first PO left the desk. The customer-facing email explains that the goods have been ordered. It should not say the sofa is on its way before the vendor has shipped it. Use customer-facing groups for understandable progress and retain the detail on the internal purchase record.

Priya's team also knows who is waiting for the acknowledgment. A status update does not replace that buying task. The customer's confidence should rest on accurate progress, not optimistic wording.

6. Compare the acknowledgment with the purchase

The vendor's acknowledgment needs a line-by-line review. Priya compares the model, fabric, finish, dimensions, quantities, cost, and timing with the PO. A similar fabric description or a different date is a difference to resolve, not a harmless variation in formatting. With reply capture set up, the response and attachment land on the PO and are available to the team. Plans with the shared Inbox bring the conversation into the team's queue as well. Another buyer can continue the discussion without asking for a forwarded personal email chain.

If the acknowledgment shows a later date, Priya establishes the revised commitment and whether it changes the customer's agreed expectation. She records the answer and sends the customer a useful update when needed. A vendor date should not silently overwrite the store's promise without a decision.

The acknowledgment guide explains why this document deserves its own check. Sending the PO starts the conversation; reading the answer makes the commitment understandable.

7. Handle a sent-PO change with the vendor

A sent purchase can require an edit, but the vendor's production state still matters. Review the supported unreceived lines, establish whether the vendor can accept the change, and use the edit and resend process for the agreed revision. Received goods and completed receipts need their own correction process.

If Jordan asks for a different finish after the PO is sent, the customer agreement must be reviewed too. Priya resolves feasibility and cost before the salesperson presents the revised sale. Keep the customer's renewed approval and the vendor's acceptance connected to the same change.

Do not assume that saving a revised PO stops work already underway. The explicit response from the vendor is the evidence that the revised instruction has been accepted.

8. Receive the actual arrival

The receiving team counts and inspects what reaches the warehouse. For the sample chair shipment, two chairs arrive but one is damaged. Record one accepted and one rejected with a reason, while the other purchase and the sofa remain outstanding. Keep photographs and the damage discussion with the purchase, and give the recovery a named owner. The rejected chair is not usable stock merely because it crossed the dock. If a correction is needed later, retain the reason instead of making the first receipt disappear.

Received units are held for the customer orders they cover. Staff can trace the accepted chair back to Jordan's sale and distinguish it from surplus units bought for stock. Use the correct receiving location and the warehouse's physical identification process so the goods are as easy to find as the record.

9. Advance readiness only when the goods support it

A goods-received connection can move an order toward readiness when its configured conditions are met. For Jordan's partial shipment, the team still has a sofa, outstanding chairs, and damage recovery to resolve. The customer should not receive a whole-order delivery promise based on the first accepted chair.

When the required units are accepted, review the customer's delivery arrangement and any balance due. Goods received, goods ready for handover, and goods delivered are separate events. Keep each event tied to what has actually happened.

The Monday routine is repeatable:

1. Review agreement, payment, and purchasing holds.
2. Shape POs from the remaining sold demand.
3. Resolve minimums, destination, and outward instructions.
4. Send or record the actual vendor commitment.
5. Compare the acknowledgment and resolve differences.
6. Receive accepted and rejected units accurately.
7. Review readiness and the next customer update.

Continue with one sofa from showroom to living room for the final handover beyond receiving.