Ouro Release Notes
These release notes cover the latest updates in ouro, the complete software solution for jewellery wholesalers. This version improves bulk inventory handling, streamlined dispatch processes, and enhanced integration with retail channels.
- Resolved an issue in the adjustment entry screen where the total weight was not updated automatically after scanning a barcode. With this fix, the corresponding bom weight is now populated automatically upon barcode scan, and the total weight is updated without requiring the user to click or manually enter details in the main item/join item section.
- Resolved an issue in the adjustment entry screen where joining a barcoded item with available stock weight to an unbarcoded item incorrectly displayed the error "the item is not in stock/insufficient" and prevented the transaction from being saved. The stock validation logic has been revised:
join transactions now validate the physical stock of the bom detail items. Split transactions continue to validate the physical stock of the main item. This ensures that stock validation is performed against the correct items, allowing valid adjustment entries to be saved successfully.
- The issue where the barcode generator displayed a blank page when tracking a barcode through the barcode tracking report has been resolved. Issue:
when users attempted to track a barcode from the barcode tracking report, navigating to the barcode generator detail page resulted in a blank screen instead of displaying the associated voucher. Resolution:
the navigation logic has been corrected. The barcode generator now correctly displays the corresponding voucher details when accessed from the barcode tracking report. Status:
the fix has been successfully tested, verified, and deployed.
- Added a stones number trim option in barcode generator → tag print. When enabled, the stones number is trimmed and printed in the tag according to the configured format
- Fixed an issue where accessing party account details from the barcode generator incorrectly redirected users to the login page. Users can now access party account details successfully without unnecessary re-authentication during an active session.
- Issue:
in the ledger transaction report, transactions for the selected ledger were not being displayed correctly. Resolution:
the report logic has been corrected to ensure that when a specific ledger is selected, all exact matching transactions along with their corresponding ledger entries are displayed accurately. Status:
the issue has been resolved, tested, verified, and deployed successfully.
- Introduced the certification number field in the material receipt excel import format, ensuring certification details can be imported along with item data. This resolves the issue where the certification number field was missing from the import template.
- Fixed an issue where purchase vouchers caused weight mismatches in related reports and incorrect closing gold balance and party ledger values. After the fix, updating the purchase voucher correctly reflects the weight and balances across all related reports, including the combined ledger report.
- Fixed an issue in sales invoice print template-1 where party details were displayed on multiple pages. Party details are now shown only on the first page of the printed invoice.
- Resolved an issue where the latest active rate master was not automatically loaded based on the current date when creating new vouchers. Previously, the system did not always fetch the correct active rate master while creating a new sales invoice. This issue has now been resolved across all applicable vouchers, ensuring that the latest active rate master is automatically loaded based on the voucher date.
- The issue in the trial balance report where the opening stock value was incorrectly reflected under the "difference in opening" account when selecting a specific date range within the financial year has been resolved. Root cause:
the issue occurred when no opening stock value was maintained for the financial year 2024–2025. In such cases, the system incorrectly considered the first purchase transaction as the opening stock, resulting in the opening stock value being displayed under the "difference in opening" account. Resolution:
the opening stock calculation logic has been corrected to ensure that the system no longer treats the first purchase transaction as the opening stock when no opening stock balance exists for the financial year. The trial balance report now correctly displays opening balances for any selected date range within the financial year.
- The api report has been implemented in ouro, aligned with the functionality available in nebu. Purpose of the enhancement:
to monitor and identify the status of api transactions. To track which apis were processed successfully and which failed. To identify the related vouchers for each api transaction.