PDF, QR, email and audit evidence

Understand Delivery Note PDF footer behaviour

Distinguish the installed footer-text option from the footer actually rendered by the supplied PDF code.

Audience: Administrators and developersPermission: Technical inspectionModule v1.0.0
Exact navigationNo staff-menu setting exists → Review generated Delivery Note PDF footer

What this guide covers

Distinguish the installed footer-text option from the footer actually rendered by the supplied PDF code. This guide follows the supplied Delivery Note module’s live hooks, controller actions, model rules, views and stored side effects.

Exact step-by-step process

  1. Generate a test PDF.
  2. Read the footer at the bottom of the page.
  3. Confirm it states Powered by Britixo Software Solutions UK Limited.
  4. Review the installed `delivery_note_pdf_footer_text` option only as metadata.
  5. Do not tell users that changing the option will alter the PDF unless the deployed code is later changed and verified.

Fields, choices and supported possibilities

  • Installed option default: one-time e-signature/compliance-log sentence
  • Rendered hard-coded footer: Powered by Britixo Software Solutions UK Limited

Code-backed validations and workflow rules

  • The current Delivery_note_pdf library does not read the installed footer-text option.
  • The rendered footer is repeated on pages/continuations.
  • This is a code-backed limitation, not a configurable UI feature.

Expected result and verification

  • Documentation accurately describes the footer users will actually see.

Checks, security and troubleshooting

  • Future code changes should align the option and rendered output before a configuration guide is added.
Stay within the supported flowDo not force database values, expose secure tokens, bypass permission checks, replace a stored signature or invent a status or interface that the supplied code does not implement.