# September 2025 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 %}
### **BOM (Bill of Materials) Centre** — **RM Item Filter** at the **Detail Level**.
This release introduces a new enhancement in the **BOM (Bill of Materials) Centre** — **RM Item Filter** at the **Detail Level**.\
The feature allows users to filter BOM details based on specific **Raw Material (RM) Items**, enabling faster data access, better traceability, and improved operational control when analyzing complex product structures.
***
**Overview:**
**Feature Added:** *RM Item Filter (Detail Level)*
**Location:**\
`Manufacturing → Bill of Materials → BOM Centre → Detail Level`
**Description:**\
A new dropdown filter labeled **“RM Item”** has been added within the BOM Centre Detail View. Users can now refine BOM detail listings by selecting a specific RM Item. This enhancement is particularly useful in identifying where a particular raw material is used across multiple BOMs, improving visibility in production planning and material management.
***
**Key Enhancements:**
| Feature Area | Description |
| ------------------------ | ------------------------------------------------------------------------------------------------- |
| **New Filter Field** | A filter labeled **“RM Item”** has been introduced at the BOM Detail Level. |
| **Filter Functionality** | Enables filtering of BOM records that contain the selected RM Item. |
| **Data Scope** | Applies only to the detailed BOM view, ensuring granular visibility of raw material associations. |
| **Dynamic Results** | BOM detail grid updates instantly upon RM Item selection. |
| **Integration** | Works seamlessly with existing filters like Finished Item, BOM Code, and Revision. |
***
**How To Use:**
1. Navigate to **BOM Centre**.
2. Switch to the **Detail Level** view.
3. Locate the new filter **“RM Item”** on the filter panel.
4. Select an RM Item from the dropdown list.
5. The BOM Detail grid will automatically refresh to show only entries where the selected RM Item is used.
***
**Example Scenario**
A production planner needs to verify where *RM-102 – Aluminum Sheet (3mm)* is used before approving a material change.\
By applying the **RM Item Filter**, the planner instantly sees all BOMs that depend on this specific raw material. This eliminates the need for manual verification and ensures accurate downstream planning.
### **Enhancement to Item-Vendor Mapping Display**
**Overview:**\
In the **Item** subform, under the **Vendors** tab, the table previously displayed data sourced from the *Item-Vendor Mapping*. With this update, **custom fields** defined in the *Item-Vendor Mapping* module are now also displayed in the same table.
**Key Enhancements:**
* Custom fields configured in the *Item Vendor Mapping* module will now automatically appear under the **Vendors** tab in the **Item** subform.
* This enhancement provides improved visibility and accessibility of vendor-specific custom data directly within the Item record.
* Users can now view all relevant item-vendor information—including both standard and custom fields—without switching modules.
**Impact:**\
This update enhances data consistency and user efficiency by allowing seamless access to custom vendor mapping information from the Item interface.
***
### Update to Create Purchase Order Module
**Overview:**\
New columns — **Option3Name**, **Option3Value**, and **Option3Code** — have been added to the *Create Purchase Order* module to improve data visibility and variant tracking.
The new columns will reflect across the following workflows:
* **Add Item**
* **Quick Add**
* **Last Order**
* **Advanced Variant Finder**
**Impact:**\
This enhancement ensures consistency in variant management and provides users with comprehensive option-level details during the purchase order creation process.
***
### **Addition of 'Revision' Column in** Update BOM Items **Module**
**Overview:**
This release introduces a new enhancement in the **Update Bill of Materials** Items module. A new column — **‘Revision’** — has been added specifically for the update type **‘Bill of Materials’**.\
This addition allows users to view and verify the revision level of each Bill of Material directly within the update interface, improving traceability and accuracy during BOM updates.
***
**Key Enhancements:**
1. **New ‘Revision’ Column Added**
* The **‘Revision’** column is now available when the **Update Type** is set to **‘Bill of Materials’**.
* It displays the current revision number or identifier associated with each BOM record.
* This provides greater visibility into version control during updates.
2. **Improved Traceability**
* Users can now easily track which revision of a Bill of Materials is being updated.
* This reduces the risk of applying changes to an outdated or incorrect BOM version.
3. **Data Verification**
* The system allows users to **verify the column values** to ensure that the correct revision data is displayed and mapped for each BOM.
* This step ensures data consistency between the BOM Master and the Update BOM interface.
4. **Applicable Scope**
* The enhancement applies only to the **‘Bill of Materials’** update type within the **Update BOM** module.
* Other update types remain unaffected.
***
**How To Use:**
To verify the update:
1. Navigate to **Update BOM Items**.
2. Select **Update Type = Bill of Material**.
3. Confirm that the new **‘Revision’** column is visible in the grid.
4. Verify that the **Revision values** match the data in the corresponding BOM Master records.
***
### **Addition of “Last Landed Cost” in Pricing Rules**
**Overview:**
This release introduces a new option, **“Last Landed Cost”**, in the Pricing Rule setup. This enhancement ensures that both **standard price** and **cost calculations** in Purchase Orders (PO) and Sales Orders (SO) can now leverage the last landed cost of items, improving accuracy in pricing, margin calculations, and overall financial reporting.
**Key Enhancements:**
1. **Pricing Rule Update**
* A new option, **“Last Landed Cost”**, has been added to the pricing rule configuration.
* Users can now select “Last Landed Cost” as the basis for calculating standard price and cost for inventory items.
* This ensures consistency across all procurement and sales operations.
2. **Impact on Purchase Orders**
* When creating a purchase order, if the pricing rule is set to **Last Landed Cost**, the system will automatically calculate the item cost based on the most recent landed cost recorded in the system.
* Ensures accurate costing for inventory valuation and vendor payments.
3. **Impact on Sales Orders**
* When creating a sales order, item pricing and standard cost will also consider the **Last Landed Cost** if selected in the pricing rule.
* This helps in accurate margin calculation and ensures pricing consistency between procurement and sales processes.
4. **Reporting & Financial Accuracy**
* All related financial and inventory reports, including Profit & Loss, Stock Valuation, and Cost Analysis, now reflect the Last Landed Cost wherever applicable.
* Reduces manual intervention and discrepancies in cost calculations.
**How It Works:**
1. Navigate to **Pricing Rule Module**.
2. Add or edit a pricing rule.
3. Select **Last Landed Cost** in the Pricing Rule Criteria section as the basis for cost calculation.
4. Apply the rule to relevant items.
5. Standard prices in Purchase Orders and Sales Orders will now reflect the Last Landed Cost automatically.
***
### **Addition of ‘Hide Pricing’ Toggle at Presentation Level in B2B Portal**
**Overview:**
This release introduces a new **‘Hide Pricing’** toggle at the **Presentation level** in the B2B Portal. The feature allows users to control the visibility of product prices across the portal, offering greater flexibility for business presentations, catalog sharing, and customer demonstrations.
***
**Key Enhancements:**
1. **New ‘Hide Pricing’ Toggle**
* A **‘Hide Pricing’** toggle has been added at the **Presentation level** in the B2B Portal interface.
* The toggle allows users to temporarily hide all product prices from the portal view.
2. **Default Behavior**
* The toggle is **OFF by default**, ensuring that prices are visible to users unless manually hidden.
3. **State Retention on Refresh**
* The toggle’s selected state (ON/OFF) is **retained after page refresh**, providing a consistent user experience without requiring repeated configuration.
4. **Functionality When Toggle is ON**
* When **‘Hide Pricing’** is enabled:
* All product prices across the portal are hidden from view.
* Prices remain invisible during browsing, search, and product detail views.
* Prices become **visible only at the time of checkout**, ensuring necessary visibility for transaction confirmation.
**How It Works:**
1. Navigate to the **Presentation level** in the B2B Portal.
2. Verify that the **‘Hide Pricing’** toggle is visible and **OFF by default**.
3. Turning the toggle ON ensures:
* All product prices across the portal are hidden.
* Prices appear only during checkout.
4. On refreshing the page, the toggle’s state is **retained**.
***
### **Addition of ‘MO Number’ Filter in MO Centre**
**Overview:**
This release introduces a new **‘MO Number’** filter in the **MO Centre** module. This enhancement enables users to easily search and filter Manufacturing Orders (MOs) by their unique MO Number, providing quicker access to relevant records and improving efficiency in managing manufacturing operations.
***
**Key Enhancements:**
1. **New Filter – ‘MO Number’**
* A dedicated **‘MO Number’** filter has been added to the filter section of the **MO Centre** screen.
* The filter allows users to directly search for specific Manufacturing Orders using their MO identifiers.
* Supports both **exact** and **partial** MO Number searches for enhanced flexibility.
2. **Improved Usability**
* Simplifies navigation in the MO Centre, especially when working with large datasets.
* Helps users instantly locate target MOs without scrolling or manual lookup.
3. **Consistent Functionality**
* The filter behaves consistently with other existing filters in the module.
* Works seamlessly with other applied filters to refine search results further.
***
**How It Works:**
1. Navigate to the **MO Centre** module from the main menu.
2. Locate the new **‘MO Number’** field in the filter panel at the top of the screen.
3. Enter an **MO Number** (full or partial) into the field.
4. Click on the **Search/Apply Filter** button.
5. The system will instantly display all Manufacturing Orders that match the entered MO Number.
6. You can clear or adjust the filter to perform a new search.
***
### **Addition of ‘Customer PO’ Field in Invoice Credit Memo**
***
**Overview:**
A new **‘Customer PO’** text box has been added to the **Credit Memo Header i**n the **Invoice Credit Memo** module. This enhancement ensures that the Customer Purchase Order (PO) information from the original invoice is automatically carried over when the invoice is pulled into the credit memo.
***
**Key Enhancement:**
1. **New Field – ‘Customer PO’**
* A **Customer PO** text box has been introduced in the **Invoice Credit Memo** form.
* When an invoice is selected or pulled into the credit memo, the system will automatically populate this field with the **Customer PO** value from the linked invoice.
2. **Improved Data Consistency**
* Ensures that the **Customer PO** details remain consistent between the original invoice and the associated credit memo.
* Reduces manual data entry errors and improves traceability between documents.
***
**How It Works:**
1. :Navigate to the **Invoice Credit Memo** module.
2. Create or open a new Credit Memo.
3. Pull or link an existing Invoice.
4. The system automatically copies the **Customer PO** from the selected Invoice and displays it in the **Customer PO** field on the Credit Memo.
5. The user can review or modify the **Customer PO** if required (based on configuration)
***
### **Added “Other” Tab in Create Estimate Page**
**Feature:** New “Other” Tab in Create Estimate Page
**Overview:**\
A new **“Other”** tab has been added to the **Create Estimate** page. This tab includes the following fields:
* **Order Tags**
* **Order Type**
* **Brand**
* **Risk Analysis**
* **Custom Comment**
**Key Enhancements:**
* When converting an **Estimate to Sales Order (SO)**, the newly added fields from the “Other” tab are now carried forward into the Sales Order.
* The **Estimate Centre’s view subform** has been updated to display the **“Other” tab**, ensuring visibility of all related fields.
**Impact:** Improves data consistency and visibility by allowing additional order-related information to be recorded and transferred seamlessly from Estimate to Sales Order.
***
### **Added New Fields to Batch Update in Manufacturing Order (MO) Centre**
**Module:** Manufacturing → Manufacturing Order (MO) Centre\
**Feature:** Batch Update Enhancement
***
**Overview:**
A new enhancement has been introduced to the **Batch Update** functionality within the **Manufacturing Order (MO) Centre** in XoroERP.\
This update allows users to efficiently update key fields across multiple MOs simultaneously, improving workflow speed, data consistency, and operational control.
***
**Newly Added Fields:**
The following fields have been added to the **Batch Update** window of the MO Centre:
* **Default Finished Goods Location**
* **Default Raw Material Location**
* **Memo**
* **Custom Fields**
***
**How It Works:**
1. Navigate to **Manufacturing → MO Centre.**
2. Select multiple Manufacturing Orders from the grid.
3. Click on **Batch Update** from the toolbar.
4. The newly added fields — *Default Finished Goods Location*, *Default Raw Material Location*, *Memo*, and any *Custom Fields* — will now be available for update.
5. Enter the desired values for the Column Name(in this case, **Default Finished Goods Location)** and execute the batch update. **The screenshot below illustrates how to update the Default Finished Goods Location.**
The system will automatically validate and update the selected fields for all eligible MOs.
***
**Validations**
To maintain data integrity and ensure alignment with manufacturing workflows, the following validations are applied:
1. **Default Raw Material Location** can only be updated when the MO is in **Open** or **Released** status.
* If the MO is in any other status, the system will restrict the update and display an appropriate error message.
2. **The Default Finished Goods Location** cannot be updated if the MO is in the **Produced** status.
* This ensures that once production is complete, the output storage location remains fixed.
3. **Location Validity Check:**
* The system validates that the selected location exists and is active within the ERP.
* Invalid or inactive locations will trigger an error.
4. **Valid Location Types:**
* Only the following location types are permitted for updates:
* **Warehouse**
* **Store**
* **Manufacturing**
* **Stage** (*applicable only for Default Finished Goods Location when WMS is enabled*)
***
### **Added Project/Class to Batch Update in Item Centre**
**Module:** Inventory → Item Centre\
**Feature:** Batch Update Enhancement
**Overview:**\
The **Batch Update** functionality in the **Item Centre** has been enhanced to include the following fields:
* **Project/Class**
Users can now update the **Project/Class** attributes for multiple items simultaneously, improving efficiency and data consistency in inventory management.
**How It Works:**
1. Navigate to the **Item Centre**.
2. Select one or more items from the grid.
3. Click on **Batch Update**.
4. The newly added field **Project/Class** are now available for update.
5. Enter or select the desired values and execute the batch update.
### **Added “Is Reconciled?” Column in BILL and ITEM RECEIPT Centre Pages**
**Overview:**\
The following enhancements have been made to improve the visibility of reconciliation status in XoroERP:
1. **Bill Centre:**
* A new column, **“Is Reconciled?”** has been added to display the reconciliation status of each bill.
2. **Item Receipt Centre:**
* A new column, **“Is Reconciled?”** has been added to indicate whether the item receipt has been reconciled.
**How It Works:**
* Users can now easily identify which bills and item receipts have been reconciled directly from the centre pages without opening individual records.
### **Added “Expiry Date” and “Quality” Columns in Item Inventory Snapshot**
**Module:** Inventory → Item Inventory Snapshot
**Overview:**\
The **Item Inventory Snapshot** module has been enhanced to provide more detailed information about inventory quantities.
* In the **Item Inventory Quantity Detail** subform, (accessible by clicking *Available Qty*), the following columns have been added:
* **Expiry Date**
* **Quality**
**How It Works:**
1. Navigate to **Item Inventory Snapshot**.
2. Click on **Available Qty** for any item to open the quantity detail subform.
3. The newly added **Expiry Date** and **Quality** columns will now be visible, providing better visibility into inventory status.
***
### **Added “Item Sub Category” Field in Short Inventory Planner**
**Module:** Inventory → Short Inventory Planner
***
**Overview:**
The **Short Inventory Planner** module has been enhanced with the addition of a new field, **“Item Sub Category,”** to provide better classification and filtering of inventory data.\
This improvement allows users to analyze shortages more efficiently by item grouping and sub-category segmentation.
***
**Key Enhancements:**
* A new field, **“Item Sub Category”** has been added in the **Short Inventory Planner** view.
* The field displays the **sub-category** linked to each item’s master record.
* Users can now sort, filter, or group inventory records based on **Item Sub Category** for deeper insights.
***
**How It Works:**
1. Navigate to **Inventory → Short Inventory Planner.**
2. Open the planner view to display inventory shortage data.
3. The **Item Sub Category** field is now visible in the grid alongside other item attributes.
4. Use it to:
* Filter items belonging to specific sub-categories.
* Analyze shortage trends by product grouping.
* Improve purchasing or production planning based on sub-category data.
***
### **Added “Total Producible ATS” Columns to the Data Export Centre**
**Module:** Inventory / Data Export Centre
**Overview:**
The **Data Export Centre** has been enhanced to provide better visibility into producible inventory by adding two new columns:
* **Total Producible ATS**
* **Total Producible ATS (Inc PO)**
These columns can now be included as fields in data exports, enabling more comprehensive reporting and analysis of producible stock levels.
***
**Key Enhancements:**
* **Total Producible ATS:** Displays the producible available-to-sell stock based on current inventory and BOM.
* **Total Producible ATS (Inc PO):** Displays producible stock, including open Purchase Orders (POs), giving a complete view of potential production capacity.
* Both fields are now exportable directly from the **Data Export Centre**.
***
**Prerequisite / App Configuration**
To enable this functionality, the following app configuration must be turned on:
* **Enable BOM Producible Inventory Levels**
* This setting allows the system to maintain BOM producible inventory levels.
* It activates the **BOM Producible Inventory Sync Job**, ensuring accurate calculations.
* The BOM producible levels can also be accessed via the **Inventory Snapshot** module.
***
**How It Works:**
1. Navigate to **Data Export Centre**.
2. Select the desired export template or create a new one.
3. Include the newly added fields: **Total Producible ATS** and **Total Producible ATS (Inc PO)**.
4. Execute the export to generate a file containing the producible inventory data.
***
### **Support for Multi-Select Custom Fields in B2B Order Cart (Header Section)**
**Module:** B2B Portal → Order Cart
***
**Overview:**
The **B2B Order Cart** has been enhanced to support **multi-select custom fields** at the **order header level**. This addition provides users with greater flexibility in capturing complex order-specific information directly from the B2B interface.
***
**Key Enhancements:**
* The system already supports **custom fields at the order line level** when the app configuration **“Enable Custom Fields in B2B in Order Summary”** is turned on.
* With this update, **multi-select custom fields** can now be defined and displayed in the **header section** of the order cart.
* Users can select multiple values for a single custom field, making it easier to record additional data such as multiple delivery preferences, tags, or order attributes.
***
**Configuration Requirement:**
To enable this feature:
1. Go to **App Configurations** and ensure **“Enable Custom Fields in B2B”** is turned **ON**.
2. Define custom fields (including multi-select types) under **Custom Field Setup** for the Order Header entity.
***
**How It Works:**
1. Navigate to the **B2B Order Cart** page.
2. When the above app configuration is enabled, the header section will display the newly defined **multi-select custom fields**.
3. Users can select multiple values from the dropdown while creating or editing an order.
4. The selected values are saved with the order and can be accessed or edited later as needed.
### **Added Custom Field Mapping Support from SO Detail to MO Header**
**Module:** Manufacturing → Manufacturing Order (MO)\
**Related Module:** Sales Order (SO)
***
**Overview:**
A new enhancement has been implemented to extend **custom field mapping capabilities** between the **Sales Order Detail** and **Manufacturing Order Header**.\
This allows seamless transfer of custom field data from sales orders to manufacturing orders during MO creation, ensuring data consistency and reducing manual entry.
***
**Feature Details:**
* Added support for **mapping custom fields** from the **SO Detail** to **MO Header**.
* When a Manufacturing Order is generated from a Sales Order, the defined **custom field values** from the SO Detail level will automatically populate the corresponding fields in the MO Header.
* This enhancement enables better control and automation of data flow between sales and production modules.
***
**How It Works:**
1. Define custom fields at both **Sales Order Detail** and **MO Header** levels.
2. Configure the **custom field mapping** between these two entities in the system setup.
3. When an MO is created from an SO, the mapped custom field values from the SO Detail will be automatically copied to the MO Header.
4. Users can review or modify these values in the MO Header as needed before processing.
***
### **Customer PO Field Added to Invoice Credit Memo**
**Module:** Accounts Receivable → Invoice Credit Memo
***
**Overview:**
A new **Customer PO** field has been added to the **Invoice Credit Memo** form. This enhancement ensures better traceability and alignment between invoices and credit memos, simplifying financial and customer reconciliation processes.
***
**Feature Details:**
* **Customer PO Text Box:** A new text field named **Customer PO** is now available in the Invoice Credit Memo.
* **Automatic Population:** When pulling an invoice into a credit memo, the system automatically populates the **Customer PO** field with the value from the original invoice.
* **Consistency and Accuracy:** This eliminates manual entry errors and ensures that customer purchase order references remain consistent across invoices and credit memos. Users can check the corresponding entry in the Credit Memo Centre.
**How It Works:**
1. Open the **Invoice Credit Memo** form.
2. Pull an existing invoice to create a credit memo.
3. The **Customer PO** field in the credit memo will automatically inherit the Customer PO from the pulled invoice.
4. Users can verify or edit the field if required before saving the credit memo.
***
### **Auto-Select Default Item Location for Item Receiving and MO Production/Disassembly**
**Overview:**
A new App Config — **“Auto-Select Default Item Location for Item Receiving and MO Production/Disassembly”** — has been added to XoroERP.
When this configuration is enabled, the system automatically places items into their **default location** during:
* **Quick Receive**
* **ASN Receiving** (both regular and RMA)
* **MO Production**
* **MO Disassembly**
Items are received, produced, or moved **directly into their default location** without manual selection.
***
**Configuration Details:**
* **App Config Name:** Auto-Select Default Item Location for Item Receiving and MO Production/Disassembly
* **Type:** Multi-select Dropdown
* **Available Options:**
* Receive PO
* Produce/Disassemble MO
Users can enable one or both options depending on operational requirements.
***
**Functionality When Enabled**
* The system **auto-assigns the item’s default location** during PO receiving, ASN receiving, MO production, and MO disassembly.
* Manual location selection is no longer required, ensuring faster and more accurate operations.
***
**Validation Rules**
* If the item’s **default store** or **default location** is **not defined**, the system will throw an error.
* If the **default store** does not match the **store selected** in the PO or MO, the system will also throw an error.
These validations ensure items are only placed in valid and correctly mapped locations.
***
#### **PO Receiving (ASN) Logic**
* When the app config is enabled for **Receive PO**, and a user manually receives an ASN:
* The checkbox **“Auto-Select Default Location By Item”** is **checked by default**.
* The system automatically fills the item location field with each item’s default location.
***
#### **MO – Finished Goods Location Logic**
* **On Item Change:**
* The *Finished Goods Location* auto-fills with the item’s default location if the MO’s store matches the item’s default store.
* **On MO Save:**
* The Finished Goods Location is set based on the item’s default location.
* **Sub-MO Logic:**
* If a **Raw Material Location** is defined in the parent MO or in the Settings Map,\
then the **default item location of the Sub-MO** (Finished Goods Location)\
must match the raw material location of its **parent MO** (through which it was auto-triggered).
* This logic applies **only during MO/Sub-MO creation**, not for existing MOs.
***
### **Sales Order – Copy Selected Line to Existing PO Enhancement**
**Overview:**
In the **Create Sales Order** module, the **“Copy selected line to existing PO”** functionality has been enhanced.
Previously, the Select Existing PO pop-up displayed **only POs** with an **Open** status.\
With this update, it now shows **both Open and Released POs**, providing greater flexibility when copying lines to existing purchase orders.
***
**Key Enhancements:**
* Users can now copy sales order lines to **released POs** in addition to open POs.
* Streamlines the process of linking sales orders to purchase orders, reducing the need for manual adjustments.
* Improves efficiency and visibility when managing orders and inventory.
***
### Restrict Price Recalculation on Customer Change
**Feature Name:** Restrict Price Recalculation on Customer Change\
**Module:** Sales\
**Type:** New App Configuration
**Overview:**
A new App Configuration setting, **“Restrict price recalculation on customer change”** has been introduced to provide better control over how prices are managed when changing customers in Sales Orders and Estimates.
**Description:**
When this configuration is **enabled**, the system restricts **automatic price recalculation** based on pricing rules whenever the customer is changed in a Sales Order or Estimate.
* This ensures that the existing item prices remain unchanged even if the selected customer has different pricing rules or discount structures.
* The feature is useful for users who need to preserve the originally entered prices while switching customers during order entry or quotation preparation.
When the configuration is **disabled**, XoroERP will continue to follow the standard behavior — i.e., **prices will be recalculated automatically** according to the pricing rules defined for the newly selected customer.
{% hint style="info" %}
This configuration **does not impact other pricing restrictions** or validations already in place within the system.
{% endhint %}
***
### **New Fields in Wave Header**
**Overview:**
New informational fields have been added to the **Wave Header** section in both **Wave Centre** and **Data Export Centre** to provide better visibility into customer and order details.
***
**Key Enhancements:**
* **Customer Account Number:** Displays the customer’s unique account identifier from the master record.
* **Customer Ship To Fields:** Capture detailed shipping address information for the order, including:
* **Ship To Address Name** – Name associated with the shipping address.
* **Ship To Company Name** – Customer’s company or business name.
* **Ship To Address 1 & 2** – Primary and secondary address lines.
* **City, State, Country, Zip Code** – Geographical details of the shipping location.
* **Customer PO:** Reflects the **Purchase Order number** provided by the customer for cross-reference and tracking.
* **Payment Terms:** Displays the payment agreement or terms defined for the customer (e.g., Net 30, Prepaid).
* **Memo:** Shows any additional notes or comments related to the wave or order for quick reference.
{% hint style="info" %}
These fields will **only display values when a wave contains a single order**.\
For **multi-order waves**, the fields will remain **blank** to avoid conflicting or combined data.
{% endhint %}
***
**Impact:**
This enhancement improves **data visibility, export accuracy, and operational traceability** in both **Wave Centre** and the **Data Export Centre**, making customer and order-level insights more accessible to users.
***
### **Scan to Verify – Enhancements to Pick Wave Module**
**Overview:**
A new **Scan to Verify** feature has been added to the **Pick Wave** module in XoroERP to improve accuracy, control, and operational efficiency in the picking and shipping process. With this release, you can enforce full verification before shipping, control how scanned items update quantities, and directly manage shipment creation from the wave interface.
***
#### 1. New Access Control
**1.1 App Module Access: Scan to Verify Mode**
* New **App Module Access** permission, **Scan to Verify Mode**, determines whether the feature is visible and usable.
* The feature will only appear for users/roles with this access enabled.
***
#### 2. New App Configurations
**2.1 Enforce Full Verification Before Shipping**
**Title:** **Enforce Full Verification Before Shipping**
**Tab: Warehouse**
**Behavior:**
* **Enabled:**
* The **Close Wave** button in the **Scan to Verify** modal is **disabled** until **all picked quantities are verified**.
* **Shipping** tab fields are enabled only when **Verified Qty = Picked Qty**.
***
**2.2 Scan Verification Mode**
**Title:** Scan Verification Mode\
**Description:** Determines how scanned items update quantities on wave detail lines.
**Tab: Warehouse**
**Options:**
1. **Pick & Verify**
* Updates both **Picked Qty** and **Verified Qty**.
* Validation: **Verified Qty cannot exceed Allocated Qty**.
* Partial picks are aligned automatically before updating scanned quantities.
2. **Verify Only**
* Updates **Verified Qty** only.
* Validation: **Verified Qty cannot exceed Picked Qty**.
***
#### 3. UI Enhancements in Pick Wave Module
**3.1 Toolbar Buttons**
* **\[Scan to Verify]**
* Appears when **Scan to Verify Mode** access is enabled.
* Opens the Scan to Verify modal with the verification section.
* **\[Print Labels]** *(if shipping integrator is connected)*
* This opens a modal displaying the shipment information for the order. The modal is available only for orders or wave lines that have been closed.
* **Sub-button: \[Print Multiple Labels]**
* Opens freight modal sub-form.
* Enables creating multiple cartons manually.
{% hint style="info" %}
**Print Label** is enabled only for closed wave lines or orders.
{% endhint %}
***
**3.2 Scan & Verify Modal Behavior**
* **Search / Scan Input:** Search by **Item #**.
* **Verify Button:** Updates quantities based on Scan Verification Mode.
* **Detail View:** Displays line-level details: Item #, Allocated Qty, Picked Qty, Verified Qty, and status messages.
***
#### 4. Shipment Creation & Shipping Section
**4.1 Automatic Shipment Creation**
* Closing a wave automatically closes the order and creates a shipment for it. After the shipment is created, the **Shipment** tab is enabled, where shipment information can be reviewed and updated.
**4.2 Shipping Section Details**
* **Fields**: Address, Header Fields, Carton Fields (from the Pack Ship Freight modal), Shipping Terms, Ship Service, Confirmation Type, Tracking #, Ship Date, Carton Weight, Rate, Shipping Notes.
{% hint style="info" %}
In the case of multiple cartons, these fields are automatically disabled and cannot be edited.
{% endhint %}
* Creates shipment for **closed wave lines only**.
* Supports **single carton creation** from the Shipping Section.
* For **multiple cartons**, use the **\[Print Multiple Labels]** sub-form.
**4.3 Shipping Tab – Print Label**
The **Print Label** functionality in the Shipping tab allows users to view and edit shipping-related information for an order, depending on the carton configuration.
* **Single Carton Orders:**\
If the order contains a single carton, all shipping information fields can be edited directly using the **Print Label** option.
* **Multiple Carton Orders:**\
If the order includes multiple cartons, shipping details must be edited using the **Print Multiple Label** option, available from the **Print Label** dropdown. This enables users to manage and update shipping information for each carton associated with the order as shown in the case below.
**4.4 Independent Toolbar Button for Print Label**
* Rendered in the Pick Wave module toolbar **after \[Scan to Verify]**.
* Opens modal with **Shipping Section only**:
1. Works independently of the "**Scan to Verify"** process.
2. Handles **Print Label Request** or **Print Request** based on the number of cartons.
***
**5. Functional Impact**
* **Access-based visibility:** Scan to Verify appears only for the authorized users.
* **Config-driven verification:** Enforce full verification or use flexible verification modes.
* **Enhanced workflow:** Combines scanning, verification, and shipment creation in one module.
* **Shipping flexibility:** Single-carton shipments directly or multiple-carton shipments using the sub-form.
* **Operational benefits:** Reduces shipping errors, ensures compliance, and streamlines label printing and shipment management.
***
### **Ship Service Auto-Population Enhancement**
**Module:** Shipment / Delivery\
**Feature:** Ship Service Auto-Population Logic Update
**Overview:**\
The system behavior for auto-populating the *Ship Service* field has been enhanced to ensure better consistency with the related Sales Order (SO).
**New Logic:**
* If the **selected carrier** matches the **carrier from the related Sales Order (SO)**:
* The system will now **automatically populate the Ship Service** from the corresponding Sales Order.
* *(Previously, the system always used the default Ship Service associated with the selected carrier.)*
* If the **selected carrier** is **different from the SO’s carrier**:
* The system will continue to **populate the default Ship Service** linked to the newly selected carrier.
**Pick Wave Module > Pack and Ship > Pack and Cartonize section**
**Impact:**\
This update ensures that shipments created using the same carrier as the Sales Order maintain consistent Ship Service information, reducing manual edits and improving operational accuracy.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.xorosoft.com/whats-new/release-notes/previous-releases/2025/september-2025-release.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.