August 2025 Release

Enhanced Sales Order Detail View

Overview Two new clickable columns have been introduced in the Sales Order detail view in SO Centre and Create SO module to improve navigation and user experience.

New Features:

  • Clickable (Linked PO): This column provides direct access to the linked Purchase Order associated with each sales order line. Users can now click on the PO number to quickly navigate to the corresponding PO record.

  • Clickable (Invoice Number): This column enables users to click on the displayed invoice number to view the related invoice details instantly.

Enhanced Auto Allocation Options in App Config Module

Overview:

This enhancement introduces three new Locked Wave allocation options under the following configuration settings in the App Config Module:

  • Auto allocate linked sales orders when stock is received

  • Auto allocate linked sales orders when linked MO is produced

These options offer improved control and precision in how inventory is auto-allocated to linked Sales Orders through Locked Waves.


Enhancement Details:

New Options Introduced:

  1. Full Order (Locked):

    • Auto allocation will occur only when stock is available for all lines and full quantities in the Sales Order.

    • Allocation will be executed through a Locked Wave.

    • Ensures complete shipment readiness before committing inventory.

  2. Full Qty Line (Locked):

    • Allocates only those lines where the entire quantity for the line is available.

    • Partial line fulfillment is skipped.

    • Allocation is performed as a Locked Wave, preserving wave integrity and planning.

  3. Allocate What’s Available (Locked):

    • Enables allocation of partial stock across one or more lines.

    • Even if full order or line quantities are not available, the system will allocate what’s currently in stock.

    • Allocation is done via a Locked Wave, ensuring that the resulting pick wave remains frozen and system-controlled.

Configuration Path:

To configure:

  1. Go to App Config Module

  2. Locate the settings:

    • Auto allocate linked sales orders when stock is received

    • Auto allocate linked sales orders when the linked MO is produced

  3. Select from the newly added Locked Wave options:

    • Full Order (Locked)

    • Full Qty Line (Locked)

    • Allocate What’s Available (Locked)

New 'Multi-line Text' Field Type in Custom Field Definition

Overview:

A new field type – ‘Multi-line Text’ – has been introduced in the Custom Field Definition module. This enhancement enables users to capture paragraph-style, free-form text, offering greater flexibility for storing detailed information.

Additionally, to ensure a clean and user-friendly interface, a “Show More” toggle has been implemented for long custom field values.

Enhancement Details:

New Field Type: Multi-line Text

  • This new field type allows users to define custom fields where multi-sentence or paragraph-level input is required.

  • Useful for storing detailed notes, descriptions, instructions, comments, or any other long-form text.

Auto "Show More" for Long Content

  • When the value in a custom field exceeds 12 words, the field will display a truncated preview with a “Show More” link.

  • On clicking "Show More," the full content becomes visible.

  • This prevents long text from cluttering list views or detail panels, maintaining UI readability.

Credit Memo Line Views with Custom Price Columns

Module(s):

  • Data Export Centre

  • Credit Centre

Overview:

The Credit Memo Line views in both the Data Export Centre and the Credit Centre module have been enhanced to provide better visibility and flexibility by incorporating additional Custom Price columns.

Enhancement Details:

First Five Custom Price Columns Added

  • The following columns are now available in the Credit Memo Line views of both:

    • Data Export Centre, and

    • Credit Centre Module

    → Custom Price 1 → Custom Price 2 → Custom Price 3 → Custom Price 4 → Custom Price 5

  • These columns will display corresponding custom pricing values defined in the system, ensuring full transparency and control over line-level pricing adjustments.

How to Access:

  • Navigate to Data Export Centre → Export Type: Credit Memo Line

  • Navigate to Credit Centre → View: Credit Memo Line

  • Scroll or customize the view to see the newly added Custom Price 1–5 columns.

Addition of “Vendor Internal Notes” Column in Purchase Order Item Line

Overview:

A new column, "Vendor Internal Notes," has been added to the Purchase Order Item Line to improve communication and visibility of vendor-specific information directly within the PO workflow.

Enhancement Details:

  • New Column: → Vendor Internal Notes

  • Location: This column is now visible at the line-item level in the Purchase Order module.

  • Data Source: The values in this column are automatically pulled from the Internal Notes field defined in the Item Vendor Mapping Module, ensuring consistency and eliminating the need to manually copy or reference notes across modules.


How to Use:

  • Open any Purchase Order and navigate to the Item Line section.

  • Look for the new column titled "Vendor Internal Notes."

  • The value shown will reflect the corresponding Internal Notes set in the Item Vendor Mapping for that Vendor-Item combination.

Restrict Save on Tax Calculation Error

Overview: Added a new setting Restrict Address-Based Tax Calculation for Specific Sources that, when enabled, restricts saving Sales Orders, Invoices, Estimates, Credit Memos, and Sales Receipts if the address-based tax calculation returns an error. This ensures that documents are not saved with incorrect or missing tax details.

Functionality:

  • Applicable to: Sales Order, Invoice, Estimate, Credit Memo, and Sales Receipt.

  • Trigger: Address-based tax calculation error.

  • Effect: Save action will be blocked until the tax calculation issue is resolved.

New Upload Budget Module

Overview:

A new Upload Budget module has been added under the Utilities section. To access: Menu > Utilities > Data Import > Upload Budget.

Functionality: This feature allows users to upload budget data directly into the system, addressing the current limitation where budgets could only be defined manually within the application.

Enhanced Credit Limit Enforcement & B2B Presentation Filter Control

Overview: This release introduces two major enhancements to improve credit control and B2B presentation usability.

1. Restriction on B2B Presentation Filters Reload A new configuration "Restrict reload presentation filters" has been added under App Config.

  • If Enabled: B2B filters will remain as selected without reloading after choosing any filter in the presentation page while adding an item to the cart.

  • If Disabled: Filters will reload after selection, maintaining the existing functionality.

Usage: Navigate to any B2B Presentation (Internal or External link) to experience the updated behavior based on the config setting.


2. Extended Credit Limit Restriction to B2B Orders The existing "Restrict Defaulter Customer Sales" configuration has been enhanced with multi-select options, giving users granular control over restriction behavior.

Enhancements:

  • If a customer’s Credit Limit is exceeded and the relevant config option is enabled, new orders cannot be created from the B2B portal (New Functionality).

  • If Credit Limit Exceeded or Overdue Invoices options are selected in config, Sales Orders cannot be released and Invoices cannot be created from XoroERP modules (Existing functionality remains unchanged).

Usage:

  1. Open any customer profile → Options → Balance Overview.

  2. Check “Defaulter” status, “Has overdue invoices,” and “Credit exceeded” values.

  3. Credit limit values can be set from the Customer module.

Impact:

  • B2B orders will now respect the customer’s credit status, preventing bypass of restrictions through automatically released orders.

  • Presentation page filters can be locked in place for faster and more controlled ordering workflows.

Selective Qty/Price Editing in Advanced Variant Finder

Overview: A new setting "Update Qty/Price in Edit Advanced Variant Finder" has been added under General Settings to provide more control over which fields can be edited in the Advanced Variant Finder.

Key Details:

  • Default Behavior: Both Quantity (Qty) and Price can be updated in the Advanced Variant Finder matrix.

  • If “Price” is selected:

    • Only Price can be updated.

    • Qty and Purchase Ratio fields are disabled.

  • If “Qty” is selected:

    • Only Qty can be updated.

    • Price and Purchase Ratio fields are disabled.

  • Duplicate Items Handling:

    • If duplicate items exist at the Sales Order line level, changes to Price or Qty will apply to all duplicate instances.

Dependencies: To use this functionality, both of the following settings must be enabled:

  1. Update Qty/Price in Edit Advanced Variant Finder

  2. Enable Price Editing in Advanced Variant Finder

Impact:

  • Allows greater precision and control in item editing within the Advanced Variant Finder.

  • Prevents accidental changes to fields not intended for modification.

Added "Average Unit Cost" Field in BOM Item Line Level

Overview:

  • A new field "Inv Average Unit Cost" has been added at the item line level (Detail level) in the following areas:

    • BOM Centre

    • BOM Module

    • BOM Subform

Functionality:

  • The field displays the average unit cost of the selected item.

Minimum Sell Quantity Feature

New Features Implemented

  1. Minimum Sell Quantity Field

    • Added to Product Page and Upload Products sections.

    • Allows you to define the minimum number of units a product can be sold in.

  2. Force Product Minimum Sell Qty Checkbox

    • Added in the Presentation Centre.

    • When enabled, the system will enforce the minimum sell quantity rules across the platform.


Functionality Details

1. Minimum Sell Quantity on Product Info Popup

  • If a product has a Minimum Sell Quantity defined, this value will be displayed in the product info popup for user reference.

2. Quantity Validation

  • If a user tries to add a quantity less than the Minimum Sell Quantity, the system will prevent the action.

  • Products can only be added to the cart if the total quantity is equal to or greater than the Minimum Sell Quantity.

3. Handling Zero Quantity

  • If the total product quantity in the cart is zero, the user can still update the cart freely.

4. Single Variant Add to Cart

  • When using the Single Variant Add-to-Cart feature, the system will automatically default the added quantity to the product’s Minimum Sell Quantity.


This ensures customers are informed about minimum purchase requirements, prevents accidental under-ordering, and maintains consistency across the cart experience.

Launch Date Column Enhancement in Item Module

Feature Implemented: A new "Launch Date" column has been introduced to improve product data tracking and management across the Item module.

Details of the Implementation:

  1. Other Attributes Tab – Item Module & Subform

    • Added a new column "Launch Date" under the Other Attributes tab at both the main Item module and its subform level.

    • This allows users to record and view the official launch date of an item directly within its detailed attributes.

  2. Item Centre Integration

    • The Launch Date column is now available in the Item Centre, enabling quick visibility of product launch dates in the central listing view without navigating into item details.

  3. Upload Items/Products Module Support

    • The Launch Date column is now supported in the Upload Items/Products functionality.

    • Users can input and bulk upload product launch dates along with other item details using the existing upload templates.

Enhancement in Customer Tax Number Handling

Overview:

We have introduced a new App Configuration option: “Select Customer Tax Number Options” in XoroERP. This feature provides flexibility in handling customer tax numbers with the following updates:

  1. App Config (Multi-Select Options)

    • Users can configure whether Tax Number 1, Tax Number 2, or both should be treated as mandatory.

    • Once enabled, mandatory validation is enforced in the Customer Module under Sales Tax details.

    • This validation is only applicable when a customer is marked as taxable and the app configuration is turned on.

  2. Customer Upload Enhancements

    • During customer master uploads, Tax Number 1 and Tax Number 2 will now be validated as mandatory fields (based on configuration).


Module Impact

  • Customer Module (Sales Tax Section):

    • Ensures proper capture of mandatory tax numbers.

    • Reduces errors during customer creation and tax reporting.

  • App Configurations:

    • Provides administrators with flexible control over tax number requirements.

    • Different business units can tailor compliance settings as per local tax regulations.

  • Customer Upload Module:

    • Prevents incomplete or invalid customer records during bulk uploads.

    • Enforces tax compliance from the very first point of data entry.

Void option in the Refund Sub-form

Overview:

We have introduced a new “Void” option in the Refund Sub-form of XoroERP. This option functions in the same way as the existing “Delete” option available in the Customer Refund Centre, thereby providing consistency across modules.

With this update, users now have greater control and flexibility when managing refund records directly within the sub-form, without navigating back to the main Refund Centre.


How It Works

  • The “Void” action can be applied to a refund record in the Refund Sub-form.

  • Once voided, the refund behaves in the same manner as if it were deleted from the Customer Refund Centre.

  • This ensures that incorrect or unnecessary refund entries can be efficiently cancelled at the point of entry.


Module Impact

  • Refund Sub-form:

    • Gains a new action option (Void) to manage refund records more effectively.

    • Refunds on credit card payments are now blocked for better payment compliance.

  • Customer Refund Centre:

    • Functionality remains consistent across modules, reducing user confusion.

    • Credit card refund restrictions ensure financial integrity.

Enhancement in Item Subform (Vendors Tab)

Overview:

We have introduced two new columns in the Vendors tab of the Item Subform view:

  • Purchase UOM Name

  • Purchase UOM Code

These fields provide direct visibility into the purchase unit of measure (UOM) settings for each vendor associated with an item.

The Purchase UOM Name/Code values displayed in the Vendors tab correspond directly to the UOM Name/Code defined in the respective Item-Vendor Mapping.


How It Works

  • When an item is linked to a vendor, its Purchase UOM details (Name & Code) will now appear in the Vendors tab of the Item Subform in the Item Centre.

  • These values are automatically derived from the Item-Vendor Mapping, ensuring consistency across modules.


Module Impact

  • Item Centre > Item Subform (Vendors Tab): Gains two new columns for improved vendor-specific purchase data visibility.

  • Item-Vendor Mapping: Acts as the source of truth for Purchase UOM information, maintaining consistency in data representation.

Customer Centre (Alert Note added to Batch Update)

Overview:

A new field, “Alert Note”, has been added to the Batch Update functionality in the Customer Centre.

This enhancement allows users to update the Alert Note for multiple customers at once, directly through the batch update process.


How It Works

  • In the Customer Centre → Batch Update, users will now see the “Alert Note” field available for selection.

  • When applied, the entered Alert Note value will be updated for all selected customer records.


Module Impact

  • Customer Centre (Batch Update): Gains the ability to mass-update the Alert Note field.

  • Customer Records: Ensures consistent and quick updates of important alert information across multiple customers.

Credit Memo & Credit Centre Enhancements

Overview:

Two key improvements have been introduced in Credit Memo and Credit Centre modules to provide more flexibility and control in managing customer credits:

  1. Delete Credit Memo

    • Users can now delete Credit Memos with statuses Transferred and Partially Transferred.

    • This has been implemented through a Parent–Child relationship mechanism while applying credits, ensuring consistency and integrity when credits are linked.

  2. Delete Customer Credit (Type: Transfer)

    • New functionality has been added to delete or batch delete customer credits of type Transfer directly in the Credit Centre.

    • This allows for bulk clean-up of erroneous or obsolete transfer credits.


How It Works

  • Credit Memo Deletion:

    • Navigate to the Credit Memo module.

    • Credit Memos in status Transferred or Partially Transferred can now be deleted, provided related credit applications are managed via the Parent–Child relationship logic.

  • Customer Credit Deletion (Transfer Type):

    • In the Credit Centre, select customer credits with type Transfer.

    • Use the Delete or Batch Delete option to remove selected records.

App Config: Additional Required Fields for Company-Type Customers

Overview:

Introduced a new app configuration setting: Additional Required Fields for Company-Type Customers.

Functionality:

  • Admin users can now configure certain fields to be mandatory when creating or updating company-type customers.

  • The available fields that can be set as required are:

    • Tags

    • Groups

    • Default Project Class

    • Order Type

  • Once configured, the system will enforce validation checks on the selected fields across all input methods:

    • Create Module

    • Customer Uploads

    • API Integrations

  • Scope:

    • These validations apply only to customers classified as Company.

    • Customers classified as Individual remain unaffected, and no additional validation is applied to them.

U.S. 1099 Vendor Tax IDs (SSN & Federal ID)

Overview:

We’ve added two tax-identifier fields for U.S. 1099 vendors across vendor creation and management surfaces:

  • Social Security Number (SSN)

  • Federal ID (commonly EIN)

These fields appear only when:

  1. Home Country = United States, and

  2. Is 1099 Vendor? = checked

They are also available in Upload Vendors, Data Export, and Vendor Centre.


Functionality

1) Create Vendor (UI)

  • When the vendor’s Home Country is set to United States and Is 1099 Vendor? is checked:

    • SSN and Federal ID fields become visible and can be captured.

  • If either condition is not met:

    • The fields remain hidden (no user distraction, no accidental data capture).

2) Upload Vendors

  • SSN and Federal ID columns are now supported in the vendor upload template.

  • During upload:

    • If Home Country = United States and Is 1099 Vendor? = Yes, the values (if provided) are ingested and stored.

    • If conditions aren’t met, the columns are ignored (no errors raised solely due to their presence).

3) Vendor Centre

  • New columns/fields are available for viewing and editing vendor records that meet the visibility conditions.

  • You can quickly audit or backfill SSN/EIN for existing U.S. 1099 vendors.

4) Data Export

  • SSN and Federal ID can be included in exports for reporting or downstream compliance workflows.

    Note: These are sensitive identifiers. Restrict export access to authorized roles only.

Introduction of Multibox Configuration in Item Setup

We are excited to announce the addition of a new feature called Multibox on the Create Item page. This enhancement provides users with the ability to define multiple cartons (boxes) with dimensions for a single item, enabling more accurate and flexible packing operations.

Overview:

  • Multibox Option: When enabled for an item, a new sidebar tab appears on the Create Item page.

  • Users can define multiple cartons for the same item.

  • Each carton can have its own dimensions (length, width, height) and associated configurations.

  • This makes it possible to map real-world packaging scenarios, especially for items that ship in more than one carton or in cartons of varying sizes.


Integration with Express Ship

The Express Ship process now leverages the Default Ship Carton Configuration (available via App Config) to determine how cartons are created during shipment. The behavior changes depending on the configuration selected:

  1. SINGLE CARTON

    • Regardless of how many multibox configurations are defined, the system will always create a single carton for the item.

    • Use Case: Useful when an item must always be shipped in one container, regardless of its defined multibox structure.

  2. CARTONS PER ITEM

    • For each item, the number of cartons created will correspond to the configured multibox definitions.

    • Example: If an item has 3 different cartons defined under Multibox, each time that item is shipped, 3 cartons will be created.

    • Use Case: Ideal for items with a fixed multi-carton packaging standard (e.g., furniture sets shipped in 2–3 cartons).

  3. CARTONS PER QUANTITY

    • Each unit of item quantity shipped will be assigned the defined number of cartons.

    • Example: If 2 units of an item are shipped and the item has 3 cartons defined under Multibox, a total of 6 cartons will be created.

    • Use Case: Perfect for scenarios where each unit of the item always requires multiple cartons (e.g., gym equipment, machinery parts).

Introduction of “Customization Info” Column

Overview:

We have introduced a new column called Customization Info across the following modules:

  • Sales Order (Detail) Centre

  • Create Invoice

  • Invoice Centre (Detail)

  • Invoice Subform

  • Sales Order Subform


How it works?

  • The Customization Info column is now visible in the above modules.

  • On clicking the value in this column, a modal window opens up.

  • The modal displays detailed customization information relevant to the selected record, giving users quick and direct access without navigating away from their workflow.

With this enhancement, both Sales Order and Invoice management become more efficient, enabling users to make better-informed decisions during order creation, review, and billing.

Support for Custom Fields in Advanced Variant Finder

Overview:

Previously, when items were added using the Advanced Variant Finder, any associated custom fields were not automatically populated. This caused gaps in data consistency and required users to manually re-enter details.

With this release, the system now supports custom field population during item selection via the Advanced Variant Finder.


How It Works

  1. Create Custom Field Definitions

    • Users can define custom fields for:

      • Item

      • Customer

      • Vendor

      • Estimate Detail

      • Sales Order (SO) Detail

      • Purchase Order (PO) Detail

  2. Establish Custom Field Mappings

    • Mapping enables the system to carry values from one entity to another. Supported mappings include:

      • Item → SO Detail, Estimate Detail, PO Detail

      • Vendor → PO Detail

      • Customer → Estimate Detail, SO Detail

  3. Automatic Population

    • Once mappings are in place, when items are added through the Advanced Variant Finder, the defined custom field values are automatically populated into the corresponding detail lines (SO, PO, Estimate).

Addition of "Ship To First Name" and "Ship To Last Name" Columns in Customer Info

Overview:

We have enhanced the Customer Info module for improved visibility and order tracking.

  • Under the "Orders and Estimates" tab, two new columns have been introduced:

    • Ship To First Name

    • Ship To Last Name

These fields display the recipient's first and last names associated with the order’s shipping address.

Customer Deposits Column in Sales Order Centre

Overview:

A new enhancement has been introduced in the Sales Order Centre for better financial visibility and quick navigation.

  • New Column Added: Customer Deposits

  • This column displays all deposit amounts associated with each Sales Order.

  • On clicking the deposit value, the system redirects directly to the Customer Deposit page, allowing users to review full details of the transaction.

  • The displayed amount is always synchronized with the deposit taken against the order, ensuring accuracy and consistency.

Auto-Select Default Item Location for PO Receiving and MO Production/Disassembly

Overview:

A new application configuration has been introduced: “Auto-Select Default Item Location for PO Receiving and MO Production/Disassembly.”

This app config is available as a multi-select dropdown with the following options:

  • Receive PO

  • Produce/Disassemble MO

The feature streamlines item location assignment by automatically using the item’s default location during key inventory processes, reducing manual effort and ensuring accuracy.

How it works?

When Enabled

  • During PO Receiving (via Quick Receive or ASN) and MO Production/Disassembly, the system automatically assigns the item’s default location.

  • Items are directly received, produced, or moved into their default location without requiring manual selection.


Validations

The system ensures data integrity by validating against defined configurations:

  • If an item’s default store or default location is not defined, the process will throw an error.

  • If the default store does not match the store selected in the PO or MO, the system will prevent location assignment and throw an error.


PO Receiving (ASN) Logic

  • If the app config is enabled for Receive PO, when a user manually receives an ASN, the system automatically checks the box: “Auto-Select Default Location By Item.”

  • This ensures consistency and removes the need for repeated manual location selection.


MO – Finished Goods Location Logic

  • On item change, the Finished Goods Location auto-fills with the item’s default location, provided the MO’s store matches the item’s default store.

  • On MO save, Finished Goods Location is updated to the default location.

  • For Sub-MOs:

    • If a raw material location is defined in a parent MO or via the settings map, then the Sub-MO’s Finished Goods Location (default location of the Sub-MO item) must match the raw material location of its previous MO (through which it was auto-triggered).

    • This logic applies only at MO/Sub-MO creation, not for existing MOs.

Addition of "RefNo" Column and Enhanced Search in Estimate Centre

Overview:

A new enhancement has been introduced in the Estimate Centre module, adding improved visibility and search capabilities for users working with estimates.

New Functionality

  1. Addition of "RefNo" Column

    • A new column, RefNo (Reference Number), has been added to both:

      • Estimate (header level)

      • Estimate Detail (line level)

    • This allows users to quickly identify and reference estimates using a dedicated reference number field.

  2. Enhanced Search Options

    • New search parameters have been introduced:

      • Order Number

      • Reference Number (RefNo)

    • These search options are now available in both:

      • Estimate

      • Estimate Detail

How it works?

  • The RefNo column serves as an additional identifier, useful when multiple estimates are generated for the same customer, project, or product.

  • With the enhanced search capabilities, users can now quickly locate estimates by either:

    • System-generated Order Number, or

    • User-defined/externally provided Reference Number.

  • This is particularly valuable in ERP workflows where estimates need to be reconciled against external documents, RFQs, or customer reference codes.

Validations & Considerations

  • The RefNo field is displayed as an additional column but does not alter existing numbering sequences or system-generated order numbers.

  • Both Order Number and Reference Number are independent search parameters, ensuring flexibility without overlap.

  • If no RefNo is provided, the column remains blank, and the search will return no results for that parameter.

Enhancements to Wave Centre – Wave Header

Overview:

New Columns Added

  • Ship Service

  • Third Party Ref Name

  • Third Party Notes

Module: Wave Centre → Wave Header


How it works?

  1. Ship Service

    • Captures the shipping service method (e.g., FedEx Ground, UPS Express).

    • Enables quick visibility and operational clarity on how shipments within a wave are being fulfilled.

  2. Third Party Ref Name

    • Stores the reference name for a third-party logistics provider or partner.

    • Useful for identifying and linking external logistics parties directly within the wave.

  3. Third Party Notes

    • Provides a text field for additional instructions, clarifications, or remarks from the third party.

    • Ensures critical details are logged and easily accessible during the wave process.


Validation / Behavior

  • All three columns are read/write fields and can be updated during wave creation or editing.

  • Data entered here flows through reporting and operational dashboards for better tracking.

  • If left blank, system processes continue as usual (no blocking behavior).

Configurable Print Options After Quick Ship/Express Ship

Overview:

A new App Config has been introduced under the Sales tab: “Print Options After Quick Ship/Express Ship.”

This configuration allows users to define which links (e.g., documents, labels, or reports) should appear on the success modal once a shipment is processed via Quick Ship or Express Ship.


Functionality

  • After completing a Quick Ship or Express Ship, the system displays a success modal.

  • The links shown on this modal (such as Print Invoice, Print Packing Slip, Print Shipping Label, etc.) are now fully configurable by the user.

  • Administrators can enable or disable specific options via the new App Config, tailoring the post-shipment workflow to organizational needs.

  • For Sales Orders with multiple waves, the system will display multiple links, one for each wave.

Default Sales Store and Default Ship Store at Customer Level

Overview:

This release introduces the ability to define Default Sales Store and Default Ship Store at the customer level. These defaults apply consistently across both UI and API processes, streamlining store selection and ensuring data integrity.

Modules Impacted

  • Create Customer

  • Upload Customer

  • Customer Centre

Functional Behavior

  1. In Transaction Modules

    • Applies to: Estimates, Sales Orders, Invoices, Credit Memos, and Sales Receipts.

    • When a customer is selected:

      • The system will pre-select and override the user’s default store with the customer’s default store, if one exists.

      • If the customer’s default store is not part of the user’s store mapping, the system will not assign any default store.

API Enhancements

  • A new flag UseCustomerDefaultStores has been introduced in the following APIs:

    • Upload Sales Order

    • Invoice API

    • Credit Memo API

  • Behavior:

    • When UseCustomerDefaultStores = true:

      • The system will prioritize the customer’s default store over the store provided by the user in the upload/API payload.

    • When UseCustomerDefaultStores = false or not provided:

      • The system will continue to use the store value provided by the user in the payload.


Validations & Constraints

  • Default Sales/Ship Stores must exist within the user’s store mapping to be auto-selected.

  • User must have access to the store.

  • If unavailable, the system will not assign defaults and the user must manually select a valid store.

  • UseCustomerDefaultStores flag is optional; backward compatibility for existing API integrations is maintained.

Batch Update for Custom Fields in Sales Order Lines

Overview:

A new option “Batch Update Custom Fields” has been added on the Create Sales Order page (line items section).


Functional Behavior

  • Users can now batch update custom fields on Sales Order lines.

  • The functionality mirrors the existing Batch Update Columns feature available in the Sales Order Centre.

  • Upon selection, the entered value(s) will be applied simultaneously across multiple or all selected line items, reducing the need for repetitive manual entry.

Validations & Considerations

  • Batch updates apply only to editable custom fields defined in the Sales Order schema.

  • User permissions for editing custom fields will continue to apply.

  • Audit logs will capture batch updates for traceability.

    • Existing values will be overwritten when batch update is applied.

Void Cheque Date Selection

Module: Payments

Overview:

Enhancement: Introduced the ability to specify a Void Cheque Date when voiding cheque-based payments.

Details:

  • On initiating a void action for cheque payments, the system will now prompt the user with a pop-up window.

  • The user can select the desired Void Date.

  • Upon confirmation, the payment will be voided and the system will record the selected date as the Void Cheque Date.

Available In: This functionality is now supported in the following modules:

  • TaxPayment

  • TaxInstallment

  • TaxInstallmentCentre

  • TaxPaymentCentre

  • CreateRefundReceipt

  • RefundCentre

  • InvoicePaymentViewSubForm

  • BillPaymentChequeSubForm

  • OutgoingPayment

Impact: This enhancement ensures greater flexibility and accuracy in managing cheque void transactions by allowing users to define the effective date of the void action.

Item Inventory Snapshot Consolidate View Optimization

Overview:

  • Performance improvements have been implemented in the Item Inventory Consolidate view to make it faster and more efficient.

  • A new configuration option has been introduced in App Config: Enable Optimized Views.

  • This is a multi-select type configuration (currently only one option is available: Inventory Snapshot Consolidate).

  • When this view is selected in App Config, the system will use optimized functions to enhance performance.

Impact: This enhancement improves system responsiveness and provides administrators the flexibility to enable optimized views, ensuring faster access to consolidated inventory data.

Minimum Order Quantity Enhancements

Modules Impacted:

  • Item Centre

  • Item Module

  • Data Export Centre

  • Presentation Module (Other Attributes)

  • B2B Portal


Overview

1. New Column: Minimum Order Qty

  • A new column Minimum Order Qty has been introduced in the following areas:

  • Item Centre

  • Item Module

  • Data Export Centre

  • This field allows users to define the minimum quantity of an item that can be ordered.

  • When maintained, this field ensures consistency between back-office operations and customer-facing portals.


2. New App Configuration: Min/Max Qty to Show in B2B Portal

  • A new configuration option has been added in App Config:

    • Min/Max Qty to show for items in the B2B portal

  • Functionality:

    • When enabled, the B2B portal will display the Minimum Order Qty and Maximum Order Qty (if defined) for each item.

    • This ensures customers are informed upfront about order quantity restrictions before placing an order.

  • Benefit:

    • Provides transparency to customers.

    • Reduces order rejections or modifications due to non-compliance with minimum/maximum quantity rules.


3. New Checkbox Option: Force Minimum Order Qty

  • A new checkbox option Force Minimum Order Qty has been introduced in the Presentation Module → Other Attributes section.

  • Functionality:

    • When checked, the system will enforce the Minimum Order Qty during order entry (both internal ERP orders and B2B portal orders).

    • Orders cannot be placed for quantities lower than the defined minimum.

Last updated

Was this helpful?