Changelog

Connect external locations to Endless buildings from one mapping dialog. Find locations where supported or enter them manually. The integration’s Connected Buildings table shows each connection’s location, fulfillment processing, and inventory push settings.

Faire, Sellbrite, and Orderful now share inventory only from connected buildings enabled for inventory push. Faire and Orderful combine eligible stock; Sellbrite uses each connection’s location ID. Faire applies its buffer and maximum to the combined quantity.

Disabling inventory push or removing a connection leaves previously published stock in the other system. A confirmation explains this before you proceed.

ShipBob receiving hubs now appear when you connect or map a building. Each option identifies whether it is a location, a receiving destination, or both.

Before sending a supply shipment, choose how it arrives, whether boxes contain one SKU or several, and whether to include lot numbers. Review packing shows the proposed carton or pallet contents and packing assumptions before you accept. Matching product pack quantities are used for single-SKU packing. Products not registered in ShipBob are listed as omitted, and failed inventory checks or conflicting receiving orders block sending.

You can return to the shipment to adjust it before sending. ShipBob does not allow the receiving settings to change after the receiving order is created. Bulk sends use each shipment’s defaults.

Rithum inventory updates now use the SKU mapped for the integration and run hourly. If a product has no mapping, Endless uses its own SKU. Conflicting mappings for one destination stop the update with an error.

Quantities include only active buildings configured as inventory destinations for that connection. Each building counts once; allocations, demand, and bundle availability still apply. If no destination has a Rithum warehouse code, Endless skips the update.

Failed or partly accepted batches are retried. Updates remain unconfirmed until Rithum reports that it has processed them.

A supply shipment now has separate Delivery and Received dates, plus a Payment Due date. Delivery is when the shipment reaches the building. Received is when it is received into inventory. The new Dates card on the shipment shows Shipment, Delivery, Received, and Payment Due, with an Expected and Actual toggle and a net-terms calculator.

Moving a shipment to In Transit, Delivered, or Received opens a date picker, and the date you choose is recorded. The shipments list has sortable Received and Payment Due columns, and the arrival columns and filter are now labeled Delivery. The row that was called Received Date in Key Information was the arrival date and is now Delivery.

Inventory now uses the Received date, and falls back to Delivery, for the date stock was received and for the landed cost date. CSV import and export include both new dates.

On a draft fulfillment, open an item’s menu and choose Assign location or Change location. Stock for that item is reserved only from the location you choose. If the location cannot cover the quantity, the fulfillment shows an error that names the location. Items without a chosen location allocate across the warehouse as before.

An assigned item shows “Only fulfill from” and its location under the quantity. Each component of a bundle can have its own location. Clear the assignment to let the item allocate across eligible locations again. The location must be active and pickable in the same building. To change a location on an allocated fulfillment, revert it to draft first.

ECHO has an Actions menu with a Delete ECHO data option. Use it to remove incorrect imported order history, shipment history, or inventory snapshots across every page of a filtered view, rather than one row at a time.

The dialog starts with the filters of the view you came from, and you can change them before deleting. It shows how many manual and adjustment records match and asks you to type a confirmation such as DELETE 24 RECORDS. Records ECHO created automatically are never deleted. Table bulk selection is replaced by this dialog. Editing a quantity and deleting a single row work as before.

A combined inventory export now includes every item that matches your filters instead of stopping at a row limit. Exports split by warehouse or location keep their existing filters and row limit.

A combined export cannot use a location filter. The export dialog disables Combined while a location filter is active, explains how to turn it on, and switches to Split by location when the current choice would be invalid. Your filters are kept. If the request fails, the dialog stays open and shows the error.

A sales order that is Pending, Ordered, or In Progress can now be reverted to Draft from the Actions menu or the command palette. Use it to keep a future order on record without reducing current inventory availability.

Cancel every fulfillment order first. Revert to Draft is blocked until each fulfillment is canceled, and the dialog explains why. The order keeps its details, history, and payment status, including payment already received. The reversion appears on the order timeline, and inventory and demand reporting refresh when you revert and when you confirm the order again.

Mintsoft shipments now bring item quantities, tracking, and dispatch dates into Endless automatically. Pickable inventory updates every fifteen minutes, with manual pulls available when needed.

You can also send inbound supply shipments to mapped Mintsoft warehouses using Send to WMS. Products must already exist in Mintsoft. Confirm the warehouse’s database time zone before the first shipment import.

ECHO now uses one date range across charts, tables, and exports. The overview brings together units ordered, units shipped, and inventory, with breakdowns by sales channel and warehouse. Sort records and filter by multiple SKUs to investigate the details.

Shipping reports use the actual ship date when known and the recording date otherwise. Missing inventory history appears as gaps. Inventory reporting remains in beta.