Delivery Confirmation Email Template: Delivered, Photo Proof, and Missing Package Paths

A delivery confirmation is most useful when it closes the fulfillment loop. It should confirm the carrier event without claiming that the customer personally received the package.

Trigger and evidence

Send only after the carrier or fulfillment system reports delivered. Capture:

• order and shipment number;
• delivered timestamp and recipient timezone;
• carrier and tracking link;
• delivery location or photo proof when supplied;
• item summary;
• support or missing-package path.

If the carrier reports “delivered” but the event is later corrected, send a correction or route the case to support. Do not silently send a second contradictory confirmation.

Template

Subject: Delivered: order {{order_number}}

Preheader: Your package was marked delivered {{delivered_time}}.

Hello {{customer_name}},

Your {{product_summary}} from order {{order_number}} was marked delivered on {{delivered_date}} at {{delivered_time}}.

{{delivery_location_or_photo}}

[View tracking details]

If you can’t find the package, check with household members, your building desk, and the carrier’s delivery location first. If it is still missing after {{investigation_window}}, [report a missing package].

{{company_name}}

Edge-case copy

Photo proof

“The carrier provided a delivery photo. Please check the location shown before reporting the package missing.” Link to the carrier record rather than embedding a low-resolution or private image without consent.

Signature required

“The carrier recorded delivery with a signature from {{signer_name}}.” Use the name only when the carrier supplies it and policy allows it.

Delivered to a pickup point

This is not a delivered-to-door message. Use the pickup location, opening hours, collection deadline, and ID requirements instead.

Customer reports missing package

Stop generic delivery reminders and create a support or carrier-investigation event. The customer should not receive “your package was delivered” again while a case is active.

QA checklist

• The delivered event is authoritative and deduplicated.
• Timezone and carrier location are clear.
• Photo or signature data is shown only when available.
• A missing-package path has a real deadline and owner.
• Pickup-point deliveries use the pickup template.
• The link does not expose another customer’s order.

See the out-for-delivery template for the previous status and the delayed shipment template for exceptions.

When “delivered” is not the end

Keep a separate case path for:

• delivered to a pickup point;
• delivered to a neighbor or building desk;
• photo proof that does not match the customer’s location;
• a package reported missing within the carrier investigation window;
• a shipment delivered to the wrong address.

The confirmation can link to the case form, but it should not imply that the customer is responsible for investigating a carrier error. Preserve the carrier event and the customer’s report so support can see both.

Measurement

Track delivery-confirmation opens only as a secondary signal. More useful measures are missing-package contacts, successful self-service reports, delivery-related refunds, and time to resolution. Test the message with and without photo proof, long item lists, and international address formats.

Match the confirmation to the handoff

“Delivered” can mean different things operationally. Choose the variant from the evidence:

Do not convert a pickup-point or desk delivery into “left at your door.” If the carrier gives only an approximate location, label it as such.

Make missing-package recovery concrete

The self-service path should create a case with order, shipment, carrier event, and delivery location context. Show the investigation window and who owns the next update. If the customer reports a missing package, suppress generic post-delivery cross-sells and review requests until the case is resolved.

Test partial orders, multiple packages, a gift recipient, an international address, missing photo proof, a carrier correction, and a case opened immediately after the send. The best confirmation closes a state while leaving a humane next step when the state is wrong.