Changelog

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.

Add a Wait action to pause an automation for one minute to twenty-four hours. Optionally schedule it within selected weekdays and hours. Conditions on the next action are checked when it runs, so it can respond to changes made during the wait. Actual execution may be later than the scheduled time.

Orders show waiting automations, their remaining steps, and scheduled times in your local time zone. Create Fulfillments also waits for order approval; canceled orders and waits lasting thirty days are skipped.

Excel changes some values when it opens a CSV file: it drops leading zeros, turns long numbers into scientific notation, and treats values that start with +, =, @, or - as formulas. Exports now put a leading apostrophe on those values so Excel shows them as written. Imports remove one leading apostrophe and accept it in SKU, UPC, GTIN, HTS, PO number, warehouse, location, shipment, and tracking number columns.

Imports reject a number already in scientific notation, such as 6.00106E+13, and read two-digit years in dates, so 8/3/26 becomes 2026. Anything other than a spreadsheet that reads an export will now see the apostrophe.

Change your password from Profile Settings → Security. Password forms show the requirements as you type, including a minimum of twelve characters and a mix of letters, numbers, and special characters.

Passwords expire after a year. Ten consecutive failed sign-ins lock an account until its password is reset, including access through magic links. The sign-in screen explains when a reset is needed; existing sessions stay signed in.

Endless works out what needs attention on every order and writes it as a sentence with the numbers already in it: “3 units have no fulfillment plan,” “3 units have no inventory at any building,” “sent to Windsor, no shipment created.” You no longer have to know what to look for, or build a filter to find it.

Each signal sits in one of three groups that say what you can do about it. Needs action means you can fix it now. Blocked means something has to change first. Waiting means someone else is already working on it and the order needs nothing from you. Knowing an order is accounted for saves as much time as knowing one is broken.

Signals keep themselves current. One appears within seconds of the change that caused it and clears when it stops being true, so nothing remains on an order after it has been handled. The most urgent sit at the top.

The order list has a Signals column, and the Signals page opens on Needs action with shortcuts for Blocked, Waiting, and All. On an order, its needs-action signals sit at the top of the page, each with the action that resolves it.

Automations gain a Process Fulfillment action. Add it to the fulfillment-created trigger and choose what should happen to each new fulfillment: allocate it, mark it ready, or hand it off to the warehouse.

It is a simpler alternative to a fulfillment processing rule rather than a replacement for one. Reach for the action when the same few steps should run on every new fulfillment; keep processing rules for the more involved workflows they are built for. Both take the same steps in the same order, so choosing one over the other does not change what happens to the fulfillment.

A fulfillment that already has a processing rule attached is left to the rule, so the two never both try to move it. When a step fails the completed ones are kept — a fulfillment with no integration lands ready with its inventory reserved and the failed handoff is logged, rather than the allocation rolling back.

The separate product-label and carton-label trays are now one Create Labels tool. Rows can come from selected products on the products list, an uploaded CSV or Excel file, pasted rows, or order lines, and every column on the source can print on the label. A row is matched to a product by SKU or UPC, and an uploaded file is read in the browser rather than stored — the list is a lookup, not data to keep.

The tool adds Code 128 barcodes from any field, multi-across roll stocks with sheet gutters, printing order and rotation options, and retailer identifiers as printable fields, so a label can carry a retailer-specific SKU or UPC alongside the Endless one. Company-wide saved recipes let a label configuration be reused across the team, and can be created, updated, and archived.

Generating carton labels for a fulfillment downloaded the PDF to the browser and nowhere else, so the compliance artifact lived on whichever laptop the packer used rather than on the order.

The generated PDF is now filed in the order’s Documents section alongside the rest of the order’s files. The file name comes from the fulfillment number, so regenerating labels replaces the existing document instead of stacking copies. Filing happens in the background, so the confirmation says the labels downloaded and the document is on its way — give it a moment before looking for it under Documents.

The embedded tariffs tool is up to HTS 2026 Revision 17, so classifications and duty rates match the latest release the ITC published. Three August news items missed on the primary Federal Register and USTR sweep are added to the tool’s Updates feed after being verified against official sources.

Documents attached to a record used to be a list of filenames — usually whatever the supplier’s system produced — so a Bill sat next to a Packing List with no way to tell them apart at a glance and no way to narrow the list.

Every attachment now takes an optional short tag. Set it once from the row’s edit icon and pick from the tags already used on that record type across the company: the fourth PO you open offers Invoice, Packing List, BOL, and Specs on its first upload. Type to search, hit Create when nothing matches, or clear the tag with Remove. Every click saves and closes.

A filter above the list scopes the visible documents to one tag, with Untagged shown when the record has both tagged and untagged files. The tag itself renders as a badge next to the filename so the list reads as a set of categories rather than a stack of file names.

Tags are per-record, plain text, and capped at 50 characters. Orders, products, purchase orders, supply shipments, and suppliers all get it in the same shape. A read-only record — an archived PO, a non-editable product — shows the badge without the edit control.