This article serves as the central hub for integrating RocketShipV2 Cirro 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 split.

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 RocketShipV2 Cirro 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:

RocketShip V2 Cirro does not replace any previous integration. There is Rocketship and Rocketship (v2). This carrier is part of Rocketship (v2).

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.
4	Order Settings		Transaction	Defines advanced service options.

Carrier Specifications and Constraints

This section outlines specific operational behaviors and data limitations inherent to the RocketShipV2 Cirro integration. 

Label References

RocketShipV2 Cirro supports mapping label references using Reference 1 through Reference 4. Select the required mapping based on your operational needs.

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 RocketShipV2 Cirro. These constraints are enforced by the provider and must be considered when planning your shipping workflow:

• Shipment type: Small Parcel (SP).
• International shipping: Not supported for Cirro in Rocketship (v2).
• Rate Shopping: Supported (requires correct Rates & Markups configuration).
• Void: uses the Primary Tracking Number. Multi-package shipments (when used) share a single primary tracking number for void operations.

The label endpoint enforces stricter address validation than the shipment endpoint. Missing/invalid address elements may allow shipment creation but can block label generation.

Proceed to Phase 2: Setting up the Baseline Carrier Connection.