Changelog

Searching for a product to add to a Purchase Order, a Supply Shipment, a bundle, an echo SKU, or from the command palette now returns results quickly on very large catalogs — pages that used to time out and show “No products found” on accounts with over a hundred thousand products come back in a fraction of a second. Name and SKU search return the same products as before, just fast enough to actually use.

Report Issue — the action for flagging an operational problem on an order, which tags the order, adds a note, and can alert your ops team in Slack — can now reship in the same step. Tick “Reship order?” in the Report Issue dialog and the button becomes “Report & Reship”: the report is filed, then a Duplicate Order dialog opens already filled in, with the new order number suggested as the original plus an -R suffix and a reship tag applied (for example, OPS - Reship - No Movement).

Duplicate Order also gains more control at every entry point, including reship: a sales channel selector — defaulting to the source order’s channel, so you can send a duplicate to a different channel and keep channel reporting clean — and an additional-tag field that adds a tag to the copy alongside the ones it carries over. Reporting an issue also works on every order now; it had been failing on some newer orders, and that’s fixed.

You can switch a fulfillment’s fulfillment integration directly from the fulfillment. A small edit modal lets you pick a different integration and save without dropping into the underlying order or rebuilding the fulfillment. Useful when an order lands with the wrong integration attached and needs to move without a full recreate.

The Fulfillment Orders list opens quickly now, even for companies with a huge number of fulfillments — on the largest accounts it went from tens of seconds to roughly a tenth of a second. Only the page you’re looking at is loaded, rather than the whole company’s fulfillments, and the rows appear as soon as they’re ready while the total count fills into the pagination bar a moment later. The header count is the real filtered total, blocker details load when you open a status instead of on every page load, and switching sort stays fast.

Creating a new fulfillment on a Shopify order no longer fails when the order has an archived fulfillment sitting behind it. The next per-order fulfillment index now looks across archived rows too, matching the database uniqueness rule, so the new fulfillment picks an unused index instead of colliding.

The fulfillment creation experience on a sales order is now one coherent workflow. A single Create Fulfillments menu offers three ways in — Choose Building, Use Strategy, or Add to existing — and item selection has moved into the creation dialog itself, defaulting to all unassigned items with per-line quantity editing, removal, and building-specific availability shown inline. The menu stays hidden while the order is still a draft.

Automations are surfaced before they run: creating a fulfillment, applying a routing strategy, or assigning a fulfillment rule now warns you about active automations that will fire as a result, so nothing runs behind your back.

The “Not in Catalog” status badge on an order item is now clickable and opens the Link Product action directly. Before, that action lived behind the item’s edit menu and then a three-dot menu, so most people never found it. Clicking the badge takes you straight there.

For EDI orders, the EDI document list, create, and deliver flows now have their own “EDI” tab on the order page, alongside Sales Order, Fulfillments, and Timeline. Same documents and actions as before, just easier to find. The tab appears only when the order is actually an EDI order — other orders don’t get it. The old hidden /edi URL, which nothing linked to, is gone.

A fulfillment stuck in Failed To Fulfill can now be cancelled. Cancelling first walks the fulfillment back to draft so allocation unwinds cleanly, instead of erroring on the state check and stranding the fulfillment.

“Fulfillment Profile” is now “Fulfillment Rule” throughout the app, and rules are no longer required to process a fulfillment. A draft fulfillment can be allocated manually or have a rule applied — either works, and nothing forces you to attach one to move forward.

The fulfillment settings screens got a pass too: language across routing strategies, rules, and profiles was tightened to match how the ops team actually talks about it, informed by interviews with people who live in these screens.