Cargowise Documentation ❲Cross-Platform❳

| Pitfall | CargoWise Solution | |---------|--------------------| | Wrong consignee on B/L | Customer data locked to a trade compliance profile; cannot edit without approval. | | Missing customs reference | Mandatory field rules – shipment cannot close without entering EORI/GST/HTS. | | Duplicate document numbers | System-wide unique constraint on House B/L, AWB, or booking reference. | | Outdated revision sent to customer | Document versioning; email only pulls latest from live data. | | No proof of delivery (POD) | Automated POD request linked to “Delivered” event; stores signed PDF. |

Every time a user creates, edits, or prints a document, Cargowise logs it. cargowise documentation

Even experienced users fall into traps. Here are the three most frequent errors in Cargowise documentation: | | Outdated revision sent to customer |

Many forwarders mistakenly view documentation as an administrative burden. In reality, within the Cargowise ecosystem, documentation is the engine of the Forwarding, Customs, and Accounting modules. Even experienced users fall into traps

While often provided by the shipper via EDI, Cargowise can generate these if you are acting as a NVOCC consolidator.