Purchase orders from the sold specification: stop retyping the sale

The customer buys a sofa in natural Belgian linen with a deeper seat. The salesperson records the choices correctly. Later, the buyer types “linen, natural, standard depth” into a separate vendor order, because standard is what that frame usually ships in. The difference survives until somebody unwraps the sofa.

Building furniture purchase orders from the sold specification removes that second act of interpretation. OrderPilot carries configured customer lines into purchasing, groups them by vendor, and connects the resulting POs to the orders they serve. Your team still reviews the purchase. It reviews the actual sale, rather than reconstructing it from memory.

Begin with a specification another person can use

The sold specification must identify the piece completely enough for purchasing to order it without consulting the showroom display. Record the model, dimensions, fabric or leather identifier, color, grade, arm style, leg finish, quantity, and any approved instructions that affect what the maker produces. “Same as the floor” is wonderfully brief until someone changes the floor.

An option name should distinguish the customer's choice from a similar one. Natural linen and natural performance linen might sit beside each other in the sample library while carrying different costs and care instructions. The description needs to survive that separation from the sample book.

The source record also needs the commercial agreement: what the customer approved, which terms apply, whether the required signature is present, and whether the order is ready to place. A complete specification that has not been approved is still a proposal. Purchasing should not have to infer approval from an enthusiastic comment on the quote. The special-order process begins in the showroom because that is where uncertainty is cheapest to resolve. Once the customer has left, a missing option creates a call. Once the maker has started, it can create a replacement.

Separate what is sold from what must be bought

Purchasing starts with outstanding demand, not simply every line on an order. A customer may buy stock already in your warehouse, a fresh unit from the maker, and a service such as design time. Those lines require different actions even though they belong to the same sale.

Choose the source before creating the purchase. Stock supplied by this location or another location should not become an unnecessary new vendor commitment. Order New identifies a fresh purchase. Service lines stay out of the PO workbench because they are not physical goods being bought from the furniture vendor.

One customer's quantity can be served through more than one source. If part is available from stock and the rest must be ordered, record the appropriate quantities through the source and line-splitting workflow. Verify the remaining demand before sending a PO. The point is to buy the shortage, not the total again.

The decision between drop ship, stock, and special order includes the destination as well as the source. “Order New” answers where the piece comes from; the PO ship-to answers where the vendor should send it. Neither alone describes the entire route home.

Use the workbench to organize the buying run

The PO workbench brings sold lines together by vendor so purchasing can see the buying job across customer orders. The source order, configuration, quantity, and vendor belong in the same review. That lets the buyer spot a missing fabric choice before it becomes a question in the vendor's inbox. A configured piece can include tracked components that appear as separate purchasing items. Review those components with their parent piece so a frame and the materials required for it remain coherent. A component line is not permission to assume the maker understands an incomplete parent description.

The workbench also supports splitting a customer line across POs. That helps when a quantity must be purchased in separate runs or from different approved vendors. Keep an eye on what each PO covers and what remains outstanding. Splitting the purchase should preserve the connection to the original demand. The workbench guide follows a split in detail. For ordinary stock replenishment, use standalone stock POs through the same purchasing process without inventing a customer sale to justify them.

Review the vendor's requirements before sending

Vendor requirements should be part of the final PO review, rather than something discovered after a rejection. OrderPilot supports vendor quantity and value minimums, allowed vendors on templates, and choices about printing SKUs on that vendor's documents. Those controls help the buyer catch a purchase the vendor cannot use.

A draft can remain below a minimum while you gather the buying run. Sending waits until each enforced minimum is met. A shortfall is a decision to resolve: combine suitable demand, wait, change the purchase, or discuss the requirement with the vendor. Buying an unwanted accent chair merely to satisfy a threshold deserves its own commercial review. The minimums guide explains the difference between quantity and value checks. The vendor-requirements setup guide covers allowed vendors, SKU display, and the other details worth standardizing before a busy market season.

Make the destination unmistakable

The PO destination should name the place the vendor is expected to deliver to, with instructions that fit that place. A showroom, warehouse, and customer's home are different destinations. Verify the address against the order's intended route, especially when the billing address or selling location differs from the receiving location.

For a warehouse shipment, the vendor needs the receiving address and useful delivery instructions. For a drop shipment, purchasing needs to know that the vendor can provide the agreed service and communicate the delivery arrangement. A customer address on a PO does not by itself turn a freight service into white-glove delivery.

Keep requested dates separate from confirmed dates. The requested date states what the store wants. The acknowledgment tells you what the vendor has accepted. Neither should silently become a customer delivery promise without allowing for transport, inspection, and the final appointment.

Give the vendor a document they can act on

The vendor receives the PO with item descriptions, configuration details, quantities, costs, and the destination. OrderPilot supports the store's own PO numbering, and the outgoing email carries the PDF. Review that actual PDF, not only the staff screen, before treating the communication as complete. If the vendor wants a SKU, use the correct item identifier and the vendor's SKU-print setting. Printing an identifier helps only if the identifier distinguishes the item the vendor should make. A frame SKU does not replace upholstery choices that remain part of the specification.

Customer references need particular attention: the PO PDF does not print a per-line customer order number or the PO's Side Label field. Add a clear reference in Vendor notes when the vendor needs it, and review the resulting document. The furniture PO template shows what belongs in the communication, including information the buyer may need to add deliberately.

Distinguish sending from acceptance

A sent PO records an outgoing instruction. An acknowledgment records the vendor's response to that instruction. Treat them as separate milestones, because the response can contain a different cost, fabric, quantity, destination, or ship date.

OrderPilot's email flow lets staff review the message before sending and shows the sending state. Delivery and open activity help the team follow the communication. An open event is a useful signal, but it is not proof that the vendor has accepted the specification or reserved production. With reply capture configured for the email domain, vendor replies and attachments stay on the PO. The team can continue the conversation from the record, and the shared Inbox brings those conversations together on plans that include it. The PO email guide explains that handoff.

Read the acknowledgment against the purchase rather than filing it unread. The acknowledgment checklist makes the comparison concrete: ordered specification, accepted specification, cost, quantity, ship-to, and timing. A document attached to the PO is valuable because another person can find it and use it.

Keep phone and portal orders in the same process

You can still place a vendor order by phone or through the vendor's portal. The important question is how the store records the commitment afterward. If the vendor already has the order, sending another ordinary PO email can create confusion about whether it is a duplicate purchase.

OrderPilot can confirm a PO placed outside the app as sent. Use that path after verifying what was placed, and keep the vendor's confirmation with the purchasing record. The outside-order confirmation guide covers that distinction.

For portal-only vendors, compare the final portal confirmation against the sold specification. A connected PO gives the buyer a dependable starting point, but a separate portal still deserves a final comparison. If the portal changes a choice or rejects an option, resolve that difference before telling the customer the piece is on order.

Follow a sofa through the complete purchase

Say a customer buys a Madison sofa for $5,200, choosing natural Belgian linen, a 38-inch depth, and walnut legs. This is an illustrative sale. The store will receive the sofa first, inspect it, and arrange delivery. A pair of lamps on the same order comes from stock.

Sales records the sofa's choices, obtains the required agreement, and settles the payment arrangement. Purchasing reviews the customer record, sources the lamps from stock, and buys only the fresh sofa. The PO workbench carries the sofa's configuration into the vendor purchase instead of asking the buyer to reconstruct the associate's notes.

Before sending, the buyer verifies Atelier Nord as the vendor, the warehouse as ship-to, and the required SKU display. The PDF contains the 38-inch depth. A project reference is added in Vendor notes because the receiving team and vendor need an agreed label. The buyer reviews the outgoing message and sends the PO with its PDF.

The acknowledgment returns with a standard-depth sofa. That is the moment to stop and resolve the difference. Purchasing replies on the PO, identifies the depth mismatch, and asks for a corrected acknowledgment. The customer has not changed their mind; the vendor has not yet confirmed the right purchase.

After the correction, the accepted specification and ship estimate stay with the PO. When the piece arrives, receiving compares it against the agreed purchase. The order can then move toward customer delivery with the lamps, or the store can agree a split handover. The same record supports that decision without treating the lamp pickup as proof that the sofa arrived.

Handle changes as another agreement

A customer's fabric change after sending is a request to change two connected commitments: the sale and the vendor purchase. Start by establishing whether the vendor can still change the piece, and what happens to cost and timing. Do not promise the customer an unchanged delivery date while that answer is outstanding.

If the change is accepted, revise the customer-facing agreement and obtain the required new signature. Then make the permitted PO changes and communicate the revision clearly. OrderPilot allows edits to supported unreceived quantities and resending of a revised PO; received goods impose restrictions because the receipt already records what entered stock.

The edit, resend, and cancellation guide explains the record controls. It also distinguishes cancelling a PO in the system from securing the vendor's agreement to stop the purchase. The store needs both the accurate record and the actual vendor response.

A discontinued fabric deserves the same discipline. The backorder playbook starts with the affected choices and the customer's decision. For a date change without a specification change, use the vendor-delay communication guide so the internal update becomes a useful customer answer.

Receive the quantities that actually arrived

Receiving should record the physical outcome, including partial shipments and rejected units. A truck at the door is not proof that the entire PO is complete. Compare the arrival with the purchase and record received and rejected quantities against the correct items. OrderPilot connects received units to the customer orders they cover and holds those units for the relevant demand. Standalone stock purchases create stock for future sales through the same buying process. That distinction helps the warehouse avoid selling a customer's arriving piece as uncommitted inventory.

Receipt costs matter too. Freight, duty, and brokerage can be allocated across the purchase using the supported landed-cost methods. With QuickBooks Online connected and mapped, the purchasing flow includes POs and bills associated with receipts. That accounting connection supports the buying record and the cost of the goods; the buyer still needs to review the actual charges.

Separate purchasing from the vendor-payment decision

The PO should agree with the payment arrangement, but a purchase and a payment are different events. Buying staff need to know whether the vendor expects prepayment, a deposit and balance, or payment after an agreed credit period. Otherwise, a perfectly specified order can wait because nobody knew a payment was due.

Use the vendor-payment terms guide to compare those arrangements. For imported purchases, the wire transfer and letter-of-credit guide explains why the payment instrument deserves attention before the first commitment. The terms negotiation guide shows how to bring a concrete purchasing history to that discussion.

Track the outcomes as well as the promises. A vendor scorecard makes timing, damage, fill, and margin comparable. Keep vendor credits visible until they are resolved, and give co-op advertising claims their own supporting records so a promised allowance does not disappear after market.

Use market buying to improve the next buying run

A clean purchasing process begins before the salesperson's first customer order. At market, collect the vendor's ordering requirements, terms, contact details, and product information along with the pieces you like. A beautiful floor sample without usable ordering information creates work for every later sale.

The High Point Market preparation checklist and after-market purchasing plan help turn those conversations into a usable buying list. If you are considering shared purchasing arrangements, the buying-group guide considers that separate business decision.

OrderPilot's POs are the purchasing records for the linked custom-sale workflow described here. You do not need to recreate the same vendor commitment in a second PO system merely to use that connection. Decide which record your team will operate from, especially where ordinary stock purchasing already follows another process. The Shopify purchasing guide covers that broader choice.

Check the handoff before the PO leaves

A final review is easier when each question has a visible answer:

Give one person ownership of the unresolved differences, with a next action that the rest of the team can find. The aim is a buying process another colleague can pick up without repeating the showroom conversation.

For the complete sequence in a single order, continue with signed sale to vendor PO to arrival.