Postal delivery and bulk tracking

Bulk update postal details for selected letters

Apply the same postal fields to multiple currently selected history rows. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Jump to steps

Where to goAdmin Area → Letter Manager → Sent Letters History → select rows → Postal Update Selected

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 you’ll accomplish

Apply the same postal fields to multiple currently selected history rows. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Follow these steps

Select the checkbox for each visible letter.
Use Select all visible letters when appropriate.
Select Postal Update Selected.
Verify the modal shows the selected count.
Enter the common status, courier, tracking code and date.
Save and verify each affected row.

Fields and options to review

Action scopeApply the same postal fields to multiple currently selected history rows.

Module version1.0.0

Exact routeAdmin Area → Letter Manager → Sent Letters History → select rows → Postal Update Selected

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

Rules the system enforces

Selected IDs are sent as a comma-separated letter_ids value.
The controller deduplicates positive integer IDs and performs one where_in update.
The same tracking code is applied to every selected record.

How to confirm 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.