Skip to content
Home » CustomCo

CustomCo

CustomCo integration

CustomCo transportation data, connected.

Plan a CustomCo integration that brings approved carrier data into FTM and Salesforce. Because CustomCo supports customizable electronic connections, the project can focus on the quoting, tracking, document, or data-exchange workflows your operation actually needs.

Custom integration scopeAccount access required
CustomCo Integration BlueprintPlanning
Carrier sourceCustomCo services
Operational destinationFTM in Salesforce
WorkflowQuoting
WorkflowTracking
WorkflowDocuments
Carrier-supported pathsEDI and API
Additional optionWeb XML

Planning illustration only. Final interfaces, fields, and workflows require CustomCo confirmation and implementation.

CustomDefined around your use case
SalesforceOperational system of record
EDI/APICarrier-supported options
Account-basedAccess must be confirmed
Five step workflow

How a CustomCo integration project moves from idea to production

First, the team defines the operational result it needs. Then FTM and CustomCo access requirements are confirmed before any fields, endpoints, or automated actions are treated as production-ready.

01

Define the workflow

First, choose the business process, such as quoting, tracking, documents, pickup events, or invoicing.

02

Confirm carrier access

Next, CustomCo confirms the electronic service, account permissions, credentials, and technical documentation available.

03

Map the FTM records

Then, the team maps carrier fields and events to Lane Quotes, Loads, documents, or related Salesforce records.

04

Build and test

Afterward, the connection is tested with approved sample data, error cases, authentication, and expected responses.

05

Release the workflow

Finally, validated data appears in the selected FTM workflow with monitoring and clear ownership for support.

Important: This page describes an integration planning path. It does not present every CustomCo web feature as an active, prebuilt FTM connector.

Capability planning

Choose the CustomCo data that should support your FTM workflow

CustomCo publicly provides online quoting and shipment tracking, while also describing customizable EDI, API, and web-based XML options. However, a useful FTM project begins by selecting the data that improves a real operating process.

Potential CustomCo data domains

These carrier capabilities can guide discovery, although access must be confirmed.

QuotingRates and service options
TrackingStatus and movement history
ReferencesShipment, BOL, PO, or PRO data
DocumentsAuthorized carrier images
EventsPickup and delivery milestones
BillingElectronic invoice data

Possible destinations inside FTM

After the scope is approved, selected data can support the records and users that need it.

  • Lane Quote context for approved rate information
  • Load milestones for approved tracking events
  • Related files for authorized document retrieval
  • Billing records for supported invoice data
  • Operational alerts for selected exceptions
Implementation guardrail: A public portal feature does not automatically mean a programmatic interface is enabled for every customer. Therefore, access and documentation must be confirmed first.
Clear integration scope

Carrier capability is not the same as a live FTM connector

CustomCo offers customer-facing technology and customizable electronic connections. Nevertheless, the exact FTM workflow depends on the services CustomCo enables for your account and the project FTM implements.

Verified carrier capabilities

Online services and customizable data exchange

CustomCo publicly supports online quoting and tracking. In addition, the carrier describes EDI, API, web-based XML, and electronic invoicing options.

Requires project confirmation

FTM endpoints, fields, and automated actions

However, this page does not claim that quoting, tracking, documents, pickups, invoicing, or EDI are already active in FTM. Each item requires approved access, mapping, implementation, and testing.

Why connect the systems

Put approved CustomCo data beside the transportation record it supports

Instead of treating carrier information as a separate portal task, a configured integration can connect selected data to the relevant FTM record. Consequently, operations can work with carrier context inside the Salesforce workflow.

1

One operational context

Because selected carrier data can connect to the load or quote, users spend less time matching information manually.

2

A purpose-built scope

Moreover, the project can prioritize the workflow with the clearest value instead of connecting data that no one uses.

3

Controlled implementation

Finally, authentication, mappings, failures, and support ownership are tested before the workflow reaches production.

Before and after

What changes after the approved CustomCo workflow is connected

Without an integration, users often move between the carrier portal and the transportation record. With a configured CustomCo integration, however, selected data can appear where operations already manage the shipment.

Without the integration
  • Open a separate carrier workflow
  • Search by shipment or reference number
  • Copy selected information manually
  • Match the result to the correct FTM record
With the integration
  • Use the mapped FTM record as context
  • Exchange only approved fields and events
  • Apply tested validation and error handling
  • Review connected data inside Salesforce
Potential project outcomes

What a properly scoped CustomCo integration can support

01

Less portal switching

First, approved carrier information can reach the FTM record where the user already works.

02

Connected shipment status

Next, authorized tracking events can support load visibility when programmatic access is available.

03

Consistent field mapping

In addition, identifiers and carrier values can follow tested mapping rules instead of manual interpretation.

04

Document context

Likewise, authorized carrier documents can be associated with the correct Salesforce record when the chosen interface supports retrieval.

05

Structured data exchange

Because CustomCo describes EDI, API, and XML options, the project can evaluate the path that fits the approved use case.

06

A scalable first phase

Finally, teams can begin with one valuable workflow and expand only after the first connection performs reliably.

Explore more
CustomCo FAQ

Questions about the CustomCo integration

For planning guidance, the FTM team can review your desired workflow, available CustomCo access, record mappings, and implementation requirements.

It is a custom integration project that connects approved CustomCo carrier data or events to selected FTM records and workflows in Salesforce. The final function depends on the electronic services and account permissions CustomCo confirms.
CustomCo and FTM

Define the right CustomCo workflow for your FTM operation

Bring the carrier process you want to improve, whether it involves quoting, tracking, documents, pickup events, or structured data exchange. Then the FTM team can help define the access, mappings, implementation, and testing required.

CustomCo account access and technical confirmation are required. Final scope depends on the approved electronic services and customer requirements.

Leave a Reply

Your email address will not be published. Required fields are marked *

Let's Talk!

Thanks for stopping by! We're here to help, please don't hesitate to reach out.

Watch 3-Min Demo
↑