Decide what happens to an order that arrives after you close

Highlight

Decide what happens to an order that arrives after you close. Every operation has a version of this problem. An order lands at 11pm for a store that opens at 8am, or a provider drops a delivery on a Sunday when nobody is there to catch it. Until now the answer was the same for everyone: dispatch it and sort it out later. This week you get to choose, and the choice for a brand-new order doesn't have to match the choice for a delivery that just lost its driver.

• Say when you're open, once. Set a default opening time, closing time, and pickup cutoff, then add overrides only for the days that differ. A shop that's open 9–5 with late Thursdays and closed Sundays needs one default and two exceptions, not seven rows to keep in sync.
• Two decisions, not one. Initial dispatch can allow an out-of-hours order through or reschedule it to the next open day. Reassignment gets a third option: prevent it, so a delivery that needs a new provider at 2am stops and waits for a person instead of quietly going out. Both default to allow, so nothing changes until you change it.
• Keep your on-time numbers honest. When an order reschedules to the next open day, you decide whether its on-time baseline moves with it or stays pinned to what you originally promised. Either answer is defensible; the point is that it's yours, and it's explicit.

Find it in Organization settings → Operations. See Dispatching outside your operating hours.

New & improved

Orchestration

• Run a workflow across the orders you've selected. Pick them on the Orders page, choose Run Workflow, and Nash starts one run per order with a result you can open individually. See Running a workflow by hand.
• A workflow that's switched off can still be run by hand. inactive now means "doesn't fire on its own" rather than "can't run at all", useful for testing a change before you turn it back on.

Platform API

• Orders can declare their units. Send weightUnit as lbs or lengthUnit as in and Nash converts to the kilograms and centimeters it stores, rather than rejecting the order or taking the number at face value. An unrecognized unit comes back as a clear error instead of a surprise. See Order validations.
• Strings containing quotes, backslashes, or JSON survive a REST request intact instead of arriving double-escaped.

Fleet

• Give a route a name a dispatcher recognizes. Rename it from the Execute page, including after it's dispatched, or name a route as you split stops into it, and that name leads on printed handoffs and in the Portal. See Naming a route.
• Filter Execute routes by the provider assigned to them, or by having no provider assigned yet.
• Route orders on the Execute page carry their package reference fields, so a dispatcher can match a physical parcel to a stop without opening it.

Nash Agent

• Ask about products and inventory in chat and the answer comes back as a browsable widget, a product carousel with images rather than a list of SKUs.
• Agents can embed proof-of-delivery photos in the files they produce, so a PDF an agent writes up carries the photo evidence inline. New agents have it on; existing agents keep their current setting, and it's a per-agent toggle in the agent's tool settings.

Portal

• Dates, times, durations, numbers, weights, and prices follow your organization's preferences across the Portal, so a kilogram org and a pound org each see their own units in the same table.
• Creating a child organization asks for its country up front, which is what routes its billing correctly from the start.
• Order and route activity, and webhook replay, are gated on permissions, so read-only roles can look without being able to re-fire anything.

Fixes

Orchestration

• A delivery whose reassignment fails raises the *Tasks Attempts Exhausted* notification trigger instead of going quiet, so the delivery that needs a person gets one.
• Australian PO Box addresses resolve to the right city rather than failing to parse.
• Shifts no longer offer optimization strategies that were deleted.
• A workflow's version history is listed in version order.

Fleet

• Routes report their travel metrics, distance and duration, including per-package driving metrics on batch dispatch.

Portal

• The Report Incident drawer opens instead of crashing the page.
• Date-range presets stay relative when you switch between saved views, so "last 7 days" still means last 7 days tomorrow. Picking one end of a range no longer briefly reads "Invalid Date".
• Automation conditions show your organization's currency rather than always a dollar sign.
• Map pin tooltips name the business at the stop, not the customer's account.
• Wix stores get their own onboarding steps.

Integrations

• Uber pick manifests accept items with no substitutes listed.
• Quotes from ANC and Team Global Express stay valid longer, so a quote picked later in a planning cycle is still good when you dispatch it.