> 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/delivery-order-prefix.md).

# Delivery Order Prefix

**YouTube:** [How to Configure Default Prefixes in Delivery Orders?](https://www.youtube.com/watch?v=PEVEwzt-dKU)

## How to Configure Default Prefixes in Delivery Orders?

In this tutorial, we will learn how to define a **default prefix** or configure **multiple prefixes** for Delivery Orders in Logic ERP.

This feature allows users to customize the Delivery Order prefix according to their business requirements and select the required prefix while creating a new Delivery Order.

***

### Access to the Delivery Order Configuration

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

> **"Delivery Order Prefix"**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2F5x6gOwocMXjlLRkKEJ1p%2FCNF.png?alt=media&amp;token=f9a7dea0-e467-43f2-933e-8536871ea91b" alt=""><figcaption></figcaption></figure>

***

### Define the Delivery Order Prefix

The **Delivery Order Prefix** option allows you to modify the existing prefix or define new prefixes.

* To modify the existing prefix, edit the default **DO** prefix.
* Enter the required prefix according to your business requirement.
* You can also define **multiple prefixes** by separating each prefix with a comma.
  * **Example:** DO, DL,DLO

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FOt6QHsH9zySuRVCSOWUH%2FDO%20Prefix.png?alt=media&amp;token=abfc6094-d83c-419e-ac46-1bf5ded5630f" alt=""><figcaption></figcaption></figure>

* Once the required prefixes are defined, save the configuration changes.

***

### Verify the Configured Prefixes

Now, let's verify the configuration.

* Reopen the **Delivery Order** window.
* Initiate a new Delivery Order entry.
* Open the **Delivery Order Prefix** dropdown.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2F0UX4EPw4idiGcdgDax33%2FOrder%20Prefix.png?alt=media&amp;token=524f1746-c4b1-4001-90c3-943fcb0d67f1" alt=""><figcaption></figcaption></figure>

**System Behavior**

* The dropdown now displays the prefixes defined in the configuration.
* Select the required prefix from the available list.
* Continue creating the Delivery Order using the selected prefix.

***

### Key Benefits

* Allows customization of the Delivery Order prefix.
* Supports multiple prefixes based on business requirements.
* Makes it easier to identify Delivery Orders using different prefixes.
* Provides flexibility when managing Delivery Order numbering.

#### Final Outcome

By configuring the **Delivery Order Prefix** under **Other Settings**, you can modify the default prefix or define multiple prefixes. These configured prefixes are then available in the **Delivery Order Prefix** dropdown for selection while creating a new Delivery Order.


---

# 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/delivery-order-prefix.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.
