Changelog

Internal notes on Sales Orders, Purchase Orders, and Shipments can now be edited. Each note you wrote shows an Edit action that opens the same dialog you used to add it, prefilled with the current content. Saving updates the note in place and marks it with an “(edited)” indicator so anyone reading the timeline knows it changed since it was posted. Only the note’s author can edit their own notes; everyone else’s stay read-only.

Searching for a product to add to a Purchase Order, a Supply Shipment, a bundle, an echo SKU, or from the command palette now returns results quickly on very large catalogs — pages that used to time out and show “No products found” on accounts with over a hundred thousand products come back in a fraction of a second. Name and SKU search return the same products as before, just fast enough to actually use.

Purchase Order and Supply Shipment detail pages load faster across the app, and the improvement is biggest on large documents — pages that used to take several seconds now open quickly no matter how many line items they have. Product names, images, and cost totals appear together instead of trickling in row by row, with no change to the numbers themselves.

The Supply Shipment detail page is refreshed to match the Purchase Order redesign. Destination is an always-available sidebar selector — building, location, or a custom destination — that saves automatically, and closed shipments show it read-only. The item table folds the product image into the details column, keeps the purchase-order grouping, and moves sorting into Actions → Sort. Status changes live under a single “Change Status” action with everything else in a three-dot menu, and the tabs are more compact, with document and note counts and a dedicated Notes tab.

You can now sort the line items on a purchase order. Open Actions → Sort, pick a column, and choose ascending or descending.

Supply shipments now pass through a Received step between In Receiving and Closed. WMS integrations (Extensiv, Gobolt, Infoplus) mark a shipment as received automatically once the downstream system reports receiving complete, so the shipment no longer jumps straight to closed while receiving finishes. Closing is now a deliberate manual step from Received, which keeps Closed as the finalized state you commit to when you’re done.

The timeline, status badges, filters, and shipment status groupings all pick up the new step. Cancelling from In Receiving and Received is allowed. A shipment needs at least one item and a destination to enter Received.

Each Extensiv integration now decides, separately, what Endless sends as the line-item lot number and as the receipt advice number. Choose the real lot recorded on the shipment line, the shipment reference, the shipment number, or nothing at all, from the integration’s settings.

The two overlapping switches this replaces keep working until you edit the integration, at which point you pick a source for each. Receiving a shipment that carries the same SKU on more than one line no longer posts the quantity twice.

The Purchase Orders list has a status filter — draft, issued, in production, in transit, delivered, closed, canceled — matching the status lifecycle the PO detail page already used. The old “approved” filter, which never quite worked, is gone.

Supply shipment items now carry a lot number, so one PO line can be split into multiple shipment rows — same SKU, different production batches — each with its own quantity and its own lot. Assign lot numbers when adding items to a shipment, edit or split an existing line across lots, and filter shipments by lot number from the list. Lot-aware product costs surface on rows where they’re relevant. Coverage math sums per lot bucket, closing a case where two lots on the same PO line collided and one row’s quantity silently vanished from the totals.

WMS/ASN payloads and lot-aware inbound sync aren’t wired yet — those follow once the WMS side sends a lot identifier.

Purchase-order notes now live in the same Internal Notes system every other object uses, so the notes card on the PO Details tab behaves the same way it does everywhere else in the app. Milestone progress updates stay on the milestone card and are separate from notes — the two are no longer tangled together.

Existing PO notes were migrated over with their original ids, timestamps, archived state, and author preserved.