Stock Adjustments
Bringing the system into line with what is physically on the shelf after a count.
DigitalKey ERP — Docs · digital-key.co/docs/warehouses/stock-adjustment
warehouse.manage5,000 IQD / monthOverview
However carefully stock is managed, the recorded figure and the shelf drift apart — breakage, miscounts, unrecorded samples. An adjustment records what you actually counted and moves the system to match it.

System versus actual
Each line holds two numbers, and the difference between them is the adjustment:
| Parameter | Type | Required | Description |
|---|---|---|---|
qty_system | decimal | Optional | What the system believes is held in the warehouse you counted. Filled in for you. |
qty_actual | decimal | Required | What you actually counted. This is what you enter. |
unit_cost | decimal | Optional | Cost per unit, used to value the difference. |
- 1
Count the stock
Do the physical count first, on paper or on a tablet. Counting against a screen that already shows the expected number invites confirmation bias.
- 2
Start an adjustment
Go to Warehouses and create a new stock adjustment.
- 3
Choose the warehouse
Say which location was counted. Optional for a single-location business.
- 4
Enter the counted quantities
Add each product you counted and enter the actual figure. The system quantity and the difference are shown as you go.
Warehouses — Adjustment lines
Adjustment lines — Counted quantities with the differences from the system figure highlighted. - 5
Record the reason
Say why the count differs — annual stocktake, spot check, suspected loss. This is what makes the adjustment defensible later.
- 6
Save
Stock is set to the counted figures and a movement is written for each change.
Fields
| Parameter | Type | Required | Description |
|---|---|---|---|
warehouse_id | integer | Optional | Location counted. Optional for single-location businesses. |
reason | string | Optional | Why the adjustment is being made. |
notes | string | Optional | Any further detail. |
items | array | Required | The counted lines. |
items[].product_id | integer | Required | Product counted. |
items[].qty_actual | decimal | Required | Quantity actually counted. |
items[].unit_cost | decimal | Optional | Cost per unit, for valuing the difference. |
The adjustment record
| Parameter | Type | Required | Description |
|---|---|---|---|
adjustment_id | integer | Optional | Internal identifier. |
adjustment_no | string | Optional | Reference number. |
adjustment_date | timestamp | Optional | When it was made. |
warehouse_name | string | Optional | Resolved location name. |
Who can adjust
Adjustment or damage?
Good practice
- Count when the shop is closed, so nothing moves mid-count.
- Count high-value and fast-moving lines more often than everything else.
- Investigate large differences before posting them — a miscount is cheaper to fix than a wrong write-off.
- Always fill in the reason. In six months it is the only thing that will explain the movement.
Related
- Stock Management — damage records and movement history.
- Stock Transfers — moving rather than correcting.
- Smart Reports — finding dead stock before it becomes a write-off.