Transactions
The Transactions tab of the Inventory page provides a complete ledger of inventory movements across your system. Every time an item changes location, whether through manual action, RFID scanning, or workflow automation, a transaction record is created. Use this page to audit item movements, investigate discrepancies, and track the flow of inventory through your facilities.
Overview
Transactions record the movement of inventory items between locations. Each transaction captures where the item came from, where it went, what type of transaction it was, and what triggered the movement. Close-out transactions (such as Ship or Consume) have no destination location: they remove the item from inventory and set its lifecycle state to Closed. An item with no location, whether it was never placed or has been closed out, is shown as Outside inventory.
From the Transactions tab you can:
- View all inventory transactions across items and locations, server-paged for fast performance even with a long history
- Search across items, tags, transaction types, locations, source, and description
- Filter by source location, destination location, transaction type, and date range
- Drill into a specific transaction's own page
For background on how transactions relate to lifecycle states, see Inventory Item Lifecycle.
Permissions
| Permission | What It Allows |
|---|---|
| View Inventory | Access the Transactions tab and view transaction history |
Search and Filtering
Text Search
Type in the search bar to filter across instance ID, item ID, item description, active tag, transaction type, from/to location names, source, and description. Search is case-insensitive and updates automatically after a brief typing pause. Paste a correlation ID (a full GUID) into the search bar and Tagnet matches it exactly: a quick way to find every transaction recorded by one bulk operation without opening the filter drawer.
Filter Bar
Click the filter icon on the right side of the filter bar to open the filter drawer:
| Filter | Description |
|---|---|
| From Location | Show transactions originating from this location (includes descendants) |
| To Location | Show transactions going to this location (includes descendants) |
| Transaction Type | Show only transactions of one or more specific types |
| Date | From/to date range. Dates are your local calendar days; Tagnet converts the boundaries to UTC internally so a day always means midnight to midnight where you are, not where the server is |
Each active filter appears as a chip below the search bar. Click the X on a chip to remove it, or Clear All to reset everything.
The Transactions Grid
Columns
| Column | Description |
|---|---|
| Time | When the transaction occurred |
| Instance ID | The inventory instance's own ID. Auto-generated GUID ids show as an Auto GUID badge; hover for the full value |
| Item | The catalog item ID, with its description beneath |
| Type | Transaction type with icon and color |
| Tag | The active RFID tag on the item at the time |
| From | Source location, or "Outside inventory" if the item had none |
| To | Destination location, or the disposition name (e.g., "Shipped") for close-out transactions |
| Source | What triggered the transaction (e.g., manual move, RFID scan, API, workflow); hidden by default |
| Correlation | A shortened prefix of the transaction's correlation ID, with the full GUID on hover; hidden by default |
| Created by | The user, workflow, or API key that recorded the transaction; hidden by default |
Use the column menu to show or hide columns; your preferences are saved between sessions.
Drill-Through Links
A few other places in the system link into the Transactions list with a filter already applied. The Movement card at the top of a location's, an item's, or an inventory item's page has a View transactions button: it opens the list filtered to that location, to every instance of that catalog item, or to that one inventory item. A transaction's own Correlation ID links to every other transaction recorded by the same operation. On an inventory item's Location History tab, clicking an entry opens that specific transaction's own page directly rather than a filtered list.
Grouping by Operation
Many transactions are recorded together: a dock door reads a truckload of pallets and a workflow moves all of them, or a Quick Import places a spreadsheet of items. To see each of those as one row instead of hunting for one transaction and filtering on its correlation ID, choose By operation in the arrangement selector at the left of the filter bar (it shows List by default). Your choice is kept for the session and in the page's address (?view=operations), so you can bookmark or share it.
Each row is one operation:
| Column | Description |
|---|---|
| Time | When the operation's latest transaction was recorded (hover the header for a reminder) |
| Caused by | The workflow that ran it, linked to the workflow execution, or the feature that recorded it: Quick Import, Commissioning, Pending mapping, Movement rules, Manual move, Live Reads, API, or System (Several sources if more than one recorded it) |
| By | The user or API key that recorded it, System for automated work, or Several people |
| Type | The transaction type, or Mixed when the operation recorded more than one |
| From / To | The one location the inventory came from and went to, Outside inventory, a location and outside inventory when only some items were placed or removed, or Several locations when they differ |
| Items | How many inventory items the operation moved |
The filters and search apply to the transactions before they are grouped, so an operation's row counts only the transactions that match. Sort by Time or by Items to find the largest operations.
A transaction recorded on its own (a manual move, an API call, an item's first location when it was created) is a row with one item, so every transaction appears exactly once. Clicking it opens that transaction's page.
Transactions are recorded as one operation when they come from the same workflow execution (Move Inventory and Movement Rules actions), the same Quick Import, the same mapping of a pending scan group, or the same commissioning batch.
Operation Page
Clicking an operation opens its page (/transactions/operations/{id}):
- Operation: when it happened (and how long it took, if it spanned more than a second), what caused it, who recorded it, the type, the from and to locations, how many items it moved, and its correlation ID
- Items: every inventory item the operation moved, with its RFID tag. Type, From and To columns appear here only when they differ between items. Click a row to open the inventory item.
View in list opens the regular Transactions list filtered to this operation's correlation ID, for sorting by any column. Back to Transactions returns to the grouped view.
Transaction Details
Click any row to open the transaction's own page (/transactions/{id}), showing:
- Movement: the from-location, transaction type, and to-location as a row of chips, so the "what happened" reads at a glance, with when it happened and its source beneath
- Details: Type, timestamp, source, the Operation it was part of (a link such as "10 items moved together", or "2 transactions recorded together" for one item, that opens the operation page; shown when other transactions were recorded with it), correlation ID (with a link to every transaction from that same operation in the list), and description
- Inventory Item: The instance and item this transaction belongs to, with a View inventory item button that opens it, plus the RFID tag active on it at the time
- Custom Fields: Any transaction-specific custom field values that have been set
- Audit Information: Created and updated timestamps with user attribution
Custom Fields on Transactions
New transaction custom fields can't be created for now: workflows don't record them yet, and in an RFID deployment most transactions come from workflows. Transaction fields created earlier still work where they did: the manual Move form captures them, and the transaction's page displays the ones with values. They're listed on the Transactions tab of the Custom Fields page, where they can still be edited and reordered.
Best Practices
- Use location filters for auditing: Filter by a specific location to see all inbound and outbound activity for that area.
- Check the Source column: It helps distinguish manual actions from automated ones when investigating unexpected movements. Show it from the column menu if you hide it by default.
- Search a correlation ID to see a whole operation: Paste the GUID from a transaction's Details section into the search bar, or follow the Correlation link, to see every transaction a single bulk mapping, import, or workflow run created together.
- Review regularly: Transaction history provides the audit trail needed for compliance and operational accountability.
- Use transaction types consistently: Define clear transaction types (Add, Move, Remove, Transfer, Ship, Consume) and use them consistently so the ledger is easy to interpret. Mark close-out types with the "Removes from inventory" toggle so lifecycle states update correctly.
- Filter on close-out types to audit outflows: Filter by a close-out transaction type (e.g., Ship) to see all items that left inventory through that channel.