Changelog

EDI 850 orders coming in through the Orderful path could fail to import on every order when the inbound template didn’t include a shipping carrier service. Order creation was rejecting the input outright, even though the carrier service is supposed to be set later at fulfillment, not on the inbound PO.

EDI 850 orders without an inbound carrier service now import as expected. Any carrier mapping the template does send is still picked up.

ASNs to Extensiv buildings were silently failing on items that don’t have lot tracking turned on in Extensiv. Endless was attaching a lot number to every receiver line, and Extensiv was rejecting the whole receiver when the item wasn’t lot-tracked, so the ASN never landed.

There’s now a “Send lot number” setting on the Extensiv integration, off by default. Turn it on for accounts where every item is lot-tracked; leave it off otherwise and ASNs go through without a lot number attached. Integrations already configured to send a reference number as the lot number are unaffected — that setting still wins.

If you run multiple ShipStation stores behind a single ShipStation connection, you can now route orders to the right store based on the sales channel they came in from. Map each sales channel to its ShipStation store id on the ShipStation integration, and orders from that channel will ship out of that store. Channels without a mapping continue to use the integration’s default store, so nothing changes until you start filling the mappings in.

A single building can now serve more than one fulfillment integration. Instead of every fulfillment from a warehouse defaulting to that warehouse’s one integration, each fulfillment can carry its own — and playbooks can pick the right one automatically based on the rules you set up (order source, brand, customer type, anything a playbook condition can read).

In practice: one building can route some fulfillments to ShipHero, others to Extensiv, others to a 3PL — all from the same physical location, all automated. The Send / Resend button on the fulfillment card now shows the actual integration the fulfillment is going to, and downstream work — cancel, schedule, retry — follows the same routing the playbook chose, end to end.

The Sales Channels panel on an integration’s Data tab has been rebuilt. The mapping table now shows External ID → Internal Sales Channel side by side, with Add, Edit, and Delete buttons on each row. Adding a mapping opens a dialog where you pick the internal channel from a dropdown. Editing a mapping lets you change the external ID; to point an external ID at a different internal channel, delete the row and add it back. Shopify, Orderful, and Veracore are on the new editor today.

An external ID can now map to at most one live internal channel per integration. If automatic discovery tries to write a mapping that would collide with one you already have, it stops and tells you instead of adding a duplicate.

Auto-discovery writes and the Infoplus ship-order step are reading and writing through the new system as well. Trackstar is still on the older one for now and will follow.

The Add Alias button for shipping carriers is no longer Shopify-only. Custom carrier mappings can now be added on every integration except QBO — including EDI (Orderful), Amazon, Walmart, Rithum, Business Central, Cin7, Sellbrite, Skubana, Extensiv, Gobolt, Trackstar, MasonHub, Infoplus, ShipHero, ShipStation, Veracore, and Faire.

DSCO orders now ship out with each brand’s own carrier service names. Up until now, every brand on a DSCO connection shared the same integration-wide carrier mapping — even when a brand had its own mapping set up. Brand-level mappings now take priority, with the integration-wide mapping kicking in only when a brand doesn’t have its own.

Shipments from ShipHero now flow back into Endless automatically in real time, with a daily backfill catching anything missed. Endless also records the carrier service name on each shipment, so labels like “UPS Ground” appear on the order without manual entry.

This is a continuation of the ShipHero integration first announced in May.

Rithum (formerly DSCO) is now available as a sales integration in Endless Commerce. Orders sent through the Rithum network arrive in Endless and can be fulfilled through the same workflows used for every other sales channel, with shipment information flowing back to Rithum on dispatch.

For businesses already selling through Rithum-connected retailers, this hooks that volume directly into the same inventory, order, and fulfillment tooling used for every other channel.

ShipHero is now available as a fulfillment integration in Endless Commerce. Inventory and fulfillment data can flow between Endless and ShipHero alongside other 3PL connections like Extensiv and ShipStation.