Does this require access to the full CargoWise Landside suite, or just Profit Tools?

It depends on what a specific carrier already runs, not on a fixed requirement from Doublefast. Profit Tools TMS is one product inside the broader CargoWise Landside portfolio, which also includes Trinium, Compcare, and GTG TMS, among others. A carrier running Profit Tools alone doesn’t need to license additional Landside modules for this architecture to work — what matters is confirming, during discovery, exactly which modules the carrier’s WiseTech agreement covers and which of those hold the data an integration would need to touch.

How does this interact with an existing Samsara integration?

If a carrier already runs the documented Samsara–Profit Tools integration — which syncs driver available hours and vehicle location into the Profit Tools dispatch board for current Samsara and Profit Tools customers — that data is already inside Profit Tools by the time Doublefast’s architecture would touch it, so there’s no conflict to resolve. Doublefast’s terminal and container monitoring covers a different category of data (LFD, holds, appointment status) than the driver-availability and location data Samsara feeds in, so the two can run alongside each other.

Is Doublefast a certified Profit Tools or WiseTech integration partner?

No. Doublefast is not a certified Profit Tools or WiseTech partner, and nothing on this page should be read as claiming that status. What CargoWise and Samsara publish confirms that Profit Tools supports external system connectivity in at least one documented case (the Samsara integration); what any specific carrier’s account and module licensing support for a new connection has to be confirmed directly, not assumed from a partner listing.

What if our IT team requires a formal security review before any external system connects?

That’s common in enterprise CargoWise Landside environments, and it’s one of the first things we’d expect to work through during discovery rather than after. Enterprise carriers running WiseTech products often have a defined vendor-approval process — security questionnaires, data-handling review, sometimes a formal IT sign-off — before any new system, including Doublefast, is authorized to connect. Building that timeline into the plan up front avoids a surprise delay later.

Does Doublefast replace Profit Tools or CargoWise Landside?

No. Doublefast is built to run alongside an existing TMS, including Profit Tools, rather than replace it. Profit Tools/CargoWise Landside would remain the system of record for dispatch, billing, and track-and-trace; Doublefast’s role is the operating layer around it — data intake, normalization, monitoring, and human-reviewed output — not a swap-in replacement.

INTEGRATIONS

Profit Tools Integration Architecture for Drayage Automation

This page covers how Doublefast's operating layer can connect to a Profit Tools/CargoWise Landside-based drayage operation: where incoming order and terminal data comes from, how it gets normalized into structured records, how a handoff to Profit Tools or another system can work through an EDI feed, an API, or another interface where one is available, how terminal and container monitoring runs alongside that, where human review sits in the flow, and how status updates, documents, and billing data go back out. It is the technical/architecture companion to our more conceptual explainer on how AI can work alongside Profit Tools.

Last reviewed: August 17, 2026. This analysis was prepared by Doublefast.

Doublefast prepared this analysis and may be considered a competitor or complementary provider. Product details and pricing can change. Verify final requirements and pricing directly with each vendor.

Architecture

How the integration architecture works

Profit Tools TMS is one drayage-focused product inside WiseTech Global's CargoWise Landside portfolio, which also lists other drayage TMS products such as Trinium, Compcare, and GTG TMS. At a high level, the flow between a carrier's data and a Profit Tools-based operation is a chain of six steps. Each is described in its own section below with the honest caveats that apply to it — this is a description of how the pieces fit together, not a claim that every step is turnkey or already certified for every Profit Tools account.

Incoming data

INTAKE

Terminal websites, EDI feeds, email, PDFs, and the carrier’s own Profit Tools records arrive continuously and in mixed formats.

Normalization

NORMALIZE

Raw inputs are parsed into structured records: container number, LFD, appointment window, accessorials, and status.

Profit Tools / API / EDI handoff

HANDOFF

Structured records are made available to Profit Tools or another downstream system through whichever interface the carrier’s WiseTech account and trading-partner setup support.

Terminal & container monitoring

MONITOR

Container and appointment status is checked against live terminal data on an ongoing basis, independent of how the handoff step is configured.

Human review

REVIEW

Defined checkpoints hold ambiguous data, exceptions, and anything touching money or dispatch for a person to confirm.

Outbound data

OUTBOUND

Confirmed status updates, documents, and billing data flow back out to customers, drivers, and the carrier’s billing stack.

Step 1

Sources of incoming data

A drayage operation running Profit Tools rarely has all of its data inside Profit Tools alone. Order and status information typically arrives from several places at once:

Terminal websites. Container status, LFD, appointment availability, and hold information published directly by the terminal.
EDI feeds. Order (204), status (214), or invoice (210/990) transactions where a trading-partner relationship already exists.
Email and PDFs. Delivery orders, rate confirmations, and accessorial notices sent the way customers and brokers already send them — the same category of input CargoWise Landside's own Order Automation product is built to parse, accepting PDF, CSV, and XLS delivery orders by upload, drag-and-drop, or email forwarding.
The carrier's own Profit Tools data. Loads, driver assignments, and status already recorded inside the carrier's existing Profit Tools account — including any driver-availability or vehicle-location data already synced in via an existing telematics integration such as Samsara.

See our dedicated pages on terminal integrations and email and document intake for more on how each of those source types is handled on its own.

Step 2

Data normalization

Each of those source formats represents the same handful of facts — container number, LFD, appointment window, addresses, accessorials, status — differently. The normalization step takes the raw input, regardless of source format, and maps it into one structured record shape before anything downstream touches it. This is what makes a terminal-website update, an EDI 214, and a PDF delivery order comparable to each other, and it is what a downstream handoff (Profit Tools, another TMS module, or a billing system) actually consumes.

Step 3

Profit Tools / API / EDI handoff

Once data is normalized, it needs a way into (or out of) Profit Tools or whatever system the carrier runs day to day. CargoWise's own Profit Tools TMS product page describes order management, dispatch, billing/settlements, and track-and-trace modules in detail, but it does not publish EDI standards or a public API reference the way we could point to for some other platforms — so we're not going to claim we found a documented Profit Tools API surface there. What is documented: CargoWise Landside's separate Order Automation product, which uses machine learning to parse PDF, CSV, and XLS delivery orders and, per WiseTech's own description, sends orders “directly into your TMS after a quick review or automatically once the required data threshold is met.” Separately, Samsara publishes a live, working integration with Profit Tools that syncs driver available hours and vehicle location data between the two platforms for current customers of both, available in the US and Canada — concrete, third-party evidence that Profit Tools already supports external system connectivity through its own ecosystem, not just internally.

None of that is the same thing as Doublefast holding a live, certified integration with Profit Tools or CargoWise Landside today — it does not, and we are not going to claim otherwise. What it means in practice: depending on which Landside modules a carrier is licensed for, whether an EDI trading-partner relationship already exists within the WiseTech ecosystem, and whether the carrier already runs the Samsara integration described above, a handoff to or from Profit Tools can potentially be built through an EDI feed, a flat-file exchange, or another interface that specific account supports. Which of those is actually available, and what scope it covers, has to be confirmed for each customer's account and cannot be assumed from this page alone.

For a broader look at how this compares across TMS platforms generally, see our TMS integrations page and our overview of drayage TMS platforms.

Step 4

Terminal and container monitoring

Profit Tools' own track-and-trace module already covers port/terminal information, geofencing, container holds, and yard-duration tracking, per CargoWise's product description. In parallel with whatever handoff path is in place, Doublefast's architecture checks container and appointment status against live terminal data on an ongoing basis: LFD changes, appointment availability, holds, and gate activity. This monitoring runs independently of the Profit Tools handoff step — it is watching the terminal, not just watching Profit Tools — so status updates can be caught even if the only path back into a carrier's system of record is a manual one for a given account.

Step 5

Recommended human review points

This is the explicit control boundary in the architecture. Regardless of which handoff path is configured, we recommend a person confirm before anything crosses these lines:

Any record with a missing or ambiguous field the normalization step could not resolve.
Any write back into Profit Tools or another system of record, before it is committed.
Any change to an accessorial charge, rate, or invoice line before it goes to billing.
Any dispatch-affecting change — driver assignment, appointment time — before it is sent.
The first several transactions on any newly configured handoff path, as a validation period.

Where those review points sit, and who staffs them, is part of what gets defined during the discovery process described below — not something fixed in advance for every account.

Step 6

Outbound status updates, documents, and billing data

Once a record has cleared any relevant review point, the same normalized structure supports outbound flow in the other direction: status updates to customers and brokers, delivery documents and proof of delivery, and billing data pushed to whichever billing stack the carrier actually uses — that may be Profit Tools' own billing and settlements module, or a separate accounting or factoring system downstream of it. Our TMS integrations page covers what that billing and status handoff looks like in more detail once data is already structured.

Want to walk through what this looks like for your specific Profit Tools setup?

Discuss your current TMS setup

Before You Start

Implementation discovery checklist

A CargoWise Landside environment tends to sit inside a larger enterprise IT footprint than a standalone drayage TMS. Before any integration work starts, a carrier's team should be able to answer, or go find the answer to, each of these:

1Whether the carrier’s WiseTech agreement covers Profit Tools alone or a broader set of CargoWise Landside modules, and which of those modules are actually active.
2Whether the carrier’s IT or enterprise procurement process requires a formal vendor security review or approval before any external system can connect.
3Whether an EDI trading-partner relationship (ISA/GS identifiers, VAN) already exists within the WiseTech/CargoWise ecosystem.
4Whether the carrier already runs the documented Samsara–Profit Tools integration, and what driver-hours and location data is already flowing into Profit Tools as a result.
5Which terminals and port complexes the fleet operates at, and whether existing terminal-website credentials are available.
6What sits downstream of Profit Tools today — billing/accounting software, a factoring company, or a customer portal.
7Who inside the carrier’s organization (or its WiseTech account team) owns admin access and can authorize a new connection.
8What status, document, and billing data the carrier’s customers or brokers expect to receive, and how often.

Dependencies

Required permissions and dependencies

None of these are things Doublefast can supply on its own — each depends on what the carrier's Profit Tools/CargoWise Landside licensing, EDI relationships, and internal (or WiseTech account team) admin access already look like.

Required permissions and dependencies for a Profit Tools integration
Dependency	What it means
Confirmed module scope	A written answer to whether the license covers Profit Tools alone or additional CargoWise Landside modules, and which of those hold the data an integration would need to read or write.
Enterprise IT/security approval	Enterprise carriers running WiseTech products commonly require a formal vendor-review process — security questionnaires, data-handling sign-off — before any new system is authorized to connect.
EDI trading-partner setup within the WiseTech ecosystem	If the handoff is EDI rather than API, this means confirmed ISA/GS identifiers and a working relationship with the carrier’s VAN or EDI provider inside that ecosystem.
Written authorization from the account owner	Doublefast does not self-provision access to a carrier’s Profit Tools account. Credentials and scope are issued by the carrier’s own admin or WiseTech account team.
Defined user roles for review dashboards	Anyone doing manual review needs an assigned role and login, scoped to only what that review step requires.
Agreement on which fields are read vs. written	A specific, written list of what Doublefast is authorized to read from Profit Tools and what, if anything, it is authorized to write back.

Integration availability and scope must be confirmed for each customer. Nothing on this page should be read as a promise of a turnkey, pre-certified Profit Tools or CargoWise Landside integration — what's possible depends on the specific account and its module licensing.

FAQ

Frequently asked questions

Tell Us What's Slowing
Your Team Down

We'll show you how Doublefast fits into your current stack, starting with the workflow costing you the most.

Request a Conversation

Profit Tools Integration Architecture for Drayage Automation

How the integration architecture works

Sources of incoming data

Data normalization

Profit Tools / API / EDI handoff

Terminal and container monitoring

Recommended human review points

Outbound status updates, documents, and billing data

Implementation discovery checklist

Required permissions and dependencies

Frequently asked questions

Tell Us What's SlowingYour Team Down

Tell Us What's Slowing
Your Team Down