> 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/generate-indirect-party-wise-do.md).
# Generate Indirect Party Wise DO
**YouTube:** [How to Generate Indirect Party-Wise Delivery Orders?](https://youtu.be/uRdESFGAt80)
## How to Generate Indirect Party- Wise Delivery Orders?
In this tutorial, we will learn how to enable the option to generate a **Delivery Order based on the Indirect Party** defined in a Sales Order.
***
### Understand the Default Behavior
* Click on **Sales Order Selection**.
* Select the required **Sales Order**.
* Click on **Generate Order**.
**Result:** By default, the Delivery Order is generated based on the **Customer Name** defined in the Sales Order.
***
### Let's Enable Indirect Party-Wise DO
* Open the **Delivery Order Configuration** window.
* Navigate to the **General Settings** section.
* Locate and enable the option labeled as:
> **"Generate Indirect Party Wise DO"**
* Save the configuration changes.
**Generate the Delivery Order**
* Reopen the Delivery Order window.
* Initiate a new entry.
* Click on **Sales Order Selection**.
* Select the required **Sales Order**.
* Click on **Generate Order**.
**Result:** The **Party Name** column now displays the **Indirect Party Name** defined in the selected Sales Order.
This allows you to generate the Delivery Order based on the **Indirect Party**, instead of the primary customer defined in the Sales Order.
***
### Final Outcome
After enabling **"Generate Indirect Party Wise DO"**, Logic ERP automatically considers the **Indirect Party** defined in the Sales Order while generating the Delivery Order, providing greater flexibility in party-wise order processing.
---
# 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/generate-indirect-party-wise-do.md?ask=&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.
