Logiwa IO allows warehouse administrators to require users to provide an adjustment reason whenever inventory quantities are manually updated. Once enabled, the system displays a validation prompt — blocking the operation until a reason is selected — ensuring a complete and accurate audit trail for all inventory changes.

The requirement is configured at the warehouse level and controlled by two separate flags, each targeting a different type of operation.

Navigate to Warehouse Setup and locate the Adjustment Reason settings. Two independent toggles are available:

Both flags default to off for existing warehouses. They can be enabled independently — for example, you may require a reason for cycle counts only, without enforcing it for manual adjustments.

When Require Adjustment Reason for Manual Updates is enabled, an adjustment reason becomes mandatory for the following actions on the Inventory by Location screen:

A dropdown to select the reason will appear in the sidebar before the action can be saved.

When the flag is enabled, the Add Inventory Excel Import requires an Adjustment Reason column to be populated for each row belonging to that warehouse. Rows with a missing or invalid reason will fail individually and be logged in the Import History screen. Valid rows in the same file will still process successfully.

When the flag is enabled, the following Open API endpoints require the adjustmentReasonName field in the request payload:

If the field is missing when the flag is on, the API returns a 400 Bad Request with the message: "Adjustment Reason is required for this warehouse by policy."

When Require Adjustment Reason for Cycle Count Updates is enabled, a reason selection prompt appears when using the Update Inventory action on the:

The update cannot be committed until a reason is selected.

After completing a location count on the mobile app, if a quantity difference exists between the counted and system quantities, an Adjustment Reason bottom sheet appears before the inventory update can proceed. The operator selects a reason from the configured list and confirms.

When the flag is enabled, the cycle count inventory update endpoint also enforces the requirement:

All adjustment reasons provided — regardless of entry point — are recorded in the Transaction History Report under the relevant transaction line, providing a full audit trail of all inventory changes and the reasons behind them.

Couldn't Find What You Were Looking For?

Visit our Help Center to search for more documents!