This article serves as the central hub for integrating Metropolitan Warehouse & Delivery 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
  • Information to be Provided
  • Settings to be Verified
• Configuration Hierarchy and Guides
• Carrier Specifications and Constraints
  • Label References
  • Operational Constraints

Onboarding Requirements

Before configuring Metropolitan Warehouse & Delivery in techSHIP, you must gather specific credentials and verify account settings. 

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:

Settings to be Verified

The following account configurations must be validated to prevent errors during the connection setup or the shipping process:

If your workflow requires rate shopping, the Setup Rate API fields must be completed. If not using rate shopping, these fields may remain empty.

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:

LEVEL	COMPONENT	MANDATORY	SCOPE	DESCRIPTION	CONFIGURATION GUIDE
1	Onboarding Requirements		Requirements	You are here.
2	Baseline Account		Carrier	Establishes the core technical connection. Must be created first.
3	(Billing) Account		Client	Connects a specific client to the Baseline. At least one is required to ship.

Carrier Specifications and Constraints

This section outlines specific operational behaviors and data limitations inherent to the Metropolitan Warehouse & Delivery integration. 

Labels

The following table summarizes BOL and label support specific to this carrier:

ITEM	SUPPORTED
Label
References
BOL

The table below specifies the hard limits for Label References enforced by Metropolitan Warehouse & Delivery. Data exceeding these limits may be truncated on the physical label or cause manifest errors:

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 Metropolitan Warehouse & Delivery. These constraints are enforced by the carrier and must be considered when planning your shipping workflow:

• Metropolitan is LTL and supports domestic shipping only.
• If a phone number starts with digit "1", the carrier may remove it because it is interpreted as a country code.
• If techTrack is enabled for this carrier, Tracking Api Key must be configured to enable tracking updates.