Quick Overview
VelocityOS and CargoWise can work together rather than as replacements, with Velocity acting as a modern front end over CargoWise as the back-office system of record. On October 31, 2025 WiseTech moved customers to a per-transaction Value Pack bundling over 216 modules, adding a $19.95 automation fee per import container with an inland leg and $9.95 per standalone customs entry.
CargoWise Value Pack Explained: What Changed in October 2025
On October 31, 2025, WiseTech Global announced its largest commercial overhaul in more than a decade. By December 1, 2025, approximately 95% of CargoWise customers had been transitioned, mandatorily, from the legacy seat-based licensing model to a new per-transaction "Value Pack" structure that bundles more than 216 modules and AI-driven features into a single offer priced by usage.
The mechanics are straightforward in principle: every full import container with an inland leg now carries a documented $19.95 automation fee; every standalone customs entry is billed at $9.95. In practice, those line items compound across every booking, every milestone update, every entry and forwarders began seeing the result in the first invoices that landed in January 2026.
What the documented numbers actually look like
- Cost increase range: 20–50% above prior-year billing for the typical mid-market forwarder, with extreme cases as high as +150% reported by industry commentators. Mid-range observation tends to cluster between 25–35%.
- Notice period for some enterprise customers: as short as three business days before the new model went live, with monthly invoices jumping by $35,000+ in the most cited cases.
- Annual impact at scale: shippers moving 100,000 TEU per year are reported to be facing additional costs of $1.5–$2.4 million, depending on service tier.
- Forecast revenue uplift for WiseTech: approximately 6% projected revenue lift across FY26-FY27, drawn from this single commercial change, meaning the increase is not symbolic, it's structural.
- Market position behind the change: CargoWise holds an estimated ~70% share of the international freight forwarding TMS market and sits inside a parent company with a ~$16 billion market capitalization. Forwarders describe the dynamic as a "monopoly" precisely because there is no easy walk-away option.
Why the conversation is louder than the price tag alone
If this were a clean price increase, the industry would have absorbed it and moved on. Instead, two specific events compounded the cost shock:
First, on the eve of Black Friday 2025, WiseTech is reported to have logged into customer production environments to push the new commercial model live. Jamie Andrade, SVP Product Management at SEKO Logistics, described the experience publicly on LinkedIn:
"It was like an episode of Black Mirror, logging directly into your production environment the eve of Black Friday."— Jamie Andrade, SVP Product Management, SEKO Logistics (LinkedIn, December 2025; cited by The Loadstar)
Second, the rollout's communication left long-time customers feeling that core change-governance norms had been bypassed. Anthony Miller, a former WiseTech M&A team member turned freight tech commentator, captured the gap between commercial intent and execution in a widely-shared LinkedIn post:
"The new commercial model is quite brilliant. The execution? Not good. Not good at all."— Anthony Miller, freight tech commentator (LinkedIn, December 2025)
By February 2026, the conversation had moved from confusion to financial planning. Capterra's CargoWise One profile shows a 2.9 / 5 overall rating with Customer Service at 1.9 / 5 as of March 13, 2026, the lowest sub-score on the page. Aggregate review themes that show up repeatedly include "raised prices four times," "extremely complicated costing," and the inability to confidently forecast a forwarder's monthly software bill from one month to the next.
WiseTech's CEO Zubin Appoo, who returned to the role in September 2025, has framed the shift as a structural reset rather than a price hike:
"This isn't just a price rise, it's the release of more than 200 new features."— Zubin Appoo, CEO, WiseTech Global (cited by The Loadstar, ~February 2026)
The honest reading: Value Pack is permanent. Forwarders are not waiting for it to be reversed. The decision in front of every CargoWise customer is no longer whether the cost base has changed, it is what to do about the part of the workflow that is the most fee-sensitive: the quote desk.
Should You Complement CargoWise or Replace It?
Start by identifying which workflows need improvement. If your main challenges involve maintaining rates, preparing quotes or giving customers online access, evaluate whether a connected platform can address those needs while your existing TMS continues to support operations.
A full replacement requires a broader assessment. It may involve moving operational records, rebuilding integrations, validating financial processes and retraining teams. Compare that scope with a more focused project before choosing an approach.
Define what each system will manage
Create a workflow map before discussing implementation. For each activity, record the current system, the proposed system and the information that must pass between them.
| Workflow | Question to resolve |
|---|---|
| Rate management | Where will rates be maintained, validated and updated? |
| Customer quoting | Which system will calculate prices, apply approvals and issue quotes? |
| Booking creation | How will an accepted quote become an operational booking? |
| Customer records | Which system owns the customer record, and how will changes be synchronized? |
| Shipment updates | Where will milestones originate, and how will customers receive them? |
| Customs and accounting | Which existing processes and records must remain available? |
| Documents | Where will documents be stored, and which teams need access? |
For a CargoWise and VelocityOS setup, confirm the required connector, supported data fields, direction of synchronization and handling of unsuccessful transfers. Include any configuration or development work in the implementation proposal.
Test the handoff before expanding
Begin with a defined workflow, such as preparing a quote and transferring an accepted shipment into operations.
Use representative shipments to check that customer details, charges, currencies, references and documents arrive correctly. Test amendments and failed transfers as well as successful bookings.
Expand only after the teams responsible for pricing, operations and finance agree that the workflow meets the acceptance criteria.
How to Calculate the Cost of Changing Your Quote Workflow
Build the comparison from your invoices, contract terms and actual team workload. Separate potential productivity improvements from software charges that will genuinely stop.
Moving quote preparation to another platform does not automatically remove charges associated with bookings, containers or customs entries that remain in the existing TMS.
Gather the costs that matter
| Cost category | Information to collect |
|---|---|
| Existing software | Subscription, user, module and transaction charges, including minimum commitments |
| Charges that could stop | Specific invoice items that the proposed change would eliminate, confirmed against contract terms |
| Additional platform | Subscription, usage limits, optional modules and support |
| Integration | Initial setup, connector charges, maintenance and monitoring |
| Implementation | Data preparation, configuration, testing and training |
| Parallel operation | Temporary overlap in subscriptions and staff workload |
| Internal administration | Time spent maintaining rates, correcting records and resolving synchronization errors |
Calculate first-year costs separately from ongoing annual costs. Implementation and parallel operation can make the first year more expensive even when later years show a benefit.
Use a transparent savings calculation
First-year net software saving = confirmed existing charges avoided − additional annual software and integration costs − one-off implementation costs
Measure staff-time improvements separately. Time released for other work is a productivity benefit; it becomes a cash saving only when expenditure actually falls.
Hypothetical example
Assume a forwarder confirms that a workflow change would remove $18,000 in annual charges from its existing software contract.
| Component | Illustrative amount (USD) |
|---|---|
| Confirmed annual charges avoided | $18,000 |
| Additional annual platform cost | $10,000 |
| Annual integration and support cost | $2,000 |
| One-off implementation and training | $4,000 |
| First-year net software saving | $2,000 |
| Following-year net software saving, with the same recurring costs | $6,000 |
These figures are hypothetical amounts in USD, not VelocityOS or CargoWise prices or promised results. Charges for retained workflows remain payable and are excluded from the avoided-cost figure.
If the existing contract does not allow the identified charges to stop, revise the calculation before making a purchasing decision.
Validate the business case in a pilot
Measure quote preparation time, correction rates, repeated data entry and successful booking transfers before and during the pilot.
Use those results alongside written supplier proposals to decide whether the change improves the workflow and justifies its total cost.
See Velocity in action
If your team is still quoting in spreadsheets, email chains, or disconnected tools, you don’t need “more effort”, you need an architecture that makes speed repeatable.
Build an instant quoting system with Velocity and move from 24 hours to 2 seconds without losing margin control.
What Stays in CargoWise vs. What Modernizes via Velocity: The 14-Module Decision Matrix
The biggest reason "partial migration" remains a vague phrase in industry coverage is that nobody publishes a module-by-module decision. Below is the matrix we use when scoping a CargoWise / Velocity coexistence, every line is mapped against the actual capabilities that each platform owns today.
| CargoWise module / function | Stay in CargoWise (back-office) | Modernize via Velocity (front-end) |
|---|---|---|
| Customs declarations (AES, ICS2, country filings) | ✓ Stay | |
| Accounting, invoicing, accruals, GL posting | ✓ Stay | |
| eDocs, B/L generation, transport instructions | ✓ Stay | |
| Audit log & compliance reporting (5–7 year retention) | ✓ Stay | |
| Historical shipments, closed bookings, archived files | ✓ Stay (read-only OK) | |
| Carrier execution data, manifest generation | ✓ Stay | |
| Operational reporting (back-office KPIs) | ✓ Stay | |
| Rate management (buy/sell rates, surcharge schedules) | ✓ Modernize via Velocity Rate Management | |
| Quote desk (multi-modal quote generation, branded PDFs) | ✓ Modernize via Velocity Quote Management | |
| Surcharge & accessorial naming + normalization | ✓ Modernize (AI-driven via Velocity charge normalization) | |
| Customer-facing portal (self-serve quotes / bookings / tracking) | ✓ Modernize via Velocity Digital Freight Portal | |
| Sales pipeline, opportunity tracking, lead routing | ✓ Modernize via Velocity CRM Integration | |
| Pricing rules, markup governance, customer-specific logic | ✓ Modernize (Velocity pricing rules engine) | |
| Sales analytics, win-rate reporting, customer trends | ✓ Modernize (Velocity analytics dashboard) |
Why this asymmetry works
Notice the dividing line: every module that keeps a regulator happy stays in CargoWise; every module that touches a customer's perception of speed and clarity moves to Velocity. The Value Pack per-transaction model penalizes the second category disproportionately, every quote, every milestone touch, every portal interaction is a metered event — while the first category is just doing the audit-trail work it has always done.
The asymmetry also resolves the "monopoly" complaint without forcing a confrontation with it. CargoWise's strength, 20-country customs coverage, deep accounting integrations, regulator-trusted audit infrastructure, is not what most forwarders are angry about. The anger sits on the commercial side, where the per-transaction model rewires the relationship between revenue and software cost. Velocity sits exactly in that gap.
The 12-Week Front-End Modernization Plan (Without Touching the Back-Office)
This plan is built on Velocity's documented phased modernization framework (Rates → Quotes → Portal → Operations) and adapted to a CargoWise-coexistent setup. The structure intentionally separates "what the sales team learns" from "what the operations team sees", operations sees nothing, by design.
| Week | Activity | Velocity capability |
|---|---|---|
| Week 1–2 | Audit current CargoWise quote-desk workload. Export rate sheets, contracted lane schedules, and active customer master data via XML / eDocs / standard CargoWise export formats, keeping the audit trail intact. Decide what NOT to migrate (closed shipments, historical declarations stay where they are). | Discovery / scoping |
| Week 3–4 | Velocity sandbox provisioning. Map exported customer master into Velocity CRM. Configure pricing rule policy, markup logic, and customer-specific exceptions. No production traffic yet. | Rate Management setup |
| Week 5–6 | Rate management goes live in Velocity. The AI charge normalization engine consolidates inconsistent surcharge naming across carriers and agents. Pricing analysts validate normalized output against CargoWise rate output for the same lanes. | AI Charge Normalization |
| Week 7–8 | Quote workflow goes live. For 14 days, quotes run in parallel, sales team produces quotes from both CargoWise and Velocity, and pricing analysts compare totals, breakdowns, and validity logic for consistency. | Quote Management |
| Week 9–10 | White-labeled customer portal launch. Beta customers (typically 5–10 accounts) move to Velocity's portal for quote viewing, acceptance, document upload, and milestone tracking. CargoWise customer-facing email flows continue in parallel during the beta. | Digital Freight Portal |
| Week 11–12 | TMS integration goes live: accepted quotes flow from Velocity to CargoWise via API, triggering booking creation in CargoWise. Operations team sees a CargoWise booking exactly the same way they always have. The quote-desk transition is complete. | TMS Integration |
What you DON'T migrate (the most-skipped detail in industry coverage)
Most published "CargoWise migration" content treats data export as a binary problem: extract everything, import everything. In a partial-modernization architecture the answer is the opposite, extract narrowly, leave most of the data behind. Specifically:
- Closed shipments older than 90 days: stay in CargoWise. They are the audit trail; moving them is the highest-effort, lowest-value part of any migration.
- Historical customs declarations: stay in CargoWise. Customs auditors will look here; do not duplicate the file in two systems and create a reconciliation problem.
- Closed accounting periods: stay in CargoWise. Accounting reconciliation should never have two sources of truth.
- What you DO move: open quotes within their validity window, active customer master records, current rate sheets and surcharge schedules, contracted lane definitions, and the pricing-rule logic the sales team uses today.
The principle is simple: migrate the active, leave the closed. The sales team is rebuilt around Velocity in 12 weeks; the customs team's day doesn't change.
Audit Trail Continuity: How Read-Only CargoWise Access Works for 6-12 Months
One question stops most partial-migration conversations cold: what happens to the audit trail? US AES filings, EU ICS2 declarations, and most national customs regimes require records to be retrievable for 5 to 7 years. A forwarder cannot simply terminate CargoWise on day 90 of the migration, the records have to remain accessible to auditors, regulators, and the forwarder's own compliance team.
The clean answer in a Velocity-on-top architecture is read-only CargoWise access for 6 to 12 months after the front-end transition completes:
- Seat reduction, not seat termination. Operator seats that were used purely for quoting can step down to read-only seats over the 6–12 month window. The license cost drops; the data access stays.
- Operations team continues unchanged. Customs brokers, accounting staff, and the operations control tower all keep their existing CargoWise access. No retraining, no broken workflows, no compliance gap.
- Audit retrievability is preserved. When an auditor asks for a 2024 customs declaration, it is exactly where it has always been, in CargoWise, and the read-only access ensures the forwarder can pull it without paying for active operator seats.
- Optional: cold-storage export at the end of the read-only window. At month 12 (or whenever the forwarder is comfortable), a structured export of remaining audit-trail data can be archived to long-term storage, and CargoWise access can be terminated. The decision is operational, not architectural, most forwarders choose to keep read-only access live for the full retention window.
The audit trail problem is not handled by Velocity's data model. It is handled by leaving CargoWise's data model exactly where it is and letting the regulators interact with the system that was certified for that purpose. That is the entire reason "complement" is structurally safer than "replace", the highest-stakes data never moves.
Anonymized Migration Story: A 60-Seat European Forwarder's Front-End Switch
A European-based 60-seat freight forwarder, eight years on CargoWise across two regional offices, completed a front-end modernization in 11 weeks at the start of 2026. The trigger was the first January Value Pack invoice: container automation fees pushed the monthly CargoWise spend roughly 38% above the previous quarterly average, with no clear way to recover the cost in customer pricing.
The forwarder did not change customs broker software, accounting, or eDocs. CargoWise stayed in place for everything that touched a regulator. What moved was the commercial layer: 14 sales coordinators and 3 pricing analysts moved to Velocity for rate management, quote generation, pricing-rule governance, and a branded customer portal. CargoWise read-only access was provisioned for 12 months to preserve audit retrievability.
By week 11, quote turnaround time on contracted lanes had moved from a working-day cycle to under 6 minutes end-to-end. Estimated monthly savings on the Value Pack commercial-layer fees landed in the ~$11,000 / month band, while the customs and accounting infrastructure stayed exactly where it had always been. The audit trail was preserved through CargoWise read-only access.
The story is anonymized by request. The structural pattern, partial migration, sales-side transition only, audit trail preserved through CargoWise read-only access, is not unusual. It is the default play once a forwarder accepts that the cost asymmetry between commercial-layer activity and back-office customs work is real.
See Velocity in action
If you are sitting on a January 2026 invoice that has changed the shape of your monthly CargoWise spend and a full replacement still doesn't work for your customs footprint, the front-end path is the conversation worth having. Talk to us about your front-end switch, we'll map your CargoWise quote-desk workload to a 12-week Velocity transition plan, with the back-office staying exactly where it is
FAQ: 10 Questions Forwarders Ask About Adding Velocity to CargoWise
No. The architectural goal is the opposite: keep CargoWise as the system of record for customs, accounting, eDocs, and audit trail. What changes is the seat composition — some operator seats can step down to read-only access over 6–12 months as the quote desk transitions to Velocity, but the platform itself stays live.
Export the active operating data: open quotes within their validity window, current rate sheets and surcharge schedules, active customer master records, contracted lane definitions, and the pricing-rule logic the sales team uses today. Leave the rest in CargoWise, closed shipments, historical customs declarations, closed accounting periods, and the audit trail belong where the regulator already trusts to find them.
Through Velocity's TMS Integration layer. When a customer accepts a quote in the Velocity portal, the data flows to CargoWise via API and creates a booking, operations sees a familiar CargoWise booking, with no manual re-entry. The sales team's tool changed; the operations team's screen did not.
The documented Value Pack components are $19.95 per full import container with an inland leg and $9.95 per standalone customs entry, layered on top of the Value Pack subscription tier. Industry-typical cost increases versus the prior seat model fall in the 20–50% band. The calculator framework in §3 above sizes the quote-desk-only portion of that spend so you can isolate exactly which part of the bill is sensitive to a partial-migration architecture.
Yes — that's the structural premise of the front-end modernization. Customs declarations (AES, ICS2, country-level filings), accounting, eDocs, transport instructions, and the operational reporting your back-office team relies on continue running inside CargoWise. No retraining, no migration window for the operations side.
Yes. Closed shipments, historical declarations, and closed accounting periods stay in CargoWise; read-only access during the 6–12 month transition window keeps every audit query answerable in the system the regulator is already familiar with. New quotes generated after go-live live in Velocity.
Two weeks is the typical parallel window for the quote workflow (Weeks 7–8 in the plan in §5). During that time, sales produces quotes in both systems and pricing analysts validate that totals, breakdowns, and validity logic match. Two weeks tends to be enough to surface edge cases (multi-currency rounding, complex surcharge stacks) without dragging the transition into a multi-month parallel cost.
No. CargoWise certification covers operations, customs, and back-office workflows — the exact areas that don't move in this architecture. The operations team keeps its certifications, its training, and its day-to-day tool. The retraining burden is concentrated on the sales / quote desk roles, typically 8–14 people in a 60-seat forwarder, learning Velocity over 2–4 weeks.
Yes, and most forwarders should. The DSV pattern (region-by-region partial migration, ~30% of operations as of February 2026) is the precedent. Starting with a single region, typically the one with the highest commercial-layer Value Pack exposure, lets the team validate the Velocity workflow on a contained footprint before extending it across the rest of the network.
Velocity prices on a flat platform model, sized to volume in the demo conversation rather than metered per booking. The point of the front-end architecture is precisely to remove the per-transaction compounding that the Value Pack model creates on the commercial side; routing the quote desk to a flat-fee platform is what makes the cost math work.