What we shipped, in plain language.

Creating a replacement order from a sales return failed every time because no billing or shipping address was copied. It now succeeds.

A customer return now puts the goods back in stock at the cost they were issued at, with a matching accounting entry (stock debited, cost of sales credited), one delivery per receipt line. Deliveries that issued nothing are reported rather than restocked. Point-of-sale returns could not restock before and now do.

Deliveries take the variant from the sales order line and use only that variant's stock and batches. The point of sale checks availability per variant and lists a variant-stocked product one row per variant. Free-of-cost deliveries and job work lines carry a variant too, and a sales order shows size-level availability.

Material planning now counts open requisitions, purchase orders, stock and reorder points per variant, and a combined production order is no longer counted once per size.

• Components can take the parent's variant, a mapped variant or a fixed one; unresolved components are reported, never defaulted.
• Production reservations, goods issue, back-flush and sub-contract issue and return carry the component variant.

Stock cover, open purchase order and inventory ageing reports can now be read by variant.

Materials set to require variant stock control now hold stock, batches and ledger entries per variant. Stock can be reclassified from one variant to another without any accounting entry, and a variant stock matrix shows the position by size and colour. Materials that do not require it post exactly as before.

Purchase requisition, RFQ, purchase order, sub-contract component and vendor invoice lines can now name a variant. The variant is carried through goods receipt (one batch per variant) and return.

• Variant grids on the requisition and purchase order dialogs, and receive-by-variant on the goods receipt.
• Per-variant supplier pricing and shade codes, with a maintenance screen.

The Release action skipped the standard cost freeze that Change Status performs. Every route to Released now goes through the same status service.

The status field on the edit form is locked, so an order could not be released while editing. A new Save & Release button saves the order and releases it.

Management-by-Exception digest emails were sent without the company context, so they skipped the company's configured email channel and used the shared platform sender instead. Each company's digest now uses its own channel and records the send in its own log.

Platform administrators can now set the password or API key of an email channel (the value is never shown again; leaving it blank keeps the stored one) and send a test email from the channel form or the channel list. A failed test is reported as a message instead of an error page.

Bundle labels now print on a roll of stickers laid out in a grid. Set the sticker size, stickers per row, gaps, print margin, shift, rows per page and orientation; the preview matches the printout and the layout is remembered in your browser. Label printers that create the gap themselves are supported so pages no longer drift.

The Separations list now pages, searches, sorts and filters on the server, so it stays fast with many records.

• Search also matches what the cells show, such as "pending" or "voluntary".
• New filters for separation date range and regretted state, including exits not yet assessed.
• A Pivot view tab and saved column layouts.

A signed-in session from a company's address could be recognised on the main platform address with that company's administrator rights, reaching platform administration and shared content.

• A company user is now accepted only on that company's own address, and on the main site is limited to what the platform allows a company user.
• Support Desk agent status is granted only to platform users, so one company's administrator can no longer see tickets from other companies.

Creating a company from the template database could fail while giving the first administrator their group and permissions, and a failed set-up could leave the server returning errors until it was restarted.

• The administrator group and permissions are now saved in the new company's own database.
• A company created while the server is running no longer opens a transaction on every request.
• Set-up retries its database connection if the first attempt arrives while the database is still being re-created.

Help videos can now be recorded from a short script of captions and steps, converted to MP4 with a poster image and uploaded to the matching Help Centre article in one command. Re-recording replaces the earlier video and keeps its position and view history.

The shop-floor Complete button closed an operation however much was still open, so 60,000 of 70,000 showed as Completed. It now refuses, states the open quantity, and points to Final Confirmation for a deliberate short close.

Opening an existing production order for editing crashed the form. It now opens normally.

Editing a purchase order opened with blank notes, terms and addresses because the form used the list record. It now loads the full order, and the expanded grid row shows Notes and Terms.

A data upload matched a value such as a department name against every hierarchy, so a name that existed in two hierarchies matched twice and the row failed. A lookup now honours the field's own scope (for example, only the enterprise hierarchy for a department), and the upload template lists the same choices.

The Vendor and Customer Balance List Excel export now has Opening and Closing Dr / Cr columns, including the totals row, so the sign of a balance is no longer ambiguous.

• Saved column layouts per user, column chooser, resizing, and Excel and PDF export.
• Date columns filter by range (between, before, after) by day.
• The sales order filter loads quickly from the operations themselves.

Production Confirmation now records what was produced in each sitting and adds it to the operation's totals. The operation stays In Progress until good plus scrapped reaches the order quantity, or the confirmation is marked Final to close it short.

• A partial confirmation posts nothing; the closing one posts the back-flush, receipt and scrap once, on the cumulative quantities.
• Two confirmations of the same operation at the same time both count.

A rework quantity can be keyed on confirmation. It is a record only: reworked pieces come back and are confirmed as good later, so they do not consume components, are not written off and are not received. Negative quantities are refused.

Five UAT scripts (setup, run and calculation, approval and payment, interim and supplementary runs, exit bonus and reports) and Help Centre articles for Statutory Bonus.

Statutory bonus is calculated from released regular payroll results on the wage types flagged as bonus wages, with arrears counted in their original month. The Act is a floor: the employee receives the higher of the scheme and the statutory amount.

• Bonus year per company with category rules, staff slabs, gift amounts and minimum wages; copy to a new year, close and reopen.
• Bonus groups resolved from the assignment, payroll area or employee type.
• Full, interim and supplementary runs: calculate, check (override, hold, disqualification, deduction), submit and approve (HR Manager, Management Auditor, MD).
• Approval pays through one bonus off-cycle run per payroll area, with TDS, GL posting and bank files of up to ₹49 lakh each; confirm paid, or reverse before the bank file.
• A month with no payroll result is reported as an exception, never counted as zero.

Final Settlement pulls the bonus due to a leaving employee, with an eligibility panel. Employees see their bonus under My Bonus in self-service, with a bilingual bonus slip.

Audit report, abstract, bank statement, cash acquittance, exceptions, unpaid, exit, provision and year-on-year reports, plus statutory Form C and Form D.

Every Help Centre category, article and search results page returned a server error after the help content formatting update. The pages now load the formatting they need and open normally.

On Windows the browser installer could hang after the download, so every start of the demo shell downloaded Chromium again and never launched.

• The shell now checks whether Chromium is actually installed rather than trusting the installer's exit.
• A first install finishes as soon as the browser is complete, with a 15 minute limit.