Record courier and tracking code
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Store the delivery service and its reference with the letter.
Where to goAdmin Area → Letter Manager → Update Postal Tracking → Courier Service / Tracking Number
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
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.
Follow these steps
- 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 and options
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.
Rules and limits
- The module does not call courier APIs or validate tracking-code format.
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.
Related guides
Was this guide useful?Your response is stored only in this browser.