# Adjust stock and investigate stock movements
URL: https://support.starshipit.com/articles/14700000000020-adjust-stock-and-investigate-stock-movements
Canonical: https://support.starshipit.com/articles/14700000000020-adjust-stock-and-investigate-stock-movements
Markdown: https://support.starshipit.com/articles/14700000000020-adjust-stock-and-investigate-stock-movements.md
Updated: 2026-09-15

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

> Use stock adjustments, movement logs, and process logs to keep inventory accurate and maintain a reliable audit trail over time.

Even with well-run processes, inventory drifts over time. Damage, mis-picks, supplier short-ships, and process gaps all create small variances that compound. The tools in this guide help you correct those variances and understand why they happened.

**Stock integrity** tools in WMS include:

* **Manual stock adjustments** — immediate corrections to on-hand quantities
* **CSV adjustment batches** — import or export manual adjustment batches when many rows need correction
* **Location-wide adjustments** — adjust all inventory in a location when a whole area needs correction
* **Packaging inventory** — tracking consumable packaging items
* **Stock movement logs** — a line-by-line history of every inventory change
* **Process logs** — a timeline of system events (orders, jobs, syncs)
* **Process log warnings** — actionable alerts for issues that need attention

## Manual stock adjustments

Use **stock adjustments** to correct inventory outside of a stocktake. Common uses:

* Recording damaged or lost stock
* Accounting for shrinkage or theft
* Adding found stock to the system
* Correcting a known data entry error quickly

### Creating an adjustment

You need `inventory.adjust` and existing products and locations to create adjustments.

1. Go to **Inventory > Stock Adjustments > Adjustments**.
2. Select the **product (SKU)**.
3. Choose the **location** — the form shows current quantities at each location so you can make an informed choice.
4. Enter the **quantity** (positive to add stock, negative to remove it).
5. Select a **reason code** (Damage, Found, Administrative correction, etc.).
6. Select **Add adjustment to batch**.
7. Review the queued rows, then select **Submit adjustments**.

For batch- or serial-tracked products, WMS will prompt you to select or enter the specific batch or serial number being adjusted. This keeps traceability intact.

The adjustment builder shows the product, location, current stock, quantity change and reason before you add the line to a batch.

![The manual stock adjustment builder with product, location, quantity and reason fields](/uploads/articles/starshipit-wms/web/inventory-management/stock-adjustment.png)

Each successful submitted adjustment updates on-hand inventory and creates a stock movement record. Adding or importing a queued row does not change inventory.

:::note
Use adjustments sparingly. Frequent adjustments usually indicate a process issue rather than a one-off event. Review patterns in movement logs to identify root causes.
:::

### Adjustment batches and location corrections

For larger corrections, use CSV import and export on **Inventory > Stock Adjustments > Adjustments**. Each batch supports up to 200 rows, and import files must be 5 MB or smaller. There is no standalone blank adjustment template.

1. Add a representative adjustment to the batch.
2. Select **Export batch (count) (CSV)** to download the queued batch. The count shows the number of queued rows.
3. Edit that file with the required corrections, keeping the headers and required tracking details.
4. Remove any queued rows duplicated in the file, then select **Import CSV**. Imported rows are added to the existing batch.
5. Review the queued rows and validation errors, then select **Submit adjustments**.
6. Verify the resulting balances and stock movements. Successful rows leave the queue; correct and retry only the failed rows.

Split larger corrections into batches of up to 200 rows. See [Import and export WMS data by CSV](/articles/14700000000041-import-and-export-wms-data-by-csv) for the adjustment columns.

For physical reconciliation, use **Inventory > Stocktakes** to export a stocktake CSV, enter counted quantities, and import the file to submit the counts. See [Run stocktakes and cycle counts](/articles/14700000000015-run-stocktakes-and-cycle-counts) for approval and processing. Use location-wide adjustment only when the entire location has been counted or cleared and you are confident every line should change.

## Packaging inventory

Packaging materials (boxes, satchels, void fill, inserts) can be tracked as inventory in WMS:

* Adjust packaging stock the same way as product stock
* Movement logs provide a full audit trail for packaging consumption
* When an order ships, packaging is automatically decremented if packaging items are configured on shipments

## 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 the **Refresh** action on the movement log view to pull the latest data if recent changes are not yet visible.

Filtered stock movement views can be exported. Use this 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.

## 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.

## Practices for long-term stock integrity

* **Use consistent reason codes.** Standard codes (Damage, Lost, Found, Stocktake variance, Supplier error) make it possible to report on patterns.
* **Schedule cycle counts.** Count fast-moving, high-value or problem-prone SKUs regularly — weekly or fortnightly for the highest-risk items.
* **Restrict who can create manual adjustments.** Limit this permission to specific roles to reduce untracked or accidental changes.
* **Align with finance.** Write-offs and scrap recorded in WMS should be reflected in your financial systems where applicable.
* **Review movement logs regularly with your team.** When issues arise, walk through the log together to identify what happened and build better habits.