WebApp Version 25.31 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] New Search Products Tools

  We’ve added a new configuration called “Text Search Page Size” to enhance the search experience for products with numerous variants. Previously, when searching with a keyword (e.g., "Product"), the system returned data based on variants, which sometimes resulted in only one product (e.g., Product A with 20 variants) appearing, even though more products matched the keyword. With this setting, you can define how many variant results should be retrieved per search. For example, if set to 40, the system will return the top 40 matching variants, allowing full display of Product A’s variants and potentially other matching products in the same search result.

  

  We’ve also introduced a new filter in the Product List called “Search Mode”, with two options: Product and Variant. When set to Product, the search will look for matches based only on the product name, and if a match is found, all of its variants will be displayed. However, if your search keyword (e.g., "Item A") is the name of a variant, it will not appear in the results when using Product mode. To search using variant names, you’ll need to switch to the Variant mode. This filter provides more control over how search queries behave depending on your use case.

  

• [Logistics] Shipped Picklist Use Reference Number Setting

  We’ve introduced a new configuration setting called “Shipped Picklist Use Reference Number”, which can be enabled from the setup menu. When this configuration is turned on, the system will prioritize using the Reference Number instead of the default Invoice Number when generating the Outbound Logistic Number. This allows for smoother synchronization, especially for integrations such as Omni, which rely on Reference Numbers for better tracking alignment.

  

  In the Fulfillment module, when an order progresses to the Pack stage and is then shipped, an Outbound Logistics record will be generated as usual. With this setting enabled, the system will check if a Reference Number exists on the order. If it does, that number will be used for the Outbound Logistics Number. If the Reference Number is empty, the system will fall back to using the Invoice Number, maintaining consistency in record creation.

  

  In the Logistics module, when users initiate an outbound shipment from an unsent invoice, the behavior will follow the same logic. If the configuration is active and a Reference Number is present, the Outbound record will use the Reference Number as its identifier. This enhancement provides improved control and traceability when managing outbound logistics across systems and workflows.

  

• [Promotion - Coupon] Point Deduction Setting

  A new setting has been added when creating a coupon, called "Point Deduction". This option will appear only after assigning the coupon requirement specifically to certain customers. For example, if you assign the coupon to Customer A, the system will show the Point Deduction toggle, allowing you to activate it and input a Deduction Amount (e.g., 100). This means that the customer must have at least 100 points in their account to be eligible for the coupon, and those points will be deducted immediately upon coupon creation.

  

  This deduction will also be calculated based on the "Usage Limit" and "Total Coupon" fields when setting up the coupon. For example, if the Deduction Amount is 100, the Usage Limit is 10, and the Total Coupon is 5, then the total point deduction will be 100 x 10 x 5 = 5000 points. These values are important to review before finalizing the coupon setup to ensure sufficient points are available and used accordingly.

  

  Once the coupon is created, the deduction will be reflected in the Customer's Point History under the Customer module. If only one coupon was generated (Total Coupon = 1), the log will show "Single Coupon Created (#CouponCode)". If more than one coupon was created, the log will show "Multiple Coupon Created (#NumberOfCoupon)", providing full traceability of the point deduction event.

  

Minor Improvements:

• [Products]

  • Provide Infinite List for Product List

  • Provide Search Outlet Feature for Inventory Tab in Variant Info

    

• [Shift] Differentiate Invoice & Join Invoice Record in Payment Tab

  

• [Orders - Customer Invoice]

  • Hyperlink Coupon to Coupon Info

    

  • Provide Reference Number Value Type Filter

    

• [Orders - Voided Invoice]

  • Standardize Filter Similar to Customer Invoice Filter

  • Implement Non-Sargable Query Configuration

    

  • Display Placeholder Based on Number Filter Comparator

    

• [Debt] Restrict Payment Option in Join Invoice & Join Bill Info with Payment Outlet Access Control

  

• [Logistics - Outbound]

  • Restrict Data Deletion with Outlet Write Access

  • Exclude Invoice with Picked Fulfillment from Order Option in Outbound Form

  • Allow Users to Search Orders by Reference Number in Outbound Form

  • Display Reference Number in Orders Option on Outbound Form

    

• [Fulfillment] Display Reference Number in Fulfillment Info

  

Bug Fixes:

• [Dashboard] Fix Inventory Tab / Section Display Blank Data

• [Reports - Monthly] Fix Incorrect Data in Chart View When Filtering Data by Category

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