What we shipped, in plain language.

The engineer reports the machine fixed. The supervisor then runs an operator check with the badge and either confirms the repair, which closes the breakdown, or sends it back to the engineer. Downtime is calculated automatically and one failure history record is written.

A new Machine QR Labels page produces the labels that supervisors scan when reporting a breakdown.

The roles PM Maintenance Manager, PM Production Supervisor and PM Stores Keeper are added, with permissions to report, assign, work on and issue spares for breakdowns. Administrators must assign these roles to users.

A production supervisor scans the machine's QR label and the operator's badge on a phone to report a stoppage. Maintenance managers are notified straight away in the app and by web push.

Managers see a queue of open breakdowns and assign an engineer. The list shows each engineer's current open jobs. The engineer accepts the job and the reporter is notified. The Report, Assign, My Jobs and Stores tabs are on a new mobile breakdown page.

Engineers classify the breakdown from a category and failure-mode list, record the diagnosis, and raise the emergency work order from the job sheet. They can then start the repair.

Engineers reserve spare parts, and a purchase requisition is raised automatically for items out of stock. They can also request an external service order. Reservations can be cancelled or short-closed.

Stores staff see open spare reservations, most urgent first, and can check where stock can be picked. They issue the parts to the cost centre, and the parts are recorded on the work order.

Entries that were deleted at the Front Desk were still appearing in the entry list, dashboard counts, pending goods receipts and emailed reports. They are now excluded everywhere.

A daily Front Desk report filtered to one category used to be sent as an empty email when only other categories had entries. It is now sent only when entries match the filter.

You can now schedule an end-of-day email listing everything the Front Desk received today, oldest first. It can be limited to one category, set to a fixed cutoff time or a specific date, and can optionally send a 'nothing received' email on empty days.

When you cost the next size by pressing New Version on the previous one, a price revision used to re-price only the last sheet in that chain. It now re-prices each different item, along with the finished fabric and greige sheets they are built on.

Moving an order out of Credit Block on the edit form now records a proper credit release, so the next save no longer puts it back in Credit Block. Only users with credit release authority can do this.

Reducing the amount of a credit-released sales order keeps its release. Increasing the amount still requires a new credit check.

If the key is missing, rejected, out of credit or lacks permission, the message now says it concerns your organisation's AI account. It also points administrators to where to fix it. Data chat falls back to simpler answers when no key has been added.

Administrators can add their organisation's own Anthropic and OpenAI keys on a new AI Provider Keys page. All AI features now run on your organisation's key.

Document numbering patterns can now use the year the fiscal year starts, for example 2026 for 2026-27. This works with fiscal-year numbering resets.

Unpublished release notes, and editing the changelog, now need Biztimize platform staff. Previously a tenant administrator could see them and change changelog content.

The Help Assistant can now answer from released notes, and permission, company and licence refusals carry an error code that finds the related notes. The Support Desk Knowledge Base and FAQ are replaced by Notes.

Biztimize Notes are numbered, versioned articles on known issues, corrections and how-tos, read at /notes/ on the Help Center with the same sign-in as Help. Search by number or text, compare versions, download a PDF, give feedback, report a problem and subscribe to a note.

The Note Assistant lists the notes that apply to your system, with a status and checklist for each. HotNews appear as a banner and are emailed to the administrators of affected tenants, and a “Notes for this screen” button shows the notes relevant to the page you are on.

Raising a PR-sourced PO line above the requisition quantity is refused, which read as the goods receipt locking the line. The message now explains that an excess delivery is accepted through the line’s over-delivery tolerance, which the goods receipt already honours.

Purchase Orders, PO Line Items, Purchase Requisitions, RFIs, RFQs, Supplier Evaluations and Evaluation Templates, the Expeditor worklist, the Replenishment worklist, Vendor Master, Supplier Onboarding and Discovery, and Vendor Capacity now use the standard list screen: header icon bar, Grid and Pivot tabs, saved layouts and Excel export. PO Line Items can also be downloaded as a PDF.

Incoming Shipments, Supplier Invoices, Supplier Documents Review and Supplier Analytics use the same standard list screen.

A new Newsletter Subscription page in the user menu lets you subscribe to a weekly or monthly digest of Biztimize product news, delivered at your local hour. Subscription is confirmed by email, every email carries a one-click unsubscribe, and nothing is sent when there is nothing new.

Contract Management is now its own licensed module (permissions prefixed ctm.) instead of being licensed only with Compliance Management. Existing role grants carry over.

Contracts can be signed (with a new contract PDF), a certificate signs only for its owner, and unapproved purchase orders are refused by name. Clause versions, variables and applicability rules have their own screens, and vendor, company and document pickers replace typed ids.

Submitting a contract starts the Contract Approval workflow (role “Contract Approver”). Contracts are approved, rejected or returned only in My Approvals, which now shows the contract on its Document tab and explains a refused approval.

A new “Terms from Clause Library” button on a draft purchase order assembles its Terms & Conditions from the vendor contract in force on the order date, asking for any value the contract does not state. The printed PO now shows the clauses.

A contract is submitted once it has its clauses and every required value, approved by someone other than the submitter, and can then be renewed or terminated. It can be returned to draft with a reason; only a draft is edited, and overlapping active contracts are refused.