Buy Online Return in Store Inventory: The BORIS Control Layer

NRF and Happy Returns estimate that 19.3% of online sales will be returned in 2025, with total retail returns reaching $849.9 billion. For omnichannel retailers, that number is not only a customer-service challenge. It is an inventory-control challenge, because more shoppers expect to return online orders at the nearest store and receive an instant refund or exchange.

That workflow is usually called BORIS: buy online, return in store. Shopify, Square, Lightspeed and specialist returns platforms all describe the customer benefit clearly: fewer parcel labels, faster refunds, more store visits and a better omnichannel experience. What many ranking articles skip is the operational layer behind the counter. When the store accepts an online return, who decides whether that unit can be sold again, where it should live, and which channel is allowed to promise it next?

The answer matters more in 2026 because physical stores are no longer isolated tills. They feed webshop availability, marketplace stock, B2B order promises, warehouse pick lists and sometimes endless-aisle orders. A single bad restock can turn into an oversell on bol.com, Amazon, Shopify or a store shelf within minutes. That is why retailers need buy online return in store inventory rules, not only POS refund buttons.

Why BORIS is different from a normal store return

A normal store return usually has one operational home: the item was sold from the store, the customer brings it back to the store, and the POS can reverse or exchange the transaction inside the same stock location. BORIS breaks that simplicity. The sale may have started on Shopify, WooCommerce, Amazon, bol.com or another webshop. The order may have been picked in a warehouse, shipped by a carrier, reserved from a central inventory pool, or allocated from another store.

When that item lands at the cash desk, the associate sees a customer who wants a quick solution. The stock system sees a chain of events: original order, fulfillment location, parcel delivery, payment capture, return reason, inspection result, refund, and new stock location. If those events are collapsed into one “return to stock” action, inventory drift starts immediately.

Competitor content often treats BORIS as a conversion tactic. That is useful, but incomplete. The operational question is not “can we accept the return?” It is “can we accept the return without polluting sellable stock?” That is the gap an omnichannel POS setup must close.

The hidden inventory states behind one returned item

One returned jacket can have many legitimate next states. It might be pristine and ready for the rack. It might need a missing hangtag, a steam, a battery check, a new box, a serial-number check, or a fraud review. It might be sellable in the physical store but not acceptable for marketplace fulfillment because the packaging is opened. It might be a wrong item, a decoy return or a warranty case that should never re-enter available stock.

NRF's 2025 returns research reported that 9% of returns are fraudulent, and that retailers are seeing tactics such as overstated quantities, empty boxes and counterfeit items. That does not mean every store associate needs to become a fraud investigator. It means the POS return flow should give associates simple, fixed choices that translate into inventory rules.

The BORIS control layer: three separate events

The cleanest way to manage online returns in store is to split the workflow into three separate events. First, the customer-service event: identify the original order and decide whether the shopper receives a refund, exchange, voucher or repair path. Second, the inventory-disposition event: decide whether the unit is sellable, quarantined, damaged, pending inspection, returned to supplier, or routed to a warehouse. Third, the stock-publication event: decide which channels can see that unit as available.

Those events can happen seconds apart, but they should not be the same database action. An instant refund is good service. Instant restocking is only good if the item has passed the right checks. Retailers that connect POS, WMS and sales channels through one operational layer can give the customer speed while keeping marketplace stock conservative.

The safe BORIS rule is simple: refund fast, restock deliberately, publish stock only after the unit has a confirmed location and condition.

A practical workflow for stock-safe store returns

For a retailer using stores, webshop orders and marketplace listings, BORIS should look closer to reverse fulfillment than a simple refund screen. The associate should not need to understand every downstream system, but the workflow should force the right operational choices in the right order.

1. 1
   Find the original order, not just the receipt

   Match the returned item to the ecommerce order ID, SKU, barcode, batch, serial number where relevant, customer and payment transaction before any stock is adjusted.
2. 2
   Separate refund from restock

   A customer can be refunded instantly while the item stays non-sellable until inspection. Treat those as two events, not one POS button.
3. 3
   Assign a return disposition

   Use fixed statuses such as sellable, inspect, damaged, missing accessory, wrong item, counterfeit suspicion, return to supplier or refurbish.
4. 4
   Route the unit to the right stock location

   Store shelf, backroom quarantine, webshop pool, central warehouse and marketplace allocation should each have their own inventory state.
5. 5
   Reconcile exceptions daily

   Review returns where payment, stock or order status disagree before the discrepancy reaches marketplace stock feeds.

ChannelDock's role in this model is the control layer between sales channels and operations. Retailers can connect webshops, marketplaces, POS flows and warehouse work through ChannelDock integrations, then keep stock decisions aligned with the inventory control features that prevent premature availability.

Where most POS and ecommerce guides stop too early

Shopify's return documentation explains that POS can process returns and optionally restock items at the assigned location. Square describes the value of an integrated POS where online purchases, in-store returns and loyalty can update in a central system. Lightspeed highlights real-time inventory updates from sales, returns and transfers. Those are strong product capabilities, but the retailer still needs a policy for what “restock” means.

The missing piece is condition-aware stock. A returned product should not move from “customer brought it back” directly to “available on every channel.” It should pass through a disposition matrix. Fashion, electronics, cosmetics, home goods and refurbished products each need different rules. A sealed phone case can return to webshop stock quickly. A used wearable, opened beauty item or serialised device may need inspection, quarantine or supplier handling.

The stock-location model that avoids overselling

The safest setup uses more than one stock bucket. “Store stock” is too broad for BORIS. At minimum, retailers should separate front-of-house sellable stock, backroom pending inspection, damaged or unsellable stock, return-to-warehouse stock and central online stock. If marketplaces share the same SKU pool, there should also be an allocation or buffer that stops one returned unit from being promised twice.

This is where omnichannel POS becomes operational rather than cosmetic. If a store accepts an online return at 11:05, the webshop should not automatically show one extra unit at 11:06 unless the item is sellable in that location and allowed for online fulfillment. If the unit must go back to the warehouse, it should enter an inbound or transfer workflow. If it is sellable only in-store, the online pool should stay unchanged.

Retailers already using order routing can extend the same logic to returns. A return creates an inbound event, a disposition, and then a stock-publication rule. That rule can feed webshop availability, marketplace quantities and store picking promises through one source of truth. The operational payoff is fewer manual corrections, fewer false “in stock” promises and cleaner margin reporting by channel.

What to measure before scaling BORIS

Before rolling BORIS across every store, measure the process for two weeks. Track average return handling time, percentage of returns restocked immediately, percentage moved to quarantine, number of mismatches between POS and warehouse stock, number of customer-service escalations, number of marketplace stock corrections after returns, and value recovered through resale or exchange. These numbers reveal whether the workflow is genuinely controlled or simply convenient for the customer.

The most useful metric is not return volume. It is return-to-sellable time by condition. A pristine item should move fast. A questionable item should move slowly or not at all. A damaged item should never quietly inflate sellable stock. Once that discipline exists, the retailer can confidently promote BORIS, BOPIS, endless aisle and ship-from-store without creating hidden stock debt.

If returns often trigger follow-up warehouse work, connect the return process with order management rules so exceptions, exchanges and replacement shipments do not live in store notes. For retailers selling through several channels, the goal is one queue for operational truth, not another isolated POS task.

FAQ

Conclusion

BORIS is a strong omnichannel promise, but it exposes weak inventory processes quickly. The customer sees a simple return at the counter. The operation sees a reverse order, a payment decision, a condition check, a location move and a new stock promise. If all of that is hidden behind one POS restock button, inventory drift is inevitable.

The better model is an inventory-first BORIS control layer: identify the order, refund the customer, inspect the item, assign a disposition, move it to the right stock bucket and only then publish availability to webshops, marketplaces and store teams. That is how retailers keep the convenience of buy online return in store without sacrificing stock accuracy.

ChannelDock helps retailers run that control layer across POS, ecommerce, marketplaces and warehouse operations. If store and online stock still feel like separate businesses, start by mapping the return states. Then connect the systems that decide whether a returned unit is actually safe to sell.