> For the complete documentation index, see [llms.txt](https://claimlane-docs.gitbook.io/claimlane-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://claimlane-docs.gitbook.io/claimlane-docs/troubleshooting-and-faqs/shipping-error-422-missing-customs-data.md).

# Shipping Error 422 – Missing Customs Data

### Error Summary

**Error Code:** 422\
**System:** Webshipper/Other Carriers\
**Stage:** Shipment Booking\
**Typical Message:**

Goods Contents - Line Contents is mandatory for international shipments

This error occurs when attempting to generate a **shipping label for an international shipment** where **required customs information is missing**.

### Example Error

You may see an error similar to the following in the logs:

```
Errors

Step: webshipper-book-shipment (Error)

{
 "name": "Error",
 "message": "Request failed with status code 422",
 "status": 422,
 "statusText": "Unprocessable Entity",
 "url": "https://liewood.api.webshipper.io/v2/shipments?include=labels",
 "method": "post",
 "data": {
   "errors": [
     {
       "title": "Goods Contents - Line Contents is mandatory for international shipments",
       "detail": "carrier - Goods Contents - Line Contents is mandatory for international shipments",
       "code": "100",
       "status": "422"
     }
   ]
 }
}
```

#### Root Cause

One or more products in the order **do not have required customs data configured in Claimlane**.

For international shipments, carriers require customs information such as:

* Product description
* HS code
* Country of origin
* Item value
* Line contents

If any of these fields are missing, **Webshipper/Carrier rejects the shipment creation request with a 422 error**.

## How to Identify the Issue

1. Open the **ticket in Claimlane**.
2. Click the **information button** on the ticket.

<figure><img src="/files/Ur3NyPRP5x1SYgFQASSX" alt=""><figcaption></figcaption></figure>

3. Check the **product customs fields**.

If customs information is missing, the fields will appear as **invalid or missing**.

<figure><img src="/files/JM972xLNCOjTml2bM6zp" alt=""><figcaption></figcaption></figure>

## How to Fix the Issue

1. Open the **ticket in Claimlane**.
2. Locate the **product with missing customs data**.
3. Click on the **missing fields**.
4. Enter the required information.
5. Save the changes.

After entering the required data:

* Fields previously marked with a **red X** should become **valid**.
* The shipment label can now be generated successfully.

## Keywords (for Fin AI recognition)

Shipping error 422\
Webshipper error 422\
Missing customs data\
Goods contents line contents mandatory\
International shipment customs error\
Webshipper shipment creation failed\
Claimlane customs fields missing\
Cannot create a label


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://claimlane-docs.gitbook.io/claimlane-docs/troubleshooting-and-faqs/shipping-error-422-missing-customs-data.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
