HOW-TO · OMNICHANNEL POS

So synchronisieren Sie POS- und Onlineshop-Bestand

When a customer buys the last unit in-store, your online shop, marketplaces and warehouse team must see that change before another checkout accepts the same item. This guide shows how to sync POS and online store inventory with ChannelDock’s POS system, stock-level sync and order routing.

Kostenlos bis 500 Bestellungen · Keine Kreditkarte nötig

Map
one SKU and one stock source
Buffer
protect the last units
Audit
catch sync lag daily
Inventory sync boardstore + online
Shared stock source24 available
POS counter−1 sale
Webshop23 live
Marketplaces20 capped
Warehouseroute ready
POS sale → stock ledger → webshop cap → marketplace update

Research across Shopify Community, Reddit, Lightspeed, Square, WooCommerce, SKUPlugs, Cin7, G2 and POS integration guides showed one recurring issue: sellers ask for “real-time sync”, but overselling usually starts with split stock sources, unmapped variants or no buffer for the last unit.

SKU paritybarcode, variant, bundle
Location rulesstore, warehouse, pickup
Stock bufferlast-unit protection
Latency auditprove updates land

Before you start: inventory sync prerequisites

The safest setup is not just a fast connector. It is one operating model for what “available” means when the same SKU can sell at the till, on Shopify or WooCommerce, on bol.com or Amazon, and through a warehouse picker at the same time.

One sellable SKU map

Match POS item, ecommerce variant, barcode, bundle components and marketplace SKU. If the red T-shirt is one product in the POS and another product online, sync speed will not fix the mismatch.

One stock source per promise

Decide whether online checkout may sell store stock, warehouse stock or both. Then decide which locations may support pickup, ship-from-store and marketplace orders.

A last-unit safety rule

Use channel caps or buffers for fast-moving products. The last unit is where most overselling pain appears because a store sale and online checkout can race each other.

Competitor gap: many ranking articles say “connect your POS to ecommerce.” Retailers need the next layer: which location feeds which channel, how quickly updates are verified and what happens when sync is delayed during a busy hour.

Step-by-step: sync POS and online store inventory

Use this workflow before opening a new physical store, connecting a POS to Shopify or WooCommerce, adding marketplaces to a retail operation, or launching click and collect.

Choose the stock ledger that wins

Start by naming the source of truth. For many retailers this is the inventory layer that sits between POS, webshop, marketplaces and warehouse. The POS can still be the place where store staff sell, but the shared ledger should decide what every channel may promise.

Common mistake: letting the POS own store stock while the webshop owns online stock, then trying to reconcile after orders are accepted.

Clean the SKU, barcode and variant mapping

Export POS items and ecommerce variants. Compare SKU, EAN or barcode, size, colour, bundle status, tax class and location availability. Fix duplicates before you switch on automatic sync. A connector cannot know that “TEE-RED-M” and “Red tee medium” are the same item unless the mapping says so.

Common mistake: testing with three simple SKUs while bundles, variants and gift sets remain unmapped.

Define location rules for store, warehouse and pickup

Decide which physical stock is sellable online. Some retailers expose only warehouse stock online. Others expose store stock for click and collect or ship-from-store. Write the rule per location, not per channel, so staff know why one store can fulfill online orders and another cannot.

Common mistake: making all store stock available online, including display items, damaged units or stock that staff need for walk-in customers.

Set channel buffers before the first busy period

Use a small buffer for products that sell in-store and online at the same time. For example, if the store has five units, show four or three online, or cap marketplace stock lower than the true shelf count. ChannelDock’s stock-level sync can help keep these caps visible across channels.

Common mistake: waiting for the first refund before adding buffers. Buffers should be part of launch, not a repair after customer trust is lost.

Test the last-unit race

Pick one SKU with low stock. Sell it at the POS, then watch the webshop, marketplace feed and warehouse pick list. Repeat the test in the other direction: create an online order and confirm the POS cannot sell unavailable stock. Document the delay you actually see.

Common mistake: testing only whether products appear in both systems, not whether stock updates land quickly enough to protect checkout.

Route orders by the stock source that accepted them

If warehouse stock accepted the order, route it to the warehouse. If store stock accepted click and collect, route it to that store with a pickup hold. Use order workflows to keep the fulfillment path connected to the stock promise.

Common mistake: accepting an online order against store stock but sending the pick task to the central warehouse.

Create a daily sync exception check

Every day, compare POS sales, online orders, marketplace updates, manual adjustments and negative-stock events. Look for SKUs where one channel still shows stock after another channel sold out. The goal is not a report for finance. It is a fast operational alarm.

Common mistake: discovering sync errors during customer service, not during operations.

Train store staff on what not to override

Staff should know when to stop selling, when to check a product location and when to escalate a mismatch. A manual POS stock correction can be useful, but it should not hide a broken SKU map or a delayed marketplace feed.

Common mistake: allowing counter staff to “fix” available quantity without a reason code, making the next reconciliation harder.

The operating rule: availability is a promise

A POS and ecommerce integration is not finished when data moves between systems. It is finished when every channel makes the same promise about the same physical units, and when the team can prove how that promise changed after each sale, return, receipt or manual adjustment.

Real-time sync helps, but stock confidence comes from one source of truth, clear location rules and a buffer for the moments when channels race.

SKU map
Stock ledger
POS sale
Online cap
Safe sync = SKU parity + location rule + stock buffer + exception audit

Common POS inventory sync pitfalls

  • Using the same SKU name but different variant IDs in the POS and webshop.
  • Letting online checkout sell stock from stores that cannot pick, pack or hold orders.
  • Publishing true shelf quantity to every marketplace without a channel cap.
  • Ignoring bundles, kits, display units and damaged stock during sync tests.
  • Updating stock on a schedule without a last-unit buffer for busy products.
  • Allowing manual POS adjustments without reason codes or daily review.

Manual reconciliation vs. ChannelDock POS workflow

Manual updates can work when you sell from one counter. They break when physical stores, webshops, marketplaces and warehouse teams all touch the same stock.

Without ChannelDock

  • Store sales and online orders are reconciled after the fact.
  • Marketplace stock stays live until the next batch update.
  • Staff hide stock mismatches with manual corrections.
  • Customer service discovers overselling after payment is captured.

With ChannelDock

  • POS, online orders, marketplaces and warehouse workflows share one operating layer.
  • Stock caps protect channels from selling the same last unit.
  • Order routing follows the location that made the stock promise.
  • Daily exception checks reveal SKU and latency problems before support tickets pile up.

Explore ChannelDock POS system →

FAQ zur POS-Bestandssynchronisierung

Map each POS item to the matching ecommerce variant, choose one stock source, define which locations can sell online, then connect POS sales, online orders and marketplace feeds through a stock-level sync workflow.

Most overselling comes from split stock sources, unmapped variants, delayed marketplace updates, missing buffers or locations that are exposed online even though the store cannot fulfill the order.

Only if the store can reliably pick, hold or ship that stock. If the store is busy, has display units or lacks picking discipline, expose warehouse stock online and keep store stock for walk-in sales.

Start with one or two units for slow-moving products and a larger channel cap for fast-moving or seasonal SKUs. The buffer should reflect sales speed, sync latency and the cost of refunding an unavailable order.

Run a daily exception check and a deeper weekly review. Focus on negative stock, manual adjustments, SKUs sold in two channels within minutes and products where marketplace availability differs from the stock ledger.

ChannelDock POS system connects in-store orders with stock-level sync, marketplaces, webshops, order routing and warehouse workflows so inventory changes do not live in a separate POS silo.

Verwandte POS- und Bestandsleitfäden

After POS inventory sync is stable, tighten the safeguards around buffers, latency, pickup holds and reporting.

POS inventory buffer

Protect last units across channels.

Read how-to

Sync latency audit

Measure how quickly updates land.

Read how-to

BOPIS pickup holds

Keep pickup stock reserved.

Read how-to

POS sales reports

Export POS and ecommerce proof.

Read how-to

Halten Sie Filial- und Onlinebestand in einer operativen Wahrheit

Use ChannelDock POS system to connect counter sales, online checkout, marketplace caps, warehouse routing and daily sync exceptions before the last unit becomes a refund.

Kostenlos bis 500 Bestellungen · Keine Kreditkarte nötig