| Available, Ready to list, or another derived count disagrees. | Compare each labeled value with Damaged, Pending receiving, quarantined stock, and the channel’s own rules. Check whether the Inventory surface is showing Ready to list under a non-negative Available label. Capture every displayed quantity and label, product/size/location, last-changed time, and channel or store timestamp. | If only derived inputs or a channel display differ, this is a derived or channel-layer disagreement, not proof that physical stock is wrong. Do not write a derived number. | Use How the inventory numbers fit together and What syncs and who wins for read-only comparison. Stop and contact support if the derived inputs disagree with physical-unit or audit history, the label is ambiguous, or someone proposes a write. |
| The physical count disagrees with the expected quantity. | Confirm the count type, location, scope, status, ownership mode, and count window. Review later receipts, sales, transfers, and adjustments before interpreting the variance. Capture count ID/name, expected and counted quantities, variance, status, scope, operator, timestamps, and post-count activity IDs. | Complete count context and later activity can distinguish an actual variance from an active or incomplete count, an invalid baseline, or overlapping activity. A later event can explain the current number without requiring a new quantity event. | Use Inventory Counts’ supported discrepancy-review path only after the evidence is complete; do not click Apply, Adjust, or Set to zero from this investigation. Stop and contact support if the count is active/incomplete, activity overlaps the window, the baseline is invalid, or the result needs an unexplained quantity change. |
| Reserved stock or Pending receiving work makes the numbers look different. | Check whether Reserved was already removed from Available. Separately check whether the unit is received but still waiting for authentication, quality work, or Put-away. Capture reservation ID/state, order/customer, Available and Reserved before/after values, receiving or put-away operation ID, unit/serial, location, and timestamps. | Reserved units can still be in the building, while pending receiving or put-away can keep a received unit out of Ready to list. These are separate explanations; subtracting Reserved from Available again double-counts the commitment. | Hand off to Sales, reservations, and allocation, Send and receive a purchase order, or Put away and locate stock as applicable. Do not release a reservation to make the count look right. Stop and contact support if the reservation cannot be matched to the business/order or pending work has no source event or terminal result. |
| The location or Sublocation does not match where the pair was found. | Compare the inventory item’s location with the unit’s assigned Sublocation and the observed shelf, bin, or rack. Capture location ID/name, assigned and observed Sublocation, unit/serial, count scope, scan ID, and before/after placement history. | A count can preserve evidence of a mislocated unit without moving it. The inventory location, the unit placement, and the observed physical place are separate facts. | Use Put away and locate stock for placement or the current transfer workflow for stock moving between locations. Do not choose Move here without a verified placement decision. Stop and contact support if the unit belongs to another business/location, the assigned place is missing, the unit is in transit, or the proposed move is unverified. |
| A source event is missing, repeated, queued, or only partly applied. | Compare the original request/operation ID with the audit trail, task result, and current quantity. Capture client scan ID, task status, source event, actor, exact timestamps, and before/after values. A repeated scan or request may be an idempotent retry rather than a second physical event. | A conflicting or still-running result, or a source success without durable AIM evidence, cannot be safely classified. A second attempt could create another quantity event. | Use Inventory Counts for count scans or Send and receive a purchase order for receiving work. Retry only from that named workflow after its current result is understood. Stop and contact support when the same ID has conflicting results, the operation is running, durable evidence is missing, or another attempt could create a second event. |
| A serialized unit is not found or a serial appears twice. | Check the exact serial or unit, active status, consumed/returned state, assigned location, and count scan history. Capture serial/unit ID, barcode, unit status, sale or receipt identity, count ID, scan/application ID, scan reversal state, and timestamps. | A missing scan is not proof that the physical unit is missing, and a duplicate scan is not proof of duplicate stock. Conflicting lifecycle or source evidence leaves the physical outcome unresolved. | Use Inventory Counts for count-scan review, then the owning receiving, sale, return, or inventory-unit workflow when lifecycle is the issue. Do not create a replacement unit to make totals agree. Stop and contact support when lifecycle states conflict, no trustworthy source event exists, or the physical outcome is unknown. |
| Owned, Consignment, sale, or order attribution does not match. | Compare Owned and Consignment quantities with the sale/order line, selected unit, location, cost evidence, reservation when that flow creates one, and source status. Capture business, ownership, consignor when applicable, sale/order and line, product/size, unit/serial, reservation, cost, source status, and before/after inventory evidence. | Ownership, physical custody, and sale attribution are separate questions. A flow may create a reservation, but a mixed owned/Consignment row cannot be safely resolved by an aggregate change. | Use Marketplace Sales, Fulfillments, Cancelled Sales, or Returns & Exchanges for the source event. Do not reverse/restock, transfer ownership, or change a mixed row from this page. Stop and contact support if the line or unit is ambiguous, the sale is partial or in Attention, the return/cancellation has no physical outcome, or an aggregate change is proposed. |
| A channel or store shows a stale or different quantity. | Compare AIM’s channel-specific quantity with store/location identity, last sync attempt, last successful sync, provider response, and current product or variant link. Capture channel, store, Location link, product/variant link, external item identity, AIM quantity, provider quantity, sync status/error, and all timestamps. | A channel display is not a replacement for an AIM physical count. A confirmed-sync disagreement is a channel/publication or mapping issue, not permission to rewrite raw Available. | Use What syncs and who wins and the channel’s own sync or publication review. Do not change Available to hide a channel discrepancy. Stop and contact support if identity is unclear, provider and AIM still disagree after confirmed sync, a write would conceal the local discrepancy, or the issue crosses businesses. |