> ## Documentation Index
> Fetch the complete documentation index at: https://betterdatainc.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Inventory Adjustments

> How to make inventory adjustments and corrections

# Inventory Adjustments

Inventory adjustments correct discrepancies between system inventory and physical inventory.

## Creating an Adjustment

1. Navigate to **Run** → **Adjustments**
2. Click **Create Adjustment**
3. Select:
   * **Location**: Where the adjustment occurs
   * **Product**: Product to adjust
   * **Adjustment Type**: Increase or decrease
   * **Quantity**: Amount to adjust
   * **Reason Code**: Reason for adjustment (industry-pack specific)

## Adjustment Types

### Increase

Add inventory to the system:

* **Found Inventory**: Physical inventory found but not in system
* **Return to Stock**: Returned items added back to inventory
* **Correction**: System count was too low

### Decrease

Remove inventory from the system:

* **Shrink**: Inventory loss (retail)
* **Damage**: Damaged items removed
* **Expired**: Expired items removed (Healthcare, Food & Beverage)
* **Correction**: System count was too high

## Reason Codes

Reason codes are industry-pack specific:

**Healthcare:**

* PATIENT\_DISPENSE
* EXPIRED
* DAMAGE
* RECALL

**Retail:**

* SHRINK
* CUSTOMER\_RETURN
* DAMAGE
* THEFT

**Manufacturing:**

* WO\_ISSUE
* REWORK
* SCRAP
* DAMAGE

## Adjustment Workflow

1. **Create**: Enter adjustment details
2. **Review**: Review before applying
3. **Approve**: Approval may be required (configurable)
4. **Apply**: Adjustment is applied to inventory
5. **Audit**: Adjustment is logged for audit trail

***

## Related Pages

* [Inventory Overview](/sense/inventory-overview)
* [Cycle Counts](/execute/cycle-counts)
* [Viewing Inventory](/execute/viewing-inventory)

***

## Permissions & Roles

<Tip>
  Making adjustments requires inventory management permissions. Some adjustments may require approval. Contact your organization administrator for details.
</Tip>