# Investigate WMS inventory discrepancies
URL: https://support.starshipit.com/articles/14700000000092-investigate-wms-inventory-discrepancies
Canonical: https://support.starshipit.com/articles/14700000000092-investigate-wms-inventory-discrepancies
Markdown: https://support.starshipit.com/articles/14700000000092-investigate-wms-inventory-discrepancies.md
Updated: 2026-11-08

> For the complete documentation index, see [llms.txt](https://support.starshipit.com/llms.txt).

> Trace an unexpected stock balance through movement and process logs, count the affected stock and choose a reviewed correction.

Investigate an unexpected stock balance before changing it. Identify the affected SKU and location, trace its recorded movements and count the physical stock to establish the correct quantity.

## Before you begin

You need access to the affected inventory and logs. A count, stock adjustment or integration sync requires its own permissions. Record the SKU, location, expected quantity and approximate time of the difference.

## Investigating a discrepancy

When you find unexpected variances during a stocktake, cycle count or order shortfall, use this approach:

1. **Identify the scope** — which SKU? which location? is it a one-off or recurring?
2. **Check movement logs** for:
   * Recent adjustments you were not aware of
   * Unusually large or small receipt quantities
   * High-volume picks or expedited flows that may have bypassed normal scanning
   * Returns or write-off adjustments
3. **Check process logs** for:
   * Orders that changed, were cancelled, or were re-allocated close to the time of the variance
   * Expedited flows (Pack Now, Batch Pack Now) that completed picks without scanning
4. **Run a cycle count** for each affected product and location to confirm the physical quantity.
5. **Post a correction** via cycle count or manual adjustment with an appropriate reason code.
6. **Address the root cause** — update processes, add training, or adjust location setup to prevent recurrence.

## Stock movement logs

Every inventory change — regardless of how it happened — is recorded as a **stock movement**. These logs are your primary audit tool.

Common movement reasons you will see:

| Reason | What triggered it |
|---|---|
| RECEIVE | Stock received against a purchase order |
| PUTAWAY | Moved from staging to a storage location |
| PICK | Collected for an order |
| TO_BENCH | Staged to a packing bench |
| SHIPMENT | Shipped on a completed order |
| ADJUSTMENT | Manual stock correction |
| STOCKTAKE_VARIANCE | Change posted from a stocktake or cycle count |
| REPLENISHMENT | Moved from bulk to a pick face |
| KITTING | Stock consumed or created by a kitting job |

For batch- and serial-tracked products, logs are linked to specific batch or serial numbers — supporting recall, compliance and supplier dispute scenarios.

The **Actor** column and expanded movement details show who performed each new movement. User actions show the recorded user, automated movements show **System**, and older movements created before actor tracking show **Unknown**. The Actor value is also included when you export filtered movement history to CSV.

Use **Process** to select broad groups such as **Direct Receiving**, **Cross-dock Receiving** or **Putaway**, and **Reason** to narrow the exact movement description. Both filters support multiple selections. Process groups are based on recorded reason text; check the movement details to confirm what happened. Combine these with product, location, reference and date filters to focus an investigation.

Select **Refresh** to load recent changes, then export the filtered movement history when investigating a supplier issue, customer claim, stocktake variance or finance reconciliation.

## Process logs

**Process logs** record higher-level system events:

* Order imported into WMS, and status changes (PENDING → RELEASED → SHIPPED)
* Pick and pack job creation and completion
* Expedited flows (Pack Now, Batch Pack Now)
* Product syncs from Starshipit or connected commerce platforms
* Background operations and scheduled tasks

Process logs also capture commerce inventory sync results — useful when investigating whether a failed sync caused a discrepancy between WMS and a connected storefront or inventory platform.

Process log rows can be actioned in bulk where supported, such as resolving reviewed entries or retrying eligible failed processes. Older process logs may move into archive storage, so use filters and date ranges when investigating historical issues.

### Actionable warnings in process logs

The Dashboard surfaces **actionable warnings** for issues that need your attention, such as:

* Missing SKUs during order import (an order arrived but WMS did not recognise a product SKU)
* Integration errors during inbound or outbound flows

Each warning includes context about what went wrong and options to:

* **Retry the import** — re-attempt the operation using the stored event
* **Create missing SKUs** — navigate to product creation pre-filled with the missing details
* **Dismiss** — mark as resolved if the issue is no longer relevant

Warnings automatically resolve when the underlying issue is fixed.

## Verify the correction

After a reviewed count or adjustment, refresh the product and location balances. Check the corrective movements and the connected platform’s completed writeback if applicable. Keep the original movement history so the cause and correction remain traceable.

## Related articles

* [Adjust stock in WMS](/articles/14700000000020-adjust-stock-in-wms)
* [Run stocktakes in WMS](/articles/14700000000015-run-stocktakes-in-wms)
* [Reconcile WMS stock movements and costs](/articles/14700000000076-reconcile-wms-stock-movements-and-costs)
* [Manage background work in WMS](/articles/14700000000066-manage-background-work-in-wms)