The four handoffs where special orders break

The sofa arrived on Tuesday, wrapped and labeled. It stayed in the warehouse for nineteen days because receiving put it away and nobody told the delivery desk. The customer discovered it had arrived when she called. In this illustrative case, the missing step was a handoff between people who had each completed their own task.

Audit special orders at the boundaries: sales to purchasing, purchasing to receiving, receiving to delivery, and delivery to service. At each boundary, identify the record the next person needs and the signal that tells them to act. OrderPilot keeps those records connected to the sale.

Find the gap between “done” and “ready for you”

A department's task can be finished while the order is still waiting. The associate has a signature, but purchasing has not checked the configuration. The buyer sent a PO, but receiving cannot identify its cartons. The warehouse accepted the sofa, but no one has contacted the customer.

Look for the receiving person's evidence. Can they open the record and see what is complete, what remains uncertain, and what they now own? If the answer depends on catching a colleague in the hallway, the handoff is fragile.

The special-order playbook defines the whole procedure. This audit concentrates on the information that has to cross each boundary. It works even when the same employee wears several hats; the change of task still needs a clear completion signal.

Handoff one: carry the agreed specification into purchasing

Sales hands over the piece the customer agreed to buy. Purchasing needs the model, size, fabric identifier and grade, finish, arm style, quantity, and any special instructions. It also needs the payment and approval position and the customer's delivery expectation.

“The blue one” is not a purchasing specification, even if everyone at the appointment knew exactly which blue. Upholstery libraries have a remarkable ability to contain another blue.

Give purchasing the current signed version and flag any unresolved choice before the PO is sent. Define when a complete, released order should be purchased so it does not wait behind unrelated office work. If the order is not ready, leave a specific reason and an owner for the correction.

OrderPilot's PO workbench builds purchasing lines from the configured customer order and groups them by vendor. Vendor minimums are checked before sending. Staff can review the actual choices without recreating them in a separate document. The showroom-to-PO guide explains how to make the first record complete. The handoff is finished when purchasing can use it confidently and knows which order it is authorized to place.

Handoff two: make the arriving cartons identifiable

Purchasing hands receiving an expected shipment, not just an emailed PO. Receiving needs the vendor's reference, the goods and quantities expected, the linked customer order, and any differences found in the acknowledgment. The acknowledged dispatch date belongs with that record.

Read the vendor's reply while there is time to correct an error. A changed fabric code, split shipment, or revised date should not become a discovery at the dock. With reply capture configured, OrderPilot keeps vendor replies and attachments on the PO so receiving and the order desk can find the same evidence. If a packing slip lacks your customer order number, match the vendor PO reference, SKU, configuration, quantities, and carton information to the linked PO lines. Ask the vendor to include an agreed reference in the packing paperwork. Where needed, put a reference in the PO's Vendor notes, which prints.

OrderPilot does not print the stored per-line customer order number or Side Label on its PO PDF, so do not rely on those fields to identify cartons at arrival. Staff can use the linked customer-order information on the PO and the documented vendor references to reconcile the goods.

When the goods arrive, record received and rejected quantities against the correct PO. If only part of a set is present, keep the remaining quantity outstanding. The signed-sale-to-arrival walkthrough follows that record across the purchasing boundary.

Handoff three: turn receipt into a delivery decision

Receiving hands delivery a statement about actual goods: which pieces are here, which are saleable, where they are stored, and which are still outstanding. The delivery coordinator also needs the current balance and any customer arrangements that affect release.

On Professional, a status-map connection can respond to receiving, move the order to the appropriate readiness stage, and notify the staff responsible for the next action. A full-readiness condition needs all the required goods; a partial arrival should remain visibly partial. Use the Orders list and its pickup-related views to find the next work, then inspect the line details. Stock reserved for the customer should remain connected to that order. The stock-held-for-orders guide explains why a ready sofa must not become another salesperson's available floor piece.

Name who tells the customer. In a small store that may be the order-desk person; in a larger operation it may be the delivery coordinator. That person should make contact after the receipt and release information is clear, rather than assuming an automated arrival message has arranged a delivery.

When receiving finds damage, separate the affected goods from saleable stock and record the exception. Keep photos and the vendor follow-up with the purchasing record, assign the remedy, and tell the coordinator before they offer a delivery slot. The customer needs a truthful explanation of the affected piece and the next update.

Handoff four: give service the actual delivery record

Delivery hands service the end of the sale's physical journey. Record which units were delivered or collected and when, along with serial numbers where the process calls for them. A whole-order completion label cannot substitute for a unit that was delivered later than the rest.

This matters because customers expect the relationship to continue. In Home News Now's 2025 Consumer Insights Now account of in-store shopping, 69% of the in-store shopper group wanted a store relationship for warranty and service after purchase. The research was sponsored by Bread Financial; it is not a measure of this app's customers.

OrderPilot keeps handover records by line. On Professional, when the optional warranty module is enabled, coverage begins with the unit's actual delivery or collection, and serial numbers can identify individual units. Service can then trace the piece back to its configuration and vendor. A service call should begin with the piece and the reported problem. The record should answer the preliminary questions without asking the customer to reconstruct a sale the store already handled.

Audit a few completed orders before adding more meetings

Use a small sample as a diagnostic exercise. For example, take five recent special orders and record the elapsed time between signing and PO sending, receipt and customer notice, and arrival and actual delivery. These are your store's observations, not industry benchmarks.

Distinguish a legitimate wait from an unnoticed gap. A customer-requested hold is different from an order nobody called about. A vendor production delay is different from a ready PO sitting unsent. Fix the longest avoidable gap first, then test whether the next person can work from the record.

Keep the handoffs visible in a small team

One person can sell, purchase, and coordinate delivery if time and volume allow. Write the handoff as a change of responsibility within their day: release the sale, check the acknowledgment, record arrival, contact the customer, and record handover.

Give a backup enough access and context to continue that sequence. The status map can show what the next move waits for, but someone still owns the work behind it. Start the next audit with the question the nineteen-day sofa would have answered: who was supposed to notice that it was ready?

Sources

1. Consumer Insights Now Week 4: in-store versus online experience — Home News Now, October 10, 2025; research sponsored by Bread Financial.