Changelog

Two changes this week on how Endless talks to your accounting integration.

Connecting QuickBooks Online no longer asks you for an app API key and secret. Every Endless customer uses the same Endless-side QuickBooks connector app, so those credentials are managed for you now. The connect flow just walks you through picking the QuickBooks account you want to link.

You can pick which accounting customer a sales channel bills to. Sales Channel Settings and the Data Mapping tab render the same picker against the same mapping, so a change made in one place shows up in the other. For an accounting integration the picker chooses by name and stores that name alongside the reference, so a rename in QuickBooks does not leave a stale label in front of the right customer. Every order financial on the channel inherits that customer by default, and you can override it on a single document from its Accounting tab; the field is labelled to distinguish an inherited value from an overridden one, and Cancel reverts, Save commits, like every other field on the card. A sent document’s customer can be changed and pushed to QuickBooks — the update path used to copy the remote value and skip the write, so an edit was a silent no-op. Consolidated receipts group by customer as well as by channel and date, so a channel with overridden documents produces more than one receipt per cadence where it produced one before. When a channel has no accounting route, or more than one, the override field is hidden with a short explanation instead of listing customers from an arbitrary integration.

An order can now hold fulfillment lines that don’t line up with a current order item. When an integration records a replacement — one sales-order line but two real fulfillment orders and two shipments — the historical shipment stays visible under the fulfillment it actually shipped from, and the current line still shows the current demand covered by the current shipment. Before this, retaining that historical line would have made the order look over-fulfilled, so it was dropped from history.

On the order detail, a fulfillment line without a linked order item now shows its inventory product — SKU, name, image — instead of a blank row, and is labelled so you can tell it stands on its own. Coverage rules for lines that do link back to an order item are unchanged, and outbound integration planning skips standalone-only work cleanly.

Celigo is a first-class integration now, listed on the integrations screen and available as a filter on the integrations list. Behavior that had been sitting inside a generic custom sales integration for Celigo has moved into the Celigo integration itself, and a task migrates any existing Celigo setups over so nothing needs to be reconnected.

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.

Setting up a Packiyo integration no longer asks for a 3PL Customer ID. The warehouse picker lists every warehouse on the connected Packiyo tenant, and you map a building to the one you want. Any value still stored on an existing integration is ignored.

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.

The Get shipment action, used to re-record a shipment from the warehouse when the periodic poll missed one, used to record the shipment with no line items and mark the fulfillment fulfilled outright. That left a repaired shipment indistinguishable at a glance from one the poll recorded properly — the record read as complete on the fulfillment, but what actually shipped could not be seen on it.

The action now records the same shipment shape as the poll, with the line items on the shipment, and lets the fulfillment’s state follow from what was covered. A partial shipment repaired by hand leaves the fulfillment in progress instead of forcing it to fulfilled, so a partial repair reads correctly on the order.

Applies to newer sales orders. Older sales orders are unchanged.

Work is underway to let Endless connect with AI assistants like Claude and ChatGPT. The connecting, sign-in, and permissioning pieces are in place, and answers to a range of everyday order and account questions are being wired up. It is not open for general use yet — the pieces are still coming together internally, and access will open when we are ready to say more.