What Do You Do When Sales Channels Show Different Stock for the Same SKU?

What this question usually means

The rewrite cluster is: which system should win, whether the mismatch is stale data or a real oversell, how reservations affect available quantity, and what happens if you ship against the wrong number. People also want the product to “sync stock.” That implies live connection and silent overwrite. Both are prohibited here.

A mismatch failure is often time-ordering, not malice. One export ran before a reservation; another ran after a cancellation. Your job is to reconstruct sequence, not to pick the lower number and hope.

Materials or prerequisites

Bring order, inventory, and logistics exports from each channel for the SKU and warehouse pair in question. Include reservation or hold reports if your stack uses them.

Bring exception definitions and assigned owners for inventory corrections. If you only have marketplace-available quantity and not warehouse on-hand, say which export is missing.

Step 1: Name each source of truth and its timestamp

Marketplace listing quantity, channel buffer, warehouse WMS on-hand, and ERP aggregate may all differ. Write export time and timezone for each. A number without a timestamp is not evidence — it is a snapshot claim.

Step 2: Subtract reservations and inbound ambiguity

Open cart holds, unshipped order allocations, and quarantine bins reduce sellable stock. Compare available-to-promise, not headline on-hand. Two channels showing “10” may mean ten sellable on one and ten gross on another.

Step 3: Measure oversell risk on open orders

List unfulfilled order lines against the lowest defensible available quantity. If demand exceeds that quantity, flag oversell risk and customer impact before marketing or support promises delivery dates.

Step 4: Keep disagreeing rows visible — no silent overwrite

When exports conflict, store both values in the review set. Cross-channel records may disagree and are never silently overwritten. ResolveBay uses supplied information for review and planning; it does not push a corrected quantity back to a platform.

Step 5: Route stock correction to an authorized operator

The next safe action might be a cycle count, a reservation release, or a listing pause — planned in writing. Refunds, cancellations, and stock corrections need an authorized operator. Describe the mismatch in ResolveBay with exports attached; do not claim the warehouse was updated.

Step 6: Document what would verify alignment

Write the check that would prove alignment after human action: matching ATP on two exports taken within the same window, or a pick scan. That is a candidate workflow output, not a guaranteed result.

Verification

You can explain why the channels disagree, which orders are at risk, and what an authorized operator must do next. No row in your review set should show a single merged quantity that hides the conflict.

Limits that stay in inventory review

Cross-channel records may disagree and are never silently overwritten. Refunds, cancellations, and stock corrections need an authorized operator. Do not claim live connection to external platforms.

Do not claim production availability, verified outcomes, or guaranteed results. A side-by-side comparison in ResolveBay is sample output for planning, not synchronized inventory.

What ResolveBay does in this workflow

ResolveBay compares channel and warehouse exports you supply, highlights timestamp gaps and reservation effects, and prepares a mismatch summary for the inventory owner. It does not replace WMS authority or marketplace APIs.