Skip to main content
Inventory transactions record stock movements that aren’t tied to a purchase or sale — adjustments (correcting on-hand up or down) and transfers (moving stock between warehouses). Each transaction allocates quantities to specific bin locations and follows a draft-to-posted lifecycle.

​
Prerequisites

​
Transaction types

To count a whole warehouse, aisle, or item set against system quantities and post the variances in one approved batch, use Inventory counts instead of entering adjustments line by line. Posted counts appear in this list as adjustments sourced from the count. A customer return that you receive posts its own restock movement — quantity back on hand at the item’s posting cost — rather than an adjustment you enter here.

​
Record an inventory transaction

1

Open Inventory Transactions

  1. In the sidebar, open Inventory.
  2. Click Inventory Transactions.
The list shows each transaction with its type, date, and status. Search matches transaction number, type, warehouse, or status, and the Type and Status column filters offer the labeled values. Click a row to open it.
2

Create a new transaction

Click New and choose Adjustment or Transfer. For a transfer, pick the from and to warehouses.
3

Add lines

On the line grid, pick each item and enter the quantity:
  • Adjustments take a signed quantity — enter a negative number to reduce on-hand. Pick a Reason (Damage, Theft, Cycle count, Found, Promo / Sample, Write-off) and confirm the unit cost; it defaults to the item’s cost.
  • Transfers take a positive quantity to move from the source to the destination warehouse.
4

Allocate to bins

In the bin allocation cell, assign the quantity across bin locations. adorabl shows a remaining-quantity indicator and flags over-allocation so every unit is placed before you post.
5

Post

  • Save as Draft — keeps the transaction editable with no stock or GL impact. Drafts display as Draft — the transaction number is assigned when you post.
  • Save — updates on-hand and bin quantities. Adjustments also post a journal entry: a decrease debits the reason’s offset account and credits Inventory; an increase debits Inventory and credits the offset account. The transaction shows a link to its journal entry.
Posted transactions can be voided from the overflow menu, which reverses the stock and bin movements and, for adjustments, posts a reversing journal entry.
Bin allocation here mirrors the model used when receiving stock against a purchase order. See Purchasing and Bin locations.

​
Example: Trail Ridge Outfitters

A cycle count at the Denver DC finds two fewer AP-3300-NV daypacks than the system shows. Trail Ridge records an Adjustment for -2 with reason Cycle count, allocated to bin A-12-3, and posts it. On-hand and the bin balance both drop by two, and a journal entry debits 5150 · Inventory Shrink and credits 1300 · Inventory for $74.00 (2 × $37.00). When the Shopify 3PL location runs low, Trail Ridge records a Transfer of 40 units from Denver DC to Shopify 3PL, allocating out of the source bins and into the destination bins. Quantity moves; no journal entry is created.

Stock on hand

See resulting quantities across warehouses and bins.

Bin locations

Set up the bins you allocate to.

Warehouses

Define the locations you move stock between.

Items

Only Stock-type items track quantity.

Adjustment reasons

Map each reason to the account it posts against.

Inventory counts

Count a warehouse and post variances as one approved batch.

​
Troubleshooting

Confirm every line has an item and quantity, and that the full quantity is allocated to bins with no over-allocation. For transfers, both warehouses must be set.
Map the reason to an offset account under Adjustment reasons, and make sure the line has a unit cost (or the item has a cost to default from). Drafts save without either; posting requires both.
The transaction date falls in a period where inventory posting is closed. Change the date or reopen the period in Fiscal calendar.
Only posted transactions move stock. A draft has no inventory impact until you post it.
Use Void on the posted transaction. adorabl reverses the on-hand and bin allocations rather than editing the original in place.