How shipment creation works in CargoWise
CargoWise is the transport management system (TMS) that many freight forwarders run as their system of record, and shipment creation is one of its core forwarding workflows. CargoWise describes its forwarding product as a single platform to "manage bookings, documentation, carrier connections, customer updates, and internal workflows", and the path that creates a shipment runs through a few clear stages.
It starts with schedules and rates. CargoWise lets a forwarder "search schedules from leading carriers and airlines, compare routes, and apply voyage details with real-time ETD and ETA updates", and compare buy and sell rates by lane, carrier, and commodity before converting a quote into a booking.
Next is the booking. CargoWise eBookings let a forwarder "book and manage shipments electronically and directly within the platform", and CargoWise can capture bookings directly from a customer's own TMS electronically. Where several bookings can travel together, CargoWise can build a consolidation from multiple booking requests and advise how the shipments were consolidated.
Then come the shipping instructions (SI) and the verified gross mass (VGM). CargoWise frames this as helping shippers meet their VGM obligations and documentation cut-off times and send the full data through electronically, so the forwarder works from structured data rather than email and PDF.
Finally, documentation and tracking. CargoWise can "create bills of lading, air waybills, invoices, and packing lists directly from bookings and job data", and carrier event updates flow back so the record stays current. CargoWise frames the whole sequence as an order-to-cash cycle, from booking through to invoice.
Where the manual work actually sits
Creating the shipment record in CargoWise is one thing. Getting that shipment booked and the shipping instructions accepted at the carrier is another, and it is where most of the manual hours go.
CargoWise handles forwarder-side data exchange consistently, but each carrier's own portal is where workflow-specific rules apply. The structured-data layer ends at the carrier's door, and the booking, SI, and documentation then have to clear that carrier's specific validation: Maersk enforces an HS-code minimum at SI submission, MSC sanitises certain characters on its portal, and Hapag-Lloyd routes ICS2-bound cargo through a different SI form. None of that is uniform, so the work does not reduce to one repeatable step.
In practice that means re-keying or re-checking booking and SI data on each carrier's portal, handling per-carrier validation and document-type rules, and chasing confirmations and status events back into CargoWise. The volume scales with shipment count, which is exactly the labor a per-transaction billing model puts a price on.
What CargoWise does, and where the execution gap is
The split is consistent across the workflow: CargoWise owns the forwarder-side record, and each carrier's portal or API owns acceptance. The CargoWise integration page covers the mechanism in full.
| Stage | Handled in CargoWise | Where the carrier-side gap is |
|---|---|---|
| Schedules and rates | Search schedules, compare routes and rates, convert to a booking | Carrier schedule and rate sources feed in by API, EDI, or spreadsheet |
| Booking | Create and manage the booking electronically, capture from a customer TMS, consolidate | Submitting the booking on each carrier's portal or API and handling per-carrier rules |
| Shipping instructions and VGM | Receive structured SI and VGM data, meet documentation cut-off times | SI validation differs by carrier (HS-code minimums, character rules, ICS2 SI forms) |
| Documentation | Create bills of lading, air waybills, invoices, and packing lists from job data | Document-type changes that lock at booking on certain carriers |
| Tracking | Carrier event updates flow back to the record | Pulling consistent status events back from each carrier and writing them in |
The 2026 backdrop: per-transaction billing
One reason this workflow is under fresh scrutiny is cost. As of 1 December 2025, CargoWise replaced its seat and transaction license model with Value Packs, an all-in-one fee charged per logistics job, where a job is a shipment, a standalone customs declaration, a land transport movement, or a warehouse order line. When billing attaches to each job rather than to seats, the operational labor behind each shipment carries a more direct price.
The reported impact has been uneven. The Journal of Commerce and The Loadstar reported cost increases in the range of 20% to 50% for some existing customers; those figures come from trade reporting and forwarder accounts, not from WiseTech, so they read as reported experience rather than a published rate. The picture has also kept moving since launch: reporting since 1 December 2025 describes a transitional pricing protection line on early invoices and a further pricing adjustment landing in 2026, so the December 2025 model is best read as a starting point rather than the complete current picture. The full breakdown is on our CargoWise Value Packs pricing change page.
Automating the carrier-side half
Automating shipment creation splits into two halves that the comparison guides tend to blur. The first is getting data into CargoWise: reading a booking confirmation or BL document and creating or amending the shipment record. That is the document-capture half, and it is a different tool's job, not Expedion's. The second is getting the booking and shipping instructions out to the carrier and the status back: submitting on the carrier's portal or API, clearing per-carrier validation, and writing the result into CargoWise. That carrier-side execution half is where Expedion works. Mechanically, Expedion reads shipment state from CargoWise through eAdaptor as reference reads, executes booking, SI, BL, documentation, and tracking on each carrier's own channel, and writes completed events back through eAdaptor so CargoWise stays the system of record. Carrier-side, that means authenticated portal sessions on the six carrier portals where the portal is the execution surface (Maersk.com, myMSC, My CMA CGM, ONE eCommerce, SynCon Hub, and ShipmentLink), carrier-published REST APIs on Hapag-Lloyd, CMA CGM, and ONE where production endpoints exist, and EDI through INTTRA, Infor Nexus, or CargoSmart as the fallback. This capability is in supervised production with design partners, not general availability. You can read how the eAdaptor integration works in full.
No migration and no replatforming. CargoWise stays the system of record and the forwarder-side workflow, and Expedion automates the carrier-side labor on top of it.
Expedion does not read documents into CargoWise or create the CargoWise record, and it does not run accounting, customs filing, or warehouse workflows. It handles the booking and shipping instructions out to the carrier and the status back.
Authorization is forwarder-provided, with explicit, auditable scope. The reads agents perform are reference reads that do not by themselves add billable CargoWise transactions; confirm the transaction-count detail with your CargoWise account team.
Frequently asked questions
How do you create a shipment in CargoWise?
In CargoWise, shipment creation runs from schedules and rates into a booking, then shipping instructions and verified gross mass, then documentation and tracking. A forwarder can search carrier schedules, compare rates, and convert a quote into a booking, capture bookings electronically from a customer's TMS, receive structured SI and VGM data, and create bills of lading, air waybills, invoices, and packing lists from the booking and job data. CargoWise frames the sequence as an order-to-cash cycle from booking to invoice.
Can shipment creation in CargoWise be automated?
Partly, and it helps to separate two halves. Getting data into CargoWise, which means reading a booking or BL document and creating the record, is the document-capture half, already a known automation play handled by document-processing tools. Getting the booking and shipping instructions out to each carrier and the status back is the carrier-side execution half, which the comparison guides often leave out. Both can be automated, but they are different problems handled by different tools.
Will automating shipment creation change my CargoWise bill?
It depends on your specific CargoWise contract, so confirm the detail with your CargoWise account team. Where Expedion is involved, agents read existing booking, SI, and BL records as reference reads rather than new transactions, and write back milestone events as they occur. Most agent-driven activity does not increase billable transactions on CargoWise's side, but specific contract terms vary. Separately, CargoWise's own Value Packs model bills per logistics job as of 1 December 2025, so your underlying per-shipment cost depends on that model too.
Does Expedion do the data entry into CargoWise?
No. Expedion is the carrier-side execution half: it submits the booking and shipping instructions on the carrier's portal or API and writes completed events back to CargoWise through eAdaptor. Reading a document and creating or amending the CargoWise record itself is the document-capture half, which is a different tool's job, not Expedion's. Expedion also does not run accounting, customs filing, or warehouse workflows.