From a website quote request to a signed, paid order

At 11:48 on Tuesday night, Jordan configures a Madison sofa, adds a pair of stocked lamps, and requests a quote. By Thursday lunch, the specification is signed and the deposit is recorded. The sofa is still a long way from a delivery truck, but the store knows exactly what has been agreed.

This illustrative order belongs to the invented showroom Linden & Oak, with associate Marco handling the request. The route uses OrderPilot's website quote flow, shared Inbox, customer portal, signing, and deposit collection. It is a worked sequence, not a promised response time or a result from a real customer.

1. The product page preserves the chosen sofa

Jordan starts on the store's own product page. The OrderPilot options block sits within the theme's product section, with the template set to Request a quote. In the quote-only setup used here, the price stays hidden while Jordan chooses the sofa's length, fabric, and legs. The shopper can copy a design link to share the choices with a partner. That link reopens the configuration at current prices; it is not a saved project the store can already see. The store gets a record when Jordan submits the request.

The website selling-mode guide explains that choice. A store should decide whether this product displays a price or asks the team to prepare one before building the customer journey around it.

2. The quote cart keeps the sofa and lamps together

Jordan adds the configured sofa and two regular Shopify lamps to the quote cart. The selected fabric and legs stay with the sofa line, while the lamps retain their own product identity and quantity. The customer is asking about a room purchase, not sending unrelated messages about each piece. Linden & Oak asks for the room and delivery ZIP code on its request page. Those answers help Marco review service and destination rather than follow up with the same basic questions. Quote rules by tag, category, or collection determine which products can enter the flow. The store can require sign-in for requests, but this sample request does not. State that choice clearly on the website. A visitor should not discover an unexpected account requirement only after spending time configuring the room.

3. The confirmation tells the shopper what happens next

The Request sent page confirms that the request reached the store. Its appearance belongs to the store's branded request flow. Jordan also receives the “We got your quote request” email, which acknowledges the request without pretending it is already a finalized order. The confirmation is a useful place to set a realistic expectation. It should identify the next action without promising a response deadline the team cannot keep. The customer has finished submitting; the next job belongs to the showroom.

4. Marco takes ownership in the shared Inbox

The next morning, Marco opens the request in the shared Inbox and takes responsibility for it. The review drawer shows the selected sofa options, lamps, and request details. An internal note asks purchasing to confirm the fabric's timing before Marco sends the final proposal. Another colleague can help without becoming a second, contradictory voice to the customer. Inbox assignment identifies the owner, and the order editor shows concurrent activity and warns when the record has changed instead of silently overwriting another person's work. Staff still need to read the latest state before saving or replying.

The Inbox-to-priced-quote guide covers this middle section in detail. Here, Marco's next job is to resolve the outstanding facts and produce a quote Jordan can actually approve.

5. The updated quote includes the whole sale

Marco confirms the sofa configuration, prices it, and adds a named white-glove delivery fee. The lamps will join the sofa delivery in this sample, so the quote has one agreed delivery arrangement. The customer should not learn about the service charge only after signing the merchandise.

Marco reviews the PDF and sends the updated quote with the portal link. The proposal states the selected options, quantities, prices, delivery service, and terms. Any production timing the customer needs is included in the communication; option lead time does not automatically print on the quote PDF. Suppose the agreed total is $5,000, including the tax and delivery used in this example. Marco explains that the requested deposit will be $2,000 and the remaining balance $3,000. At this point those are agreed amounts, not receipts. The payment history will change when the money arrives.

6. The portal keeps the finish question beside the sofa

Jordan opens the portal and pins a question to the leg finish: is the walnut darker than the small website swatch suggests? Marco replies with a photograph and a plain description. The question stays attached to the choice, rather than becoming an email saying “the darker one” with no obvious subject. Jordan marks the reviewed items Looks good. Those markings support review; they are not the final signature. The customer and team settle the open questions and change requests before the signing action is ready for the agreed version.

The customer portal guide explains the broader account experience. Jordan follows the link from the store's email without needing a storefront account, subject to the store's portal access settings. The website request's sign-in rule and portal access are separate parts of the setup.

7. Jordan signs the settled specification

With the finish question resolved, Jordan reviews and signs the quote in the portal. OrderPilot preserves the signed terms and PDF with the sale. The signature belongs to this sofa configuration and agreement, not to every future change the customer might request. If Jordan later asks for a different length, staff review that request and any vendor consequences first. A customer-facing revision invalidates the current signature and calls for a fresh one where required, while the earlier signed record remains available.

For this order, the agreed configuration stays unchanged. Marco can now review the signature state and move to the payment step without translating a friendly “looks lovely” into a purchase approval.

8. The deposit becomes a recorded payment

Linden & Oak uses enabled Admin deposit orders for this sample before placing the main order. Marco prepares the $2,000 request and sends its payment link. The deposit has its own Shopify checkout order; when paid, it counts toward the sale and reduces the remaining balance.

Deposit orders work before placement on any Shopify plan, while native percentage deposits, POS Take Deposit, partial manual payments on placed orders, and ordinary minimum-deposit requirements need Shopify Plus. Select the route before release, including the deposit-order restriction on tax-split orders, so the customer is given a link the sale can actually use. Marco verifies Paid at $2,000 and Balance at $3,000 after payment. A paid deposit does not mean the order is fully paid. A configured Professional status connection can support the next stage, but the buying handoff still needs the correct signature, payment position, and release decision.

If the quote email stays unopened

The owner of the request should review delivery and open activity, then decide on a useful follow-up. An open event is a signal that the message was accessed, not proof that the customer has read or approved every term. A missing open is also not a reason to send the same email repeatedly.

OrderPilot's optional automatic reminder sends at most one email for a quiet quote still in Draft. It is not a follow-up sequence for every sent quote, so Marco manages any other follow-up deliberately through the order's email tools. Check the contact details, the last conversation, and the customer's next decision before sending.

The shared Inbox guide explains how ownership and waiting states help the team avoid duplicate replies. If a colleague takes over, the record should show what Jordan has already received and what remains unanswered.

Set the request flow up before inviting traffic

Start with the products that can be quoted, the questions the customer must answer, and the colleague who owns incoming requests. Then test the confirmation, portal access, signing, and payment route with sample data. Turn on the portal and complete reply-capture setup where the workflow uses it.

The result should be one readable handoff from a shopper's choices to an agreed sale. Purchasing now knows what Jordan bought, which version was signed, and what was paid. Continue with one sofa from showroom to living room for the work after the sale.