Mainfreight LTL V2 Onboarding Requirements and Configuration Guides [Information]

Modified on Mon, 23 Feb at 3:40 PM

This article serves as the central hub for integrating Mainfreight LTL V2 with techSHIP. It details the necessary credentials for onboarding, explains the configuration hierarchy required to start shipping, and outlines operational constraints specific to this carrier.

   

   
   

  

To review all supported carriers and their specific requirements, see: techSHIP supported Carriers - Master List [Guides List].

   

   

   

TABLE OF CONTENTS


Onboarding Requirements


Before configuring Mainfreight LTL V2 in techSHIP, you must gather specific credentials and verify account/workflow inputs required for rating and shipping. 


Information to be Provided


The following credentials and data points are mandatory to establish the connection. Ensure you have these items available before starting the setup:

     

DATA ELEMENTSOURCE (HOW TO OBTAIN)
API KeyProvided by Mainfreight for API access.
Account Number / Account CodeProvided by Mainfreight as the LTL account identifier.
Sender (Induction) Address
Provided by the shipper (warehouse/induction location). Required fields include Address 1, City, Postal Code, Country.
Pickup Window (Optional)Defined by the shipper (pickup open/close time, ready time, weekends mode) when used operationally.

   

Settings to be Verified


The following configurations must be validated to prevent errors during rating or shipment processing:

   

FEATURE/SETTINGVALIDATION ACTION
Rating InputsConfirm your workflow provides a Delivery Date for rating requests, or that it is defaulted (for example, to Pickup Date).
CoverageConfirm shipment lanes match carrier support: US Domestic/Regional and US → Canada for international.
Weight FormatConfirm weights are provided as whole numbers (no decimals).
Document TypeConfirm your Baseline configuration selects the required Label type (US Label or US BOL) per operational need.

   



Rating requests require a Delivery Date. If your source system does not provide it consistently, default it (for example, to the Pickup Date) before rate shopping or processing shipments.

 
   

   

   
   

  

Mainfreight LTL V2 supports PDF documents only. Select the required document type in the Baseline Account: US Label or US BOL.

   

   

   

Configuration Hierarchy and Guides


To establish a valid connection and start shipping, you must complete the mandatory levels in the following order: 


Gather Onboarding Requirements  

Carrier Baseline Account 
Client (Billing) 
Account 


Use the table below to access the detailed configuration guides for each level:

   

LEVELCOMPONENTMANDATORYSCOPEDESCRIPTIONCONFIGURATION GUIDE
1Onboarding RequirementsRequirementsYou are here.
2Baseline AccountCarrierEstablishes the core technical connection. Must be created first.[ADD LINK]
3(Billing) Account
ClientConnects a specific client to the Baseline. At least one is required to ship.[ADD LINK]
4Order Settings   TransactionDefines advanced service options.[ADD LINK]

   

Carrier Specifications and Constraints


This section outlines specific operational behaviors and data limitations inherent to the Mainfreight LTL V2 integration. 


Label References


While techSHIP supports the mapping of references within your labels, the final output is determined by the carrier's capabilities. The table below specifies the hard limits enforced by Mainfreight LTL V2. Data exceeding these limits may be truncated on the physical label or cause processing errors:

   

CONSTRAINT TYPELIMIT/REQUIREMENTNOTES
Max. References Supported[Technical validation required]Confirm how many references are exposed/printed by Mainfreight LTL V2 documents.
Character Limit[Technical validation required]Confirm per-field length constraints (if any) for Mainfreight references/house bill fields.
Specific Field Rules[Technical validation required]No carrier-specific reference rules confirmed yet for Mainfreight LTL V2.

   

   
   

  

For a comprehensive guide on how to use label references , see: Using order References in your labels [Step-by-Step guide].

   

   

   

Operational Constraints


This section details specific operational rules and limitations imposed by Mainfreight LTL V2. These constraints are enforced by the carrier and must be considered when planning your shipping workflow:

  • LTL only: This integration supports LTL workflows only.
  • International scope: Supported for US → Canada lanes.
  • Rating requires Delivery Date: A Delivery Date is mandatory for rate shopping/rating requests (default if missing).
  • Whole-number weights only: Decimal weights are not supported by the carrier API.
  • Freight lines: If two pieces are identical, two separate freight line entries are still required.
  • Document output: PDF only.
  • Document selection: Supported label types are US Label and US BOL, but the carrier API cannot return both document types together.


Mainfreight LTL V2 cannot return US Label and US BOL together. Select the document type required for your operation (US Label or US BOL) in the Baseline Account.

 
   

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article