What the CargoWise Value Pack Change Means for Small Freight Forwarders

CargoWise’s published Value Pack list pricing charges by transaction. Its published version 26.10 lists $19.95 for an import FCL/FTL shipment and $9.95 for a stand-alone import customs procedure. The Forwarding Value Pack includes customs functions, so check which procedures are included with your forwarding shipments before adding separate customs charges. Your actual bill depends on your transaction mix and agreement. Ask CargoWise which listed charges apply to your jobs, then compare your current invoices with the previous arrangement. That gives you a real basis for deciding whether to absorb the fee, change systems, or reduce the manual work around CargoWise. TIO has no CargoWise adapter today, so its potential impact must be established in a scoped pilot.

WiseTech Global now publishes a CargoWise Value Pack model with a transaction-based Automation Fee. Review the current community pricing and your own agreement before comparing it with your previous bill.

For a small forwarder, the impact depends on the mix of shipments and stand-alone customs work.

What the published transaction fees cover

The CargoWise Value Pack pricing table lists different charges for forwarding shipments and stand-alone customs procedures. Its Forwarding Value Pack includes customs functions.

In the published table:

• Import FCL/FTL shipment: $19.95 per shipment
• Stand-alone import customs procedure: $9.95 per formal procedure

Check your contract for any other services or charges that apply to your account.

A hypothetical month with 200 import FCL/FTL shipments and 150 separate, stand-alone import customs procedures would produce $3,990 in forwarding fees (200 × $19.95) and $1,492.50 in stand-alone customs fees (150 × $9.95), or $5,482.50 for that month. At the same volume for twelve months, that is $65,790 in these listed fees. Do not count customs work included in a forwarding shipment again as a stand-alone procedure.

The increase or decrease against a previous bill cannot be determined from the list price alone.

WiseTech’s answer: pass it to the shipper

The official framing is that the Automation Fee is a disbursement, not a software cost. When configured correctly in CargoWise, it auto-posts to the customer invoice. The idea is that your P&L never sees it.

Passing the fee through depends on your agreement with the shipper and how you bill. If you absorb it, it reduces your margin; if you pass it through, the customer sees it. Model both cases against your own invoice mix.

Three realistic options

Option 1: Switch TMS

GoFreight, Magaya, and other platforms may be worth comparing if CargoWise no longer fits your operation. Request current written pricing and integration terms from each vendor.

The switch cost is real: historical data migration, retraining, parallel operation, and rebuilding integrations can outweigh a lower software price. Compare those costs with your actual CargoWise bill before deciding.

Option 2: Stay and hire more staff

The idea is to do more work by hand to avoid software charges.

That trade depends on which transactions are billable and how much manual work your team would take on. Measure the work before treating manual processing as a saving.

Option 3: Stay on CargoWise and add an AI inbox layer

The third option: keep CargoWise and automate the part of the workflow it was never designed to handle, getting data from emails into the TMS.

What an AI layer on top of CargoWise actually means

An AI layer sits between your email inbox and CargoWise, handling the coordination work your ops team currently does by hand. It does not re-create CargoWise’s job management, billing, or customs filing.

Every inbound freight email contains structured data. Pre-alerts carry the MBL, container number, vessel, voyage, ETD, and ETA. Booking confirmations have the shipper, consignee, HTS code, and lane. ISF worksheets have the party entities and filing fields. Your team reads each one and types that data into the CargoWise record.

The amount of manual entry varies with the documents, the TMS setup, and the team’s process. Track it on your own jobs before assigning a savings figure to automation.

An agent layer can read inbound freight documents, prepare fields, and send exceptions to a person. TIO has production adapters for other TMS platforms, but has not built a CargoWise adapter. TIO would first check your access and scope that connection before an agent could write to CargoWise. Each allowed action would have its own review setting.

The pilot would establish which prep can be automated and which decisions stay with your team.

The Automation Fee covers CargoWise transactions. An agent layer addresses the separate work of reading and preparing the information that arrives by email. Its impact on your operation needs to be measured in a pilot.

How to scope a TIO inbox layer for CargoWise

CargoWise can stay the system of record. The connection must be built before an agent writes to it.

1. Review access. Confirm which mailbox and CargoWise actions your team can authorize. TIO has no CargoWise adapter today.

2. Test the documents. Use your pre-alerts, booking confirmations, and arrival notices to see what fields an agent can extract and match to a shipment.

3. Build and test the adapter. Define the CargoWise fields and actions needed for the pilot, then validate the connection before enabling writes.

4. Set review rules. Agree which actions can run, which need review, and which must wait for a person’s reply.

5. Measure the pilot. Compare the agent’s output against your team’s work on real documents and check exceptions before expanding the workflow.

The CargoWise workflow remains in place. The inbox-to-TMS time saved, if any, should be measured from your pilot.

What does staying put actually require?

Staying on CargoWise calls for a review of the actual bill and the surrounding work. Price your transaction mix in dollars against the current agreement. Check which services your team uses and what your renewal terms permit. Then measure the time spent moving shipment information from email into the system. Those facts tell you whether to negotiate, change systems, or automate part of the prep.

The math

A hypothetical operation with the mix above would incur $65,790 over twelve months at the published list prices for those specific transactions. A customer with a different mix or contract will have a different bill.

For the labor side, record the number of emails your team handles, the time spent preparing each job, and the loaded cost of that work. Run a pilot before claiming that the time is recoverable.

You were already paying that time cost. It just showed up as payroll instead of a software invoice.

FAQ

Does TIO replace CargoWise?

No. TIO is an agent layer for freight operations, not a replacement TMS. TIO has not built a CargoWise adapter yet. We first check what your CargoWise access allows, then scope an adapter and pilot. CargoWise would remain your system of record.

Does TIO work if we stay on CargoWise at the new CVP pricing?

A CargoWise deployment needs a dedicated adapter that has not been built. Staying on CargoWise does not itself block a pilot, but TIO must check access, build the connection, and validate the workflow before any CargoWise write.

What does TIO actually do with the emails?

On supported TMS platforms, TIO agents read inbound documents, prepare shipment fields, and send exceptions to a person. No TIO agent writes to CargoWise today. A CargoWise pilot would define the adapter, allowed actions, and review settings before any write is enabled.

How long does it take to see results?

That depends on your mailbox access, document mix, and the CargoWise adapter work. TIO would scope a pilot on your own documents before setting a result or rollout date.

---

Request a demo to scope a CargoWise pilot against your own documents and access.