HOW-TO · OMNICHANNEL POS

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.

Measure
store-level accuracy
Reserve
pickup stock instantly
Release
uncollected orders safely
BOPIS stock cockpitlive
Online pickup orderSKU-JACKET-38reserve 1
Store availabilityOn hand: 4buffer 1
ChannelsPOS + Shopify + bolsynced
Checkout → reservation → pick task → ready for pickup

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.

97.2MAmericans regularly use BOPIS, according to Capital One Shopping Research.
95%+Store-level accuracy is the practical threshold before advertising local pickup.
MinutesThe danger window between online checkout and in-store picking.
1 stock ownerThe rule that stops POS and ecommerce tools from overwriting each other.

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.

Location-level stock

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.

Clean SKUs and barcodes

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.

Reservation rules

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.

Research gap: competitor content often says “enable local pickup” or “connect your POS.” Seller forums show the harder issue: an item can be available online, already in a BOPIS basket, physically missing from the shelf, or sold at the till before the picker reaches it. The inventory state matters more than the checkbox.

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.

Common mistake: enabling every retail location because stock exists there, even when staff cannot pick or stage online orders reliably.

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.

Common mistake: treating the last unit as sellable online even though it may be on a mannequin, behind the counter or already in a shopper’s hand.

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.

Common mistake: letting the POS, webshop and marketplace connector all overwrite quantity totals instead of sending events into one stock owner.

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.

Common mistake: waiting until staff mark the order as picked, creating a gap where the same unit can still sell in store.

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.

Common mistake: sending only a customer email or POS notification, leaving store staff to manually search orders during busy hours.

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.

Common mistake: sending ready messages when the order is accepted online, not when the store has actually picked it.

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.

Common mistake: leaving expired pickup orders reserved forever, then wondering why the store shows stock but the webshop says unavailable.

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.

Common mistake: measuring only pickup sales instead of the failures that damage customer trust.

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.

Checkout
Reserve
Pick
Pickup
BOPIS availability = on hand − committed − pickup reservations − blocked − local buffer

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.

Explore stock-level sync ->

BOPIS inventory sync FAQ

BOPIS means buy online, pick up in store. A customer places an order online and collects it from a physical store instead of receiving a parcel delivery.

Reserve stock as soon as the pickup order is placed, subtract pickup reservations from channel availability, keep a local safety buffer and update POS, webshop and marketplace stock from one operational inventory layer.

Use available stock. On-hand stock includes units that may be committed, damaged, displayed, in transfer or reserved for another pickup. BOPIS should expose only stock that staff can actually pick and stage.

Fast enough to protect the last unit before another channel sells it. For fast-moving SKUs, use event-based sync plus a buffer rather than relying only on scheduled updates every few minutes.

Yes, but only if marketplace availability is updated from the same stock model. Otherwise a marketplace order can sell the unit that was just reserved for pickup.

ChannelDock stock-level sync keeps channel-facing availability aligned, while POS workflows and fulfillment assignment help turn pickup orders into store, warehouse or 3PL tasks.

Related POS and inventory guides

BOPIS inventory sync is strongest when POS stock, buffers, reservations and store fulfillment rules use one operating model.

Connect POS inventory

Unify store and ecommerce stock.

Read how-to

Set POS buffers

Protect walk-in and online availability.

Read how-to

Click and collect POS

Configure the pickup flow.

Read how-to

Stock-level sync

Publish safe channel availability.

View feature

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.