> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/stock/record-stock-transactions.md).

# Record stock transactions

Use stock transactions when a stock change does not come from a work order.

This keeps your warehouse history complete.

### Common transaction types

Use stock transactions for:

* receiving deliveries
* correcting damaged or missing goods
* moving stock between warehouses
* updating stock after an inventory count

### Why transaction history matters

A clear transaction history helps you understand how stock changed.

It also helps you correct mistakes faster.

### Good practice

Add transactions as soon as the change happens.

Review unusual corrections quickly.

Use one consistent process for all warehouses.

### Frequently asked questions

<details>

<summary>When do I need a stock transaction?</summary>

Use one when the stock change did not come from normal material usage on a work order.

</details>

<details>

<summary>Can I use transactions to correct mistakes?</summary>

Yes.

Transactions are the right place for stock corrections.

</details>

<details>

<summary>Can I move stock between warehouses?</summary>

Yes.

You can use transactions to record transfers between locations.

</details>

### Related topics

* [**Stock**](/marketplace-packages-and-power-ups/power-ups/stock.md)
* [**2BA**](/marketplace-packages-and-power-ups/power-ups/2ba.md)
* [**Power-Ups**](/marketplace-packages-and-power-ups/power-ups.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/stock/record-stock-transactions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.