Postal delivery and bulk tracking

Record courier and tracking code

Store the delivery service and its reference with the letter.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationAdmin Area → Letter Manager → Update Postal Tracking → Courier Service / Tracking Number

Before you begin

Use an authorised account and confirm the customer, external recipient, template, letter or configuration is the intended one.
Follow the exact route shown above and verify the stored record, generated file and delivery evidence instead of relying on an alert alone.

What this guide covers

Store the delivery service and its reference with the letter. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Enter the carrier name, such as Royal Mail or DHL.
Enter the exact tracking reference.
Save.
Use the carrier’s own system for live tracking; Letter Manager only stores text.

Fields, choices and supported possibilities

Action scopeStore the delivery service and its reference with the letter.

Module version1.0.0

Exact routeAdmin Area → Letter Manager → Update Postal Tracking → Courier Service / Tracking Number

EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow.

Code-backed validations and workflow rules

The module does not call courier APIs or validate tracking-code format.

Expected result and verification

The requested letter, template, setting, file or tracking detail is created or updated through the supported route.
The history row, generated PDF, email/send metadata, public verification, signature evidence, client view or postal display agrees with the action.
Any warning, missing file or failed send is investigated rather than bypassed.

Security, privacy and operational checks

Apply least privilege and verify recipient identity before sending or exposing public links.
Protect PDFs, enclosures, signatures, verification URLs, email-open metadata, IP addresses and customer data under organisational policy.
Test configuration and deployment changes with controlled records before production-wide use.
Interpret email opens and e-signatures according to their documented technical limitations.