Special orders in Shopify POS: custom sale, draft order or app?
A quick custom sale, a saved draft, and a configured order leave different records behind. Choose the route that carries the sofa’s specification through purchasing and delivery.
The OrderPilot team·
The customer points at the Madison sofa and says, “This, but in green velvet, and eight inches longer.” The associate has the iPad ready. A custom sale, a native draft, and an OrderPilot quote can all start a transaction, but they leave different work for the buying desk.
Use a custom sale for a genuinely simple one-off charge. Use a native draft when the catalog already describes the goods and the customer needs to finish later. Use a configured order when the vendor must build the customer’s choices and the store needs those choices to survive every handoff.
A custom sale records a charge quickly
A custom item can put a description and price on an order without creating a normal catalog product. That makes it useful for an unusual charge that does not need a stock identity or a continuing product record.
Shopify’s custom-item guidance says these items do not track inventory, appear in product sales reports, or work with automated fulfillment and shipping apps.
For a special-order sofa, that leaves important work outside the line. Someone still has to maintain the build specification, purchase cost, vendor order, and arrival record. A note saying “green velvet, longer” is not a controlled list of allowed choices.
Keep the custom-sale route available for the jobs it handles well. A one-time service charge can be sensible there. If the same charge recurs, a reusable service product or named fee is easier for the team to recognize and apply consistently.
A native draft holds a sale for later
A native Shopify draft is useful when the customer has selected known catalog products but is not ready to complete the purchase. Shopify’s POS draft workflow requires a Pro location, and loading an Admin draft into POS removes a custom shipping rate. Those details are in the POS draft documentation.
Shopify also provides a draft price lock. Its draft documentation states that drafts created from April 1, 2025, are deleted after a year without activity. A saved cart is therefore not a permanent service archive.
For the Madison sofa, a native draft is a holding place. It does not, by itself, model fabric-level cost and lead time or create a vendor’s build instructions. Those jobs still need an intentional process.
A draft can work well when the product is already fully specified. It becomes harder to manage when the description is standing in for an entire configuration system. The custom items versus real products comparison explains the reporting and stock consequences.
Judge an app by what reaches the next person
An app should preserve the choices that matter after checkout. Ask whether the configuration carries its selling price, purchase cost, and vendor specification, and whether the team can find the customer’s accepted version.
Then test the less tidy paths. The customer leaves without signing. A fabric is unavailable. A manager needs to review a discount. The vendor sends a changed acknowledgment. These are ordinary furniture-store events, not exotic exceptions.
The right record lets the next colleague continue without interviewing the original associate. It also lets the customer recognize the same sofa in the quote, payment request, and progress update.
Ask to see the vendor document during the demonstration. A polished product picker is useful, but the purchase order is where the chosen green velvet must finally introduce itself to the maker.
Build the Madison quote on the iPad
In OrderPilot, the associate starts a quote and chooses the Madison template. Required options make the configuration explicit while the customer is still beside the swatches.
For an illustrative sale, the base sofa is $2,400, the longer length adds $400, and green velvet adds $300. The merchandise price is $3,100 before other charges or tax. The quote should show the chosen configuration and resulting price clearly enough for the customer to review later. Cost remains a back-office concern; supplier costs are not sent to OrderPilot’s register screens. Option lead time is available on the template and Admin order line, and can be shown online when enabled. The associate should use the store’s agreed timing communication rather than expect that information to appear automatically on POS.
The showroom POS guide covers the broader floor setup. Here, the important result is a readable configured line that another colleague can use.
Choose the source and handover for the actual piece
Order New tells the team this sale needs a purchase, rather than the floor unit or existing stock elsewhere. Select the intended pickup or delivery arrangement for each physical item. A lamp on the same sale may leave with the customer today. The sofa remains to be ordered. Keeping those handovers distinct prevents a completed payment from being mistaken for completed delivery.
If an identical configured sofa is already in stock, staff can choose the stock route instead. The configuration remains the same; the source of the unit changes. Review that choice before promising a lead time based on a new build.
OrderPilot’s screens and Shopify’s native register capabilities have separate requirements. Pro availability should be confirmed for the intended Shopify checkout route; do not infer it from the presence of an app tile.
Keep the quote open if the customer is not ready
The customer can leave with the quote and a clear next action. Send the agreed choices for review and invite a specific response: approve the green velvet, ask about the length, or sign when ready.
OrderPilot provides signing by link or QR code, with the customer’s accepted terms retained. A customer-facing revision invalidates the current signature and calls for a fresh one, while the earlier record remains available.
There is no need to make the sale appear complete merely because the showroom conversation has ended. Keep purchasing behind the store’s release requirements and tell the customer what remains to be settled.
For a quiet draft quote, an optional reminder can send one follow-up email. Staff still own the conversation and any decision about revising the offer. A reminder cannot decide whether the velvet will suit the rug.
Choose the payment route before the customer reaches for a card
OrderPilot’s native percentage deposit terms, POS Take Deposit, and minimum-deposit requirements need Shopify Plus; enabled Admin deposit orders provide a separate payment-link route on any Shopify plan before placement.
On the supported Plus flow, the associate reviews the required signature and deposit, then hands the payment to Shopify POS checkout. On the Admin deposit-order route, an authorized colleague creates the request and sends its link.
For the example, suppose the agreed collection is $1,500 against the $3,100 merchandise amount, with other charges settled separately before the request. The team should see the amount actually received and the remaining obligation on the order. Don’t use a typed note as the payment ledger.
The iPad close walkthrough follows signing, collection, and receipt in more detail.
Release the same specification to the vendor
After the order meets the store’s release requirements, the configured line appears in OrderPilot’s PO workbench under its vendor. Purchasing reviews it, creates the PO, and sends the vendor-facing document. The vendor receives the selected options, quantities, and costs. Keep any required reference in the PO’s vendor notes. Vendor replies and attachments can stay with the PO when reply capture is configured, so the next colleague can read the acknowledgment.
The order is not safely purchased merely because it reached the workbench. Someone must review the destination, send the PO, and resolve differences in the vendor’s reply. The special-order process follows that handoff.
Compare the records each route leaves behind
| Decision | Custom sale | Native Shopify draft | OrderPilot configured order |
|---|---|---|---|
| Counter work | Quick description and charge | Hold known products for later | Select the agreed options |
| Stock identity | No tracked custom-item inventory | Comes from catalog products used | Source and configuration remain connected |
| Product reporting | Custom items excluded | Depends on the product lines | Configured sales stay in the app’s order and reporting workflow |
| Vendor instruction | Separate process | Separate process | PO built from configured lines |
| Acceptance and payment | Arrange separately | Native supported payment route | Signing and supported deposit/payment route |
| Follow-up | Separate record | Saved draft and customer contact | Quote, conversation, and order history |
A special order should appear in the reports appropriate to its record. Don’t treat a custom item’s absence from product reports as proof that revenue vanished, and don’t treat an unplaced quote as a completed sale.
Choose the route by what the store must do after the customer leaves. Continue with the complete made-to-order Shopify guide to connect that choice with receiving, delivery, and service.
Sources
- Creating draft orders — Shopify Help Center.
- Managing draft orders on Shopify POS — Shopify Help Center.
Ask to see the vendor document during the demonstration.