You expect 100 units of a new product. Your store promises 60 to walk-in customers while the website accepts another 60 preorders. The problem is not the payment button: it is that two channels have made promises against the same 100 units without a shared allocation rule.

This 2026 POS preorder buying guide focuses on that promise. It explains how to compare order allocation, launch limits, supplier delays, deposits, and fulfillment across the register and online store. A preorder feature is useful only when the quoted setup can keep those records consistent through cancellations and partial deliveries.

POSadvice.com helps you compare POS systems. The quantities and dollar amounts below are hypothetical evaluation scenarios. They are not vendor performance claims or guaranteed outcomes. We distinguish official product documentation from the capabilities you still need a provider to demonstrate.

Define preorder, backorder, reservation, and deposit

Use precise terms when asking for a proposal. For this guide, a preorder is a commitment for an item before it is ready for fulfillment, commonly associated with a future release. A backorder concerns an unavailable item you ordinarily sell. A reservation holds an allocation for a customer under defined terms. A deposit records a payment toward an order; it does not, by itself, reserve supply.

Providers may use these terms differently. Describe the customer journey instead of assuming the feature label means the same thing everywhere. Can staff take a commitment at the counter, can a customer place one online, when is stock allocated, when is payment collected, and what happens if the expected shipment is short?

Write down whether you sell a finite release, made-to-order products, or replenishable goods. A finite release needs a hard allocation ceiling. A made-to-order business may need production capacity and estimated dates rather than an incoming-stock count. Those are different buying requirements even if both use a preorder button.

Compare the underlying order approaches

Preorder approaches and the proof to request before buying
ApproachPossible fitAdvantageRequired demonstration
Unified POS and order-management workflowBoth store and online staff accept commitmentsPotentially fewer separate order recordsBoth channels consume the same allocation without duplicate promises
Ecommerce preorder app plus store handoffLaunch orders originate online and may be collected in storeA focused online purchase experienceStore staff can see the correct order and complete the supported handoff
Special order or invoice with controlled reservationsLow-volume, staff-assisted ordersCan suit a deliberate, reviewed sales processPayment, allocation, and fulfillment stay linked without uncontrolled spreadsheet edits

A unified product name is not proof of unified allocation. Likewise, two connected tools can be workable if their responsibilities and failure handling are clear. Ask where the authoritative preorder limit lives, who can change it, and what happens when the connection between systems is interrupted.

A documented online feature may not be a POS feature

Shopify’s official preorder overview says that preorders require a preorder app and are managed in Shopify admin. Depending on the options offered, customers may pay in full, partially, or not at the time of ordering. The documentation also identifies supported payment-provider requirements.

Crucially, Shopify’s preorder setup documentation says these preorder products are supported only on the Online Store and Custom Storefront sales channels. That documented purchase-option feature should not be presented as native Shopify POS preorder support.

If a seller proposes Shopify plus an app for a physical store, ask for the exact supported counter workflow. It might involve directing the customer through an online checkout, using a separate special-order process, or another documented solution. Do not assume one of those exists or is included until the provider demonstrates it and explains the limitations.

This distinction generalizes beyond one vendor. “Works with our ecommerce platform” does not establish counter ordering, local pickup, payment collection, or cancellation behavior. Review each channel separately and then test how they share the same customer commitment.

Set an allocation ceiling with explicit arithmetic

Use this illustrative launch scenario: a supplier confirms 100 units, and you reserve 10 as a contingency allowance. Your initial preorder ceiling is 90. That is a business decision, not a universal formula; the important point is that the limit is written down and controlled.

Accept 40 online orders and 25 counter commitments, each for one unit. You now have 65 commitments and 25 remaining under the ceiling. Ask the system to show the counts by channel and in total. It must also distinguish those expected units from physically received stock that customers can take home today.

Next, attempt to accept 30 more orders across both channels. If your policy is a hard ceiling, at most 25 should be confirmed. Ask what the other five customers see: sold out, waitlist, a later shipment, or an explicitly approved exception. A vague “inventory can go negative” setting is not an allocation policy.

Run a near-simultaneous last-unit test with the provider. Observe whether both checkouts can promise the final unit, whether one holds it temporarily, and when abandoned reservations are released. Record the observed result rather than accepting a broad statement that synchronization is real time.

Test supplier changes before you take customer money

Reduce the confirmed shipment from 100 units to 70. With 65 existing commitments, you can no longer retain a 10-unit contingency allowance and honor every commitment without changing the plan. The software should make that conflict visible; it cannot solve a supply shortage simply by refreshing an arrival date.

Ask how staff select an action: lower the remaining sales limit, move eligible orders to a later batch, offer cancellations, or change the contingency allowance through an authorized review. Preserve what each customer was promised and record any accepted change. Do not silently rewrite all order dates and erase the original commitment.

Receive only 50 units first. If you allocate by order time, priority tier, or another disclosed rule, test that rule with the sample orders. A partial receipt should not automatically mark all 65 orders ready for pickup. Have the provider show both the waiting orders and the orders ready to fulfill.

Connect the trial to your receiving workflow. Our POS purchase orders guide explains broader supplier and receiving checks. For preorders, the extra requirement is mapping a real receipt to the particular promises it can fulfill.

Keep payment status separate from fulfillment status

Compare three payment models: full payment at order, a deposit with a later balance, and no payment until a defined later step. Each can produce a valid business workflow, but the quoted platform, payment provider, and customer terms must support the one you choose.

For a hypothetical $120 product with a $30 deposit, the remaining balance is $90 before any separately applicable tax, delivery charge, or adjustment. Cancel the order before fulfillment and show how the deposit is handled under your stated policy. Then test a partial order cancellation involving two products with different arrival dates.

Do not assume an authorization remains collectible until the goods arrive. Ask the provider how delayed collection works, what consent and saved-payment method are required, what happens if collection fails, and how staff request a new payment. Avoid workflows that require staff to record full card details outside the approved payment system.

Our POS deposits guide covers balance tracking in more depth. Here, confirm that “paid,” “allocated,” “received,” and “fulfilled” are distinct enough for staff to understand. A fully paid order can still be waiting on supply; a reserved item can still have a balance due.

Make pickup and shipping part of the buying demonstration

For pickup, have a staff member locate the order, verify the appropriate customer or authorized collector, collect any supported outstanding balance, and record the handoff. Then search again from another register. The order should not appear as an uncollected item ready to release a second time.

For shipping, ask how the system handles an order containing one available item and one preorder item. Can you hold both, split shipment, or offer the customer a supported choice? What happens to shipping charges and payment timing? Do not let a vendor demonstrate only a one-item basket if customers routinely mix products.

Include a mistaken fulfillment in the test. Staff should be able to correct the record through a reviewable process, not by deleting the order and recreating a payment. Request the event history and confirm that customer notifications do not announce contradictory statuses after the correction.

If pickup is central to your business, use our retail pickup POS guide alongside this checklist. Preorder allocation decides who has a claim on future stock; pickup controls decide whether the right person receives the stock when it is available.

Pros and cons of a dedicated preorder workflow

Pros

  • Clearer commitments: staff can identify the quantity promised and the customers waiting for it.
  • More controlled launches: a demonstrated allocation limit can support your chosen sales ceiling.
  • Better exception handling: linked order records can make shortages, cancellations, and failed collections easier to investigate.

Cons

  • More operational decisions: allocation priority, payment timing, partial receipts, and customer updates need explicit policies.
  • Possible channel restrictions: an online preorder app may not support the counter workflow you expect.
  • Additional dependencies: apps, payment services, and fulfillment tools may have separate charges and support responsibilities.

The value depends on the volume and complexity of your commitments. A few staff-assisted orders may justify a controlled special-order workflow. A limited release sold simultaneously online and in store deserves a much stronger shared-allocation test.

Require a launch-ready proposal, not a feature checkbox

Send providers the 100-unit scenario and ask for a written response covering the ceiling, supported channels, deposit handling, short receipts, cancellations, and fulfillment. Request separate costs for the POS subscription, preorder app, order-management tools, setup, migration, payment processing, and ongoing support.

Also request an exit plan. Shopify’s overview warns that uninstalling a preorder app deletes the app-created preorder data, excluding customer payment information, after 48 hours unless an available backup mechanism can restore it. Before changing any app, confirm your own export, backup, and continuity process with the provider; do not use uninstalling as a live troubleshooting experiment.

Run a small pilot with test orders before opening the real launch. Reconcile promised units, received units, paid amounts, outstanding balances, cancellations, and fulfilled orders. Have the employee responsible for launch-day support complete the exception cases, not only the vendor demonstrator.

Choose the configuration that can explain every commitment when supply changes. That is the practical difference between accepting preorders and managing them.

Ready to find your perfect POS system?

Answer 3 quick questions and get free quotes from top providers.

Get Free Quotes →

Frequently asked questions

Does a preorder deposit automatically reserve inventory?

No. A deposit records a payment, while a reservation or allocation records a commitment against supply. Ask the provider to demonstrate how the proposed workflow links the payment, order, and allocation across every selling channel.

Does Shopify's documented preorder purchase option work in Shopify POS?

The cited Shopify setup documentation lists only the Online Store and Custom Storefront sales channels for preorder products. Do not assume that purchase option works natively in Shopify POS; require a separately demonstrated, supported counter workflow.

How can a store reduce preorder overselling?

Set a controlled allocation ceiling, make every supported selling channel consume that allocation, and test simultaneous last-unit orders. Separate expected supply from received stock and update commitments when confirmed supply changes.

What happens when only part of a preorder shipment arrives?

The workflow should show which orders can be fulfilled under your allocation policy and which remain waiting. Test partial receiving, customer updates, outstanding balances, and cancellations without marking the entire order pool ready.

Leave a Reply

Your email address will not be published. Required fields are marked *