Changelog

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.

The tariffs tool is now on HTS 2026 Revision 21, so classifications and duty rates match the latest release the ITC published.

The Updates feed has three new items: the September 21 BIS guidance on Section 232 pharmaceuticals, the Federal Register notice that defines the categories exempt from the pharmaceutical tariff, and the October 6 launch of CBP’s CAPE Phase 3. The simulator’s note about programs it cannot resolve on its own now states the real reason: the schedule does not carry patent status, onshoring commitments, or drone specifications.

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.

The supplier page now has an overview with a primary contact, a ship-from address, a remit-to address, and company details. A Contacts and locations tab keeps saved locations. A Products tab lists the supplier’s costs by SKU, where you can add, edit, bulk edit, and remove costs and edit the supplier SKU. Dropship cost tiers always have a minimum order quantity of 1.

Default addresses now point to the saved location they came from. Editing a location updates every default that uses it, and editing a default edits its location. Archiving a location keeps the address on the default and removes the link. Locations tables show a Default for column, and addresses are edited through locations. Editing a contact no longer removes the primary contact unless you change it.

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.

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.

The Supply Chain tab on a product now handles supplier associations end to end. Link an existing supplier or create a new one from the tab; already-linked suppliers cannot be selected again, and each attempt reports success or failure inline. Saving a purchase order also links its products to its supplier automatically, so a supplier that appears on a PO is a supplier on the product without a second step.

Each supplier card shows Part Number, Default MOQ, Purchase Orders, and Cost Estimates in a responsive grid. The Purchase Orders count includes every matching PO for that supplier and product, independent of what the table shows, and refreshes when a PO changes. Cost Estimates opens the existing estimate workflow filtered to that supplier, with adding, editing, duplicating, and deleting; a new estimate opened from here keeps the supplier automatically. Part Number and Default MOQ have their own cards on larger screens; clicking either opens a dialog that edits or clears just that value and leaves the rest of the relationship intact.

Edit supplier, Contact supplier, and Create PO are grouped under an Actions menu on each card. Default Lead Time stays on the supplier profile and appears in the summary alongside incoterms and quality rating.

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.