International logistics console

The problem

A cross-border freight forwarder ran operations across many carriers, ports, and customs jurisdictions. Existing SaaS treated every shipment generically; ops teams spoke a domain language the platform did not understand; broker handoffs and finance reconciliation lived in spreadsheets. Exceptions were caught reactively, not proactively, which cost time on every shipment.

The approach

We built a Next.js ops console structured around the actual jargon and workflows: shipment tracking across carriers and ports with normalized status codes, customs documentation generation, route exception detection, broker handoffs with explicit ownership transfer, and finance reconciliation tied to invoice line items. Carrier APIs feed shipment events; the platform normalizes and routes them to the right team without polling.

Stack and engineering choices

• Next.js ops console
• Postgres core
• Carrier API normalization
• Customs documentation generator
• Route exception detection
• Broker handoff workflow
• Invoice line reconciliation

Outcome

Ops teams work in their own domain language. Exceptions surface before they cost the customer time. Finance reconciliation lives in the same system as operations, not a separate spreadsheet, which closes the books faster every month-end.