A Custom ERP for a Freight Forwarding Company

The Challenge

Freight forwarding runs on reference numbers: booking numbers from shipping lines, container numbers, internal job IDs, customs documentation. Our client was tracking all of it across spreadsheets, a legacy desktop tool, and messaging threads. Every customer status request triggered a chain of phone calls, and billing leaked because completed jobs were invoiced late or not at all.

Off-the-shelf CRMs do not understand this domain. Logistics operations need multi-reference search, per-shipment cost tracking, and workflows that mirror how cargo actually moves — which is exactly the kind of problem custom software exists to solve.

What We Built

We designed the system around the shipment as the central entity. Any team member can pull up a job by internal ID, carrier booking number, or container number from a single search box. Each job carries its full lifecycle — booking, customs, transport, invoicing — with role-based access so operations, finance, and management each see what they need.

Under the hood: a Next.js application backed by PostgreSQL for transactional integrity and Redis for status caching, deployed in Docker for straightforward updates. Financial events flow through a double-entry style ledger so per-shipment profitability is computed rather than estimated. The system was built to be operable by non-technical staff from day one — the fastest data-entry path always wins.

Why a Custom Build

Generic CRM licensing for a team of this size is a recurring cost, and the products still do not handle multi-reference search or forwarding-specific invoicing rules without consultants and compromise. For an SME that has outgrown spreadsheets but cannot justify enterprise licensing and its implementation overhead, a custom system built by a team that took the time to learn the workflow is usually the cheaper answer over any multi-year horizon.