Custom Freight Forwarding Software Development for Forwarders Who Have Outgrown Off-the-Shelf

A focused MVP covering core forwarding workflows — shipment management, documentation, basic carrier connectivity, and client tracking — typically takes 18–24 weeks. A full-featured platform covering multi-modal operations, customs authority connectivity, LCL consolidation, agent network management, multi-currency invoicing, and data migration from an existing system runs 30–36 weeks. The most common cause of timeline extension in freight forwarding projects is customs authority integration complexity and data migration scope that was not fully assessed before development began. Both are documented and priced in Phase 01 and Phase 02 before any development starts.

Yes — data migration from CargoWise, Magaya, and legacy on-premise freight forwarding systems is something we handle as a structured phase of every relevant project. This covers historical shipment records, rate tables, client and agent records, financial history, and customs entry data — extracted, transformed, validated, and loaded into the new platform with reconciliation against your source system before go-live. We manage a parallel run period where both systems operate simultaneously so your team can validate live shipment data, declaration accuracy, and financial reconciliation before the legacy platform is decommissioned. Migration is not a hard cutover — it is a managed transition with zero data loss.

Yes — customs authority connectivity is a core component of freight forwarding platforms we build, not an afterthought. We integrate with the Australian Border Force (ABF) and ACBPS systems for Australian customs declarations, UAE Federal Customs Authority systems for GCC market operations, HMRC CDS for UK import and export declarations, and other customs authority APIs where your trade lanes require it. Integration covers automated import and export entry preparation, tariff classification database connectivity, duty and tax calculation, FTA preference management, prohibited goods screening, and declaration lodgement — with declaration status tracking and compliance audit trail management built into the operational workflow.

Yes — dangerous goods compliance is a specialist capability we build into freight forwarding platforms for forwarders handling DG cargo. This covers IMDG classification management for ocean freight, IATA DGR compliance for air freight, and ADR for road freight — including UN number verification, packaging group assignment, segregation rule enforcement across multi-commodity consignments, DG declaration generation, emergency response documentation, and carrier DG acceptance workflow management. DG screening logic is validated against current classification databases before go-live and updated as classification changes are issued by IMDG, IATA, and ADR authorities.

Yes — LCL consolidation and NVOCC operations are a distinct capability we build for forwarders running their own consolidation services. This covers consol creation and cargo booking management, dynamic space allocation across multiple trade lanes, cargo cut-off management, automated manifest generation, MBL and HBL linking, destination deconsolidation workflows, and per-consol profit and loss reporting. The consolidation module is built with the financial visibility NVOCCs need — actual versus estimated cost per consol, agent commission management, and container utilisation reporting — giving your consolidation team the data to manage profitability at the consol level rather than the shipment level.

We build carrier connectivity through EDI X12 and EDIFACT transaction sets for ocean carriers — covering booking requests, booking confirmations, bill of lading instructions, shipment status messages, and freight invoice processing. For air freight we build airline API connectivity for space booking and AWB generation. For road and multimodal we build carrier API and EDI connections specific to your carrier network. Agent network connectivity is built through dedicated agent portals — giving your overseas agents direct access to shipment status, document upload, job acceptance, and disbursement management within the platform. Every carrier and agent integration is scoped and architecturally designed in Phase 02 before development begins. See also our TMS and freight management integration experience.

Yes — multi-currency financial management is a core architectural requirement in every freight forwarding platform we build. This covers multi-currency client invoicing with real-time exchange rate integration, disbursement management in local currencies, duty and tax pass-through to clients, intercompany transaction management between agent networks, credit limit management per client, and accounts receivable synchronisation with Xero, MYOB, SAP, and Oracle. Currency conversion logic is built at the transaction level — not applied as a blanket rate at month end — so your financial reporting reflects actual currency movements across every shipment. Integrates with supply chain and e-commerce order and invoice flows where required.

CargoWise and Magaya are strong platforms for freight forwarders whose operations align with the workflows they were designed for. CargoWise in particular is the market-leading platform for large forwarders managing standard multi-modal operations with extensive carrier network connectivity already built in. Custom development makes more sense when your operation handles specialist cargo types or trade lanes that no available platform covers cleanly, when your per-user licensing cost on a commercial platform is approaching the cost of a one-time custom build over a 3–5 year horizon, when your client reporting requirements cannot be met by the platform's standard reporting tools, or when your competitive advantage depends on forwarding processes that need to be protected in proprietary software. We give you an honest build-versus-buy assessment in every discovery session — including whether CargoWise or Magaya is genuinely the better choice for where your operation is today.

Yes — multi-office and agent network management is a standard architectural requirement for freight forwarding platforms we build. This covers office-level user access controls and data segregation, intercompany job and cost sharing between offices, agent portal access for overseas partners, agent performance scorecards, commission and disbursement management across the agent network, and consolidated reporting across all offices and agents from a single management view. For forwarders operating across multiple countries, we build jurisdiction-specific compliance workflows, local currency handling, and country-specific customs authority connectivity into the same unified platform — so your global operation runs from one system without compromising local compliance requirements.

The client portal gives your importer and exporter clients self-service access to their shipments without requiring a phone call or email to your operations team. This covers real-time shipment tracking with milestone visibility from booking to delivery, document access for bills of lading, commercial invoices, packing lists, and customs entries, booking request submission directly into your operations workflow, invoice history and outstanding balance visibility, and customs entry status tracking for clients managing their own import compliance. The portal is branded to your freight forwarding business — your logo, your colours, your domain — not a generic platform that makes your clients feel like they are accessing a third-party system rather than your own.

Yes — perishables and cold chain forwarding is a specialist capability we build for forwarders handling temperature-sensitive cargo. This covers temperature-controlled space booking with carrier cold chain confirmation, phytosanitary and health certificate documentation workflows, cold chain monitoring integration with IoT temperature devices, shelf-life-aware routing logic that factors transit time against cargo shelf life, automated health authority documentation for biosecurity requirements, and pre-cooling and post-arrival temperature excursion alerting. Documentation workflows for perishables — phytosanitary certificates, health certificates, certificates of origin for FTA preference, and fumigation certificates — are generated automatically from shipment data rather than assembled manually per consignment. For pharma cold chain see our healthcare logistics experience.

Because you own the codebase, adding new trade lanes, cargo types, carrier integrations, or compliance workflows is entirely within your control — not dependent on a vendor's product roadmap or feature request queue. New capabilities are added through the ongoing development retainer by the same engineering team that built the platform. Adding a new trade lane typically involves carrier EDI or API integration for the relevant carrier network, customs authority connectivity for the destination market, and any cargo-type-specific documentation or compliance workflows. These are scoped as individual development items with clear cost and timeline estimates — not open-ended projects.

Yes — we have delivered logistics and freight software for clients across Australia, the UAE, and the UK, and we understand the specific regulatory and operational requirements that distinguish each market. For Australia this means ABF and ACBPS customs connectivity, Australian carrier and stevedore EDI standards, Chain of Responsibility compliance where applicable, and Xero and MYOB accounting integration. For UAE this means UAE Federal Customs Authority connectivity, GCC market trade compliance, and multi-currency management for AED, USD, and regional currency flows. For UK this means HMRC CDS integration for post-Brexit customs declarations, UK carrier EDI standards, and VAT handling for cross-border trade flows. Multi-market freight forwarding platforms are designed with each market's compliance requirements built in from Phase 01 — not retrofitted after the primary market version is complete.

Post-launch support covers a structured four-week hypercare period with named engineering support, agreed SLA response times for critical and high-priority production issues, and weekly review calls covering system health, declaration accuracy, and user feedback. Hypercare covers your first peak shipment period, first customs audit cycle, and first end-of-month financial close on the new platform — the three operational events most likely to surface issues in the weeks after go-live. After hypercare we transition to an ongoing development retainer covering bug fixes, performance optimisation, new carrier integrations, new trade lane additions, and platform scaling as your forwarding operation grows. The engineering team that built your platform stays involved — you are not handed to a support desk that has never processed a bill of lading. The same approach we use for supply chain and logistics platform support.