Ward Transport integration

Ward Transport LTL rates, connected.

Q: Does the Ward Transport integration book shipments?

No. The documented FTM class is rate-only, so booking is not implemented in this integration.

Q: Which shipment fields are required for a Ward Transport rate?

FTM requires configured Ward Transport credentials and Lane Quote data that includes pickup and delivery city, state, and ZIP, plus freight class, weight, pieces, handling units, and payment method.

Q: Can the current Ward Transport request send multiple line items?

Not without an extension. The current code sends one DetailItem, although the Details structure can be extended when multiple line items are required.

Q: What happens when Ward Transport does not return a usable rate?

If the net charge is missing, invalid, or zero, FTM falls back to a no service availability message. If transit days are missing or invalid, that value remains empty.

Q: What is needed to activate the Ward Transport integration?

You need Ward Transport web service credentials, a customer number, populated Lane Quote fields, endpoint access, and the appropriate Salesforce class permissions.

Request a Ward Transport LTL rate and transit estimate from an FTM Lane Quote in Salesforce. Because shipment details already live on the record, your team can quote without re-entering the same freight data on another website.

Live XML rate retrievalNet charge and transit days

Book a Demo See How It Works

FTM Lane QuoteConnected

OriginGlen Mills, PA

DestinationSeattle, WA

Freight classClass 85

Weight1,200 lb

Units3 pallets

Net charge$432.15

Transit estimate3 days

Illustrative data only. Actual results depend on account credentials and lane availability.

XMLDirect rate request

1 actionFrom the Lane Quote

LTLDomestic point rating

2 resultsCharge and transit days

Five step workflow

How the Ward Transport integration retrieves a rate

First, FTM uses the shipment information already entered on the Lane Quote. Then it sends a structured XML request and returns both available results to the same Salesforce workflow.

Open the Lane Quote

First, the user opens the relevant Lane Quote record in FTM.

Confirm freight inputs

Next, FTM uses origin, destination, class, weight, pieces, handling units, and payment method.

Request the Ward Transport rate

Then, the integration authenticates with the configured Ward Transport account and posts XML to the rate endpoint.

Parse the response

Afterward, FTM reads the net charge and the transit days when Ward returns them.

Review the result

Finally, the charge and transit estimate appear in the Lane Quote context, with safe fallbacks for invalid data.

Current integration scope: This workflow supports LTL rate and transit-day retrieval. Booking is not implemented in the documented Ward Transport integration class.

Data in, rate out

Use the Lane Quote data your team already entered

Because FTM maps Lane Quote fields into the Ward Transport request, users do not need to start another quoting session. In addition, the returned charge and transit estimate stay connected to the Salesforce workflow.

Inputs sent to Ward Transport

FTM builds the request from required account and shipment values.

OriginCity, state, and ZIP

DestinationCity, state, and ZIP

FreightClass and weight

HandlingPieces and pallets

PaymentPrepaid or collect

AccountConfigured credentials

Response shown in FTM

After Ward Transport responds, FTM parses the available values for the user interface.

Net charge returned as a readable value
Transit days returned as a number when present
No service availability fallback for missing, zero, or invalid results
Request and response traces available for troubleshooting
Results stay within the Lane Quote workflow

For calculations: Although the documented controller exposes a string for the interface, the value can be persisted to a Decimal field when arithmetic is required.

Clear integration scope

What the Ward Transport integration does today

The current FTM implementation is deliberately specific. Therefore, teams can evaluate the connection based on the live function that is documented, without confusing it with a broader booking or shipment-management suite.

Included now

LTL rate and transit-day retrieval

FTM posts Lane Quote data to the Ward Transport ratequote endpoint. As a result, users can review the returned net charge and available transit days in Salesforce.

Not included in this class

Booking and downstream execution

However, the documented integration class does not book freight. Tracking, pickup, eBOL, documents, tendering, invoicing, and EDI are not presented here as active FTM features.

Why connect rating

A cleaner way to bring Ward Transport pricing into daily quoting

Instead of moving between disconnected systems, the user initiates the request from the active Lane Quote. Consequently, the rate check supports a more consistent workflow for the operations and pricing teams.

Fewer repeated inputs

Because FTM reuses the record data, users avoid entering core freight details a second time.

Two connected results

Moreover, the Ward Transport charge and transit days appear in the Salesforce context where the quote is managed.

Graceful fallback

If no valid rate is returned, FTM provides a clear no service availability result instead.

Before and after

Keep the Ward Transport rate request inside FTM

Without a connection, a user may need to move shipment details into a separate carrier workflow. With the Ward Transport integration, however, the request begins from the Lane Quote.

Without the integration

Leave the active Salesforce workflow
Re-enter core shipment details
Move the result back manually
Risk separating the rate from its quote context

With the integration

Start from the FTM Lane Quote
Reuse mapped freight inputs
Send the XML request directly
Review charge and transit days in Salesforce

Practical outcomes

What FTM users gain from Ward Transport rate retrieval

Quicker rate checks

First, users can initiate the Ward Transport request from the record they already have open.

Customer-based pricing

Next, FTM authenticates with the configured Ward credentials and customer number rather than using generic pricing.

Consistent mapping

In addition, supported freight classes are mapped into the class codes expected by the carrier request.

Billing-term mapping

Likewise, FTM maps prepaid to PPD and collect to COD for the Ward Transport XML request.

Operational feedback

When a usable rate is unavailable, the user receives a clear fallback message instead of an unexplained blank.

Transit context

Finally, transit days can accompany the net charge when that value is present in the Ward response.

Explore more

Ward Transport FAQ

Questions about the Ward Transport integration

For setup guidance, the FTM team can review account access, required Lane Quote fields, and deployment prerequisites.

Talk to a Specialist

What does the Ward Transport integration in FTM do?

The integration posts a domestic LTL rate request to the Ward Transport XML ratequote endpoint. Then FTM parses the returned net charge and transit days for the Lane Quote interface.

Does the Ward Transport integration book shipments?

Which shipment fields are required for a Ward Transport rate?

Can the current Ward Transport request send multiple line items?

What happens when Ward Transport does not return a usable rate?

What is needed to activate the Ward Transport integration?

Ward Transport and FTM

See Ward Transport LTL rating inside a live FTM workflow

Bring your current quoting process to the conversation. Then the FTM team can show how Lane Quote data becomes a Ward Transport XML request and how the returned charge and transit days fit into Salesforce.

Book Executive Demo Explore the FTM Platform

Ward Transport account and web service credentials are required. Current documented scope is LTL rate and transit-day retrieval.

Ward