> For the complete documentation index, see [llms.txt](https://docs.xorosoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xorosoft.com/whats-new/release-notes/current-release/september-2026-release.md).
# September 2026 Release
{% hint style="warning" %}
This is a Custom Release. Feature availability depends on configuration and rollout status. Some features listed above may not be visible in your environment if they are part of a staged or custom deployment. Please contact your support representative to confirm enablement.
{% endhint %}
### **Customer Tags Column Added in On SO Details**
**Overview**
Customer Tags assigned to customers are now displayed in the **On SO Details** view of an item. This enhancement allows users to quickly identify the tags associated with customers who have Sales Orders for a specific item.
***
**Key Enhancements**
* Added the **Customer Tags** column to the **On SO Details** view for the selected item.
* Customer Tags assigned to a customer are automatically displayed against the customer's Sales Order.
* The tags displayed are based on the **Customer Tags** assigned to the respective customer from the **Other Info** tab of the Customer record.
***
**How It Works**
**Step 1:** Go to **Sales → Customer Section → Customer** and set the required **Customer Tags** in the **Other Info** tab of the Customer record.
Verify the newly created customer record in the **Customer Centre**.
**Step 2:** Create a **Sales Order** for the customer. In the **SO Details** section, click the **Availability** icon for the required item.
**Step 3:** The **Qty Details** pop-up opens. Click the value displayed under **On SO**.
**Step 4:** The **On SO Details** view opens and displays the Sales Orders for the selected item. The **Customer Tags** column displays the tags assigned to the customers associated with those Sales Orders.
***
### **Automatic Order Linking When Creating PO/TPO**
**Overview**
The **Inventory Snapshot** and **Short Inventory Planner** modules have been enhanced to provide greater control over **Sales Order-to-Purchase Order linking**.
When the **Auto Create Order Linking When Creating Purchase Order/Transfer Purchase Order** App Config is enabled, users can now configure default values for the **Link SO to PO** and **Link SO to Existing PO** options through **Page Defaults**.
The linked Sales Order and Purchase Order can be viewed from their respective **SO/PO** through the **Linked Orders** tab.
***
**Key Enhancements**
* Added **Page Default** options for the **Link SO to PO** and **Link SO to Existing PO** toggles.
* The **Link SO to PO** and **Link SO to Existing PO** Page Default options are displayed only when the **Auto Create Order Linking When Creating Purchase Order/Transfer Purchase Order** App Config is enabled.
* Added a new **Link SO to PO** toggle to the **Create new PO by default vendor** action in the **Options** menu.
* The new **Link SO to PO** toggle is displayed only when the **Auto Create Order Linking When Creating Purchase Order/Transfer Purchase Order** App Config is enabled.
***
**Configuration Details**
* **App Config Name:** Auto create order linking when creating purchase order/Transfer purchase order
* **Configuration Location:** Menu → App Config → Purchase → **Auto create order linking when creating purchase order/Transfer purchase order**
***
**Functionality**
**When App Config Is Enabled**
* The **Link SO to PO** and **Link SO to Existing PO** options are available under **Page Defaults** in the **Inventory Snapshot** and **Short Inventory Planner** modules.
* When **Link SO to PO** is enabled, the Sales Order is automatically linked to the Purchase Order when a new PO is created from the **Create new PO** header-level option.
* When **Link SO to Existing PO** is enabled, the Sales Order can be linked to an existing Purchase Order when the **Add to Existing PO** header-level option is used.
* The **Link SO to PO** toggle is also available in the **Create new PO**, **Add to Existing PO**, and **Create new PO by default vendor** popups.
***
**When App Config Is Disabled**
* The **Link SO to PO** and **Link SO to Existing PO** options are hidden in **Page Defaults**.
* The **Link SO to PO** toggle is also not available in the **Create new PO**, **Add to Existing PO**, and **Create new PO by default vendor** pop-ups.
As a result, SO-to-PO linking controls are unavailable in the **Inventory Snapshot** and **Short Inventory Planner** modules, and any required linking must be performed manually from the **Purchase Order** or **Sales Order** screen.
***
**How It Works**
**Step 1:** Go to **Menu → App Config → Purchase** and enable the **Auto Create Order Linking When Creating Purchase Order/Transfer Purchase Order** App Config.
**Step 2:** Create a **Sales Order** for the required item and release the order.
**Step 3:** Open the **Short Inventory Planner**. Click the **vertical three-dot (ellipsis) menu** and select **Page Defaults**.
**Step 4:** Enable the **Link SO to PO** toggle to set the required default behavior, and click **Save**.
**Step 5:** Select the required item record. Click the **Options** menu and select **Create new PO**.
**Step 6:** The default vendor configured for the selected item is automatically selected in the **Select Vendor for PO** pop-up.
The **Link SO to PO** toggle is enabled by default based on the configured Page Default settings, allowing the Sales Order to be linked to the new Purchase Order. Click **Add To PO**.
**Step 7:** The Purchase Order for the selected item is created once you save it.
Go to the **Linked Orders** tab, where the associated Sales Order is displayed under the **Sales Order** sub-tab.
**Step 8:** Similarly, open the created Sales Order and go to the **Linked Orders** tab. The associated Purchase Order is displayed under the **Purchase Order** sub-tab.
***
### **Linked Order Numbers in Item Sales and Purchase History**
**Overview**
The **Item View** subform has been enhanced to display linked order numbers in the **Sales History** and **Purchase History** tabs.
***
**Key Enhancements**
* Added a **Linked Order Numbers** column to the **Sales History** and **Purchase History** tabs in the **Item View**.
* The **Sales History** tab displays the **Purchase Order** numbers linked to the item's Sales Orders.
* The **Purchase History** tab displays the **Sales Order** numbers linked to the item's Purchase Orders.
* Multiple linked order numbers are displayed when applicable.
***
**How It Works**
**Step 1:** Navigate to **Admin → Item → Item Centre** and double-click the required item record.
**Step 2:** The **Item View** subform opens. Go to the **Sales History** tab. The **Linked Order Numbers** column displays the Purchase Order numbers linked to the item's Sales Orders.
**Step 3:** Open the **Purchase History** tab. The **Linked Order Numbers** column displays the Sales Order numbers linked to the item's Purchase Orders.
***
### **Display UPC in TSO and TPO Details**
**Overview**
The **Transfer Sales Order** and **Transfer Purchase Order** detail sections have been enhanced to display the **Universal Product Code (UPC)** associated with each item line. Users can now view the UPC directly in the respective transfer order details, making it easier to identify and verify items during the transfer process.
***
**Key Enhancements**
* Added a **UPC** column to the **Transfer Sales Order Details** and **Transfer Purchase Order Details** sections.
* Added a **UPC** column to the **Sales Order Centre** for Transfer Sales Orders and the **Purchase Order Centre** for Transfer Purchase Orders.
* The **UPC** displayed for each line corresponds to the UPC configured for the respective item.
***
**How It Works**
**Step 1:** Go to the **Item Centre** and view the **UPC** column for the required item. The value displayed is the UPC configured in the **Inventory** tab.
**Step 2:** Create a Sales Order for the same item. The item's **UPC** is displayed in the **UPC** column in the **Sales Order Details** section.
***
### **Vehicle Fitment Support in Data Export Centre**
**Overview**
The **Data Export Centre** has been enhanced to support **Vehicle Fitment** data, allowing users to view and export vehicle fitment information associated with items. Users can select **Vehicle Fitment** from the **Search By** option, view the associated item and vehicle details, apply search and advanced filters, and export the required data for reporting or further processing. Vehicle Fitment data can also be included in scheduled exports.
***
**Key Enhancements**
* Added **Vehicle Fitment** as an option in the **Search By** field of the **Data Export Centre**.
* Users can use **Search By**, **Advanced Search**, and other filtering options to refine Vehicle Fitment data.
* Vehicle Fitment data can be included in **scheduled exports** through the **Schedule Export** option.
* Vehicle Fitment data can be exported with associated vehicle details, such as **Model Name**, **Model Number**, and **Make Name**, using the available **header-level export options**.
***
### **Added Product-Level Third-Party Ref#**
**Overview**
A new product-level **Third Party Ref#** has been added to maintain a reference value at the product level, separately from the existing variant/SKU-level **Third Party Ref#**. The product-level reference can be set through product uploads and the Product API and can be viewed in the **Product Centre** and **Data Export Centre**.
***
**Key Enhancements**
* Added a product-level **Third Party Ref#**, separate from the existing variant/SKU-level reference.
* Added support for setting the product-level **ThirdPartyRefNo** through:
* **Upload Product**
* **Upload Product (Header Only)**
* **Product API** for create, update, and get operations.
* For products with multiple variant rows, the **ThirdPartyRefNo** from the **first row** is saved as the product-level reference.
* Added **Third Party Ref#** column to the **Product Centre** and **Data Export Centre (Product)**.
***
**How It Works**
**Step 1:** Go to the **Upload Products** module and download the CSV template.
**Step 2:** Enter the required value in the **ThirdPartyRefNo** column and upload the completed template.
For a product with multiple variant rows, the **ThirdPartyRefNo** entered in the **first row** is saved as the product-level **Third Party Ref#**. Values entered only in subsequent variant rows do not set the product-level reference.
**Step 3:** After the upload is complete, you can view the **Third Party Ref#** assigned to the product in the **Product Centre**.
***
### **Support for Route Field in Customer Batch Update**
**Overview**
The **Customer Centre** has been enhanced with the **Route** option in the **Batch Update** functionality. Users can now assign a **Route** to multiple customer records at once, making it easier to maintain customer delivery route assignments without updating each customer individually.
The **Route** batch update option is available only when the **Xoro Delivery Manager** app module is enabled.
***
**Key Enhancements**
* Added **Route** as an available **Column Name** in the **Batch Update** function of the **Customer Centre**.
* The **Clear Existing Data** option can be used to clear the existing Route value from the selected customer records.
***
**How It Works**
**Step 1:** Navigate to **Menu → Admin → Customer → Customer Centre** and select the customers for which you want to assign a Route.
**Step 2:** Click the **Options** menu and select **Batch Update**.
**Step 3:** Select [**Route**](/xoroerp-1/admin/route.md) from the **Column Name** dropdown and choose the required Route from the **Value** dropdown. Click **Update**.
**Step 4:** The selected Route is assigned to all selected customer records.
**Step 5:** Open any updated customer record and go to the **Other Info** tab. The selected Route is displayed in the **Default Route** field.
***
### **Item Tags and Material Visible at the Order Line Level**
**Overview**
**Item Tags** and **Material** can now be displayed at the **order line level** in Sales Orders. This allows users to view item-specific tag and material information directly on the Sales Order without opening the individual item record.
***
**Key Enhancements**
* Added the **Item Tags** and the **Material** columns to Sales Order line-level views.
* The columns are also supported in the **Sales Order Sub Form** and **Sales Order Centre (Search by: Sales Order Detail)**
* Item Tags and Material are first assigned to an item from the **Other Attributes** tab in the Item Centre. When the item is added to a Sales Order, the assigned values are displayed against the respective order line.
***
**How It Works**
**Step 1:** Go to the **Item Centre** and double-click the required item. In the Item subform, select **Edit in New Window** to open the item record.
**Step 2:** In the **Other Attributes** tab, enter the required value in the **Tags** field and specify the item's material in the **Material** dropdown field.
**Step 3:** Create a **Sales Order** and add the item for which the **Item Tags** and **Material** were configured.
**Step 4:** In the **SO Details** section, click the grid icon and select **Item Tags** and **Material** to display these columns in the Sales Order lines.
**Step 5:** Now, navigate to the **Sales Order Centre**, select **Sales Order Detail** in the **Search by** field, and enable the **Item Tags** and **Material** columns from the column selector.
***
### **ASN Header and ASN Detail Custom Fields Added in Data Export Centre**
**Overview**
The **Data Export Centre** now displays both **ASN Header** and **ASN Detail** custom field columns when **ASN Detail** is selected in the **Search by** field. This allows users to view and export custom field values defined at both the ASN Header and ASN Detail levels along with the corresponding ASN Detail records.
The **Expected Delivery Date** column is also available when **ASN Detail** is selected.
***
**Key Enhancements**
* Added **ASN Header** and **ASN Detail custom field** columns to the **ASN Detail** dataset.
* Custom fields defined for **ASN** and **ASN Detail** in the **Custom Field Definition Centre** are displayed as columns in the Data Export Centre.
* Added the **Expected Delivery Date** column to the **ASN Detail** dataset.
***
**How It Works**
**Step 1:** Go to the **Data Export Centre** and select **ASN Detail** as the exportable dataset.
**Step 2:** Click the **Column Selector** and view the available **ASN Header custom fields**, such as `ASN_CF_H1`, `ASN_CF_H2` and the **ASN Detail custom fields**, such as `ASN_CF_D1`, `ASN_CF_D2`.
***
### **Availability of Due Date and Vendor Bill Number in Batch Upload Bills**
**Overview**
The **Batch Upload Bills** module now supports importing **Due Date** and **Vendor Bill Number** through the bill import template. These fields can be populated directly in the CSV template and are carried over when the bill is created, making it easier to maintain complete bill information during batch uploads.
***
**Key Enhancements**
* Added **Due Date** and **Vendor Bill Number** fields to the bill import template.
* The fields are available when the **Bill Template** is downloaded from the **Batch Upload Bills** module.
* Values entered in these fields are displayed in the **Bill File Preview** before the bill is created.
* The imported values are carried over to the newly created bill in **Bill Centre**.
***
**How It Works**
**Step 1:** Go to the **Upload Bills** module and click **Download Template**.
**Step 2:** Open the **downloaded CSV template** and provide the required bill information, including values in the newly added **Due Date** and **Vendor Bill Number** columns.
**Step 3:** Save the completed CSV file. In the **Batch Upload Bills** module, click **Browse** and upload the template file. Then, click **Verify & Upload**.
**Step 4:** The **Bill File Preview** pop-up displays the bill details, including the **Due Date** and **Vendor Bill Number**, allowing you to review the information and make any final changes before creating the bill. Click **Upload Bills** to create the bill.
**Step 5:** Go to **Bill Centre**. The bill is created with the details entered in the template file.
***
### **Item Price Updates Trigger Webhook for Shopify Synchronization**
**Overview**
Item price changes in Xoro can now be automatically pushed to Shopify through the **Item Price Update webhook**. When the **Standard Unit Price** or any **Custom Price (1–14)** is updated for an item, Xoro triggers the webhook so Shopify can synchronize the corresponding mapped price fields.
This keeps item pricing in Shopify aligned with the latest price information maintained in Xoro, including updates made through batch operations, imports, uploads, or APIs.
***
**Key Enhancements**
* The **Item Price Update webhook** is triggered when an item's **Standard Unit Price** or **Custom Price (1–14)** is updated.
* Price updates are supported from:
* **Item Price Centre** batch updates
* **Item updates**
* **Item Centre** batch updates
* **Currency Price Import**
* Price updates to existing items through **Upload/API**
* Shopify uses the price-field mappings configured under **Products & Inventory** to determine which Xoro price values are synchronized.
* Webhook executions can be tracked in the **Sync Product Prices** log in the Shopify channel.
* Updated values can be verified on the corresponding Shopify product, based on the configured mappings.
***
**How It Works**
**Step 1:** Open the **Shopify channel** and go to **Products & Inventory**.
**Step 2:** Enable **Sync product prices only**. Configure the price fields to determine how Xoro prices are mapped to Shopify, including the **Item Price Currency Code**, **Price field**, **Compare Price field**, and **Buying Cost**.
**Step 3:** Go to **Item Centre** and select the item whose price needs to be updated. From the **Options** menu, select **Batch Updates**.
**Step 4:** In the **Batch Update** pop-up, select the required price field, such as **Custom Price 6**, and specify the new value. Click **Update** to apply the change.
**Step 5:** Once the item price is updated, Xoro triggers the **Item Price Update webhook**.
**Step 6:** Open the corresponding product in Shopify to verify the synchronized pricing. The updated values are reflected in the mapped fields, such as the **Compare-at price** and **Price field**, based on the configured price mappings and settings
***
### **Brand Name Displayed in the Item Dropdown**
**Overview**
The **Brand Name** is now visible below the **Item Description** in the **Item** dropdown when adding items to a Sales Order. This provides additional item information directly within the selection list, making it easier to identify and select the required item.
***
**Key Enhancements**
* Added **Brand Name** to the **Item** dropdown in the **Item Detail** popup, and it appears directly below the **Item Description**.
* Item selection now provides additional product information without requiring users to open the item record separately.
***
**How It Works**
**Step 1:** Go to **Menu → Sales → Sales Order** and create a new Sales Order. In the **SO Details** section, click **Add Item**.
**Step 2:** The **Item Detail** pop-up opens. Click the **Item Number** dropdown to view the available items.
**Step 3:** The item dropdown displays the **Item Number**, **Item Description**, and **Brand Name**. The **Brand Name** appears directly below the **Item Description**.
**Step 4:** Select the required item from the dropdown and continue adding it to the Sales 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://docs.xorosoft.com/whats-new/release-notes/current-release/september-2026-release.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.
