How to expire BOPIS pickup holds without losing stock
A BOPIS order does not stop affecting inventory when it is marked “ready for pickup”. The unit is usually removed from online availability, moved to a staging shelf, tied to a customer promise and hidden from walk-in staff. If the customer never arrives, that stock can disappear from every useful selling view. This guide shows how to set pickup-hold expiry rules with stock reservations, ChannelDock POS and real-time stock-level sync.
pickable stock for the customer
before the hold expires
stock back to ATS safely
Research across Shopify Help, Shopify Community, Lightspeed, Square Community, Salesforce, OneStock, Reddit, G2 and Capterra showed a consistent gap: most BOPIS guides explain how to enable store pickup, but very few define what happens to stock when a prepared pickup order is not collected.
Before you start: pickup-hold prerequisites
BOPIS only works when the reservation, physical item and customer status move together. Shopify documents that pickup availability depends on inventory at the pickup location. Lightspeed documents location-based pickup settings and, in some flows, pooled availability across pickup locations. Square Community threads show how quickly merchants lose confidence when online quantities stop reflecting POS reality. Your hold-expiry process has to close that operational gap.
Define the exact statuses: ordered, picked, staged, ready, reminder sent, expired, collected, cancelled and released. If “ready” is the last status in your POS, no one owns the no-show problem.
Give every pickup shelf, tote, locker or backroom zone a location code. Expiry cannot be automated if staff do not know where the reserved unit is physically waiting.
Prepare pickup-ready, reminder and cancellation messages before launch. State the hold window clearly, including when payment is refunded and when items return to stock.
Step-by-step: expire BOPIS pickup holds safely
Use this workflow for click-and-collect, curbside pickup, reserve-and-collect or any online order that is physically staged in a store before the customer collects it.
Define what a hold means in inventory
A pickup hold should reduce available-to-sell stock, but it should not be confused with shipped, collected or permanently unavailable stock. Store the unit as reserved for a named order at a named location. In ChannelDock, that logic belongs next to inventory reservations rather than in a staff note.
Choose the pickup window by product type
Do not use one default for every SKU. Fast-moving seasonal stock, limited drops and store-event items may need a 48-hour hold. Normal replenishable products can often stay reserved for five to seven days. Expensive or bulky items may need staff approval before expiry because cancellation and restocking can be more sensitive.
Scan the item into a staging location
When staff pick the item, scan the product barcode, scan the order or tote label and assign it to a staging location. This creates evidence that the unit was real, picked and waiting. Without a scan event, a no-show release can accidentally add stock back while the product is still lost, damaged or already handed to the customer.
Send reminders before the expiry event
Send the first reminder after the item is ready and the final reminder shortly before expiry. The message should include the store address, pickup deadline, order number and what happens if the order is not collected. For paid orders, mention refund timing; for reserve-and-collect orders, mention that the item returns to general availability.
Create an expiry queue for store staff
Do not rely on memory at closing time. Create a daily queue of holds expiring today, grouped by store, shelf, order value and product risk. Staff should review the queue, confirm the item is still staged, check customer service notes and approve the release event.
Release stock with a reason code
When the hold expires, scan the staged item, cancel or close the reservation, assign a reason code such as “pickup no-show”, then return the unit to its correct location. That release should update available-to-sell stock across POS, webshop and marketplaces through stock-level sync.
Handle partial and mixed pickup orders separately
If one item in a multi-line pickup order expires, decide whether the whole order cancels, only the no-show line releases, or the remaining items stay reserved. Mixed ship-and-pickup carts need even clearer rules because the shipped line may already be completed while the staged line is still waiting.
Reconcile no-show holds weekly
Every week, compare expired holds, physical staging counts, refunds, stock adjustments and customer complaints. If the same SKU, store or staff shift creates repeated no-shows, the issue may be pickup communication, bad shelf signage, poor inventory accuracy or a promise window that is too long.
The operating rule: a hold must have an expiry event
A BOPIS hold is not a static note. It is a temporary inventory reservation with a customer-facing promise and a physical location. If it does not expire, it becomes dead stock in disguise. If it expires without a scan, it can become phantom stock.
The safest BOPIS expiry rule is simple: no stock returns to available-to-sell until the reservation, customer status and physical scan agree.
Common BOPIS hold-expiry pitfalls
- Using the same pickup window for limited drops, replenishable basics and bulky high-value goods.
- Staging orders without a shelf, tote or locker code that can be scanned later.
- Releasing stock because a date passed, without checking whether the customer collected in store.
- Refunding the customer but forgetting to close the inventory reservation.
- Returning expired stock to the wrong location, so the webshop advertises pickup where the unit is not available.
- Ignoring no-show patterns by SKU, store, staff shift or campaign source.
Manual pickup shelf vs. ChannelDock reservation workflow
A clipboard can tell staff which bag is waiting. It cannot safely decide when stock should become sellable again across store, webshop, Amazon, bol.com or other channels.
Without ChannelDock
- Pickup bags sit on a shelf with no aging view.
- Staff cancel orders but forget the stock adjustment.
- Online availability depends on manual reconciliation after closing.
- No-show patterns are invisible until customers complain or shelves overflow.
With ChannelDock
- Reserved stock, order status and physical location stay connected.
- Expiry queues show which pickup holds need action today.
- Release reason codes create a clean audit trail for inventory changes.
- Stock-level sync updates online and marketplace availability after release.
BOPIS pickup hold FAQ
Related POS and inventory guides
After pickup-hold expiry is under control, tighten the connected workflows that decide whether physical-store and online stock stay reliable.
Stop losing sellable stock on pickup shelves
Use ChannelDock stock reservations and POS workflows to expire BOPIS holds, release no-show stock and sync availability back to every channel with proof.