# Transaction Search by Item
A search input that filters the page's transaction list by the items inside those transactions. Type an item ID, UPC, name, or display name and the transaction list narrows to only transactions that contain matching items.
Pair it with a **Transaction List** or **Transaction Search** block on the same page — this block doesn't render its own list; it filters the one already on the page.
## Available in
* Page modules
* Order Form modules
* Dashboard modules
* Reports modules
## When to use
* Reporting pages where users need to find every transaction that included a specific item (e.g. for warranty lookup, recall handling, or sales analysis).
* Order-history pages where the user knows the item but not the transaction number.
* Audit and reconciliation flows that work back from item to transaction.
For a generic transaction-field filter (date range, customer, status), use **Transaction List Filter** instead.
## Settings
The block opens a configuration modal:
| Setting | Description |
| ------------------------ | ---------------------------------------------------------------------------------------------------- |
| **Title** | Heading shown above the search input. Default: *Search Transactions by Item*. |
| **Placeholder** | Input placeholder text. Default: *Enter item name, ID, or UPC...*. |
| **Search Button Label** | Default: *Search*. |
| **Clear Button Label** | Default: *Clear*. |
| **Search Fields** | Which item fields to search across — Item ID, Item Name, UPC Code, Display Name. Toggle each on/off. |
| **Default Record Types** | Which transaction types the search returns (Sales Order, Invoice, Return Authorization, etc.). |
## How it works
1. The user types a search term and clicks **Search**.
2. The block runs a SuiteQL query to find every transaction internal ID that contains an item matching the search term across the enabled search fields.
3. The matching transaction IDs are pushed into the page's transaction filter state.
4. The Transaction List or Transaction Search block on the page automatically narrows to those transactions.
5. Clicking **Clear** removes the filter and the list returns to its unfiltered state.
## Examples
**Recall lookup.** Configure search fields to *Item Name* and *Item ID*. When a recall is announced, the user pastes in the affected SKU and instantly sees every customer order that included it.
**Cross-sell analysis.** Search by item name to see every order that included a popular product — useful for spotting bundling patterns.
## Common issues
* **No results when results are expected** — verify the search term matches one of the enabled search fields. Some catalogs use UPC heavily and Item Name rarely; toggle accordingly.
* **Slow search on large datasets** — narrow the *Default Record Types* to only the types you care about (e.g. just Sales Orders, not all transaction types).
## Related
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.in8sync.com/client-admin-guide/active-workflows/getting-started/transaction-components/transaction-search-by-item.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.