Postal delivery and bulk tracking

Update postal tracking for one letter

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Save delivery status and tracking fields from the row-level truck action.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Jump to steps

Where to goAdmin Area → Letter Manager → Sent Letters History → Update Postal icon

Before you start

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 helps you do

Save delivery status and tracking fields from the row-level truck action. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Follow these steps

Find the letter.
Select the truck icon.
Select Delivery Status.
Enter Courier Service.
Enter Tracking Number.
Select Date Handed to Courier.
Select Save Details and verify the Delivery cell.

Fields and options

Action scopeSave delivery status and tracking fields from the row-level truck action.

Module version1.0.0

Exact routeAdmin Area → Letter Manager → Sent Letters History → Update Postal icon

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

Rules and limits

Only the values and actions exposed by the supplied Letter Manager v1.0.0 code are supported.
Browser controls are not a substitute for server-side and operational verification.

Check it worked

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.

Was this guide useful?Your response is stored only in this browser.