> 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/sales-order-add-freight-charges-before-and-after-gst.md).
# Sales Order: Add Freight Charges Before & After GST
Logic ERP has introduced a new update to simplify freight calculation in Sales Orders. With this update, you can now add freight charges or any other expenses in the Sales Order, either before or after GST.
***
### Step 1: Applying Freight Charges **After Tax**
* First, enable the **Other Value** column from **Column Lock**.
* Create a new **Sales Order** and proceed with item selection.
* Click on **Other Details** and enter **Freight = ₹100** in **Other Value 1**.
* Click **OK**, then reopen the **Other Details** section.
* You will notice that **freight is applied after tax**.
***
#### Step 2: Applying Freight Charges **Before Tax (Voucher Level)**
* Press **F7** to open the **Calculation Configuration** screen.
* Select **Other Value 1**.
* Reposition it **above the tax fields**.
* Ensure the **Calculation Type** for **Other Value 1** is set to **Item Wise**.
* **Important Notes**
* Count the total number of calculation fields up to **Tax 2**.
* Set the **position numbers correctly** for **Tax 1** and **Tax 3**.
* Return to the **Sales Order** screen and repeat the same steps as earlier.
* You will now see that **freight is applied before tax**.
> To apply freight calculation for all Sales Orders Series, Navigate to **Sale Order Configuration → Calculation Mode** and set whether freight charges apply **before or after tax**.
For more detailed information, [click here](/logic-erp-learning-hub-tutorials-and-best-practices/order-processing/sale-order/add-freight-charges-in-sales-orders.md).
---
# 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/sales-order-add-freight-charges-before-and-after-gst.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.
