Understand the letter verification barcode | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/understand-the-letter-verification-barcode Publisher: Pixie Technologies LLC PDF generation, branding and files Understand the letter verification barcode Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Follow this guide to use the printed verification code as secondary visible evidence. Audience: CRM staff; Permission: Authenticated staff account; Module v1.0.0; Where to goOpen generated PDF → bottom digital security area 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 Use the printed verification code as secondary visible evidence. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow. Follow these steps - Find the Code 128 barcode near the end of the letter body. - Read the visible random verification code. - Compare it with the public verification page or client letter history. Fields and options Action scopeUse the printed verification code as secondary visible evidence. Module version1.0.0 Exact routeOpen generated PDF → bottom digital security area 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 barcode encodes random_verification_code. - The model creates an eight-character uppercase code using an MD5/uniqid-based value. - This code is separate from the public unique_code and signature hash. 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 Letter Manager module overview (https://pixiecrm.com/help-centre/letter-manager-module-overview)Configure company details used in Letter Manager PDFs and emails (https://pixiecrm.com/help-centre/configure-letter-manager-company-name-address-phone-and-website)Understand PDF QR verification (https://pixiecrm.com/help-centre/understand-letter-manager-pdf-qr-verification)Understand recipient-window formatting (https://pixiecrm.com/help-centre/understand-letter-manager-recipient-window-formatting)Understand Letter Manager subject and body layout (https://pixiecrm.com/help-centre/understand-letter-manager-subject-and-body-layout)Understand the PDF company closing block (https://pixiecrm.com/help-centre/understand-letter-manager-pdf-company-signature-block)Configure SMTP email delivery (https://pixiecrm.com/help-centre/configure-smtp-email-delivery)Add and manage customer contacts (https://pixiecrm.com/help-centre/add-and-manage-customer-contacts)Client portal overview (https://pixiecrm.com/help-centre/client-portal-overview)