Create Shipment replaces Mark Fulfilled on a fulfillment. Select the items and quantities that shipped, then enter the shipping date, tracking number, and carrier service. Partial shipments leave the remaining items open for another shipment.
Freight shipments can include a bill of lading and a reference number alongside the tracking or PRO number. Add Cost And Packaging reveals optional shipping costs, packaging, weight, and dimensions. A canceled shipment does not reduce the quantities available for the next shipment.
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.
Order signals are grouped into Issues, To do, and Information. The Signals page opens on Issues. On an order, signals appear in a dedicated Signals tab instead of banners above the details. Its badge counts active signals and highlights when any need attention.
Issues include differing fulfillment plans, excess shipped quantities, and fulfillments blocked by requirements such as a shipping address or carrier service. Held orders remain available through the on-hold filter. To do covers work such as creating missing fulfillment plans. Information covers partial allocations, inventory shortages, and shipments in transit.
The separate Awaiting shipment creation signal is removed. Saved filters discard retired signal selections. Actions remain beside the signals they apply to.
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.
Company and brand operators can now rebuild an order’s signals from the Actions menu on the order page and its quickview, including fulfilled orders. The action stays disabled while the rebuild runs, reports the result, and refreshes the displayed signals when it finishes.
Until now the action was hidden in the app even though the permission existed, so a stale signal on a single order needed a bulk rebuild from the list. The bulk action from the list is unchanged.
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.