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.

Use the Send Webhook action to notify another tool when an order is created, a fulfillment is created, or a fulfillment becomes ready.

Set the destination in the automation and review recent deliveries there. Failed deliveries are retried; repeated failures pause delivery until you save the rule again.

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.

Mirakl is now an integration. It pulls orders, accepts them, reports shipments with tracking numbers, and pushes inventory. The integration was built for Best Buy US and Best Buy Canada.

Orders import when they reach the Shipping status. Mirakl does not list warehouses, so you enter them by hand on the integration. Cancellations, refunds, and returns are not handled yet. Orders from Mirakl show a Mirakl origin badge.

Send shipments now follows the same rules as the automatic send. Each integration decides whether to create a shipment, update its tracking, or skip it. Clicking it again retries shipments that failed and updates changed tracking where the integration supports that. It does not submit a shipment the integration already accepted.

Faire now waits until every item on the order has shipped, then receives all packages in one request.

Actions that send data to another system or fetch data from it now sit at the bottom of each menu under an Integrations label, with the integration’s logo. Each one opens a dialog that names the integration and explains what will happen. Workflow actions such as Send for fulfillment keep their place at the top. Purchase orders have one Send purchase order action, and you choose the destination in its dialog.

Operations Integration is now an option under Custom Integrations. Choose it to let your own tools read products, submit orders and purchasing records, adjust stock, report shipments and tracking, and request exports. API credentials are created for you and use the existing credentials panel.

The integration cannot create, edit, or delete products. It cannot change allocation, routing, templates, or fulfillment workflow controls, and it cannot change company setup, integration settings, or user access. Existing integrations and roles keep their current permissions.

When a warehouse integration reports that it canceled an order, Endless now moves the fulfillment to Failed to fulfill and raises a needs-action signal. The inventory allocation and the warehouse’s external reference are kept, and the cancellation details appear on the timeline. Shipments already recorded stay in place, and a fulfillment that was already complete is flagged for reconciliation. A repeated report does not create another failure.

This covers Extensiv, ShipStation, ShipHero, ShipBob, Packiyo, Trackstar, Jazz, MasonHub, Infoplus, Shipfusion, and Mintsoft. After reviewing the warehouse status, you can move the failed fulfillment back to Allocated or Ready. Returning to Allocated respects order holds. Automatic sending stays blocked while the external reference is present, so clear it before you resend. GoBolt, VeraCore, and the custom Business Central connector do not report cancellations yet.

Walmart sometimes splits one customer order into several purchase orders that share the same customer order ID. Endless used that ID as the order number and refused any order whose number already existed on the sales channel, so the second and later purchase orders never imported and never shipped.

Purchase orders from the same customer order now import as separate sales orders. A manually created order still cannot reuse an existing order number.

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.