What we shipped, in plain language.

The application no longer fails to start in a production-like environment with debug mode on if the debug toolbar package is not installed.

A formatting slip in the production host allow-list merged three separate entries into one unusable value, causing direct-IP requests to be rejected. The allow-list is corrected and no longer includes a port number where one is not matched.

After the security hardening release made authentication the default everywhere, the public marketing website pages (blog, pricing, contact, tenant validation) started requiring a login. These are explicitly anonymous again, as intended.

The Purchase Order PDF derived a line's CGST/SGST/IGST split by checking whether the tax code's name contained the text "CGST" or "SGST" — an intra-state code literally named "GST 18%" contains neither, so its tax was wrongly bucketed entirely under IGST. The split is now read from the tax code's own configured CGST/SGST/IGST percentages instead of guessed from its name.

The unused R-Shiny analytics integration (already decommissioned) has been removed from the codebase, and the marketing product catalog refreshed with pages for modules that had none.

The Free of Cost (FOC) Delivery and Credit Management list pages now use the standard Syncfusion Grid (in line with the rest of the app) for filtering, grouping and Excel export.

Continued refinement of the garment costing entry screens: Order Info section, Batch, Making Cost, Trims & Labels and Value Additions grids updated with clearer material selection and layout.

Three new roles: Serial Number Clerk (register + capture), Serial Number Controller (full access), Serial Number Viewer (read-only).

Materials can now be flagged as serial-controlled, with a profile that decides where scanning is required (receipt, issue, delivery, transfer, count).

• Full unit history: receipt, issue, delivery, repair, return, scrap
• A unit cannot be issued or transferred from the wrong location — the system checks it is actually on hand where the scan says it is
• Delivering a serialised unit captures customer, warranty period, and raises a Customer Service asset record automatically
• Reversing a receipt or issue restores each unit's prior status from its own history rather than guessing

Build a Landed Cost Sheet against a Bill of Entry / BL-AWB / container to allocate import charges across the goods-receipt lines they belong to, even when those lines span several goods receipts and purchase orders.

• Allocate by Value, Quantity, Weight, Volume, or a manual split
• Live allocation preview before posting
• Charges already consumed from stock are automatically expensed instead of loaded onto units that no longer exist
• Non-inventoriable charges (e.g. import IGST) post as an input tax credit instead of loading stock
• Full reversal support

Two new roles: Import Costing Clerk (build sheets, enter charges) and Import Costing Accountant (full access including posting and reversal).

Three new roles: Warehouse Operator (scan + build sessions), Warehouse Supervisor (+ post + print labels), Warehouse Manager (full access).

A new Mobile Warehouse page lets a warehouse operator scan barcodes/QR codes on a phone or handheld to drive five core flows: Goods Receipt, Put-away, Transfer, Picking and Cycle Count.

• Works with a keyboard-wedge handheld scanner or the phone camera
• Recognises material, batch, bin, storage location, warehouse, purchase order, delivery note and production order codes, including GS1-128/DataMatrix labels
• Offline-safe: a dropped connection cannot double-post the same session
• Blind cycle counts never reveal the system quantity to the counter

Print QR code labels for materials, batches, handling units, bins and warehouses directly to an A4 sheet (24 labels per sheet).

Saving an invoice or other audit-tracked document occasionally froze the whole request, and every subsequent write queued up behind it. The cause was the audit log being written on a different database connection than the record it was recording — two separate connections to the same database ended up waiting on each other's lock. The audit event now always uses the exact same connection as the save it belongs to.

An approved payment run can now be exported as a bank payment file in the bank’s upload format, so payments are handed to the bank as a single file instead of being keyed into net banking one by one.

The bank’s response file is read back in, matching each payment to its UTR reference and status. Payment records therefore carry proof of remittance without anyone transcribing reference numbers.

The audit entry for a saved record could be written over a different database connection than the save itself, so the two waited on each other and the save never completed. The audit entry now always uses the same connection as the record it is recording.

Orders held on credit appear in a blocked orders worklist where a credit controller can re-run the check or release the order once payment or an exception is agreed.

Two roles ship with the feature — Credit Controller and read-only Credit Viewer. Help documentation for the module is included. Without configuration the existing order-entry behaviour is unchanged.

Credit is checked when a Sales Order is raised and again when goods are about to leave, catching exposure that has grown since the order was approved. Each check can be configured to block, merely warn, or be switched off, with a tolerance percentage and an overdue-days rule.

Every check is logged with the exposure figures it saw, so a block can always be explained.

A new Credit Management workspace shows what each customer actually owes you: open receivables, orders taken but not yet delivered, and goods delivered but not yet invoiced — added up as live credit exposure against the customer’s limit.

Limits can be set per customer with a risk class, an expiry date and a hard block, overriding the limit on the customer master.

The tamper-evident audit chain was being applied to every record saved anywhere in the system, which made unrelated saves queue behind one another and left the application unresponsive under load.

The chain is now applied only to the financial documents that statutorily require it; everything else is logged normally. Location lookups for the audit record are also cached briefly so a slow lookup cannot delay a save. The statutory trail itself is unchanged.

Open foreign-currency items — customer invoices, vendor invoices and foreign-currency bank and loan accounts — can now be revalued at the month-end closing rate as required by AS-11 / Ind AS 21.

The run is previewed first, showing every open item with its booking rate, closing rate and the resulting unrealised gain or loss, before a single adjustment entry is posted. A missing closing rate is reported as a blocker naming the currency — never guessed.

By default the entry auto-reverses on the following day, so the next month-end revalues afresh and settlement-time differences are untouched. A completed run can also be reversed outright.

Action required: configure the gain, loss and receivable/payable adjustment accounts per company, and maintain closing rates before each run.