The special-order process from showroom to vendor PO

The customer has found a sofa they love, with one change: they want it in linen, with a deeper seat and darker legs. The showroom conversation feels simple because the piece and swatches are right there. Purchasing needs that same clarity later, when the customer has gone home and the sample book is closed.

The special-order process should preserve those choices at every handoff. If a buyer retypes the notes as the standard-depth sofa, the error may not become obvious until delivery. Build the process around the same principle from the start: the vendor should receive the choices the customer signed for.

Begin with a specification someone else can read

Record the model, fabric, size, arm style, and leg finish while you are discussing them. “The darker wood” is meaningful beside a sample board; it is less helpful in a purchase order. Use the vendor's names and identifiers so a colleague can identify the choice without recreating the appointment.

For a worked example, say the customer chooses this sample Madison sofa from Atelier Nord. The names, dimensions, and lead time below are illustrative rather than specifications for an actual product.

The dimensions matter because “deeper” is a comparison, not a manufacturing instruction. A fabric code matters because the sample library can contain more than one natural linen. The maker's idea of natural may have a surprisingly extensive family tree.

Give the catalog a repeatable structure

A product template gives salespeople the choices they need to settle before quoting. OrderPilot supports required options, prices, costs, lead times, and rules that hide combinations that do not work. Shared option bundles help keep a fabric collection consistent across the pieces that use it.

The buyer and salesperson should agree how the sample specification maps to those choices. If the deeper frame cannot use a particular arm, that should be settled in the catalog rather than discovered after a customer signs. A notes field is useful for an actual exception; it should not become a second, unofficial catalog.

When a saved draft contains a choice the template no longer offers, OrderPilot flags the retired value and requires a fresh choice before creation. That is different from changing a template price: saved quotes retain their saved prices. Review the customer's agreement when resolving an unavailable choice instead of quietly substituting the closest fabric.

Lead time helps the associate explain the likely wait. It appears on the admin order line and can be shown in the online options block when enabled; it does not automatically print on the quote or PO. Put any promised timing into the communication the customer and vendor actually receive.

Build the whole quote, including the ways home

The sofa may be only part of the purchase. The customer might add a stocked side table and a lamp that can leave today. Keep the sale together while making each item's source and handover clear. Buying everything again would be an expensive way to keep the paperwork tidy.

OrderPilot mixes configured pieces and regular Shopify products on a quote. Each line can follow its own pickup or delivery arrangement. Named delivery charges and reusable service products let the quote include the service the store has agreed to provide, with a clear price and description.

For the sample order, record the sofa as a fresh purchase to the store's receiving warehouse. Identify the lamp as stock to be taken home, and decide whether the table joins the eventual sofa delivery. Those decisions give purchasing a buying list and give delivery a customer promise.

Confirm the version the customer is buying

The customer should be able to review the same choices away from the showroom. Send a quote that identifies the piece and includes the right product and category terms. Explain the next decision clearly: review the specification, settle a question, sign the agreement, or make the agreed payment.

The customer portal on Growth and Professional lets customers ask questions and request changes. A request for darker legs is a decision for staff to review, not an automatic instruction to the maker. Settle the relevant open requests before asking the customer to sign the final version. OrderPilot keeps the signed terms and PDF with the order. A later customer-facing change asks for a new signature, while the earlier signed record remains available. For the full change sequence, see change orders and re-signing.

Agreement and payment answer different questions. A signature establishes which version was approved; the payment history establishes what was received. Any Shopify plan can use enabled OrderPilot deposit orders, while native percentage deposits, POS Take Deposit, and minimum-deposit requirements need Shopify Plus. Train the handoff around the payment route your store uses.

Set a clear handoff from sales to purchasing

One named person should own the check that an order is ready to buy. The salesperson owns unresolved customer choices; the purchasing owner confirms that the specification, agreement, payment position, and intended route are ready. In a small store, the same person can hold both jobs, but the review still needs to happen.

On Professional, the store's configured status map can connect the conditions it uses to a ready-to-order stage. A Next status action supports steps that staff complete deliberately, and optional manager review can provide another decision where the store needs one. Build the conditions around the actual process rather than assuming that every paid order is ready to purchase.

If a fabric is awaiting confirmation, name the person chasing it and the next follow-up. That gives the next colleague something more useful than an order that simply appears to have stopped. The four-handoffs guide explains why this ownership matters across departments.

Build the vendor PO from the agreed order

OrderPilot's PO workbench carries the configured order lines into purchasing and groups them by vendor. The Madison sofa reaches the buyer with its chosen upholstery, dimensions, and finish. Tracked options can appear as component items, and quantities can be split across POs when the purchase requires it. An order can go to several vendors. If the sofa, table, and another ordered piece come from different makers, each vendor receives the purchase it needs while the customer sale stays connected. Review the quantities and remaining demand so a split buying run does not create a duplicate purchase.

Before sending, check the vendor minimum, SKU display, destination, requested delivery date, and instructions. A draft can wait below the minimum; sending is blocked until each enforced requirement is met. The requested date is the store's request, not evidence that the maker has accepted it.

The vendor receives the PO email with its PDF attached, and delivery and open activity are recorded. Review the PDF as the vendor will see it. When a project reference is needed, add it in Vendor notes; the document does not automatically print per-line customer order numbers or the internal Side Label. The purchasing pillar covers the complete review.

Keep the vendor's answer with the purchase order

Read the acknowledgment against the agreed purchase. If it lists a different fabric, stop that difference from becoming the production instruction. Identify the exact line and the mismatch, ask for correction, and keep the corrected acknowledgment with the PO. A similar color name does not establish an approved substitution. With vendor reply capture set up, replies and attachments land on their PO, and plans with the shared Inbox bring the conversations together. A colleague can see the question and answer without asking the original buyer to forward a personal email chain.

If the customer asks for different legs after sending, purchasing first asks whether the maker can still change them and what that does to cost and timing. Once agreed, update the customer-facing record, obtain the required signature, and edit and resend the supported unreceived PO lines. Keep the vendor's acceptance of the revision with the conversation.

Phone and portal purchases can also be recorded. Confirm a PO placed outside OrderPilot as sent after verifying the vendor commitment, rather than sending a second ordinary order email. The record should tell the next person what actually happened.

Leave receiving and service a useful record

Receiving records what arrived, including accepted and rejected quantities. If only part of a purchase arrives, the rest remains outstanding. Your team should not mark an entire order ready for delivery simply because the first carton reached the dock. Received units can be held for the orders they cover. Freight and other charges can be allocated through landed cost, giving the store a fuller picture of what the furniture cost to bring in. That record supports later decisions about delivery and the eventual margin. Where the store has configured the status connection, receiving can move the order's progress forward. The staff member still needs to distinguish physical arrival, inspection, and readiness for the customer's delivery appointment. Keep those meanings clear in the stages your team uses.

The end-to-end special-order playbook continues beyond purchasing. For a narrative through final handover, follow one sofa from showroom to living room.

A special-order process your furniture store can repeat

Before a PO leaves the store, ask whether someone who missed the showroom conversation could confidently follow it. Print this handoff checklist for the buying desk:

- Are all fabric, finish, and size choices explicit? - Does the PO match the version the customer agreed to? - Are the required signature, deposit, and approvals accounted for? - Are the vendor, destination, and order minimums checked? - Can the next team member find the vendor's replies?

The vendor should receive the same choices the customer signed for. Build each handoff around that principle, and the record remains useful when the piece arrives, goes home, or needs attention later. Continue with signed sale to vendor PO to arrival for the receiving handoff in detail.