CargoMode
Practical guides and insights for freight forwarders navigating the shift to automated logistics.

A framework for comparing RFQ automation tools for freight forwarders: parsing, marketplace rates and templates, scored against your own quote volume.

A step-by-step workflow for automating VGM capture, matching, submission and exception handling, with the code and logic you can build from today.
How container tracking data really moves between carriers, AIS and terminals, why statuses contradict, and how to monitor boxes without a spreadsheet.

A worked example of extracting packing list and bill of lading fields, the operator review step, and where the output actually has to go.

A worked example of a trustworthy CargoWise shipment-cost report: separating job costs from posted accounts, tracking missing values and picking KPIs that hold up.

Five specific places shipment data degrades between inbox and TMS, with the mechanism behind each leak and the defence that actually closes it.

A practical guide to HS heading 6910 for ceramic sanitary fixtures, covering the 6910.10 vs 6910.90 split and common material mix-ups.

Why paper bills of lading still dominate in 2026, what DCSA standards actually change, and a pragmatic checklist for going eBL without risk.

A working guide to HS heading 8482 for ball and roller bearings — subheadings, the bushing trap, and how to check your classification before customs does.

Preserve charge rows, separate currencies and reconcile CargoWise reports. Volume 3 is available with documented retrieval templates and runnable examples.

Review a CargoWise invoice against usage records, transaction categories, currencies, credit notes and customer recovery with a repeatable checklist.

Jobs created via eAdapter do not inherit the org/UNLOCODE defaults the CW UI applies. The defaults engine with four-tier precedence that closes the gap — including when NOT sending a field is the right move.

CW only sends outbound messages when a milestone carries a Completion Trigger Action. Why the most dangerous outbound failure isn't a failure at all — and the trigger map that prevents it.

Test environments are hard to get in the CW world — so teams test in prod. Push back: the test company, version-controlled fixtures, and the replay harness that turns every failure into a regression test.

A real production postmortem: three sequential eAdapter calls vs a serverless wall-clock limit — and the timeout budgets, endpoint splitting, and partial-failure flags that fixed it.

CargoWise offers three integration paths — eHub, E2E Messaging, and eAdapter. Here is the decision table, real cost data, and why the best eAdapter integration is often the one you never build.

The eAdapter returns a tracking UUID, not a result — real message status lives in the CW EDI Interchange. How to build the exception dashboard that finds dead messages before your customer does.

The eAdapter Outbound Service accepts exactly one endpoint for everything your instance emits. The relay architecture every multi-system shop ends up building — explained.

Organisation search in CargoWise requires Native XML, not Universal XML. Here's the search-after-create pattern and why org code assignment makes it necessary.

Understanding parent-level vs SubShipment DataContext rules is the difference between a working eAdapter integration and hours of debugging cryptic validation errors.

CargoWise eAdapter returns HTTP 200 even when your operation fails. Here's how to actually detect errors, parse the ProcessingLog, and stop losing data silently.

From Hapag-Lloyd's smart container fleet and the eBL tipping point to the CargoWise pricing revolt, the forwarding technology landscape is undergoing a fundamental shift.
Understand CargoWise Community Pricing, eligible transactions, pack inclusions and optional charges, with a dated USD example and official sources.