Special Order POS Guide 2026: Prevent Missed Pickups

A special order is more than an item that is temporarily out of stock. It connects a customer’s request with purchasing, an expected delivery, any payment already collected, and an eventual handoff. Businesses comparing POS systems should test that complete chain. A register may accept a deposit perfectly while leaving staff to remember who ordered the item, whether the supplier confirmed it, and when the customer should be contacted.

POSadvice.com helps you compare POS systems. This buying guide compares workflow designs rather than endorsing a provider or claiming hands-on results for a specific product. It focuses on retail special orders for merchandise that must be sourced for a customer. Made-to-order manufacturing, regulated products, and complex service projects may need additional specialist controls beyond the scope of an ordinary retail POS.

Map the order before comparing software
Start by listing the states a real customer order passes through: requested, quoted, approved, ordered, partially received, fully received, ready for pickup, and collected. Add canceled or disputed states where needed. Decide which employee can move the order between states and what evidence is required. A supplier order confirmation is different from a delivery estimate, and neither proves that the goods have arrived at your store.

Record what the customer actually approved. That may include product identifiers, color, size, accessories, quantity, estimated timing, and the terms for cancellation or changes. Free-text notes can help, but they should not replace structured fields for details that drive purchasing. If an employee must copy specifications into a separate purchase order, ask the vendor how staff detect a mismatch before money is committed to the supplier.

Compare three special-order approaches

An integrated model may reduce duplicate entry and make it easier to see which incoming units belong to which customer. The critical requirement is not simply that both sales orders and purchase orders exist. Ask whether there is a persistent relationship between them, whether one supplier order can serve several customers, and whether partial receipts update only the customer orders that actually received stock.

A separate purchasing workflow can be reasonable when special orders are infrequent or purchasing is already handled well elsewhere. The weakness is the link between the customer promise and the supplier transaction. Require a shared reference on both records and a report that finds orders with missing supplier references. If that report is a manual spreadsheet, include its maintenance in your staffing estimate.

An order-management integration may be appropriate when customers order online and collect in store, or when several branches share suppliers and stock. That complexity creates a need for clear ownership of statuses and quantities. Ask which system is authoritative for payment, customer communication, inventory availability, and pickup completion. A visible status in one application is not proof that the other application has received the update.

Demonstrate one order from approval to pickup
Give the vendor a realistic scenario: a customer orders two matching items that are not normally stocked. The customer approves the specifications and pays an illustrative $60 deposit against a $200 merchandise total, with taxes and any other charges handled according to your business rules. Ask the vendor to show the customer order, payment record, supplier order, and remaining balance without retyping the same details repeatedly.

Next, receive only one item. The order should remain partially fulfilled, and staff should be able to explain what arrived and what is still expected. Ask whether the customer can collect the available item while leaving the second open. Require the vendor to show how payments and any remaining amount are handled under that choice. Do not accept a demonstration that assumes every delivery is complete and every pickup occurs at once.

Receive the second item, mark it ready, and complete pickup. The final record should show what was collected, by whom under your verification policy, which employee handled the transaction, and whether any balance remains. Then try to complete pickup again. The workflow should not allow an unnoticed second fulfillment of the same quantity. Keep the demonstration results with the vendor’s written proposal.

Separate payment status from fulfillment status
A paid order is not necessarily a collected order, and an item ready for pickup is not necessarily fully paid. Buyers should require separate visibility into those facts. If a system uses one broad status such as completed, ask exactly what it means. Otherwise, staff may close an order after taking payment and lose the reminder that the merchandise is still sitting on a shelf.

Deposit accounting, refund treatment, and tax timing should be configured with your accountant and appropriate advisors. The buying test is whether the proposed system produces an intelligible record of money collected, later payments, refunds, and the final sale. Our POS deposits guide provides related workflow questions. Do not assume a transaction labeled deposit is automatically accounted for correctly in every connected bookkeeping application.

Allocate received stock deliberately
Special-order stock should not become freely available for sale if it has been promised to a particular customer. Ask the vendor to show the difference between physical on-hand stock, reserved stock, and quantity available for other shoppers. This distinction matters especially when the same product is also listed online. An apparently successful receipt can create an oversell if the reservation does not travel with it.

Test a delivery containing units for two customers and additional shelf stock. The receiving process should let staff allocate quantities according to your policy without changing the total physical count. If allocations are automatic, ask what priority rule applies and whether a manager can correct it with an audit trail. Our partial receiving guide covers additional tests for incomplete supplier shipments and open purchase quantities.

Evaluate communication without promising certainty
A useful notification tells the customer what is known: the order was accepted, the supplier gave an estimate, or the actual item is ready for collection. Those messages should not be interchangeable. Ask whether customer notifications are triggered by a receipt, a reservation, or a manually approved ready status. Sending a pickup message before staff have checked the delivery can create an avoidable wasted trip.

Ask what happens if an email or text fails. Staff need a way to see delivery problems and use another permitted contact method. Clarify any messaging charges, customer consent controls, and limits included in the quote. Do not assume notifications are unlimited or that a connected marketing service is automatically appropriate for transactional pickup updates. Keep communication preferences and operational responsibilities explicit.

Pros and cons of integrated special orders
The main potential advantage is continuity. Employees can follow the same customer requirement through purchasing, receiving, payment, and pickup. Managers may have fewer orphaned records to reconcile, and staff can answer customer questions without searching several applications. This value is strongest when the business handles enough special orders that manual coordination is a recurring source of missed calls or uncertain balances.

The tradeoff is configuration effort and possible rigidity. Some systems may require catalog records for every ordered item, while others allow custom lines that are harder to report on. Purchasing features may require a higher tier, and supplier changes may complicate implementation. Ask the vendor to price catalog setup and staff training, not just the register software, and identify any special-order exceptions that remain manual.

Pros and cons of keeping purchasing separate
Keeping an existing purchasing tool can limit disruption when that process already works. Staff may retain familiar supplier catalogs, approval procedures, and accounting exports. For a small number of custom orders, a disciplined shared reference and a daily review can be a reasonable choice. The buyer should compare the real workload rather than assume that every separate application must immediately be replaced.

The drawback is reconciliation. A changed supplier ETA may never reach the register, or a canceled customer order may remain active with the supplier. Require a named owner for checking discrepancies and a consistent process for updating both systems. If an integration is proposed to solve these issues, test errors and delays, not only a successful order sent while every service is online.

Test changes, cancellations, and failed deliveries
Change the color or quantity after the customer approves the initial order. Ask whether the previous version remains visible, whether the supplier order also changes, and whether staff can see that a new approval is needed. A system that silently overwrites the original specifications can make disputes harder to resolve. The record should distinguish an internal correction from a customer-requested change.

Then cancel one item after it has been ordered but before it arrives. Follow your stated cancellation policy and demonstrate the resulting supplier action, customer balance, and stock plan. If the supplier will not accept cancellation, the store may need to receive the merchandise into ordinary stock or handle a separate return. The customer-order screen should not imply that canceling a customer request automatically cancels the supplier’s commitment.

Test a damaged delivery as well. A physically received item that fails inspection should not trigger a ready-for-pickup message or count as successfully fulfilled. Ask where it appears in the receiving exception report and how a replacement is linked to the original order. This is a practical way to distinguish a workflow designed for real retail exceptions from a demonstration built around perfect transactions.

Compare quotes and define acceptance
Give every bidder the same order volume, active-order count, locations, users, supplier relationships, payment methods, and communication requirements. Ask for an itemized quote covering configuration, migration of open orders, training, notifications, integrations, and ongoing support. Open-order migration is particularly important: importing customer names without deposits, outstanding quantities, and supplier references can leave staff operating two systems for months.

Set acceptance criteria before committing to rollout. The test should include approval, deposit, supplier order, partial receipt, reserved-stock visibility, notification, partial pickup, final payment, final pickup, cancellation, and a damaged delivery. Have the staff who normally receive goods and serve customers perform the steps. Their ability to use the workflow matters as much as the administrator’s ability to configure it.

After launch, review orders that have remained in the same state longer than expected. Separate supplier delays from customer pickup delays, and assign follow-up responsibility. The strongest buying decision is the system that makes the next required action obvious without confusing payment, stock, and fulfillment. A clear chain of evidence is more valuable than a feature list that says special orders are supported but never explains how exceptions work.

Frequently asked questions

Is a special order the same as layaway?

No. A special order usually involves sourcing merchandise for a customer. Layaway commonly sets aside merchandise while payments are completed. A business may combine elements of both, so test the actual purchasing and reservation requirements.

Should a deposit mark an order as fulfilled?

No. Payment status and fulfillment status describe different events. Your workflow should separately show money collected, merchandise received, and quantities handed to the customer.

Can a POS manage special orders without purchasing features?

It may support the customer-facing portion, but supplier ordering and receiving will need another controlled process. Compare the manual reconciliation work and integration costs before choosing that approach.