What we shipped, in plain language.

Saving a price condition failed with "this field is required" for key fields that are meant to be optional — a record keyed on customer and material was asking for a price list, product variant and product hierarchy as well. A condition record now only requires the combination you actually intend to price on.

Help documentation for the SD Pricing and Mobile Warehouse modules was authored on two parallel branches, leaving the content set with two competing endpoints and blocking deployment. The branches are merged and both sets of help pages install as intended.

Typing in the Purchase Order / Purchase Requisition dialog lagged noticeably on tenants with hundreds of orders, because the list grid behind the dialog re-rendered on every keystroke. The grid is no longer redrawn while you type.

The Sales Order column on the Purchase Order grid lists every sales order on the order's lines, so filtering for a sales order that was not the first one on a multi-order purchase order returned nothing. The column now filters on "contains", which answers the question the column is actually asked: which purchase orders touch this sales order?

Price lists, condition records, customer groups and floors now use the standard Syncfusion Grid used across the rest of the application — with column filtering, grouping and Excel export — plus a searchable material picker for condition entry instead of a plain dropdown over the whole material master.

Vendor invoice totals can now be rounded to the nearest whole currency unit, with the difference posted to a dedicated Round Off account. This works on both the PO-based and non-PO (FB60) invoice forms, and the Round Off row is shown on screen as you enter the invoice.

Rounding is applied only when the company has both the setting switched on and a Round Off account configured — no account is ever guessed, so an unconfigured company keeps its exact total rather than producing an invoice that cannot post.

A Simulate button on the non-PO invoice form shows the exact journal entry the invoice would post — every debit and credit line with its resolved GL account, cost centre and enterprise node, plus the fiscal period and the debit/credit tie-out — before the invoice is saved. Nothing is written by a simulation.

Configuration problems (a supplier with no payables account, a tax code with no input tax account, a closed period) are listed as blockers beside the preview, so they can be fixed while the form is still open.

An invoice line can now be marked as Debit or Credit, so a deduction or recovery can be entered on the same document instead of needing a separate credit note.

A foreign-currency vendor invoice now carries its own exchange rate, fixed at the document date and used to translate every GL line into the company currency. The rate is proposed from the exchange rate master; if there is no quote for the pair the form asks for one rather than silently posting at 1:1.

Exchange rates can also be fetched automatically from an external provider into the rate master, so vendor invoices, foreign-currency revaluation and the financial statements all read the same stored, dated rate.

Quotation and Sales Order entry gained a Suggest Price action that reprices the draft from the engine, with chips showing which lines were priced automatically and which were manually overridden. Only drafts can be repriced — an issued document is never silently repriced behind your back.

The new Pricing workspace (/crm/pricing) includes a Simulator that prices a whole draft document in one call so you can see the effect of a change before releasing it, plus margin analytics comparing engine-priced sales order lines against moving average cost.

Selling prices now come from a maintained Price List instead of being typed on every document.

• Price lists move through Draft → Released → Archived, so a season's prices are prepared and reviewed before they can be used
• Assign a price list to a Customer Group, with a per-customer override where a specific buyer has their own deal
• Copy an existing list with a percentage uplift (e.g. "next season +8%") and export any list to Excel

Two new roles: Pricing Analyst (view and maintain draft price lists) and Pricing Manager (full access including release, floors and price override).

A single condition-record table drives base prices, percentage and amount discounts, surcharges and freight, keyed by any combination of customer, customer group, price list, material, product variant or product hierarchy.

• Most specific record wins, on a fixed and predictable ladder
• Quantity scale tiers (buy more, pay less) and validity dates
• Tax-inclusive list prices are converted to net automatically, and records in another currency are converted at the document's rate
• Every priced line stores a full breakdown of how the price was reached — including records that were considered and skipped
• The engine never invents a price: when nothing matches, it says so rather than guessing

Define a minimum price or minimum margin percentage per company, customer or material. A line that breaches it either raises a warning or is blocked outright, depending on how the floor is configured.

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.

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.

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

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 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.

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.

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.

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).

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.

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

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

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

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.