What's new

Fixed an issue where transferring a barcode to another branch replaced the existing barcode party with the branch name. Ensured the existing barcode party, actual purchase cost, and rebarcoding user details are retained correctly during branch transfer

Fixed the issue where wholesale rate, wholesale service rate, and wholesale stone rate could not be saved in material receipt. The entered rates are now saved correctly and retained after reopening the voucher.

Fixed the issue where barcode party details were missing or incorrect during branch and online stock transfers. Corrected existing affected barcodes and ensured barcode party details are retained correctly for new and future transactions

Fixed an issue where the service account configuration was automatically missing from the voucher type service tab. The service account configuration is now retained correctly to ensure uninterrupted billing using configured service items.

Updated loose diamond barcoding to display tag weight in grams (gm) instead of carats (ct) for accurate and consistent weight representation.

Fixed an issue where the labour calculation type and other labour calculation type options were not displayed on the material receipt screen when enabled in settings.

Fixed an issue where barcodes with a barcoding-adjustment entry were incorrectly shown as unavailable in stock while creating a sales invoice. The barcode validation has been corrected.

Fixed an issue where cs gross weight was missing in the material receipt during online transfers from ouro to nebu. The weight is now correctly carried over and displayed in the material receipt.

A rare issue was reported where the weight was not displayed and the corresponding stock was automatically removed for a single repair receipt voucher. This behavior was observed only for that specific bill, while the voucher appeared correctly when viewed on its original entry date. A detailed investigation was carried out, including verification of related transactions and possible triggering scenarios. However, the issue could not be reproduced in any other case. By the time the investigation began, the affected bill had already been re-entered, making it impossible to identify the exact cause. Based on the analysis, this appears to be an isolated and extremely rare occurrence, with no similar cases identified during testing or verification.