CargoWise is the dominant freight forwarding platform globally, and the case for running it is strong: multi-country customs filing, agent network management, HAWB and MAWB processing at volume, and per-job P&L tracking in a single system. The case against replacing it with custom software is equally strong — replicating CargoWise's customs depth and carrier connectivity from scratch is a multi-year, multi-million dollar project that almost no forwarder should attempt. But CargoWise's dominance as a forwarding execution platform does not mean it handles every layer of a freight forwarder's technology requirements. The client portal it provides is generic. The management analytics it generates are raw data. The modification cost for non-standard workflows is substantial. For those specific gaps, custom development is worth it. For the execution layer itself, it is not.
Key Takeaways
- CargoWise is the right choice for freight forwarding execution: multi-country customs, agent network management, HAWB/MAWB processing, and per-job P&L tracking are not practical to replicate in custom software.
- CargoWise's client portal presents CargoWise's interface rather than the forwarder's brand, creating a competitive disadvantage in mid-market shipper relationships where branded visibility is a differentiator.
- CargoWise modification charges for non-standard workflows run $10,000 to $100,000+ per change, creating compounding costs for forwarders whose operational requirements diverge from standard configuration.
- Custom analytics over CargoWise data typically costs $40,000 to $80,000 and delivers lane-level margin analysis, carrier performance dashboards, and client KPI reports that CargoWise does not generate natively.
- The right architecture for most freight forwarders is CargoWise for execution plus custom applications for client experience and management intelligence.
What CargoWise Does Well
CargoWise's position as the global freight forwarding platform is built on specific capabilities that took WiseTech Global (its owner) decades to develop.
Multi-country customs depth. CargoWise handles customs filing in over 150 countries within a single platform. Import declarations, export permits, certificates of origin, and trade compliance screening are embedded in the forwarding workflow rather than managed as separate compliance software.
Agent network management. International forwarding requires managing agent relationships in destination countries for delivery, customs clearance, and status updates. CargoWise's agent network tools — shared job visibility, agent instructions, costing and settlement between agents — are built into the forwarding workflow.
HAWB and MAWB processing at volume. Managing house bills and master bills across multiple consignments, consolidations, and deconsolidations at volume requires a data model purpose-built for freight forwarding. CargoWise handles this accurately at the scale that large forwarders operate.
Per-job P&L tracking. The job-level profitability that forwarding managers review for pricing and margin management is embedded in CargoWise's job costing model. Revenue and cost at the job level is a core CargoWise output.
These capabilities are not practical to replicate in custom software. The regulatory depth, the data model complexity, and the ongoing compliance maintenance represent investment that belongs in CargoWise, not in a custom development project.
Where CargoWise Falls Short
CargoWise's strengths are execution accuracy and compliance depth. Its limitations appear in the client-facing and management intelligence layers.
The Client Portal Problem
CargoWise provides a shipper-facing portal for shipment tracking and documentation access. That portal presents CargoWise's interface, which the shipper experiences as the forwarder's technology platform.
For a mid-market forwarder competing against larger competitors and freight brokers, the client portal is one of the few visible differentiators. A branded portal that presents the forwarder's name, the forwarder's visual identity, and the forwarder's specific visibility format communicates "our platform" rather than "we use CargoWise like every other forwarder."
The CargoWise portal does not allow the brand customization that competitive positioning requires. A custom client portal over CargoWise data addresses this: the shipper logs into the forwarder's branded portal, sees their shipments in the format the forwarder has configured for them, and receives notifications from the forwarder's communication system rather than CargoWise's.
The Analytics Gap
CargoWise generates transaction data: job records, costs, revenues, agent communications, customs entries. It does not generate the management analytics that forwarding leadership uses for business decisions.
Lane-level margin analysis (which trade lanes are profitable, which are eroding, which carrier and agent combinations drive the best margin) requires custom data aggregation over CargoWise job records. Carrier performance analytics (transit time accuracy, damage rates, exception frequency) require pulling CargoWise event data and aggregating it in formats CargoWise does not produce natively. Client profitability analysis (which clients generate margin, which generate revenue without adequate margin) requires joining CargoWise job records with client contract data.
These analytics are not available in CargoWise reports. They require either BI infrastructure (Power BI, Tableau) over a CargoWise data warehouse — a $150,000 to $300,000 investment — or custom analytics applications at $40,000 to $80,000 that deliver the specific analyses forwarding leadership needs.
Modification Charges for Non-Standard Workflows
Freight forwarders develop operational workflows over years: specific exception handling procedures, non-standard documentation formats for certain clients or trade lanes, custom rating logic for complex freight profiles. When these workflows diverge from CargoWise's standard process model, implementing them within CargoWise requires platform modifications.
CargoWise modification pricing follows a vendor-controlled change order model. Substantive modifications to the CargoWise platform or to CargoWise's custom development framework (CW1) run $10,000 to $100,000 per change. Ongoing modifications as operational requirements evolve accumulate to $100,000 to $300,000 annually for forwarders with multiple non-standard workflows.
Customer Notification Automation
CargoWise manages job-level event tracking. It does not manage the proactive customer communication workflow that mid-market shippers now expect: automated departure notifications, transit delay alerts, customs hold notifications with expected resolution windows, and delivery confirmation with proof of delivery.
Implementing this communication layer within CargoWise requires either CW1 customization (expensive) or an external integration with a notification platform (additional vendor and integration overhead). Custom notification automation that reads CargoWise event triggers and sends client-specific communications typically costs $30,000 to $60,000 and runs reliably without ongoing CW1 maintenance.
The Build vs. CargoWise Decision Framework
For freight forwarders evaluating where to invest in custom development versus accepting CargoWise's limitations:
Do not build: Forwarding execution. CargoWise's customs depth, agent network management, and job P&L tracking are not replicated in custom software at reasonable cost or timeline. The forwarding execution layer belongs in CargoWise.
Build: Client portal. A custom branded portal over CargoWise data ($50,000 to $100,000) delivers competitive differentiation that CargoWise's portal module cannot provide.
Build: Management analytics. Custom analytics over CargoWise data ($40,000 to $80,000 per application) delivers lane margin analysis, carrier performance dashboards, and client profitability reporting that CargoWise does not generate natively.
Evaluate: Non-standard workflow automation. Workflows that diverge from CargoWise's standard model should be evaluated individually. If CargoWise modification cost exceeds $80,000 to $100,000 for a workflow that custom software addresses for $60,000 to $80,000, custom software is the right answer for that workflow.
Build: Customer notification. Custom notification automation over CargoWise event data ($30,000 to $60,000) delivers the proactive client communication workflow that CargoWise does not generate natively.
Three-Year Cost Comparison
| Approach | Year 1 | Year 2 | Year 3 | Total |
|---|---|---|---|---|
| CargoWise only (all gaps via modification) | $200,000 license + $150,000 modification | $200,000 license + $150,000 modification | $200,000 license + $150,000 modification | $1,500,000 |
| CargoWise + targeted custom layer | $200,000 license + $200,000 custom dev | $200,000 license + $40,000 maintenance | $200,000 license + $40,000 maintenance | $880,000 |
The comparison assumes a forwarder paying $200,000 annually in CargoWise transaction fees and $150,000 annually in modification charges for non-standard workflows — a profile that matches mid-to-large freight forwarders with multiple non-standard requirements. The custom layer investment ($200,000 in year one for portal, analytics, and notification automation) pays back in year two when modification charges drop and the custom layer maintenance replaces them.
Conclusion
Building custom software to replace CargoWise is not worth it. Building custom software alongside CargoWise for the layers CargoWise does not address is worth it for most forwarders above a certain scale. The client portal, management analytics, and customer notification layers that CargoWise leaves behind are the appropriate targets for custom development — not the forwarding execution platform that CargoWise has spent decades building. The right architecture pairs CargoWise's execution depth with a custom layer that addresses client experience and management intelligence.
The Custom Layer Your CargoWise Deployment Is Missing
CargoWise handles freight forwarding execution. The client portal, management analytics, and workflow automation that turn CargoWise data into competitive advantage are built separately.
LOW/CODE Agency has built custom client portals, analytics applications, and workflow automation tools over CargoWise data for freight forwarders that needed specific capabilities their platform does not generate. If you have identified specific CargoWise gaps that belong in custom software, schedule a consultation with our Senior Partners.
Frequently Asked Questions
Should I replace CargoWise with custom software?
No. CargoWise's multi-country customs depth, agent network management, and job P&L tracking are not practical to replicate in custom software at reasonable cost. Custom software should address the client portal, analytics, and notification layers that CargoWise does not generate, not the execution layer it handles well.
How much does CargoWise cost per year?
CargoWise uses per-transaction pricing. Mid-market freight forwarders typically pay $50,000 to $150,000 annually. Large global forwarders pay $200,000 to $500,000 or more annually, depending on job volume, customs entry volume, and EDI message volume.
What is a CargoWise CW1 customization?
CW1 is CargoWise's custom development framework that allows platform-level modifications. CW1 customizations are built by CargoWise-certified developers and require CargoWise review and approval. They are expensive ($10,000 to $100,000+ per customization) and create ongoing maintenance obligations as CargoWise updates.
Can I add a branded portal to CargoWise?
CargoWise does not support full brand customization of its client portal. A custom portal built over CargoWise data via API delivers branded client visibility without CW1 development. Most mid-market forwarders find the custom portal approach faster, cheaper, and more brand-aligned than platform modification.
What analytics does CargoWise provide?
CargoWise provides transaction-level reports: job records, customs entries, agent communications, and revenue and cost at the job level. Lane-level margin analysis, carrier performance scoring, and client profitability dashboards require custom development or BI infrastructure over CargoWise data.
How long does it take to build a custom portal over CargoWise?
A custom client portal integrated with CargoWise via API for shipment visibility, documentation access, and status notifications typically takes 10 to 16 weeks to build and deploy. More complex portals with booking and quoting integration take 16 to 24 weeks.