Changelog

Company and brand operators can now rebuild an order’s signals from the Actions menu on the order page and its quickview, including fulfilled orders. The action stays disabled while the rebuild runs, reports the result, and refreshes the displayed signals when it finishes.

Until now the action was hidden in the app even though the permission existed, so a stale signal on a single order needed a bulk rebuild from the list. The bulk action from the list is unchanged.

Shipments imported from ShipStation now show which items shipped and their quantities. Separate packages count only the units still outstanding, so repeated item reports do not double the shipped quantity.

If an item cannot be matched, Endless keeps the tracking and records the unmatched SKU in the order history. Existing shipments with missing items can gain them when ShipStation sends an update; historical records are not changed automatically.

Supply shipment CSV imports now accept Status and Actual Ship Date. Use them to record a shipment that has already progressed instead of starting it at Pending with today’s date. Both columns are optional and are included in the importable export.

Imported statuses must follow the same requirements as changes made in the app. A shipment that cannot advance reports an import error. Canceled is not an available import status.

Activity performed through an API client linked to an integration now shows the integration’s name on timelines. An unlinked client keeps its own name and an API client label.

Historical activity also displays the current integration name. The original API client identity remains available for auditing.

Orders sent to VeraCore now use the fulfillment number as their reference, and the warehouse chooses lots when it ships. Imported shipments include the items and quantities in each package, including later quantity corrections. Multiple packages are recorded separately, so a partial shipment does not complete the whole fulfillment.

When package contents cannot be matched, Endless preserves tracking and known quantities and records a warning. Before retrying an older failed send, confirm whether VeraCore already accepted an order under the sales order number. Reconcile or void that record first to avoid creating a duplicate.

Send purchase orders and inbound shipments to Business Central from Endless. Map the supplier to a Business Central vendor, then use Send on the purchase order. You can link an existing document instead of creating a duplicate.

Links on purchase orders, sales orders, and products make it easier to move between the two systems.

The second fulfillment-number format — order number with fulfillment index — now uses the distribution center number when the fulfillment order has one. An order routed to distribution center 842 numbers its fulfillment SO12345-DC-0842 rather than SO12345-FO1. A fulfillment order without a distribution center still uses the index, so a company that does not ship to distribution centers is unaffected.

When two fulfillment orders on one order share a distribution center — for example, when a strategy sources one distribution center across two buildings — the second appends its index (SO12345-DC-0842-2). This applies only to fulfillment orders created from now on, as the setting already states.

Endless follows fulfillment changes from Shopify while preserving local work and shipment history. Partial shipments send their tracking to Shopify as they are recorded, so customers can follow each package without waiting for the whole order to ship.

Store owners can connect through a secure invitation link without an Endless login. Existing connections can reconnect to update permissions.

Endless works out what needs attention on every order and writes it as a sentence with the numbers already in it: “3 units have no fulfillment plan,” “3 units have no inventory at any building,” “sent to Windsor, no shipment created.” You no longer have to know what to look for, or build a filter to find it.

Each signal sits in one of three groups that say what you can do about it. Needs action means you can fix it now. Blocked means something has to change first. Waiting means someone else is already working on it and the order needs nothing from you. Knowing an order is accounted for saves as much time as knowing one is broken.

Signals keep themselves current. One appears within seconds of the change that caused it and clears when it stops being true, so nothing remains on an order after it has been handled. The most urgent sit at the top.

The order list has a Signals column, and the Signals page opens on Needs action with shortcuts for Blocked, Waiting, and All. On an order, its needs-action signals sit at the top of the page, each with the action that resolves it.

Shopify supplies the initial fulfillment plan when an order is created in Endless. Later planning — splitting, moving between buildings, changing quantities, or cancelling — happens in Endless. Reload Order and later Shopify webhooks bring current sales quantities across, but they do not add, move, split, or remove operational fulfillments to match Shopify’s structure.

Removed lines stay on the order at their original quantity, so you can see what was purchased alongside the current quantity Shopify reports. Fulfillment work is reconciled to the current quantities: reservations are released for reductions, fulfillments emptied by a reduction are cancelled, and ready, in-progress, and completed work is preserved. A shipment that already went out is kept even when Shopify later reduces the sales line, and an Excess demand signal is raised so you can see why a fulfilled quantity now exceeds the order.

Seeing And Applying What Shopify Reports​

The saved source fulfillment plan and its change history are visible on the order regardless of whether it differs from Endless. Open the source plan viewer from the order to see the last complete plan Shopify reported and the meaningful changes since — location, grouping, active state, and quantity. Display-only differences and retried polls do not create timeline entries.

When Shopify’s fulfillment orders differ from Endless in warehouse, quantity, or grouping, an amber “Fulfillment orders differ” badge shows in the order source bar and a Fulfillment orders differ signal is raised on the order. Warehouse comparison falls back to your Shopify location mappings when the identity registry has no entry, so a fulfillment created at the same warehouse on both sides does not read as a difference.

Update Fulfillments is available from the order Actions menu and from a right-aligned button on the drift alert. Draft and allocated differences are replaced and their reservations released; ready, in-progress, and completed work must already match, or the operation is refused. New fulfillments land in draft without running fulfillment-created automations, so the arrangement can be reviewed before it moves.