How to set up BOPIS inventory sync
BOPIS only works when your webshop, POS and store team agree on the same sellable stock. This guide shows how to set up buy online, pick up in store inventory sync with ChannelDock's stock-level sync, POS workflows and fulfillment assignment, so the last unit is reserved before another channel can sell it.
store-level accuracy
pickup stock instantly
uncollected orders safely
Capital One Shopping Research estimates U.S. BOPIS sales at $154.3B in 2025, while Shopify, Square and Lightspeed all position pickup as an omnichannel POS feature. The operational gap is narrower: most guides explain how to enable pickup, but not how to protect the local stock count while cashiers, webshops and marketplaces keep selling.
Before you start: BOPIS inventory prerequisites
A pickup order is not just an online order with a different delivery method. It reserves a specific unit in a specific store before a customer walks in expecting it to be waiting.
Each store, warehouse, pop-up, quarantine shelf and transfer location needs a separate stock role. BOPIS should only expose locations where staff can pick, stage and hand over orders during opening hours.
Map every barcode, variant, bundle and marketplace SKU before syncing quantities. If the POS and webshop identify the same item differently, the pickup promise will fail on the shelf.
Decide when stock is reserved, when it is released, who can override it, and how much buffer is kept for walk-in shoppers, theft, display units or sync latency.
Step-by-step: set up BOPIS inventory sync
Use this workflow when Shopify, WooCommerce, marketplaces or a custom webshop offers pickup from stores that also sell to walk-in customers.
Audit pickup-ready locations
List every store that could appear at checkout. For each one, record opening hours, staff coverage, storage space, barcode scanning capability and whether the store can split an order when one item is not available.
Define BOPIS available-to-sell
Do not publish on-hand stock directly. Calculate pickup availability as on-hand stock minus committed orders, existing pickup reservations, damaged goods, display stock, transfer stock and a store-level safety buffer.
Make ChannelDock the stock logic layer
Let the POS send store-sale events and let the webshop send online-order events, but use one operational layer to calculate availability. ChannelDock can then publish safer stock to webshops, marketplaces and POS-connected flows from the same model.
Reserve stock immediately at checkout
When a customer selects pickup and pays online, reserve the units before the order appears as a normal pick task. The reservation should reduce online availability, marketplace availability and store-facing sellable stock at the same time.
Create a store pick-and-stage task
A BOPIS order should become an operational task with item, location, barcode, customer name, deadline and staging area. If staff cannot find the item, the system needs a clear substitution, transfer or cancellation path.
Mark ready for pickup only after scan confirmation
Use barcode scanning or a controlled pick confirmation before sending the ready-for-pickup message. This keeps customer communication tied to physical proof that the item exists and is staged.
Release abandoned pickup stock safely
Set a pickup expiry window and release stock only after the customer is notified, payment/refund rules are applied and staff return the item to a sellable location. Record the release as an event, not a manual correction.
Monitor exceptions for 30 days
Track cancelled pickups, picker-not-found events, manual POS corrections, negative stock, delayed sync jobs and orders moved to another location. These signals show whether the issue is stock accuracy, staff process or integration speed.
The operating rule: reserve before you promise
BOPIS fails in the short window between checkout and store picking. A customer sees “available today,” but a cashier can still sell that unit unless the inventory system reserves it instantly and publishes the safer quantity everywhere else.
The pickup promise is not made when the customer pays. It is made when the system protects a real unit in a real store.
Common BOPIS inventory pitfalls
- Advertising pickup from stores that do not have a reliable pick-and-stage process.
- Publishing on-hand stock instead of available stock after reservations and buffers.
- Letting online pickup orders reserve stock only after staff pick them.
- Failing to distinguish store display stock, damaged stock and transfer stock from sellable stock.
- Sending “ready for pickup” notifications before a barcode or staff confirmation.
- Not releasing abandoned pickup reservations back into the right location.
Manual BOPIS setup vs. ChannelDock stock-level sync
A basic POS pickup setting creates a checkout option. A reliable BOPIS workflow protects the stock, creates the task and keeps every channel honest.
Without ChannelDock
- Pickup availability depends on POS totals that may include display or reserved stock.
- Store staff manually check shelves after the customer has already paid.
- Marketplaces and webshops keep seeing the same last unit until the next sync run.
- Expired pickup orders become manual corrections with no stock trail.
With ChannelDock
- Stock-level sync publishes available-to-sell quantities with buffers and reservations.
- Pickup orders become operational tasks for store or warehouse staff.
- POS, webshop, marketplace and B2B orders share one inventory model.
- Fulfillment assignment can route unavailable store orders to a warehouse or another location.
BOPIS inventory sync FAQ
Related POS and inventory guides
BOPIS inventory sync is strongest when POS stock, buffers, reservations and store fulfillment rules use one operating model.
Make BOPIS inventory reliable before customers arrive
Use ChannelDock stock-level sync to reserve pickup stock, update every channel and keep store teams working from the same availability model.