> 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/order-processing/generate-delivery-orders/generate-delivery-orders-configuration/print-delivery-order-after-save.md).

# Print Delivery Order After Save

**YouTube:** [How to Allow Delivery Order Printing After Saving?](https://youtu.be/sz2CLLiJaTM)

## How to Allow Delivery Order Printing After Saving?

In this tutorial, we will learn how to **automatically print a Delivery Order after saving** in Logic ERP.

***

### Understand the Default Behavior

* Initiate a new **Delivery Order** entry.
* Click on **Sales Order Selection**.
* Select the required **Sales Order**.
* Click on the **Generate Order** button.
* Select the required row in the document grid.
* Click **Save**.

**Result:** By default, the Delivery Order is saved without prompting to print it.

***

### Enable Print Delivery Order After Save

* Open the **Delivery Order Configuration** window.
* Navigate to the **General Settings** section.
* Locate and enable the option labeled as:

> **"Print Delivery Order After Save"**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FVgXfp0COX0HcmcyE7g1w%2FCNF.png?alt=media&amp;token=2a52e87a-114e-4531-b91c-9c3a657fa563" alt=""><figcaption></figcaption></figure>

* Save the configuration changes.

***

### Verify the Configuration

* Initiate a new **Delivery Order** entry.
* Click on **Sales Order Selection** and select the required **Sales Order**.
* Click on the **Generate Order** button.
* Select the required row in the document grid.
* Click **Save**.

**Result**

As soon as you click **Save**, the software displays a confirmation message asking

> **"Are you sure to print the selected delivery order?"**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FrmXAVcYI4Shl5CyoFSbY%2FPrompt.png?alt=media&amp;token=101e1bd3-a052-4eea-9afc-08d4b647892c" alt=""><figcaption></figcaption></figure>

* Select **No** to save the Delivery Order without printing.
* Select **Yes** to save the Delivery Order and open the selected print format in **Print Preview**, where you can review and print the Delivery Order.

***

### Key Benefits

* **Quick Printing:** Print the Delivery Order immediately after saving.
* **User Confirmation:** Choose whether to print the document or not.
* **Improved Workflow:** Reduces the need to manually open the print option after saving.
* **Easy Review:** Preview the selected print format before printing.


---

# 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/order-processing/generate-delivery-orders/generate-delivery-orders-configuration/print-delivery-order-after-save.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.
