> For the complete documentation index, see [llms.txt](https://kb.logicerp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/setups/configurations/sale-voucher-configuration/other-settings-1/do-not-affect-stock.md).

# Do Not Affect Stock

**YouTube:** [How to Disable Any Effect in the Stock While Billing?](https://www.youtube.com/watch?v=A2wLSqDYnjo)

## How to Disable Any Effect in the Stock While Billing?

In this Tutorial, we explore how to prevent stock levels from being affected during billing in Logic ERP. This feature proves invaluable for managing non-inventory items or specific scenarios where stock updates are unnecessary.

#### Steps to Follow:

1. **Pre-check Stock Levels:**
   * Verify the stock of the item in the stock reports. For example, the closing stock for a particular item is 52,985 units.
2. **Sale Voucher Configuration:**
   * Navigate to the sale voucher configuration settings.
   * Select the relevant billing series.
   * Enable the "Do not affect stock" option and save the changes.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2Fe2tLypvWjI0MLJrivade%2FDo%20not%20affect%20Stock%20Configuration.png?alt=media&amp;token=a57e9cdc-758e-4847-b77f-a2b9e5e6a7f3" alt=""><figcaption><p>Let's enable this feature and observe its impact in Billing</p></figcaption></figure>

1. **Processing with the Sale Bill:**
   * Proceed to the sale bill and transact the item whose stock was checked earlier.
   * Verify the stock report again; notice that stock levels remain constant during billing.

This feature is useful for managing non-inventory items or situations where stock updates are not needed. I hope you found this tutorial helpful.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/setups/configurations/sale-voucher-configuration/other-settings-1/do-not-affect-stock.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
