Tracking that works before there's a courier

Highlight

Tracking that works before there's a courier. The tracking link is the first thing a customer looks for after they order. Until this week, following one before the order dispatched got them an error page, the link was live, but there was no delivery behind it yet, so there was nothing to show. Now the same URL covers the whole journey, starting the moment you take the order.

• One URL, two phases. While the order waits for a provider, Nash serves an order-received screen with your branding. As soon as the delivery is created, the same link becomes the live-tracking view, nothing to swap out in your confirmation emails, texts, or order pages.
• Say what you want in the gap. Add up to 280 characters of your own copy to that screen, what happens next, when to expect an update, who to contact. Leave it blank and customers see the standard order-received message.
• Check both states before you publish. Tracking customization has a before-dispatch / delivery switcher, so you can see each phase exactly as a customer will.

Turn it on in Customization → Tracking. It's off until you do, and links behave exactly as they do today until then. See Tracking before dispatch.

New & improved

Nash Agent

• Give an agent's notifications their own title. It becomes the email subject and the opening line in Slack and text, and takes the same {{variable}} placeholders as the body, so Late deliveries, {{status}} reads usefully in an inbox without anyone opening it. See Notifications.
• Turn a single action off for one agent. Alongside auto and confirm-first, an action can now be disabled outright, the agent can't take it and there's no card to approve. See Guardrails.
• Keep an interval schedule inside working hours. An agent that runs every hour can be bounded to a start and end hour instead of running around the clock. See Set up a schedule.
• Put an agent in your own product. A custom agent's new Embed tab generates a snippet that drops a chat widget into your web app, a tracking page, an order-status page, so customers can ask about their delivery without contacting anyone. Embedded conversations are read-only no matter how the agent is configured, and each one starts from a token your own backend mints. See Embedded chat.
• Agent answers that are really reports now render as report blocks, headline figures, tables, and charts laid out as cards rather than a wall of text.
• A chat session shows which agent produced it, so a session you come back to a week later identifies itself.

Platform API

• Webhook consumers can stop retries for one message or disable an endpoint directly from their webhook response. See Webhooks for the response header and behavior.
• Public tracking URLs accept an order ID, not just a job or package ID, the addressing behind tracking before dispatch.
• A product can carry different images per provider. Set imageUrls inside a product's providerConfigs entry and a provider that shows your catalog to shoppers uses the image you picked for it. See Create or update products.

Portal

• Choose which metadata fields show on a delivery's page. An admin picks the keys worth surfacing and labels them, and they render as chips at the top of the job, the same control routes already had. Fields holding JSON are unwrapped and readable rather than printed as an escaped string.
• The Automations screen shows the default dispatch and optimization strategy on the main view, so you can see what an unmatched order falls back to without opening a rule.
• Merchant refunds can be filtered by date range and by provider.
• Delivery and order pages lead with your own references rather than Nash's internal ID tags.

Fleet

• Route and order drawers on the Execute page show a real activity timeline, what happened, when, and who did it.
• The Execute routes table has a wider filter set, and custom events you emit now appear in the route Activities view. The Exceptions filter group starts collapsed so the panel opens on the filters most dispatchers reach for first.
• In the driver app, stop details show the delivery window; pull-to-refresh works on the stop list, stop details, and items list; and a driver correcting a crate count is no longer forced to pick a reason.
• Drivers can adjust item quantities while offline, the changes queue per stop and sync when the device is back on a signal.

Integrations

• Australia Post consignments record every scan on the delivery timeline instead of only the most recent one, so the tracking history matches what the carrier actually reported. Weights are sent at gram precision.
• Autolane receives the customer's name and email on quote and delivery-create calls.

Fixes

Nash Agent

• A scheduled agent runs at the local time you picked. A 5am schedule in your time zone fires at 5am local, holds through daylight-saving changes, and catches up safely after an interruption rather than being skipped.
• A dropped connection to a tool server no longer ends a chat run mid-answer.
• Chatting with a custom agent holds its execution mode and session for the whole conversation, and an agent whose time zone was never set says so instead of showing a blank.

Orchestration

• Updating an order with an explicit dispatch strategy honors that strategy, and swapping it re-quotes against the new one instead of keeping the earlier quotes.
• Recipients on a multi-stop route get the notification for their own delivery, once, not a neighbor's, and not twice.
• Toast store prep times are read as minutes, so pickup times are no longer set days out.
• GoShare deliveries hold their status instead of flipping back to a pre-pickup state when a poll and a webhook disagree.

Fleet

• A failed or missing dropoff leaves the remaining item quantities alone instead of resetting them.
• A completed pickup stays completed when a sibling delivery on the same route fails and starts a return.
• Signatures a driver captures at a stop reach the delivery record as proof.
• Australia Post consignments no longer log a second "manifested" entry when the carrier echoes a location-only update, and pickups are booked against the local despatch date.

Portal

• Clearing a time window saves as cleared instead of silently keeping the old value.
• Selecting a tracking status while configuring a notification trigger no longer freezes the page.
• Switching organizations mid-load lands in the organization you picked.
• Links between deliveries carry the right delivery's context, so following one from a job opens that job and not the one you came from.
• Routes fall back to the customer's name when a delivery has no business name, and a drawer's close button no longer sits on top of the Dispatch action.