Changelog

Canceled Extensiv orders no longer mark fulfillments shipped. Extensiv reports a canceled order with a closed status and sometimes tracking data, and Endless used to treat that as a shipment, complete the fulfillment, and send shipping notifications. Shipment creation and updates now skip any Extensiv order whose status is canceled. Existing incorrect shipments are not reversed. Contact support if a past order needs correcting.

Orders sent to Extensiv now use Prepaid carrier billing by default. Third-party billing is sent only when it is enabled for the fulfillment and a billing account is present, with the account and billing ZIP code you supply. A missing ZIP code stays empty rather than using the recipient’s. Orders already sent are unchanged.

Sending a shipment from a DSCO fulfillment now sends that fulfillment’s shipping information. An operator can send it again even if it was previously sent; automatic sending still skips a fulfillment already sent.

The DSCO setting Send Tracking Number As SSCC places the tracking number in the SSCC barcode field for retailers that require it. It is off by default and can be enabled per integration. The timeline identifies the operator who sent the shipment.

On an EDI order that split into several fulfillments, each fulfillment’s 856 now lists only its own shipments and cartons. Before, it listed every fulfillment’s, so a retailer could receive tracking numbers that belonged to another ASN. Forward Shipment on a fulfillment card now previews and sends the same 856 the automatic send builds, and always sends when an operator starts it. Order-level documents and single-fulfillment orders are unchanged.

Each fulfillment card, and an accounting invoice scoped to one fulfillment, has a Send Invoice action that opens the EDI preview for an 810 scoped to that fulfillment. It applies to any Endless EDI connection whose invoice template is set up per fulfillment.

The EDI tab’s Variance view now shows the correct variance per column when the same SKU shipped on more than one fulfillment order. The ASN sent to the retailer did not change.

The integration settings no longer offer per-transaction ISA sender or receiver overrides or a Packing Strategy choice. Neither affected what Endless sent. The remaining settings have clearer labels and help text.

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.

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.

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.

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.

The integration timeline now records each Shopify inventory push: the number of updates Shopify accepted, and any items that were skipped because they are not stocked at their mapped Shopify locations. The details for each skipped item include its SKU, the mapped Shopify location, and the quantity that would have been sent.

Enable the affected items for stocking in Shopify and the next scheduled push will send their quantities. Successful updates and existing retries are unchanged.