WebApp Version 25.37 Changelog

This update includes new features, essential performance improvements, and usability enhancements, ensuring your daily operations run smoothly. We've also addressed several bug fixes to enhance stability and reliability. Thank you for your continued trust and feedback, which help us deliver the best possible service.

New Feature:

• [Products] Variant Display Name Formula

  In this update, we have introduced a new setting called "Variant Display Name Formula". By default, the system used to generate variant names in the format {ProductName} ({VariantName}). With this new feature, users can now fully customize the formula according to their own preferences. In the formula, both {ProductName} and {VariantName} are mandatory variables, while users can freely define separators or other formatting details. This gives more flexibility and consistency in how product variants are displayed across the system.

  

  When importing products through the Import Product module, if users do not declare the DisplayName column, the system will automatically generate the variant display name using the formula defined in the settings. This ensures that even during bulk imports, variant names follow the chosen format without requiring additional manual edits.

  

  The new formula setting also applies when creating products in the Product Form. If a product has more than one variant, the system will generate the variant names based on the formula set by the user. However, users still retain the option to manually adjust the display name if they want to make exceptions for specific variants. This balances automation with flexibility.

  

  Lastly, the formula is implemented in the Variant Form as well. When users are creating or editing a variant, the default display name will be generated automatically using the configured formula. Still, just like in the Product Form, users can override it with a custom display name if needed. This consistency across modules ensures a smooth and predictable workflow while keeping customization open to the user.

  

• [Inventory] Inventory by Category

  We have introduced a new menu called Inventory by Category, which allows users to view inventory based on product categories. Since the category structure in the system supports a tree (branching) hierarchy, this view also provides the ability to navigate through child categories. Users can expand categories using a dropdown, making it easier to explore inventory details not only at the parent category level but also at each child category level in a clear and organized way.

  

  This feature was developed based on customer request #6123

• [Adjustment] Merge Adjustments

  In the Adjustment menu, users will now see a new Merge button that allows them to combine multiple adjustment records into one. This feature was introduced because in real scenarios, some businesses have multiple users performing a stock take at the same time. Each user can create a separate adjustment record. Instead of manually editing each record, this feature enables them to merge all adjustments into a single record, making the process more efficient and practical.

  

  When the Merge Adjustment modal is opened, users can select which adjustments to merge and decide the final record they want to keep. All selected adjustments will be summed up — for example, if Adjustment-001 contains +3 qty for Item A and Adjustment-002 contains +7 qty, the merged record will display +10 qty for Item A. The conditions for merging are: the adjustments must be in draft status (enabled only if using the “with approval” workflow), must have the same adjustment type, and must belong to the same outlet. Once merged, the chosen adjustment record remains while the others are deleted automatically.

  

  This feature was developed based on customer request #4854

Minor Improvements:

• [Products] Improve Release Date Column Format in CSV Export

  

  This improvement was developed based on customer request #6197

• [Orders - Customer Invoice] Provide Filter to Display Voided Invoice in Invoice List

  

• [Orders - Supplier Bill] New Configuration to Display Bill Status

  We’ve introduced a new feature that allows users to display approval status when printing purchase orders. In the setup menu, users can configure whether their purchase order workflow follows the Instant flow or the With Approval flow. When the With Approval option is enabled, an additional setting is available to include approval status in the printed purchase order. This gives businesses more flexibility to align their purchase documents with internal approval processes.

  

  When printing a purchase order under the With Approval flow, the document will now clearly show the approval status. This ensures that all stakeholders can easily verify whether the order has already gone through the required approval steps, providing better transparency and reducing the risk of confusion or miscommunication during procurement.

  

  This improvement was developed based on customer request #5398

• [Orders] Refactor Modified Trigger in Customer Invoice & Supplier Bill

  In this update, we have refined how the Modified Information is triggered in the Customer Invoice and Supplier Bill modules. Previously, there was an inconsistency — for example, adding or editing a payment would trigger Modified, adding fulfillment would trigger Modified, but editing fulfillment would not. Since these actions (payment, fulfillment, write-off, or join invoice/bill) are not direct edits to the transaction itself, they should not update the Modified timestamp. To ensure consistency, we have removed the modified trigger from the following actions :

  • Add/Edit/Delete Payment,

  • Add/Edit/Delete Write-Off,

  • Add/Edit/Delete Fulfillment

  • Collection / Join Invoice or Join Bill.

  

  As a replacement, we now provide better visibility through the Log Update History. Specifically for Payment, Write-Off, and Fulfillment actions, the system will log Add and Delete activities in the history, so users can still track changes clearly without affecting the Modified timestamp. This ensures that Modified reflects only actual edits to the transaction, while operational activities are correctly recorded in the history log for complete transparency.

  

  This improvement was developed based on customer request #6103

• [Developer - Webhook] Provide Export Feature

  

• [Setup - Apps] Provide Tab Grouping for Apps Service

  

Bug Fixes:

• [Sell] Fix External Coupon Not Removed When Replacing Eligible Cart Item with Ineligible One

• [Contacts - Point History] Remove Returned Point History from Sales Return Transaction

• [Orders - Customer Invoice] Fix Timezone for Payment Modified Time

• [Developer - Webhook] Fix Infinite Running Time for Webhook Records

Stay tuned for more updates, and don't hesitate to reach out if you have any questions or need support.