---
title: "Data import: importing container data"
description: "A comprehensive guide to importing container data. This process supports the bulk creation of containers that belong to the organization and its contract carriers. It provides a ready-to-use catalog for order creation."
url: https://help.qargo.com/us/articles/410131-data-import-importing-container-data
locale: us
updated: 2026-08-07
---

# Data import: importing container data

Importing container data allows for the bulk creation of containers, which can belong to either the user's own company or a contract carrier. This is a critical step for organizations that manage their own container fleets, as it provides a readily available database for use in order creation. This article outlines the specific requirements, best practices and common issues related to importing container data.

* * *

## 📖 Key terminology {#h_bb93f4d3d4}

For clarity throughout this guide, the following terms are defined.

-   **Container:** A reusable transport and storage unit.
-   **Container no.:** The unique identifier for a container.
-   **Contract carrier:** A company that owns or operates a container.
-   **Code:** A unique identifier for a container from an external system, which can be used to ensure accurate data updates.


* * *

## ✅ Critical import requirements for containers {#h_a8dc0ba2c5}

Before importing container data, consider the following requirements and warnings to ensure data integrity.

-   **Contract carrier prerequisite:** Before a container belonging to a contract carrier can be imported, the contract carrier's company record **must** already exist in the Qargo system. The import will fail if the specified contract carrier cannot be found.
-   **Unique identification:** Qargo identifies existing containers by their unique **container no.**
-   **Mandatory field:** The container **name** is a mandatory field. An import will fail if this is left blank.


* * *

## 🛠️ Step-by-step data import process {#h_0320dd7921}

## Step 1: Download the template {#h_256dbde572}

A specific spreadsheet template is available to upload container data. **To make sure the data can be edited and uploaded, download a copy of the template:**

1.  Click the link: [Container data import template](https://docs.google.com/spreadsheets/d/18iCOvgK_GFgtOPK6h02Vb1Dq7hKqKnwretYO5j4nrC0/edit?usp=sharing)
2.  Once the template opens, go to **File** and select **Download**
3.  Save the template **(in .xlsx or .csv format)** to a computer and begin entering the company data.

![](https://help.qargo.com/media/035e09bc7dbc-image.png)

:::callout{tone="info"}
📚 Always use a blank template downloaded directly from here or provided by the Qargo team. Reusing an old template may lead to import errors.
:::

## Step 2: Fill in the Excel template {#h_2cf9e27d5d}

Open the template and populate it with the required data. The template contains column headers that correspond to the fields in Qargo.

-   **Required fields:** Make sure to fill out all the required fields (a comprehensive list of required fields can be found in the next section of this article). An import will fail if these fields are left blank.
-   **Formatting:** Pay close attention to the specified data format (e.g., dates, numbers, text).


## Step 3: Submit for upload {#h_33834aab0f}

1.  **During onboarding:** Work directly with the **onboarding manager** to upload the initial business data. The onboarding manager will guide the process and ensure a successful import.
2.  **After onboarding:** For all future data updates and imports, contact the **account manager**. The account manager will assist with the upload process and provide ongoing support.


* * *

## 📝 Details of the container import template {#h_723b086936}

The following table provides a detailed, field-by-field explanation of the Excel template for container import, including data formats, required fields and best practices for populating each column.

| **Column name** | **Required/optional** | **Remarks** | **Example** |
| --- | --- | --- | --- |
| name | Required | Container name displayed in Qargo |  |
| code | Optional |  |  |
| manufacturer | Optional |  | Exagon |
| container\_number | Optional |  | 1212 |
| standard\_size | Optional |  | Feet\_25 |
| note | Optional |  |  |
| subcontractor\_company | Optional |  |  |
| gross\_weight | Optional | Metric tons | 1 |
| tare\_weight | Optional | Kilograms | 1.0 |
| capacity\_volume | Optional | CBM | 1.000 |
| capacity\_weight | Optional |  | 1 |
| exterior\_length | Optional | Meters | 1.000 |
| exterior\_width | Optional | Meters | 1.000 |
| exterior\_height | Optional | Meters | 1.000 |
| custom\_fields\_\_example | Optional | To import custom field values. Note: the format uses a double underscore (`__`) to connect the prefix **custom\_fields** to the unique field ID |  |

### Standard size: accepted values {#h_b0b8beeb1c}

The `standard_size` column accepts the following values. The format must match exactly (the field is not case-sensitive, but the underscore and capitalization pattern below is recommended):

| **Value** | **Size** |
| --- | --- |
| `Feet_20` | 20 ft |
| `Feet_23` | 23 ft |
| `Feet_24` | 24 ft |
| `Feet_25` | 25 ft |
| `Feet_26` | 26 ft |
| `Feet_30` | 30 ft |
| `Feet_35` | 35 ft |
| `Feet_40` | 40 ft |

* * *

## 🔎 Troubleshooting common container import errors {#h_7279833172}

This section addresses specific errors that may arise during the import of container data.

-   **Contract carrier record not found:** This is the most common error for containers owned by contract carriers. It occurs when the name of the **contract carrier company** in the template does not exactly match an existing company in Qargo. The contract carrier must exist in the system before its containers can be imported.
-   **Sheet name:** The sheet in the Excel template file must be named exactly **'Import'**. Any other name will cause an error when uploading the file.
-   **Missing mandatory field:** The import will fail for any row where the **container** name is left blank.
-   **Case-sensitive column headers:** Column headers must be entered with the correct casing (e.g., `vat_number`, not `VAT_number`). Incorrect casing will cause the data in that column to be silently ignored and not imported, as the system will not recognize the header.
-   **Leading apostrophe errors:** Data in a cell cannot begin with an apostrophe ('). If an apostrophe is used, the system will not recognize the value, and an error may occur. **This rule is waived only if the article explicitly instructs that an apostrophe should be used for a specific field.**
-   **Custom fields:** The column name must follow the convention **custom\_field\_\_\[ID\]** (keep the double underscore to connect the prefix **custom\_field** to the unique field ID), with the specific ID retrieved from the Qargo organization settings. Click the copy button next to the custom field to copy its ID:

    ![](https://help.qargo.com/media/a6013003827e-796a5c17-3b5e-4a0d-9642-08cfd8176cd4.png)


* * *

## ✨ Best practices for importing containers {#h_90ca1ae879}

To ensure a smooth and accurate import, consider the following best practices.

-   **Make sure contract carrier data is complete:** Before importing contract carrier containers, verify that all associated contract carriers have already been successfully imported into the system as companies.
-   **Maintain data consistency:** Pay close attention to the spelling and capitalization of **contract carrier names** and **container nos.** Any inconsistencies will cause the link to fail.
-   **Use the container's code:** Although optional, using the container **code** field is highly recommended. It provides a reliable way to update container records and prevents conflicts that can arise from duplicate numbers.

* * *

## ➡️ What to do next {#h_122fb131d9}

Once containers have been successfully imported, they can be used in order creation. The next logical steps include:

-   **Importing products:** If required, products used in order creation can be imported in bulk.
-   **Importing orders:** A sample set of test orders can be imported to populate a sandbox environment.


* * *

## 📈 Use cases for container import {#h_0d31aa2d5e}

Importing container data is an invaluable tool for several key business processes.

-   **Initial fleet setup:** The primary use case is to populate a Qargo tenant with an entire fleet of containers, including both owned containers and those from regular contract carriers.
-   **Onboarding a new fleet:** When a new business unit or fleet of containers is acquired, its details can be added in bulk to the Qargo system.


## Related articles

- [Data import: importing vehicle data](https://help.qargo.com/us/articles/410124-data-import-importing-vehicle-data.md)
- [Data import: Importing driver data](https://help.qargo.com/us/articles/410123-data-import-importing-driver-data.md)
- [Data import: Importing contact data](https://help.qargo.com/us/articles/410121-data-import-importing-contact-data.md)
- [Data import – importing contact location data](https://help.qargo.com/us/articles/494334-data-import-importing-contact-location-data.md)
- [Data import - Importing product data](https://help.qargo.com/us/articles/410133-data-import-importing-product-data.md)
