> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.rendr.delivery/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.rendr.delivery/_mcp/server.

# Branded Tracking Experience Setup

Rendr provides your customers with a branded tracking page and a suite of automated notifications (SMS and email) that fire as an order moves through the delivery lifecycle. This page outlines what you can customise, what each customer touchpoint looks like, and how the workflow ties together end-to-end.

## Overview

Once an order is booked through Rendr, your customer is taken on a guided journey from confirmation through to delivery. Each stage has a corresponding communication and a live tracking experience.

## The Tracking Page

Rendr's tracking page is shared with your customers so they can receive real-time updates on their order throughout the journey. The page can be branded to match your store, with key information — including driver ETA, delivery requirements, and help call-to-actions — surfaced prominently.

### What You Can Customise

* **Logo and brand colours** – Match your storefront identity
* **Hero image / custom beacon** – A branded visual at the top of the tracking page

![Branded tracking page example showing customisable logo, image, and colour components](https://fdr-prod-docs-files-public.s3.us-east-1.amazonaws.com/rendr.docs.buildwithfern.com/64ca8ae32610124d60f48fca470997976e7467560dfc1297cf5abccabd6160fe/assets/delivery-dashboard/tracking-full-page.jpg?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIA6KXJSKKNFOCF7G4B%2F20260924%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260924T033840Z&X-Amz-Expires=604800&X-Amz-Signature=5c181f1750dd2bfcab65749aca02239d38cf3c9803d920b1c4a31f34d1f9b69e&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject)![Example custom tracking beacon icon](https://fdr-prod-docs-files-public.s3.us-east-1.amazonaws.com/rendr.docs.buildwithfern.com/526038aba78ea71f4d581ac5f593373b9bc2e7c34f3a4e7fa910f728c6a2edd7/assets/delivery-dashboard/tracking-beacon-icon.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIA6KXJSKKNFOCF7G4B%2F20260924%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260924T033840Z&X-Amz-Expires=604800&X-Amz-Signature=d824962e24f262b271747e2a40450870b3f376ce5ed3c03f28c9d90256652dbc&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject)

## Customer Communications

Customers receive automated SMS and email notifications at each key milestone. Conditional messaging can be applied based on order value, authority-to-leave (ATL) rules, or product type.

#### Booked

Sent when a delivery is booked through Rendr. Confirms the order is received and sets expectations for the next update. Conditional content (e.g. ID-on-delivery, no-ATL) appears here when triggered by order rules.

![Example Booked confirmation email and SMS, including conditional messaging](https://fdr-prod-docs-files-public.s3.us-east-1.amazonaws.com/rendr.docs.buildwithfern.com/8745eff4f3d0990e852d0927098e610834f47a014c40e3452905bd24fdc19d96/assets/delivery-dashboard/notification-booked.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIA6KXJSKKNFOCF7G4B%2F20260924%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260924T033840Z&X-Amz-Expires=604800&X-Amz-Signature=f5ed0587f012269738d612649d36ebb59c239213da09a8dd50702cf32861d7cf&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject)

#### Collected / Out for Delivery

Sent when the carrier collects the order. Includes a live ETA where the assigned carrier provides one.

![Example Collected / Out for Delivery SMS with conditional ETA line](https://fdr-prod-docs-files-public.s3.us-east-1.amazonaws.com/rendr.docs.buildwithfern.com/1b534243bfc1f18e663f9636d85058c10da35fb7beeaf0d027b756be8a2c60bf/assets/delivery-dashboard/notification-collected.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIA6KXJSKKNFOCF7G4B%2F20260924%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260924T033840Z&X-Amz-Expires=604800&X-Amz-Signature=4ef21d2c33070575ebaf43adc9fa58197d65864c5fc9f03c91fc68f9eefd055e&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject)

#### Delivered

Sent on successful delivery. Customers are prompted to review the experience via the tracking page — feedback is captured and shared back to you as the merchant.

![Example Delivered confirmation email and SMS thread](https://fdr-prod-docs-files-public.s3.us-east-1.amazonaws.com/rendr.docs.buildwithfern.com/2f9b2c703dae0ddf4fda68535e361ac5dc49d795f267ad84dc1b4f010defee3d/assets/delivery-dashboard/notification-delivered.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIA6KXJSKKNFOCF7G4B%2F20260924%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260924T033840Z&X-Amz-Expires=604800&X-Amz-Signature=465fb6ac26076e6c2064233fc7da69f14b41df4f0dfdef811731e394d7875dca&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject)![Delivery feedback modal shown to the customer on the tracking page](https://fdr-prod-docs-files-public.s3.us-east-1.amazonaws.com/rendr.docs.buildwithfern.com/7a1baed631fc0d8ca31d7f32ac81c2ca00798a4bddd96712e4e4e1db4c69cdaa/assets/delivery-dashboard/delivery-feedback-modal.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIA6KXJSKKNFOCF7G4B%2F20260924%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260924T033840Z&X-Amz-Expires=604800&X-Amz-Signature=9b3261d65215cb8f64920107001b50ad4b6aa61118a9fcf5ad622147d555a80c&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject)

## Conditional Messaging

Rendr supports conditional message variants so customers receive the right information for their order.

| Trigger                      | Example Messaging                                                      |
| ---------------------------- | ---------------------------------------------------------------------- |
| Order over a value threshold | Customer must be present to accept the delivery; no authority-to-leave |
| Age-restricted goods         | ID check required on delivery                                          |
| Carrier provides live ETA    | "Estimated Delivery Time" line included in the Collected SMS           |
| Authority-to-leave enabled   | "Your order will be left in a safe place" messaging                    |

## Updating Delivery Instructions

For supported carriers, customers can update their delivery instructions after an order has been booked.

The flow is intentionally lightweight and secure: customers don't update instructions directly on the tracking page. Instead, they request a secure link via email, then submit their changes through that link. This protects against unauthorised changes while the order is in transit.

#### Requesting a link

On the tracking page, the customer selects **Update Instructions**. This option is only shown when the assigned carrier supports mid-delivery instruction updates.

![Update Instructions option on the tracking page](https://fdr-prod-docs-files-public.s3.us-east-1.amazonaws.com/rendr.docs.buildwithfern.com/9b542c2d23c46a426c540a6bd24632f75cd23a464a341327a133374c08bb3e01/assets/delivery-dashboard/update-instructions-tracking-page.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIA6KXJSKKNFOCF7G4B%2F20260924%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260924T033840Z&X-Amz-Expires=604800&X-Amz-Signature=372915c7cfda0dfdb48ef76a6cef48ae79995bd5655cd3c736ffff3eae8f0640&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject)

#### Accessing the link

Rendr sends the customer an email with a secure, time-limited link (valid for 30 minutes from request).

![Update Your Delivery Instructions email with secure link button](https://fdr-prod-docs-files-public.s3.us-east-1.amazonaws.com/rendr.docs.buildwithfern.com/47fd19c86ac1d51482e7e883051d663b786490444c489393fb34c36b084f26c3/assets/delivery-dashboard/update-instructions-email.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIA6KXJSKKNFOCF7G4B%2F20260924%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260924T033840Z&X-Amz-Expires=604800&X-Amz-Signature=b2ac097026d474520b355c940a29232ca07378070e32250f9213d1d121836800&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject)

#### Updating instructions

The customer opens the link, enters their updated instructions, and confirms — this is passed to the carrier in real time.

![Add Delivery Instructions modal](https://fdr-prod-docs-files-public.s3.us-east-1.amazonaws.com/rendr.docs.buildwithfern.com/5ba706bff532be69c21dbcd9e746cc5e311940dbfaab6b11b26f4d460a761b3b/assets/delivery-dashboard/update-instructions-modal.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIA6KXJSKKNFOCF7G4B%2F20260924%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260924T033840Z&X-Amz-Expires=604800&X-Amz-Signature=00f3af8bd19a478ebcae9a38a8c5f5ef17acfc034768c8a3c74ef7d1ffe14adf&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject)

## Retrieving Proof of Delivery

If an order is completed by a carrier that supports proof of delivery (POD), customers can request their POD directly from the tracking page once the order has been delivered.

#### Delivery completes

A **Request POD** component appears on the tracking page (also accessible from the Help modal).

![Request POD component on the tracking page for a delivered order](https://fdr-prod-docs-files-public.s3.us-east-1.amazonaws.com/rendr.docs.buildwithfern.com/ceb4745fe7020ed8327e294571e6edbaef32f9d174d1c1d28e02e19a8a675476/assets/delivery-dashboard/request-pod-tracking-page.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIA6KXJSKKNFOCF7G4B%2F20260924%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260924T033840Z&X-Amz-Expires=604800&X-Amz-Signature=854ac966e8e001c41a3106a8a70b896d7dd226e3c0c91c8f8c9bed5ebb2d75bd&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject)

#### Customer requests POD

One tap submits the request.

#### Email delivered

Rendr retrieves the POD from the carrier and emails it to the customer.

> **Note**
>
> The Request POD component is only shown when the assigned carrier supports POD and a POD has been captured and returned to Rendr for that delivery. Otherwise it's hidden and the tracking page behaves as normal.

## End-to-End Workflow

Together, these pieces form a single flow between you, Rendr, the carrier, and your customer — from booking, through branded tracking and notifications, to delivery, feedback, and (where applicable) proof of delivery.

```mermaid
sequenceDiagram
    autonumber
    participant C as Customer
    participant M as Merchant Storefront
    participant R as Rendr
    participant Ca as Carrier
    participant T as Tracking Page

    C->>M: Place order
    M->>R: Push order via API / platform integration
    R->>Ca: Orchestrate booking with assigned carrier
    Ca-->>R: Booking confirmed
    R->>C: Booked notification (SMS + email) with tracking link
    C->>T: Open tracking page

    Ca->>R: Order collected event
    R->>C: Collected notification (with ETA if available)
    C->>T: View live tracking + ETA

    Ca->>R: Delivered event (POD)
    R->>C: Delivered notification with review prompt
    C->>T: Submit review
```