Changelog

The fulfillment order list has two new filters that reach through to the parent sales order: Sales Order Created Date, with the same range presets as the sales order date filter, and Sales Order Tags, which multi-selects across the tags on the parent order. Both compose with the existing fulfillment order filters, so you can, for example, look at fulfillments for last week’s VIP-tagged orders in one view.

The bulk actions on the Orders list now respect V1 and V2 order versions. Select V2 orders and the toolbar offers Create Fulfillments, Approve, Reload From Source, and Resend Shipment Updates. Select V1 orders and the toolbar offers the full V1 action set. A mixed selection shows both menus side by side, each labeled with how many of the selected rows it applies to, so a V1-only action never fires on V2 rows and vice versa.

Reload From Source and Resend Shipment Updates now open a confirmation dialog before running — the Resend dialog names its scope, so you know the resend covers every shipment on the order. Reload From Source is also hidden when the source integration does not support reload, so it will not appear next to orders it cannot help. Selection now clears when you change page or page size, since the same rows are rarely still on screen.

Product attributes can now be archived and restored, the same way products, suppliers, and images already can. Archived attributes drop out of the default attributes list; a filter at the top of the list includes them alongside active ones or shows them on their own, each carrying an Archived badge. Opening an archived attribute lands on a read-only detail view with a Restore action and an Archived banner at the top. On a product, an archived attribute keeps its tag with an archived treatment, and the edit toggle switches to a View details link that opens the same read-only view.

Creating a new attribute with the same name or handle as an archived one now says exactly that — an archived attribute already uses this name, restore it instead — so an operator does not silently mint a duplicate. The archive confirm dialog also reads correctly in both directions now: it was only offering Archive, and now offers Restore when the attribute is archived.

The company-wide feed of human-written notes on entities is now called Updates. In the system sidebar it reads Updates rather than Activity, and its page has moved from /system/activity to /system/updates. Bookmarks pointed at the old URL will not resolve.

Activity is now reserved for system-generated logs — the ones on entity detail pages and the Recent activity card on the dashboard — so the two feeds are named for what they are. Same notes, same replies, same feed.

New fulfillment order numbers can now follow one of three formats. The default keeps today’s shape: the order number followed by -FO- and six random hex characters, like SO12345-FO-4414A3 (a small change from the five hex characters used before). The two other options are SO12345-FO1, an order number plus a per-order sequence, and FO-4222A3, a plain code with no order prefix.

Pick a format under Settings → Creating Fulfillments → Fulfillment Order Numbers, and it saves the moment you select it. The choice applies to fulfillments created from then on; existing fulfillment numbers are never rewritten. Downstream systems that treat the fulfillment number as an opaque identifier keep working across the change.

When product photos are hosted on Shopify, the product sheet, table, and grid now ask for the thumbnail size the cell actually renders at, instead of the full-resolution original. On a catalog of print-resolution photos, page one dropped from about 13 MB of image transfer to about 270 KB, and the browser is decoding roughly one percent of the pixels it used to.

Photos hosted on our own storage or on Cloudinary are unchanged; those fall through to the original as before, and the separate variant work covers them.

A Recent activity section at the bottom of the dashboard lists what’s happened across the company — order changes, product edits, inventory movements, integration events — with each entry linking to the record it came from. The list scrolls back through older history instead of stopping at a fixed count.

The Activity card on individual orders and products keeps the same behavior, and now scrolls into older entries the same way.

Ship orders sent from Endless to Business Central now expand bundled SKUs into their component SKUs, the same way accounting exports already handled bundles. A bundle no longer arrives as a single parent line the receiving Business Central job did not know what to do with.

Anyone who has tried to answer a simple question like “How many units of this SKU did we sell each week?” knows how much work can sit behind an ordinary chart. First you export orders and line items, then clean them up, join them together, categorize them, and aggregate the result. By the time the data is useful, most of the work has already happened.

ECHO does that preparation inside Endless. It organizes detailed order history into consistent daily records, then uses them to show what was ordered and what shipped over time. Filter by date, SKU, sales channel, or source; compare periods; review channel mix and top products; or open the underlying records to see exactly where the numbers came from.

You can also bring your old history with you. Export the messy detail from the systems you used before Endless, prepare it in ECHO’s simple import format, and upload it. Endless adds new history automatically from that point forward, giving you one continuous view across the systems your business has used.

The prepared data remains visible and usable. Imported records can be maintained separately, adjustments can be added without changing the original orders and shipments, and any filtered view can be exported again. Use the dashboards in Endless for quick answers, or take the same prepared history into a spreadsheet, business intelligence tool, or AI tool for everything else.

Jazz OMS is now a connected fulfillment channel. Endless sends orders to Jazz for shipping, reads ship confirmations back on its own, and syncs inventory in both directions. A webhook installs on connect so ship notifications arrive as they happen.