Shipping Letter Generator

Problem

Shipping paperwork needs consistent recipient, destination, and item information, along with reliable reference numbers once a letter is issued. Handling that process manually makes it easy to create duplicate numbers, lose a draft, or produce documents that cannot be traced back to their creator.

Approach

The application provides a Laravel and Filament administration panel for maintaining destinations, users, and shipping letters. Operators create a draft with sender and recipient details, at least one line item, a destination, and optional notes. Draft letters can then be issued from the list view and exported as PDFs.

Issuing a letter generates a destination-specific annual number in a database transaction. The service locks the corresponding counter row, increments it, and records a formatted number such as DESTINATION-001/YEAR, preventing concurrent issues from producing duplicates.

The tool separates draft and issued states, retains a creator reference, supports soft deletes and restoration, and restricts access by active user role. It also applies security headers and rate-limits repeated login attempts.

Outcome

The result is an internal web tool that gives operations teams a structured path from shipping-letter draft to issued, downloadable PDF. It replaces ad-hoc document preparation with consistent data entry, traceable numbering, and role-aware administration. The repository does not include validated operational-impact metrics, so none are claimed here.

Responsibilities

• Built the Laravel data model and Filament resources for destinations, users, letters, and line items.
• Implemented the draft-to-issued workflow and transaction-safe, destination-based annual letter numbering.
• Created the PDF export action and shipping-letter template with DomPDF.
• Designed role-based access policies for administrators and operators, including active-account checks.
• Added soft-delete and restore flows, login rate limiting, and security response headers.