> 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-version-release-notes/january-2026/order-processing/billing-and-shipping-address-in-sale-order.md).

# Billing & Shipping Address in Sale Order

Logic ERP has introduced a new update that allows you to enter both Billing and Shipping Addresses for unregistered parties in Sales Orders.\
Earlier, this option was not available, but with this update, users can now easily add complete address details while creating a Sales Order for an unregistered party.

***

### Steps to Define shipping and Bill Address

* Create a new **Sales Order**.
* Select an **Unregistered Party**.
* Enter the **Billing Address** and **Shipping Address**.
* Fill in the required **Other Details** and save the order.
* After saving, retrieve the same order in the **Sales Bill**.
* You will notice that the process is now **much easier**, as all the saved details are **automatically Retrieved** with Shipping Details.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FQyrfEERSP9ZkLxR6lB5p%2FRet.png?alt=media&amp;token=52212882-3346-41cb-9177-2365934be1e8" alt=""><figcaption></figcaption></figure>


---

# 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-version-release-notes/january-2026/order-processing/billing-and-shipping-address-in-sale-order.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.
