> 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-wait-for-next-button-press.md).

# Do Not Wait for NEXT Button Press

[How to Enable Auto-Move to Next Row After Barcode Scan in Sale Bill ?](https://www.youtube.com/watch?v=b-G9yU7iWEs)

## How to Enable Auto-Move to Next Row After Barcode Scan in Sale Bill?

 This tutorial explains how to enhance billing efficiency in **Logic ERP** by enabling an option that removes the need to manually press the “Next” button after scanning an item.

***

### Access Sales Voucher Configuration

* Navigate to Sales Voucher Configuration.
* Select the relevant billing series.
* Locate and disabled the option “Do Not Wait for NEXT Button Press”
* Let’s first keep this option disabled and see how it behaves.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2F05SVKCQrf2qWn3nfLSmD%2FDo%20Not%20Wait%20for%20NEXT%20Button%20Press%20-%20Configuration.png?alt=media&amp;token=c10bfc91-f45a-41c0-b531-3055f725543e" alt=""><figcaption><p>Let's keep this feature Disabled and Observe its Impact</p></figcaption></figure>

* **Note:** This feature functions only when:
  * **"Lot selection is set to Auto Pick"** and "**Default Quantity is set to 1"** under the Other Settings-2.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FYtsUcPPMWBh3C9VYMmGQ%2FOther%20Settings%202.png?alt=media&amp;token=858462cf-1c36-47e3-8834-c5a9b0477c26" alt=""><figcaption><p>To use this feature, you must configure both of the options shown, as explained above.</p></figcaption></figure>

***

### Implement the Feature (Disabled)

* Navigate to the Sale Voucher and create a new Sale Bill.
* Scan or enter the **item code**.
* You’ll Observe:

  > The **Enter key must be pressed** to move to the next line, even when Auto Pick and default quantity settings are applied.

***

### Implement the Feature (Enabled)

* Return to **Sales Voucher Configuration**.
* Enable the checkbox for: **“Do not wait for the next button press”**
* Save the configuration.
* Now initiate a new billing transaction.
* Scan or enter an item code.
* You’ll Observe:

  > The **cursor automatically jumps to the next row**, streamlining the billing flow.

***

### Conclusion

By enabling this feature, you can:

* **Speed up item entry during billing**
* **Reduce manual keystrokes**
* **Improve overall cashier productivity**
* **Enhance the user experience** at the point of sale


---

# 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-wait-for-next-button-press.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.
