Changelog

Mintsoft is a connected fulfillment integration now. Set it up from the integrations screen with your Mintsoft username and password, map its carriers to yours, and pick which warehouses to route through it. Endless sends shipment requests, and shipment updates come back on the normal pull.

Shipfusion is a connected fulfillment integration now. Set it up from the integrations screen: connect, map its carriers to yours, and pick which warehouses to route through it. Endless sends shipment requests, and shipment updates come back on the normal pull.

Carton labels can now be generated on a fulfillment already closed by its source integration. The label itself had always been made — the failure was in a step running after it, which records when labels were generated and refused any closed fulfillment. So a packer saw an error, and the label sat on the fulfillment rather than being handed back. On an auto-fulfill channel every fulfillment is closed by the time a packer reaches the containers screen, so the button did not work there at all.

Labels now print through and stay on the fulfillment to reprint from the containers screen.

Adding a product to a draft sales order now fills in a starting price for you. The price is the applicable sales-channel tier for the item and the quantity you are adding, and falls back to the product’s MSRP when no channel tier applies. The line stays fully editable — changing the quantity or the sales channel afterward leaves the price you have set. Products with no configured price come in blank instead of at zero, and a real zero price is still respected.

The orders list search is faster and steadier. Filtering by an order number, a customer name or email, a SKU, a shipping name, a tracking number, a tag, or a sales channel returns in about a second on any catalog size, and the list stays responsive around it — a slow search no longer drags the rest of the app.

Before, on the largest catalogs, a keyword search worked through the whole order set and could take up to a minute and a half. Every order update refetched the list, so searches were stacking up in the background as orders arrived, and the slowdown reached beyond the list to the rest of the API — on 2026-08-20 that came out as a period of site-wide timeouts. The search now works through each part of what you type — order number, customer, item, tracking, channel — on its own path, and three of those paths (customer name on the shipment, product name, sales channel name) which used to have no fast lookup now have one.

The last-90-days order figure, and the days of supply it feeds, were counting canceled orders. The check meant to leave canceled orders out was looking for a state value the records no longer use, so it matched nothing and let every canceled order through — around 3,240 canceled orders in the last 90 days. Those figures now exclude canceled orders, so recent-order totals and days of supply reflect only orders that still stand.

You can now permanently delete an order, one at a time or in bulk. Delete Order sits in an order’s Actions menu, and Delete Orders is in the bulk menu on the orders list. Deleting asks you to type the order number to confirm, or “DELETE N ORDERS” for a selected set, and a bulk delete runs in the background with progress you can follow.

Deletion is permanent and cannot be undone. It removes the order and its related fulfillment and inventory records from Endless. The source the order came from is untouched, so an order can import again later unless you stop it at the source. This is available on the newer sales orders.

A fulfillment sent to the wrong warehouse can now be pulled back from the order screen. Revert to Allocated has always been there for a ready fulfillment; it now also appears on a fulfillment that is already out, and asks the system holding it to cancel first before releasing the fulfillment inside Endless.

When the warehouse or system on the other end cannot accept a cancellation, the action turns into a question rather than a refusal. Confirming drops the link — the fulfillment stops counting as sent and can be routed again, edited, sent from a different building, or shipped later — and if the outside system was in fact carrying a copy, any later reconciliation reaches you through company notifications. Endless is the record either way.

The cancel dialog now tells the truth about what the outside system can do. It used to say “the external system will be notified” whatever was on the other end, which was false for the four integrations that never accept a cancellation. It now reads whether cancellation is available and says one of three true things: nobody outside holds a copy, they will be told, or they cannot be told and the link will be dropped.

Some fulfillments had already accumulated in a stuck state because those four integrations declared cancellation as available without wiring the action, so a background failure never reached the user. Those integrations now read as “cannot cancel” up front, and this flow is the way through them.

A shared fulfillment page now has a Download PDF button. The download carries the same items, destination, supplier costs, carrier and service, and notes as the page on screen, paged over as many sheets as it takes to fit. A recipient forwarding the fulfillment to a supplier, a warehouse, or a filing system can save or print a copy without keeping the web page open.

The header and footer of a shared page — and the exported PDF — now carry the name of the company that sent the link, so a recipient sees who it came from. The password prompt on a protected link used to read “link not available,” which was misleading; it now says the link needs a password.

A fulfillment email entry on the order timeline and the fulfillment timeline now opens with a More details disclosure. Expand it to see who the message was addressed to, who was copied, and a clickable copy of the exact share link the recipient received.

The two timelines used to render fulfillment email entries differently — the order timeline had a details row, the fulfillment timeline did not — so which fields you saw depended on where you opened the entry. The fulfillment timeline now carries the same details, and both timelines render the disclosure the same way.